Re: [OFF] Localisation (was Re: Security Framework: authorization rights.)
Re: [OFF] Localisation (was Re: Security Framework: authorization rights.)
- Subject: Re: [OFF] Localisation (was Re: Security Framework: authorization rights.)
- From: mmalcolm crawford <email@hidden>
- Date: Mon, 3 Nov 2003 19:44:53 -0800
On Nov 3, 2003, at 7:28 PM, Wade Tregaskis wrote:
Because "en" is a *language* code; "en_UK" specifies "English as
spoken in the UK" as opposed to any other *region*. This same
reasoning (and ICU specification) accounts for "fr_FR", "es_ES", and
"pt_PT"...
Then why do the majority of US developers release stuff with US
English for the "en" code, rather than "en_US"?
For that matter then, why is it at all possible to specify a language
without a region? If it weren't possible to have a generic "en",
that'd solve this whole problem..
That would introduce a new problem -- duplication of resources.
The language locale provides a set of "default defaults" for all
regional "dialects" of that language.
Again, this is explained in detail in the "Locales" documentation, and
is touched on in Internationalization:
<
http://developer.apple.com/documentation/MacOSX/Conceptual/
BPInternational/index.html>
mmalc
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.