Bug#748215: gettext(3) should special case both C and C.UTF-8 wrt LANGUAGE lookup

2022-08-04 Thread Vincent Lefevre
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 some

Bug#748215: gettext(3) should special case both C and C.UTF-8 wrt LANGUAGE lookup

2022-08-04 Thread Aurelien Jarno
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

Bug#748215: gettext(3) should special case both C and C.UTF-8 wrt LANGUAGE lookup

2022-08-03 Thread Vincent Lefevre
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.

Bug#748215: gettext(3) should special case both C and C.UTF-8 wrt LANGUAGE lookup

2014-06-02 Thread Dimitri John Ledkov
On 2 June 2014 21:24, Jakub Wilk wrote: > * Dimitri John Ledkov , 2014-06-02, 21:12: > >>> What I find unexpected is this: >>> >>> $ LANGUAGE=de LC_ALL=de_DE.UTF-8 stat /moo >>> stat: cannot stat '/moo': No such file or directory >> >> >> Above should be in German, no?! > > > See, I was right when

Bug#748215: gettext(3) should special case both C and C.UTF-8 wrt LANGUAGE lookup

2014-06-02 Thread Jakub Wilk
* Dimitri John Ledkov , 2014-06-02, 21:12: What I find unexpected is this: $ LANGUAGE=de LC_ALL=de_DE.UTF-8 stat /moo stat: cannot stat '/moo': No such file or directory Above should be in German, no?! See, I was right when I said "unexpected". :-P The message is in German only if the de_DE

Bug#748215: gettext(3) should special case both C and C.UTF-8 wrt LANGUAGE lookup

2014-06-02 Thread Dimitri John Ledkov
On 26 May 2014 20:45, Jakub Wilk wrote: > > What I find unexpected is this: > > $ LANGUAGE=de LC_ALL=de_DE.UTF-8 stat /moo > stat: cannot stat '/moo': No such file or directory > Above should be in German, no?! It is, at least, for me. I am for special-casing C.UTF-8 as it's aimed to serve the s

Bug#748215: gettext(3) should special case both C and C.UTF-8 wrt LANGUAGE lookup

2014-05-26 Thread Jakub Wilk
[I'm not (e)glibc maintainer, just a random gettext user.] * Zygmunt Krynicki , 2014-05-15, 12:57: If the LANGUAGE environment variable is set to a nonempty value, and the locale is not the "C" locale, the value of LANGUAGE is assumed to contain a colon separated list of locale names. The funct

Bug#748215: gettext(3) should special case both C and C.UTF-8 wrt LANGUAGE lookup

2014-05-18 Thread Aurelien Jarno
On Thu, May 15, 2014 at 12:57:04PM +0200, Zygmunt Krynicki wrote: > Package: src:eglibc > Severity: wishlist > Tags: l10n > > Reading the gettext(3) man page I see the following fragment: > >If the LANGUAGE environment variable is set to a nonempty value, >and the locale is not the "C" lo

Bug#748215: gettext(3) should special case both C and C.UTF-8 wrt LANGUAGE lookup

2014-05-15 Thread Zygmunt Krynicki
Package: src:eglibc Severity: wishlist Tags: l10n Reading the gettext(3) man page I see the following fragment: If the LANGUAGE environment variable is set to a nonempty value, and the locale is not the "C" locale, the value of LANGUAGE is assumed to contain a colon separated list of loc