Re: Issue with language codes and locale codes

At 10:24 04/06/11 -0700, Mark Davis wrote:
>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 "-".

Earlier, it explains that what you send with Accept-Language is a
language range, but what the document knows of itself (e.g.
as expressed in Content-Language) is a language tag. So the
matching results below are correct.

Regards,    Martin.



>Mark
>__________________________________
>http://www.macchiato.com
>$Bcv%3(B $B`&%+`&%=`&%-`':b!"%C`&%;`&%r`&%=`&Tb!&:b!"Vb!&.b!"!"`':b!"%'`&!<`&%;`&Xb!"%C`&%g`'9cw'î(B
>----- 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 Monday, 14 June 2004 00:39:07 UTC