On Sep 27, 2010, at 15:13, Kin Mak wrote: Christiaan,
Thanks for your clarification. I think I will stick to the two-character code convention, which means I need to manually create the "xx.lproj" directories.
By the way, I find another bug in XCode: After the English.lproj folder is deleted in XCode, it will fail to add more localization.
Thanks again, Kin C. Mak
I don't think that's strictly speaking a bug. I think it will base new localizations on the development language of the project. And as I noted, it's not at all obvious how to change that as well.
Christiaan On Sep 26, 2010, at 4:59 PM, Christiaan Hofman wrote: On Sep 26, 2010, at 10:17, Kin Mak wrote:
I tried to make a Xib file localizable in XCode 3.2.3 by the following workflow:
Select the xib file
Info > Make File Localizable
After that, XCode automatically created a "English.lproj" directory for the xib file.
If I recall correctly from the online documentation, the correct prefix should be a two character language code. In this case, I thought it is supposed to be "en.lproj".
Is it a bug in XCode or am I missing something here?
Am I supposed to use the two-character language code prefix for the lproj directories on IPhone development?
Is it safe to use the English.lproj actually?
Any advice would be highly appreciated.
Thanks
Kin C. Mak
Xcode still uses English for the default development language. And there is still no UI to change the development language of a project. There was a recent thread on how to change the default development language, which requires you to edit the project file itself (this part has become slightly easier with Xcode 3.2.4). You can always change the individual languages by simply editing the folder names on your file system, or by adding an "en" localization and removing the "English" one. The long names are still supported, so it is (and will be) safe to use them, how could they not support it if they threat is as the default? The docs say that the short names are preferred, but Apple often doesn't follow its own recommendations (it also recommends using AppleGlot for localization, which still is broken on 10.6), so just ignore what they say, and do as they do.
Christiaan
|