> On Mar 12, 2015, at 5:51 PM, Charles Srstka <cocoa...@charlessoft.com> wrote:
> 
> Here’s what I’ve found, in my anecdotal experience:
> 
> 1. XIB files in Base.lproj will load all their English strings when the app 
> is run in English, even if there is no corresponding strings file in 
> en.lproj. This makes sense, because the XIB file is being used as a starting 
> point, and if there’s no custom localization, might as well just stick with 
> what’s in the XIB that you already loaded.
> 
> 2. Strings files in Base.lproj will load when run in English if there’s 
> nothing in en.lproj… but only on Mavericks and higher. If you are targeting 
> Mountain Lion, be warned that if there is no Localizable.strings file in 
> en.lproj, the app will randomly pick one from one of the other lprojs. There 
> doesn’t seem to be any rhyme or reason to what language it picked, although 
> in my testing it seems to like Simplified Chinese a lot. Having part of the 
> interface randomly show up in another language can have pretty hilarious 
> results for your end users; I got some pretty amusing reports from my beta 
> testers about this issue. Thank God that got caught before it went to release.
> 
> Anyway, long story short, I don’t recommend putting strings files in 
> Base.lproj. Even the 10.9+ behavior I couldn’t find any promise of anywhere 
> in the documentation, so who knows if even that might regress in 10.11 or 
> something.
> 
> Charles

Thanks, Charles.

We’re targeting OS X 10.9+ and iOS 8.0+ in our apps. Barring any strong 
cautions against, we may delete en.lproj and see how it goes.

----
Karl Moskowski <kmoskow...@me.com>
<http://about.me/kolpanic>


_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to