public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: Bruno Haible <bruno@clisp.org>
Cc: Bernhard Voelker <bernhard.voelker@siemens-enterprise.com>,
	 cygwin@cygwin.com, bug-gnu-gettext@gnu.org
Subject: Re: cygwin started speaking German today
Date: Thu, 08 Sep 2011 12:05:00 -0000	[thread overview]
Message-ID: <4E68AF35.9030002@cwilson.fastmail.fm> (raw)
In-Reply-To: <201109081246.23238.bruno@clisp.org>

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

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2011-09-08 12:05 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30 10:18 Voelker, Bernhard
2011-08-30 11:28 ` Charles Wilson
2011-09-08  2:31 ` Charles Wilson
2011-09-08 10:46   ` Bruno Haible
2011-09-08 10:55     ` Voelker, Bernhard
2011-09-08 11:06     ` Eric Blake
2011-09-08 12:05     ` Charles Wilson [this message]
2011-09-08 12:48       ` Andy Koppe
2011-09-08 13:13         ` Eric Blake
2011-09-08 12:51       ` Andy Koppe
2011-09-08 21:58         ` Bruno Haible
     [not found]       ` <201109082344.55506.bruno@clisp.org>
2011-09-09  9:18         ` Charles Wilson
2011-09-09 12:33           ` Andy Koppe
2011-09-09 15:00             ` Corinna Vinschen
2011-09-10 11:36               ` Thorsten Kampe
2011-09-13 18:39               ` Eric Blake
2011-09-17 21:50                 ` David Sastre
2011-09-17 22:50                   ` Ken Brown
2011-09-18  3:19                     ` David Sastre
2011-10-04 12:29                 ` Corinna Vinschen
2011-10-04 12:46                   ` Charles Wilson
2011-10-04 14:30                     ` Corinna Vinschen
2011-10-04 18:04                       ` Erwin Waterlander
2011-10-04 18:21                         ` Corinna Vinschen
2011-10-05 16:04                           ` Erwin Waterlander
2011-10-05 16:28                             ` Corinna Vinschen
2011-10-05 16:52                               ` Erwin Waterlander
2011-10-05 17:32                               ` Charles Wilson
2011-10-05 18:24                                 ` Ken Brown
2011-10-05 18:29                                   ` Corinna Vinschen
2011-10-05 18:44                                   ` Erwin Waterlander
2011-10-05 18:50                                   ` Yaakov (Cygwin/X)
2011-10-05 18:58                                     ` Christopher Faylor
2011-10-10 17:24                                   ` Corinna Vinschen
2011-10-11 15:41                                     ` Erwin Waterlander
2011-10-11 16:54                                     ` Charles Wilson
2011-10-11 17:29                                       ` Christopher Faylor
2011-10-16 18:42                                       ` Charles Wilson
2011-10-17  6:59                                         ` Corinna Vinschen
2011-10-17 13:17                                           ` Charles Wilson
2011-10-17 13:52                                             ` Corinna Vinschen
2011-10-17 13:58                                               ` Corinna Vinschen
2011-10-05 18:29                                 ` Corinna Vinschen
2011-10-06  1:35                       ` [OT] " Andrey Repin
2011-10-05 12:08                     ` Ken Brown
2011-09-09 15:13             ` Charles Wilson
2011-09-09 20:08               ` Andy Koppe
2011-09-08 13:45     ` Corinna Vinschen
2011-09-08 13:51     ` Corinna Vinschen
2011-09-08 20:57       ` Bruno Haible
2011-09-09 15:09         ` Corinna Vinschen
2011-09-09 15:58           ` Andy Koppe
2011-09-10 11:45           ` Thorsten Kampe
2011-09-10 13:50             ` Christopher Faylor
2011-09-10 16:10               ` Thorsten Kampe
2011-09-10 17:11                 ` Christopher Faylor
2011-08-31  8:39 Voelker, Bernhard
2011-08-31 14:01 ` Charles Wilson
2011-08-31 15:19   ` Charles Wilson
2011-09-01  5:30 Voelker, Bernhard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E68AF35.9030002@cwilson.fastmail.fm \
    --to=cygwin@cwilson.fastmail.fm \
    --cc=bernhard.voelker@siemens-enterprise.com \
    --cc=bruno@clisp.org \
    --cc=bug-gnu-gettext@gnu.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).