From: Jeff King <peff@peff.net>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>, git@vger.kernel.org
Subject: Re: Enhancement Request: "locale" git option
Date: Thu, 4 Dec 2014 04:55:58 -0500 [thread overview]
Message-ID: <20141204095557.GE27455@peff.net> (raw)
In-Reply-To: <54801B50.4080500@web.de>
On Thu, Dec 04, 2014 at 09:29:04AM +0100, Torsten Bögershausen wrote:
> How about
> alias git='LANGUAGE=de_DE.UTF-8 git'
> in your ~/.profile ?
> (Of course you need to change de to the language you want )
Besides being awkward in scripts (which will not respect the alias and
use a different language!), that variable will also be inherited by
programs git spawns. So the editor, for example, may end up in the wrong
language.
I think respecting core.locale would make sense (probably the change
would go into git_setup_gettext(), but you may have to fight with the
setup code over looking at config so early in the process).
However, I think the original question is not one of localizing git, but
rather of having it _not_ localized (avoiding the German translations).
There is a hack you can do that for that, which is to set
GIT_TEXTDOMAINDIR to something nonsensical (like "/"), which will mean
git cannot find the .po files, and just uses the builtin messages.
-Peff
next prev parent reply other threads:[~2014-12-04 9:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 7:32 Enhancement Request: "locale" git option Ulrich Windl
2014-12-04 8:29 ` Torsten Bögershausen
2014-12-04 9:55 ` Jeff King [this message]
2014-12-04 15:49 ` Ævar Arnfjörð Bjarmason
2014-12-04 16:12 ` Michael J Gruber
2014-12-04 16:53 ` Andreas Schwab
2014-12-04 17:21 ` Ævar Arnfjörð Bjarmason
2014-12-04 20:55 ` Jeff King
2014-12-05 15:45 ` Torsten Bögershausen
2014-12-06 19:28 ` Ralf Thielow
2014-12-08 7:50 ` Antw: " Ulrich Windl
2014-12-08 9:48 ` David Kastrup
2014-12-04 15:51 ` Ulrich Windl
2014-12-04 19:02 ` Ralf Thielow
2014-12-08 7:20 ` Antw: " Ulrich Windl
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=20141204095557.GE27455@peff.net \
--to=peff@peff.net \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=git@vger.kernel.org \
--cc=tboegi@web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.