Localization: which files go where?

[bonehead]

Apologies if this is one of those things that's obvious to Cocoa programmers, but exactly where do the localization strings files go in your xcode project to build properly? Right now I have a single folder inside my main application project folder called "languages": the layout of it is something like this:

- languages
-- de.lproj
--- Localizable.strings
-- en.lproj
--- Localizable.strings
-- es.lproj
--- Localizable.strings
-- fr.lproj
--- Localizable.strings

I added the top-level "languages" folder to my Resources folder using "Add->Existing files..." , unchecked "Copy items into destination group's folder", selected Text Encoding: Unicode (UTF-16) and clicked Add.

I find that when I switch the simulator or device language, I get somewhat random results. Some strings show up in the language I expect; often, however, they show up in French regardless of the locale settings. I've also found the behavior is pretty inconsistent between the device and the simulator.

BTW I'm consistently using NSLocalizedStringWithDefaultValue throughout my code-- the default values are in English.

Anyone else having luck with localization?

[bonehead]

-Ping-

Right now my assumption is that the strange behavior I'm seeing is a bug in the iPhone-- it may simply be loading the last (alphabetically) language strings file and using that.

I'd be curious to hear if anyone else has been able to get localization to behave properly with multiple languages.

[scottiphone]

I fiddled around with this awhile ago but put it on the back burner.

Under localization section of the guide they recommend a different setup than you have.
Settings.bundle/
Root.plist
Root.strings
en.lproj/
Root.strings
de.lproj/
Root.strings

[bonehead]

Originally Posted by scottiphone

Under localization section of the guide they recommend a different setup than you have.
Settings.bundle/
Root.plist
Root.strings
en.lproj/
Root.strings
de.lproj/
Root.strings

I think that's for the Settings bundle...I was following the example under the "Internationalizing Applications" section.

Anyway, I'll fiddle with this further and try to narrow down the bugs.