Re: [Ltru] Extended language tags

John Cowan wrote:
> 
>> * I don't think the Breton example applies.  http-accept-lang allows for
>> "br-FR;fr-FR" type fallback, so that is a solution.  If an application
>> independently wanted to make this assumption that's fine by me, but
>> this seems orthogonal to the problem we're trying to solve here.
> 
> That works for filtering (which is what Accept-Lang does), but not so
> well in practice for lookup.  Normally people don't specify multiple match patterns
> in lookup situations, they just say "I speak Breton, what's the best
> match you have?"
> 

Although actual implementations of lookup, as specified, do allow for 
it. My implementations handle this situation well and it turns out to be 
pretty useful to use a language priority list for lookup.

Traditional locale systems, however, work as John notes. I am hopeful 
that they will adapt.

Addison

-- 
Addison Phillips
Globalization Architect -- Yahoo! Inc.
Chair -- W3C Internationalization Core WG

Internationalization is an architecture.
It is not a feature.

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