Re: Question on STRINGS_FILE_OUTPUT_ENCODING
Re: Question on STRINGS_FILE_OUTPUT_ENCODING
- Subject: Re: Question on STRINGS_FILE_OUTPUT_ENCODING
- From: Ricky Sharp <email@hidden>
- Date: Tue, 09 Nov 2010 06:04:03 -0600
Speed. Memory based internals of NSString are UTF-16 (not sure offhand if that is BE or LE)
And if such data is normalized on both disk and memory, you could do stuff like memory-mapping the file.
UTF-8 is the best transport encoding but it incurs an encode/decode speed penalty. Also, depending upon the language, UTF-8 encoded data may be larger than UTF-16.
Sent from my iPhone
On Nov 9, 2010, at 1:35 AM, Ulf Dunkel <email@hidden> wrote:
> Introduced in Xcode 3.1, we now have the new Strings files output encoding option, which can be set to either "UTF-8", "UTF-16" (default), or "binary".
>
> I appreciate that Apple wants to make apps smaller (which might have been one reason why they also introduced the Interface Builder NIB Postprocessor option "Strip NIB Files" and other stuff).
>
> Why is the STRINGS_FILE_OUTPUT_ENCODING set to UTF-16 by default?
>
> I cannot find any useful reason for artificially blowing up all .strings files. You can code every Unicode character in UTF-8, by the way.
>
> ---Ulf Dunkel
> ---invers Software
> _______________________________________________
> 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
_______________________________________________
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