Bug#639166: expose iso14651/i18n as separate locale
On ons, 2011-08-24 at 20:49 +0200, Aurelien Jarno wrote:
> On Wed, Aug 24, 2011 at 09:08:54PM +0300, Peter Eisentraut wrote:
> > Package: locales
> > Version: 2.13-16
> > Severity: wishlist
> >
> > Would it be possible to expose the iso14651_t1 LC_COLLATE locale
> > definition from the source tree as a separate locale for the user? It
> > would sometimes be quite useful in applications to be able to say
> > explicitly, give me a default, language-neutral sort ordering that is
> > multi-language aware. And then for LC_CTYPE, it looks like the i18n
> > file would be a good fit. (I don't really need any of the other
> > categories for this purpose.)
> >
> > So, would this be possible with reasonable effort? Does it need
> > significant upstream changes? Or is it perhaps already available via
> > localedef somehow?
> >
>
> Why doesn't the C.UTF-8 locale doesn't fit here? Do we really need a new
> locale for that?
Hmm, C.UTF-8 appears to do what I want, but reading up on #609306, which
was the initial discussion about that locale, indicated that people
explicitly did not want C.UTF-8 to have a collation behavior different
from plain C. So it looks like the current behavior of C.UTF-8 is
wrong.
Reply to: