From: "Voelker, Bernhard" <bernhard.voelker@siemens-enterprise.com>
To: Bruno Haible <bruno@clisp.org>,
Charles Wilson <cygwin@cwilson.fastmail.fm>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>,
"bug-gnu-gettext@gnu.org" <bug-gnu-gettext@gnu.org>
Subject: RE: cygwin started speaking German today
Date: Thu, 08 Sep 2011 10:55:00 -0000 [thread overview]
Message-ID: <7856072A9D04C24B82DFE2B1112FE38A0C2AFF982B@MCHP058A.global-ad.net> (raw)
In-Reply-To: <201109081246.23238.bruno@clisp.org>
Bruno Haible wrote:
> > Bernhard Voelker wrote:
> > > Starting with today's update, cygwin started speaking German:
> > >
> > > $ mkdir -v x0
> > > mkdir: Verzeichnis „x0“ angelegt
> > > $ LANG=C mkdir -v x2
> > > mkdir: created directory `x2'
> > > $ LANG=C.UTF-8 mkdir -v x1
> > > mkdir: Verzeichnis „x1“ angelegt
> > >
> > > Default is LANG=C.UTF-8 here.
> > >
> > > Ok, the PC is in Germany, but none of my environment
> > > variables have a 'de' inside.
>
> This is as it should be. See the NEWS entry from the gettext package:
>
> * Runtime behaviour:
> - On MacOS X and Windows systems, <libintl.h> now extends setlocale() and
> newlocale() so that their determination of the default locale considers
> the choice the user has made in the system control panels.
>
> 'mkdir' is a GNU coreutils programs, which uses <libintl.h>, so it gets
> the benefit of libintl enhancements.
>
> After Cygwin 1.7 added working locales and defined LANG=C.UTF-8 for all users,
> libintl could be extended to respect the choices the user has made in the
> system control panels.
>
> ...
I had read the NEWS but wasn't aware that the behaviour in Cygwin would
change for my system with this update.
Thanks for this comprehensive explanation!
Have a nice day,
Berny
next prev parent reply other threads:[~2011-09-08 10:55 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 [this message]
2011-09-08 11:06 ` Eric Blake
2011-09-08 12:05 ` Charles Wilson
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=7856072A9D04C24B82DFE2B1112FE38A0C2AFF982B@MCHP058A.global-ad.net \
--to=bernhard.voelker@siemens-enterprise.com \
--cc=bruno@clisp.org \
--cc=bug-gnu-gettext@gnu.org \
--cc=cygwin@cwilson.fastmail.fm \
--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).