bug-gettext
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gettext] cygwin started speaking German today


From: Charles Wilson
Subject: Re: [bug-gettext] cygwin started speaking German today
Date: Thu, 08 Sep 2011 08:04:05 -0400
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666

On 9/8/2011 6:46 AM, Bruno Haible wrote:
> There is nothing to "fix". Users who don't want internationalization 
> system-wide
> can set their locale in the "Regional Settings" control panel to English.
> Users who want to have a German Windows but a non-internationalized Cygwin can
> set LANG=C or LC_ALL=C - exactly like POSIX specifies.

But setting LANG=C.UTF-8 (and not setting any of the LC_* vars at all)
should have the same behavior as setting LC_ALL=C.UTF-8.

It does not -- and THAT's the bug.  In the former case, $LANG is ignored
and the system settings are used (in the OP's case, messages are in
German).  In the latter case, LC_ALL is respected, and (in the OP's
case) messages are in English.

Here's how to reproduce:
        cygwin-1.7.9-1
        coreutils-8.10-1
        libintl8-0.18.1.1-1
        libiconv2-1.14-1
        xterm-261-1
        bash-4.1.10-4

In MSWindow's language settings, set:

* tab 1: "Regional options":
  combobox "Standards and formats": "German (Germany)"
  combobox "Location"             : "Germany"
* tab 2: "Languages":
  combobox "Language used in menues and dialogs": English
* tab 3: "Advanced"
  combobox "Language for non-Unicode programs": "German (Germany)"

Reboot.

Then, launch a bash shell (in cmd.exe, not mintty).  Launch an Xserver
-- I actually used the XMing one
http://www.straightrunning.com/XmingNotes/ not the cygwin one -- just to
eliminate the possibility that cygwin's Xserver was exercising cygwin's
[X]setlocale() function.

Then, in the bash shell:

$ LANG=C.UTF-8 DISPLAY=127.0.0.1:0.0 xterm &
$ LC_ALL=C.UTF-8 DISPLAY=127.0.0.1:0.0 xterm &

In the first xterm:

$ mkdir -v x1
mkdir: Verzeichnis „x1“ angelegt

In the seccond xterm:

$ mkdir -v x2
mkdir: created directory `x2'

Now, it may be possible to simplify this test case, but that's what the
OP reported, so that's what I reproduced...

--
Chuck



reply via email to

[Prev in Thread] Current Thread [Next in Thread]