RE: [Ltru] Proposed resolution for Issue 13 (language tags)

From: Phillips, Addison <addison@amazon.com> · Date: Tue, 15 Apr 2008 17:30:22 +0000

"No sooner do I push send..."

This text would work for me.

Addison

Addison Phillips
Globalization Architect -- Lab126 (Amazon)
Chair -- W3C Internationalization Core WG

Internationalization is not a feature.
It is an architecture.

> -----Original Message-----
> From: ltru-bounces@ietf.org [mailto:ltru-bounces@ietf.org] On Behalf Of
> Julian Reschke
> Sent: mardi 15 avril 2008 04:33
> To: HTTP Working Group; LTRU Working Group
> Subject: Re: [Ltru] Proposed resolution for Issue 13 (language tags)
>
> OK,
>
> thanks for all the feedback so far. I (hopefully) have addressed many
> of
> the issues; here's the new proposed text for 3.5:
>
> ------
> 3.5.  Language Tags
>
>     A language tag, as defined in [RFC4646], identifies a natural
>     language spoken, written, or otherwise conveyed by human beings for
>     communication of information to other human beings.  Computer
>     languages are explicitly excluded.  HTTP uses language tags within
>     the Accept-Language and Content-Language fields.
>
>     In summary, a language tag is composed of one or more parts: A
>     primary language tag and a possibly empty series of subtags:
>
>       language-tag  = <Language-Tag, defined in [RFC4646], Section 2.1>
>
>     White space is not allowed within the tag and all tags are case-
>     insensitive.  The name space of language subtags is administered by
>     the IANA (see
>     <http://www.iana.org/assignments/language-subtag-registry>).
>
>     Example tags include:
>
>       en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN
>
>     See RFC 4646 for further information.
> ------
>
> (see also <http://www.tools.ietf.org/wg/httpbis/trac/ticket/13>).
>
>
> BR, Julian
> _______________________________________________
> Ltru mailing list
> Ltru@ietf.org
> https://www.ietf.org/mailman/listinfo/ltru