Re: Displaying Unicode
Re: Displaying Unicode
- Subject: Re: Displaying Unicode
- From: Bill Bumgarner <email@hidden>
- Date: Thu, 29 Nov 2001 13:16:51 -0500
*Gack*
That would imply a potential bug in iTunes' tag editor. I will confirm
against a third party source for externalized unicode strings and, if it
is the case, report a bug against iTunes.
Thank you.
b.bum
On Thursday, November 29, 2001, at 01:11 PM, Ali Ozer wrote:
Well, the stream you have looks like plain old UCS-2, that is,
NSUnicodeStringEncoding. One thing that looks wrong is that the byte
order mark (BOM) seems reversed --- That is, it implies the characters
are stored big endian, but they really are little endian. BOM is supposed
to be 0xFEFF, which implies the chars are 0xB930, 0xC830, etc, which seem
fishy (they are all over the map). If you instead reverse them, you get
the much more reasonable 0x30B9, 0x30C8, etc. Doing this, and loading the
resulting byte stream into TextEdit, I get a reasonable looking Japanese
string (I have no idea what it says though). In addition, [NSString
initWithContentsOfFile:] should just read this fine. No need to use TEC..
.
Ali