Re: Question on STRINGS_FILE_OUTPUT_ENCODING
Re: Question on STRINGS_FILE_OUTPUT_ENCODING
- Subject: Re: Question on STRINGS_FILE_OUTPUT_ENCODING
- From: Joar Wingfors <email@hidden>
- Date: Tue, 9 Nov 2010 07:13:58 -0800
On 8 nov 2010, at 23.35, Ulf Dunkel wrote:
> Why is the STRINGS_FILE_OUTPUT_ENCODING set to UTF-16 by default?
Because Mac OS X expects for strings files found in frameworks and app bundles to be encoded in UTF-16.
This feature of Xcode 3.1 allows the developer to keep the "source copy" of the strings file in any encoding that they want, typically UTF-8 - which is friendlier to SCM (diffing) and other tools - and only convert it to the expected UTF-16 as the file is copied over to the final build product.
j o a r
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden