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 w
> 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
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 "no
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
[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 LAN
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
[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?
