RE: [Ltru] [psg.com #964] section 3.4 of -00 is hard to understand

["Addison Phillips" <addison.phillips at quest.com>]

I don't like that revision for a simple reason: it excludes extensions that do identify languages or aspects of languages. For example, an extension might be used for transliteration schemes or for very specialized kinds of categorization applied by linguists. The requirement is that extensions be compatible with language tags and that they be related in some meaningful, non-trivial way. But we shouldn't be too specific IMO.

Addison

Addison P. Phillips
Globalization Architect, Quest Software
Chair, W3C Internationalization Core Working Group

Internationalization is not a feature.
It is an architecture. 

> -----Original Message-----
> From: ltru-bounces at lists.ietf.org [mailto:ltru-bounces at lists.ietf.org] On
> Behalf Of Peter Constable
> Sent: 2005?5?12? 8:41
> To: LTRU Working Group
> Subject: RE: [Ltru] [psg.com #964] section 3.4 of -00 is hard to
> understand
> 
> > -----Original Message-----
> > From: ltru-bounces at lists.ietf.org [mailto:ltru-bounces at lists.ietf.org]
> On
> > Behalf Of Addison Phillips
> 
> > Yes. The new text reads...
> 
> Suggested slight revision:
> 
> <q>Extension subtags are those introduced by single-letter subtags other
> than 'x-'. They are reserved for the generation of identifiers for data
> categories other than language, but which contain a language component
> and are compatible with applications that understand language tags. For
> example, they might be used to define locale identifiers, which are
> generally based on language.</q>
> 
> 
> Peter Constable
> 
> 
> 
> _______________________________________________
> Ltru mailing list
> Ltru at lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/ltru


_______________________________________________
Ltru mailing list
Ltru at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ltru