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: Wade Tregaskis <email@hidden>
- Date: Tue, 4 Nov 2003 15:05:10 +1100
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.
Ah ha, but "localization" is not the default spelling, it is the US
dialect spelling. So putting it into a top-level category like "en" is
wrong. Now, as I've said, I think the English should have final veto
on what is the English language - you can argue that point if you like
- and they have voted. "Localisation" is the correct English spelling
(in this example), and so should be the one used in the 'default'
dialect, "en".
Wade Tregaskis
-- Sed quis custodiet ipsos custodes?
_______________________________________________
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.