views:

240

answers:

1

Hey guys,

I'm working on an existing Xcode 3.2.2 Universal iPhone OS project which is already localized for 4 languages (EN, IT, DE and FR). We are now adding a new language (JA) into this project.

Each existing .lproj folder (en.lproj, it.lproj, de.lproj and fr.lproj) has almost 60 files - including PNGs, HTMLs and the Localizable.strings file. Each one of those files appear as localized groups inside Groups & Files in Xcode. They're spread all over the tree.

If I right-click one of those groups (say, Localizable.strings) inside Xcode, Get Info, click on "Add Localization" and type "ja" - as the Xcode docs suggest, nothing happens. From what I read in this newgroup, it's possibly because of the way those folders are named. If they were named like English.lproj and Italian.lproj, this was supposed to work.

So, for me to actually import a new language localized file into the existing group, I have to:

  1. Right-click the localized group file.
  2. Choose "Add Existing File".
  3. Select the corresponding file inside the ja.lproj folder.

I'm about to get a new ja.lproj folder with those 60 localized files and would love to import them in the project in a way that doesn't involve searching for every single file in Groups & Trees and performing those steps... for every one of those 60 files.

Is that possible? Is there a right (or better) way to import a new language into this Xcode project?

A: 

The mailing list post basically sums up the issue: Xcode expects to find language bundles with names like "English.lproj", "Italian.lproj", etc. If you change those names, Xcode looses the ability to treat them as language bundles, and then you have to add files using the method you described. There's nothing wrong with how you're adding them to the project, that's just how Xcode works.

mipadi
Do you know then why all the sample code use "en.lproj"? I mass added a bunch of files just by dragging all of them at once into xcode, and it put each one in the correct place, but they were all in the resources folder, and maybe I misunderstood the question...
James
No idea; `en.lproj` isn't necessarily incorrect, but Apple has generally encouraged using `English.lproj`, etc.
mipadi
From what I understood, it's the other way around. `English.lproj` is legacy code which hasn't been fixed in Xcode yet. Apple now recommends `en.lproj`: http://useyourloaf.com/blog/2010/4/10/xcode-localization-frustrations.html
leolobato
I'm accepting your answer anyways as it looks like there is not other way to import those files - even if I was using the legacy `lproj` format.
leolobato