New topic: Code [zgh] adopted
petercon at microsoft.com
Sun Dec 16 09:32:09 CET 2012
When entries are added to ISO 639-2, both English and French names always included. This was not done for ISO 639-3 since the scope of language, encompassing as it does a large number of languages with very limited documentation, doesn't make it feasible to ensure we can always come up with a language name in both English and French (or even just one of those).
From: ietf-languages-bounces at alvestrand.no [mailto:ietf-languages-bounces at alvestrand.no] On Behalf Of Doug Ewell
Sent: Saturday, December 15, 2012 11:11 AM
To: ietf-languages at iana.org
Subject: Re: New topic: Code [zgh] adopted
Richard BUDELBERGER <budelberger dot richard at wanadoo dot fr> wrote:
> Writing « The code [zgh] named Standard Moroccan Tamazight » is as
> stupid as to say « The code [fr] named Standard French le français ».
It suggests to me that the JAC adopted "amazighe standard marocain" as an alternate name for the language. They have done this before for sign languages (see e.g. 'csc'). There doesn't seem to be any strict guideline as to when they do or do not adopt translations of names into 639-3. Usually when they do, at least for sign languages, the translations are limited to the spoken languages in use where the sign language is used.
For the IANA Language Subtag Registry, it is up to this group to decide whether to adopt all translated forms from a source standard, though we pretty much always do because of our reading of Section 3.1.5.
Doug Ewell | Thornton, Colorado, USA
http://www.ewellic.org | @DougEwell
Ietf-languages mailing list
Ietf-languages at alvestrand.no
More information about the Ietf-languages