On Dec 10, 2009, at 8:42 AM, Manfred Schwind wrote:
Be careful, though: Some MacOS versions have a bug where .strings
files had to be UTF16 to actually work. I don't think Apple has
fixed that yet.
Do you have more specific information about that?
I consequently always used UTF-8 for all my .strings files in every
project I ever worked on (for many years; I think I started with
10.1 or so) and never had a single problem with that.
What exactly does not work when not using UTF-16?
Maybe UTF-16 and UTF-8 both work, but - of course - no other
encoding like ISO Latin or Mac Roman etc.?
The .strings files are actually a special case of plist files. There
are three supported formats: first, the special .strings file format,
which is UTF-16 plain text consisting of lines of
"key" = "value";
pairs with optional comments; second, the XML plist format; third, the
binary plist format. The .strings file format is the recommended
format for .strings files. If you use this format, you should use
UTF-16 with a BOM. If you use the XML plist format, the encoding
specification is as per XML, but almost always one would use UTF-8.
If you use the XML or binary plist format, the contents must be a
dictionary of strings.
Douglas Davidson
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
