On Thu, Oct 17, 2002 at 05:06:29PM +0200, Thomas Wolff wrote:
> Markus Kuhn wrote:
>
> > > A decent solution to this problem would be to handle basic locale
> > > information ("en_US") and encoding suffix ("UTF-8") separately and
> > > specifiy that ANY available locale can be suffixed with ANY known
> > > encoding, so installed de, gb, whatever locales could always be
> > > run with UTF-8.
> > > Is anything specified anywhere about this?
> >
> > http://www.opengroup.org/onlinepubs/007904975/functions/setlocale.html
>
> I think that the formulation
> "If the string does not correspond to a valid locale,
> setlocale() shall return a NULL pointer and the international
> environment is not changed."
> is as stupid as it could be since it imposes an "all or nothing"
> locale matching strategy.
> I don't see why aspects that are handled independently should be
> tied together this way.
> Even more, one would expect decent fallback behaviour, e.g.
> mapping "en_GB" to "en" where "en_GB" is not available etc.
> How can this be changed?
ISO 15897 also has some fallback rules. I think that could be
extended in some way, so that you may specify more locales to
chose from, like it is done with accept-language: in http.
I think some software already does this. Current glibc supports
ISO 15897, but that support is going to be removed, as far as I know.
Best regards
keld
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
