StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POAdd new language to existing Xcode project localization
text
Body
copied!<p>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.</p> <p>Each existing <code>.lproj</code> folder (<code>en.lproj</code>, <code>it.lproj</code>, <code>de.lproj</code> and <code>fr.lproj</code>) 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.</p> <p>If I right-click one of those groups (say, <code>Localizable.strings</code>) inside Xcode, Get Info, click on "Add Localization" and type "<code>ja</code>" - as the Xcode docs suggest, nothing happens. From what I read in <a href="http://www.mailinglistarchive.com/xcode-users@lists.apple.com/msg10221.html" rel="nofollow noreferrer">this newgroup</a>, it's possibly because of the way those folders are named. If they were named like <code>English.lproj</code> and <code>Italian.lproj</code>, this was supposed to work.</p> <p>So, for me to actually import a new language localized file into the existing group, I have to:</p> <ol> <li>Right-click the localized group file.</li> <li>Choose "Add Existing File".</li> <li>Select the corresponding file inside the <code>ja.lproj</code> folder.</li> </ol> <p>I'm about to get a new <code>ja.lproj</code> 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.</p> <p>Is that possible? Is there a right (or better) way to import a new language into this Xcode project?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload