>>> 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.? > > There is a very much in passing comment in 'Internationalising Programming > Topics' guide for Cocoa. > > Note: It is recommended that you save strings files using the UTF-16 > encoding, > which is the default encoding for standard strings files. It is > possible to create strings > files using other property-list formats, including binary > property-list formats and XML > formats that use the UTF-8 encoding, but doing so is not recommended > . . .
Ah - wait! I am using UTF-8 for the files in the Xcode Project. This makes it much easier to handle them in SCM systems etc. But Xcode automatically converts the strings files into UTF-16 when copying them into the final App bundle. I'm not sure this was always the case, though. Regards, Mani -- http://mani.de - friendly software _______________________________________________ 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
