Re: Question on STRINGS_FILE_OUTPUT_ENCODING
Re: Question on STRINGS_FILE_OUTPUT_ENCODING
- Subject: Re: Question on STRINGS_FILE_OUTPUT_ENCODING
- From: Ulf Dunkel <email@hidden>
- Date: Wed, 10 Nov 2010 14:49:22 +0100
- Organization: invers Software
Hi Joar.
Because Mac OS X expects for strings files found in frameworks and app bundles to be encoded in UTF-16.
Is there any Apple statement on this? I wonder why our apps work fine
with UTF-8 built .strings files? ;-)
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.
But building with a different encoding from what you use in the source
would cause more problems when external localizers have to handle the files.
I really cannot believe that UTF-16 should be a MUST for built apps.
Please explain to me where Apple states and requires this.
Thank you,
---Ulf Dunkel
_______________________________________________
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