Bug#748215: gettext(3) should special case both C and C.UTF-8 wrt LANGUAGE lookup
On 2022-08-04 10:23:42 +0200, Aurelien Jarno wrote:
> On 2022-08-04 00:33, Vincent Lefevre wrote:
> > On 2014-05-19 00:33:00 +0200, Aurelien Jarno wrote:
> > > Until the C.UTF-8 locale is integrated directly into glibc instead of
> > > being provide like a standard locale, it's not going to be something
> > > easy to do.
> >
> > Well, on the upstream side, the C.UTF-8 locale is now provided,
> > but the bug still occurs.
>
> It is provided like a standard locale, but has not been integrated
> directly into glibc (like the built-in C locale), so it's expected that
> the bug stills occurs.
It seems that since upstream bug 17318 has been closed, upstream
won't do anything more concerning its integration (whatever this
means) and something special will be done to fix this bug (i.e.
upstream bug 16621). According to Florian Weimer, the main problem
(as opposed to the C locale) would be to handle aliases, and indeed,
while Debian currently provides only C.UTF-8, with glibc 2.35 C.utf8
and C.utf-8 also work as aliases and are also affected by this bug
(tested on an Ubuntu 22.04 LTS machine with libc6 2.35-0ubuntu3).
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Reply to: