addison at amazon.com
Tue Jul 29 18:05:50 CEST 2008
Actually, we don't. What we require is a copy of the code list at some point and the cooperation of the RA when changes are made from that point. One of the reasons for having a registry in the first place was the chaos that resulted from having multiple, free, un-synchronized mirrors of core standards that were themselves not freely available.
Globalization Architect -- Lab126
Internationalization is not a feature.
It is an architecture.
> -----Original Message-----
> From: ietf-languages-bounces at alvestrand.no [mailto:ietf-languages-
> bounces at alvestrand.no] On Behalf Of Doug Ewell
> Sent: Monday, July 28, 2008 9:37 PM
> To: ietf-languages at iana.org
> Subject: Re: ISO 639-5
> Stephane Bortzmeyer <bortzmeyer at nic dot fr> wrote:
> >> where and when will the details of ISO 639-5 standard be freely
> >> available?
> > Never? This is ISO, after all.
> I hope this only refers to the details of the standard proper, not
> code list, which is still not freely available.
> As editor of 4645bis, I was a strong proponent of including the ISO
> 639-5 code elements in the expanded Language Subtag Registry,
> that the 639-5 code list would be made freely available with little
> delay. If this is not going to happen -- and I'm basing that
> not so much on Stéphane's remark as on the continuing lack of
> information from the RA -- then perhaps we in LTRU need to revisit
> decision. We require all of the other core standards to have
> available code lists.
> Doug Ewell * Thornton, Colorado, USA * RFC 4645 * UTN #14
> http://www.alvestrand.no/mailman/listinfo/ietf-languages ˆ
> Ietf-languages mailing list
> Ietf-languages at alvestrand.no
More information about the Ietf-languages