Re: endian problems with UTF16 on Intel Macs
Re: endian problems with UTF16 on Intel Macs
- Subject: Re: endian problems with UTF16 on Intel Macs
- From: Ricky Sharp <email@hidden>
- Date: Tue, 29 Aug 2006 06:42:53 -0500
On Tuesday, August 29, 2006, at 00:59AM, Chris Suter <email@hidden> wrote:
>
>On 29/08/2006, at 3:47 PM, Donald Hall wrote:
>
>> Furthermore, I understood that "external representation" was always
>> big endian.
>
>No. The representation is as dictated by the encoding. Some encodings
>don't have an endian aspect to them (UTF-8 for example). I'm guessing
>if you pick kCFStringEncodingUTF16, OS X is free to choose big-endian
>or little-endian.
Not quite. According to <http://www.unicode.org/faq/utf_bom.html#36>, unmarked UTF-16 and UTF-32 uses big-endian by default. I would expect the Cocoa frameworks to honor that default.
--
Rick Sharp
Instant Interactive(tm)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden