Re: [Ltru] 3.1.2: extended language range not defined

["Phillips, Addison" <addison at amazon.com>]

A reference to RFC 4647 is provided in several places, but not in places where we reference the language range constructs. I'll add those to the editor's copy.

Addison

Addison Phillips
Globalization Architect -- Lab126

Internationalization is not a feature.
It is an architecture.


> -----Original Message-----
> From: ltru-bounces at ietf.org [mailto:ltru-bounces at ietf.org] On
> Behalf Of Peter Constable
> Sent: Monday, July 07, 2008 9:40 PM
> To: LTRU Working Group
> Subject: Re: [Ltru] 3.1.2: extended language range not defined
>
> Btw, "language range" or "extended language range" are also used in
> Sections 3.1.6, 3.1.7 and 4.1.
>
> Peter
>
> > -----Original Message-----
> > From: ltru-bounces at ietf.org [mailto:ltru-bounces at ietf.org] On
> Behalf Of
> > Peter Constable
> > Sent: Monday, July 07, 2008 8:41 PM
> > To: LTRU Working Group
> > Subject: [Ltru] 3.1.2: extended language range not defined
> >
> > In draft 16, there's a reference in Section 3.1.2 in the part on
> the
> > Preferred-Value field to "extended language range". That term is
> not
> > defined in the draft for 4646bis, however. Either a definition
> should
> > be given in this doc, or a reference provided to another doc in
> which
> > it is defined.
> >
> >
> > Peter
> > _______________________________________________
> > Ltru mailing list
> > Ltru at ietf.org
> > https://www.ietf.org/mailman/listinfo/ltru
>
> _______________________________________________
> Ltru mailing list
> Ltru at ietf.org
> https://www.ietf.org/mailman/listinfo/ltru
_______________________________________________
Ltru mailing list
Ltru at ietf.org
https://www.ietf.org/mailman/listinfo/ltru