Re: 'LANG=' produces German output
on my Lion box, calling LANG= bison ... I suddenly get *German* output! [...] >> >> It's seems to be a new feature of gettext 0.21, which comes with >> improved MacOS support. In the NEWS file I read > > Then you should not be seeing this problem with MacPorts since we > still use gettext 0.19.8.1. OK. Maybe it's another change, but essentially it doesn't matter :-) I added a patch to my lilypond-devel PR (which will also be soon part of lilypond upstream) to fix it. Werner
Re: 'LANG=' produces German output
> Am 2020-02-13 um 23:11 schrieb Werner LEMBERG : > >>> I'm not sure whether I like this feature. At least on the command >>> line, I consider it surprising. >> >> There is the opposite expectation: "I have set that I want the >> programs to talk to me in German. Why do I need to specify it a >> second time, through an environment variable, for the command-line >> programs?" > > Because we did this the last 20 years? As written above, I consider > it surprising, not necessarily bad... It’s just a DE-fault ;) Hraban
Re: 'LANG=' produces German output
On Feb 13, 2020, at 08:40, Werner LEMBERG wrote: >>> on my Lion box, calling >>> >>> LANG= bison ... >>> >>> I suddenly get *German* output! Ditto for other programs like >>> 'info', 'ggrep', etc., that come with '.po' files. Is this normal? >>> Is this a new gettext feature? > >> On a "normal" Unix/Linux system, I would expect "C" locale (or >> perhaps a system setting) to be that default. But Macs are a bit >> odd; their native apps get some defaults from system preference >> settings. What are your language and region settings there? > > It's seems to be a new feature of gettext 0.21, which comes with > improved MacOS support. In the NEWS file I read Then you should not be seeing this problem with MacPorts since we still use gettext 0.19.8.1. If you would like to read about why we have not updated or to help us to do so, see: https://trac.macports.org/ticket/58526
Re: 'LANG=' produces German output
Hello Bruno, thanks for your detailed answer. >> I'm not sure whether I like this feature. At least on the command >> line, I consider it surprising. > > There is the opposite expectation: "I have set that I want the > programs to talk to me in German. Why do I need to specify it a > second time, through an environment variable, for the command-line > programs?" Because we did this the last 20 years? As written above, I consider it surprising, not necessarily bad... Werner
Re: 'LANG=' produces German output
[CCing Bruno Haible] >> on my Lion box, calling >> >> LANG= bison ... >> >> I suddenly get *German* output! Ditto for other programs like >> 'info', 'ggrep', etc., that come with '.po' files. Is this normal? >> Is this a new gettext feature? > > I would suppose that without a valid locale LANG or the LC_* > variables, there would be some other default - that it's not > randomly picking a locale. You are correct. > On a "normal" Unix/Linux system, I would expect "C" locale (or > perhaps a system setting) to be that default. But Macs are a bit > odd; their native apps get some defaults from system preference > settings. What are your language and region settings there? It's seems to be a new feature of gettext 0.21, which comes with improved MacOS support. In the NEWS file I read * Runtime behaviour: - The interpretation of the language preferences on macOS has been improved, especially in the case where a system locale does not exist for the combination of the selected primary language and the selected territory. In my shell, `set` shows LANG=en_US.UTF-8 (and `LANGUAGE` is not set). Some test results: bison --helpEnglish output LANG= bison --help German output LANGUAGE= bison --help English output LANG=C bison --help English output On my GNU/Linux box that still uses gettext 0.19.8.1, I get the following with the same `LANG` setting. bison --helpEnglish output LANG= bison --help English output LANGUAGE= bison --help English output LANG=C bison --help English output My MacOS Lion box *is* a German one, so it seems that gettext extracts language information from some other places if neither `LANGUAGE` nor `LANG` is unset or set to an empty value. I'm not sure whether I like this feature. At least on the command line, I consider it surprising. Werner
Re: 'LANG=' produces German output
I would suppose that without a valid locale LANG or the LC_* variables, there would be some other default - that it's not randomly picking a locale. On a "normal" Unix/Linux system, I would expect "C" locale (or perhaps a system setting) to be that default. But Macs are a bit odd; their native apps get some defaults from system preference settings. What are your language and region settings there? > On Feb 13, 2020, at 03:50, Werner LEMBERG wrote: > > > [macports-ports 83eb0fba14b88745b29c0efa5d29aa73ee69c04b from 2020-02-12] > > > Folks, > > > on my Lion box, calling > > LANG= bison ... > > I suddenly get *German* output! Ditto for other programs like 'info', > 'ggrep', etc., that come with '.po' files. Is this normal? Is this a > new gettext feature? > > >Werner >
'LANG=' produces German output
[macports-ports 83eb0fba14b88745b29c0efa5d29aa73ee69c04b from 2020-02-12] Folks, on my Lion box, calling LANG= bison ... I suddenly get *German* output! Ditto for other programs like 'info', 'ggrep', etc., that come with '.po' files. Is this normal? Is this a new gettext feature? Werner
