> See my post responding to Peter. I"d rather deprecate "sgn-US" to
> "sgn-ase" rather than just "ase".
Noted.
> True, but then it would deviate from how lookup is actually implemented
> in various places, like JVM resource bundles and Apache (when filtering
> fails).
Mmm.... maybe. But JVMs don't even do the current BCP 47 (well, most people's don't... they can be made to, at least with the most modern JVMs :-) ). Note too that I said originally that they MAY treat the primary-extlang sequence as atomic, not that it is required. Creating a new algorithm ("Extended Lookup"?) might be preferable to altering an exiting algorithm.
Addison
Addison Phillips
Globalization Architect -- Lab126
Internationalization is not a feature.
It is an architecture.
> -----Original Message-----
> From: John Cowan [mailto:cowan at ccil.org]
> Sent: Thursday, May 29, 2008 2:02 PM
> To: Phillips, Addison
> Cc: John Cowan; LTRU Working Group
> Subject: Re: [Ltru] a modest proposal...
>
> Phillips, Addison scripsit:
>
> > Really? 'sgn'?
>
>
> > That's what I had in mind. Note that 4647 would not necessarily
> diverge
> > from 2616. It could be done as a note in Lookup, for example and 2616
> > doesn't do Lookup.
>
>
> --
> Go, and never darken my towels again! John Cowan
> --Rufus T. Firefly http://ccil.org/~cowan
_______________________________________________
Ltru mailing list
Ltru at ietf.org
https://www.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.