Unspecified File Encodings in 3.0
Unspecified File Encodings in 3.0
- Subject: Unspecified File Encodings in 3.0
- From: Nick Nallick <email@hidden>
- Date: Mon, 19 Nov 2007 11:40:16 -0700
I've recently encountered an odd change in Xcode 3.0 that took me a
while to track down so I thought I'd share it.
I have a set of localized files which I created from the original
English versions. For some reason the original English file was
marked in Xcode as using MacRoman encoding but the other files in the
same set didn't have a specific encoding (they reported "no explicit
file encoding" when I checked). Under Xcode 2.4 all these files
continued to be built using MacRoman (so I never noticed the problem)
but for some reason Xcode 3.0 decided to build one German file
differently. Most unmarked files continued to be MacRoman but this
particular file seemed to be built as UTF-8 (e.g., umlauts became two
byte characters).
I have no idea why the default behavior for this one file changed (it
seemed to be fine for other German files in the project) but setting a
specific file encoding the file's general info seemed to cure the
problem.
Nick
_______________________________________________
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