RE: Issue with language codes and locale codes

I think Martin's point is: when setting Accept-Language to get the best match for locale selection, you want the most specific tag (en-Latn-US-boont). When setting Accept-Language to get the best match for language content selection, you want the least specific tag for the job (en). In the Web services sphere this enhances the argument for not using the transport's metadata structure and for the creation of a WS-International type standard.

In passing, I should note that the extension mechanism is our Internet-Draft helps bridge this gap: locale extensions are ignored in that context, so one can specify a less exact language and yet still add locale ornamentation to the tag.

Addison

Addison P. Phillips
Director, Globalization Architecture
webMethods | Delivering Global Business Visibility
http://www.webMethods.com
Chair, W3C Internationalization (I18N) Working Group
Chair, W3C-I18N-WG, Web Services Task Force
http://www.w3.org/International

Internationalization is an architecture. 
It is not a feature.

> -----Original Message-----
> From: public-i18n-ws-request@w3.org
> [mailto:public-i18n-ws-request@w3.org]On Behalf Of Mark Davis
> Sent: 2004年6月11日 10:24
> To: public-i18n-ws@w3.org; Martin Duerst
> Subject: Re: Issue with language codes and locale codes
> 
> 
> 
> I'm confused. In that section, I see:
> 
> >A language-range matches a language-tag if it exactly equals the 
> tag, or if it
> exactly equals a prefix of the tag such that the first tag 
> character following
> the prefix is "-".
> 
> Mark
> __________________________________
> http://www.macchiato.com
> ► शिष्यादिच्छेत्पराजयम् ◄
> 
> ----- Original Message ----- 
> From: "Martin Duerst" <duerst@w3.org>
> To: <public-i18n-ws@w3.org>
> Sent: Fri, 2004 Jun 11 02:27
> Subject: Issue with language codes and locale codes
> 
> 
> >
> > I have found the following issue with regards to using HTTP
> > Accept-Language: for determining the locale of a user:
> >
> > The way HTTP matches language ranges and language tags is
> > described in Section 14.4 of RFC 2616
> > (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.4):
> >
> > Accept-Language: en     matches          Content-Language: en-us
> > but
> > Accept-Language: en-us  does no match    Content-Language: en
> >
> > This means that browsers should send general things such as 'en'
> > rather than the more specific labels such as 'en-us', or both.
> > But for using this to determine a locale, the more specific,
> > the better.
> >
> >
> > Regards,    Martin.
> >
> >
> >
> >
> >
>

Received on Friday, 11 June 2004 14:59:25 UTC