RE: [Ltru] Eliminating the preposterous ASCII ordering in lookup

+1

Actually, we should just say "map any extended language ranges to basic
language ranges before performing lookup". This has the same effect.

Addison

Addison Phillips
Internationalization Architect - Yahoo! Inc.

Internationalization is an architecture.
It is not a feature. 

> -----Original Message-----
> From: John Cowan [mailto:cowan@ccil.org]
> Sent: Wednesday, February 22, 2006 12:54 PM
> To: ltru@ietf.org
> Subject: [Ltru] Eliminating the preposterous ASCII ordering in lookup
> 
> It's really laughable to suggest that implementations might use ASCII
> tag ordering to make fallback decisions on lookup.  IMHO, the behavior
> of extended ranges on lookup should be:
> 
> 	If the first subtag of a language range is '*' and it is
> 	followed by other ranges in a priority list, skip it.
> 	If the first subtag is '*' and there are no following
> 	ranges, return the default content.  All other '*' subtags
> 	should be removed before lookup processing is done.
> 
> That is simple, clear, to the point, straightforward, and doesn't provide
> preposterous results.
> 
> --
> Verbogeny is one of the pleasurettes    John Cowan <cowan@ccil.org>
> of a creatific thinkerizer.             http://www.ap.org
>    -- Peter da Silva                    http://www.ccil.org/~cowan
> 
> _______________________________________________
> Ltru mailing list
> Ltru@ietf.org
> https://www1.ietf.org/mailman/listinfo/ltru

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