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 18:38:31 +0100
- Organization: invers Software
Perhaps Mac OS X tries UTF-8 as a fallback?
I hope so. ;-)
Sure, UTF-8 is also a
perfectly reasonable encoding for strings files, but if a specific
encoding is not declared to be the correct encoding to use for
strings files, what's to stop someone from deciding that they'd
rather use Mac Roman, Latin-1 or any other commonly used encoding?
I'd surely have voted for UTF-8 as default, just because it will be much
shorter than UTF-16 in most cases (maybe except for Chinese).
If Apple worries about the detection of UTF-8, they could have used
UTF-8 with BOM, but Xcode writes UTF-8 without BOM when you choose the
relevant STRINGS_FILE_OUTPUT_ENCODING option.
It
is not reasonable to have a scenario when Mac OS X is expected to
guess / sniff / detect the used encoding.
This is not the case, as the .strings files are always either written in
UTF-8, UTF-16 or binary format (whatever this means in this topic).
> UTF-8 is a fine choice, but so is UTF-16.
Not in terms of saving "weight" of an app.
Had the decision been made today I would think that the
choice would have been UTF-8 simply because it's so common. Back when
this decision was made, probably long before the introduction of Mac
OS X, there might have been other considerations that factored into
the choice of encoding.
Things can change. ;-)
That's about as far as I would want to get into guessing on this
topic... ;-) If you'd like to see something change wrt. this, I'd
suggest you file a bug report / feature request with the Apple Bug
Reporter.
Oh, I did already when Xcode 3.1 came out. No reply at all.
Thanks for your time and comments.
---UlfDunkel
_______________________________________________
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