• 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: US/non-US localization problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: US/non-US localization problem


  • Subject: RE: US/non-US localization problem
  • From: "David Hazel" <email@hidden>
  • Date: Tue, 15 May 2007 20:15:55 +0100
  • Importance: Normal

Thanks, that works.

But I'm still confused. Is there a difference between locale and
localization? I have always understood "locale" to be where the system
thinks it is (including language, units, formatting rules and so on), and
"localization" to be what has to be done to make an application obey the
locale rules. If the system thinks my locale is en_US, why isn't it
attempting to use the corresponding language file, if it exists? If I have
"English" as my language and "United States" as my format, my "current
locale" comes back as "en_US". If, on the other hand, I set my language to
"English" and my format to "United Kingdom", my locale comes back as
"en_GB". However, both locales, for some reason, attempt to use the generic
"en" language rather than any locale-specific variant that exists.

Is "U.S. English" the default setting for a system running in the United
States? Because if not, I will need to do more to ensure that US-based users
see the correct support information. If a US-based user selects the generic
"English" language, rather than "U.S. English" (which it seems to me they
might well do), and sets their format to be "United States", I would want
them to see the correct support information for the US. At the moment, they
would see information that would be correct for UK-based users. Is there any
way I can ensure this using the localization rules? Could I, for instance,
have a "en - en_US" localization? If so, how do I name the corresponding
localization in XCode? If I were to use this localization instead of just
"en_US", would it work in both cases (i.e. "U.S. English" language OR
"English" language + "United States" format)?


David Hazel

  -----Original Message-----
  From: Douglas Davidson [mailto:email@hidden]
  Sent: 15 May 2007 19:07
  To: David Hazel
  Cc: Apple CocoaDev list (E-mail)
  Subject: Re: US/non-US localization problem




  On May 15, 2007, at 9:25 AM, David Hazel wrote:


    I have an application which has been localized for English (non-US) and
7

    other languages. I am trying to add US English to it, mainly to provide
some

    different support details to be displayed on some of the screens.
However,

    even when my system locale is set to en_US (i.e. English language and
United

    States format), the software continues to display the generic "en"
English

    text instead of the locale-specific "en_US" text.



  Locale has nothing to do with it.  This is a matter of localization, not
locale.  To select US English localization, go to the "Language" tab of the
International preference pane, hit "Edit List..." and turn on the "U.S.
English" item about 2/3 of the way down, then click OK and make sure that
"U.S. English" is at the top of your list of languages.


  Douglas Davidson



_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

  • Follow-Ups:
    • Re: US/non-US localization problem
      • From: Thomas Engelmeier <email@hidden>
    • Re: US/non-US localization problem
      • From: Douglas Davidson <email@hidden>
    • Re: US/non-US localization problem
      • From: mmalc crawford <email@hidden>
References: 
 >Re: US/non-US localization problem (From: Douglas Davidson <email@hidden>)

  • Prev by Date: Re: [ANN] MacFUSE talk at Google
  • Next by Date: Mouse position from NSEvent starts at (0, 1) ?
  • Previous by thread: Re: US/non-US localization problem
  • Next by thread: Re: US/non-US localization problem
  • Index(es):
    • Date
    • Thread