On 15 dec 2009, at 07.47, Torsten Curdt wrote:
> Anyone know of any reasonable explanation why for Cocoa localization
> files need to be in UTF16?
Hello Torsten,
I think that this is simply a documentation bug. Cocoa expects, or at least
expected, strings files in the product to be UTF16. For that reason, the
recommendation was for you to maintain your strings files as UTF16. Recent
versions of Xcode (both 3.1.x and 3.2.x) will convert your strings files to
UTF16 automatically as they are copied over to the build product, allowing you
to maintain the "source" version of the strings file in the more manageable
UTF8.
It's easy to change the encoding of your strings files by using the file
inspector in Xcode. You'll also find that when you create new projects / files
in Xcode, strings files are provided as UTF8 out of the box.
You can find snippets of information about this in the Xcode release notes:
<http://developer.apple.com/mac/library/releasenotes/DeveloperTools/RN-Xcode/index.html>
Please file a bug report on any documentation that you find that isn't updated:
<http://developer.apple.com/bugreporter/>
Thanks,
j o a r
_______________________________________________
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
