From: Konstantin Khomoutov <flatworm@users.sourceforge.net>
To: Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: rupert thurner <rupert.thurner@gmail.com>,
msysgit@googlegroups.com, git@vger.kernel.org
Subject: Re: [msysGit] Re: Sneak peek of the upcoming Git for Windows 2.x
Date: Mon, 13 Apr 2015 10:54:16 +0300 [thread overview]
Message-ID: <20150413105416.8a2d12b530344a61f5ecb0f1@domain007.com> (raw)
In-Reply-To: <b1cc6ba927238fdaa68f685be42002c7@www.dscho.org>
On Sun, 12 Apr 2015 19:51:29 +0200
Johannes Schindelin <johannes.schindelin@gmx.de> wrote:
[...]
> > * it is talking german to me
> >
> > would it be sufficient to delete
> > c:\Apps\gitwin\mingw64\share\locale\de\LC_MESSAGES\
> > resp the whole locale directory to let it speak english?
>
> Probably. But the canonical solution is to set the `LC_ALL` or `LANG`
> environment variables accordingly.
JFTR, that won't probably fix `git gui` and `gitk` as they are started
directly, not via shell scripts, and hence are unaffected by whatever
tweaks are done in ~/.bashrc *unless* they're started from the
interactive Git bash shell and hence see that environment.
I would hence just stick LC_MESSAGES=en (or LC_ALL, or LANG) into the
environment variables (on the user's level) and solve this problem once
and for all future programs making use of Unix-y locale setup
conventions.
next prev parent reply other threads:[~2015-04-13 7:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 11:43 Sneak peek of the upcoming Git for Windows 2.x Johannes Schindelin
2015-04-11 8:37 ` rupert thurner
2015-04-12 17:51 ` Johannes Schindelin
2015-04-13 7:54 ` Konstantin Khomoutov [this message]
2015-04-13 8:32 ` Tay Ray Chuan
2015-04-15 7:17 ` Vitaly
2015-04-15 9:46 ` Johannes Schindelin
2015-04-15 12:22 ` Vitaly
2015-04-29 15:23 ` rupert thurner
2015-04-29 15:40 ` Johannes Schindelin
2015-04-29 22:12 ` rupert thurner
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=20150413105416.8a2d12b530344a61f5ecb0f1@domain007.com \
--to=flatworm@users.sourceforge.net \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=msysgit@googlegroups.com \
--cc=rupert.thurner@gmail.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 NNTP newsgroup(s).