• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Localization
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Localization


  • Subject: Re: Localization
  • From: Douglas Davidson <email@hidden>
  • Date: Wed, 19 Apr 2006 09:25:24 -0700


On Apr 19, 2006, at 8:38 AM, Paolo Bertani wrote:

What you say is right and I'll probably do what you (and Ondra Cada) suggest.

But let's suppose (for future projects) I'd like to start with the Italian localization and then later, maybe, add other languages.


CFBundle/NSBundle do not give any special place to English, except that it is used as a final resort when all other indications of language preference have failed. If you set your CFBundleDevelopmentRegion to Italian, then Italian will be the default localization for your application. You can add an Italian localization for all localizable resources in Xcode. Offhand it looks like Xcode doesn't have a convenient way of removing the English localization that it creates by default, but you can always remove it from your built application later on. (Actually, I would recommend using the language code "it" rather than the language name "Italian" as the localization name, but CFBundle/NSBundle will accept either.)


There is a sequence of fallbacks that CFBundle/NSBundle use to select the localization used when an application is launched. If one of the user's preferences matches one of the application's localizations, then the most-preferred localization will be used; if not, then the development localization will be used; if that is not present, then English will be used; if that is not present, then one of the application's localizations will be used; or if the application has no localizations, then only non-localized resources will be used.

I do not recommend going without localized resources, however, because even if your application will only ever be available in one localization, it is likely to use localized resources from the various frameworks installed on your system, and CFBundle/NSBundle need to be able to determine what localization your application is running in so as to be able to select those.

In bocca al lupo,

Douglas Davidson

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Localization
      • From: Horst Hoesel <email@hidden>
References: 
 >Localization (From: Paolo Bertani <email@hidden>)
 >Re: Localization (From: Horst Hoesel <email@hidden>)
 >Re: Localization (From: Paolo Bertani <email@hidden>)

  • Prev by Date: Generating a "left-arrow key" event
  • Next by Date: Re: Localization
  • Previous by thread: Re: Localization
  • Next by thread: Re: Localization
  • Index(es):
    • Date
    • Thread