Re: NSString really Unicode?
Re: NSString really Unicode?
- Subject: Re: NSString really Unicode?
- From: Dustin Voss <email@hidden>
- Date: Fri, 12 Mar 2004 09:59:32 -0800
On 12 Mar, 2004, at 8:47 AM, James J. Merkel wrote:
This brings up another question -- what I'm really looking at are
key-value pairs in the file. What I would like to to is use the key to
look up a string in a Localizable.strings file. However, I notice that
if I use UTF-16 encoding for the Localizable.strings file, the strings
are big endian format. Is there a way of making this file little
endian format?
It wouldn't do any good. You don't look up keys in the
Localizable.strings file directly; you look up keys in a data structure
that is created from the file. They are already in NSString's internal
format when you try to look them up.
However, you may be able to make a lookup table of your own by turning
an NSDictionary into a plist file, where the dictionary values are the
strings you want, and the dictionary keys are the raw NSData forms of
the camera file's keys.
If it is any consolation, I logged an enhancement request (#3364697) a
long time ago for Apple to add some endian-aware encodings:
NSUnicodeLEStringEncoding, NSUnicodeBEStringEncoding,
kCFStringEncodingUnicodeLE, and kCFStringEncodingUnicodeBE. These would
not use a BOM when converting data-to-string, and would not create a
BOM when converting string-to-data. It was marked as a duplicate and
closed, so maybe they will actually implement it someday. Feel free to
log the same bug to speed up the schedule. :)
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.