All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: wmpalmer@gmail.com
Cc: "Jan Hudec" <bulb@ucw.cz>, "Thomas Rast" <trast@student.ethz.ch>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Jakub Narebski" <jnareb@gmail.com>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Has anyone looked at Gettext support for Git itself?
Date: Tue, 18 May 2010 09:51:09 +0200	[thread overview]
Message-ID: <4BF246ED.3040706@drmicha.warpmail.net> (raw)
In-Reply-To: <1274122619.4780.36.camel@dreddbeard>

Will Palmer venit, vidit, dixit 17.05.2010 20:56:
> On Mon, 2010-05-17 at 19:59 +0200, Jan Hudec wrote:
>> On Mon, May 17, 2010 at 17:12:22 +0200, Thomas Rast wrote:
>>> Ævar Arnfjörð Bjarmason wrote:
>>>> On Mon, May 17, 2010 at 14:32, Thomas Rast <trast@student.ethz.ch> wrote:
>>>>> Ævar Arnfjörð Bjarmason wrote:
>>
>> There are cases though, where somebody calls *porcelain* commands in their
>> scripts and there they occasionally may need this LC_ALL=C thing. I suppose
>> having a global option to turn off localization might be useful for such
>> users.
> 
> Would it be that bad to define something like GIT_PLUMBING=1 to mean "I
> am using this as plumbing"? It seems that this is the way things are
> headed with --porcelain, even if the name is backwards.
> 
> I agree that error messages should be localised either way- if you're
> trying to parse an error message, something's always gone wrong.
> 
> Does anyone know how large of a non-english-speaking community git
> currently has? Would this effort include adding localised git command
> names or arguments?

Note that "non-english-speaking" here really means "requiring or badly
wanting translated git". There are many non-native speakers here, and
your following reasoning

> It may also be worth mentioning that a git "commit", for example,
> doesn't have anything (other than historical reasons) to do with the
> English word "commit". A git commit is a git commit, and perhaps such
> conceptual terms should best be left untranslated anyway. It would
> certainly make it easier to answer questions in #git if people continued
> to use the same terms everywhere. Just as a weak anecdotal argument,
> when someone uses the term "revision" in #git, there's generally a lack
> of understanding about what a "commit" is. "commit" means something very
> specific in git, and I would hesitate to try to translate that into
> another language as if it's just a synonym for "revision" or
> "checkpoint", or "transaction", etc

explains why many non-native speakers prefer an English git. When
confronted with the localised German git-gui for the first time, I
really did not understand the menu entries at all. And my German is
pretty good ;)

Michael

  reply	other threads:[~2010-05-18  7:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-15 22:10 Has anyone looked at Gettext support for Git itself? Ævar Arnfjörð Bjarmason
2010-05-16  0:03 ` Jakub Narebski
2010-05-16  1:12   ` Ævar Arnfjörð Bjarmason
2010-05-16  5:36     ` Dmitry Potapov
2010-05-16 13:12       ` Ævar Arnfjörð Bjarmason
2010-05-16 16:08     ` Jan Hudec
2010-05-16 17:37       ` Ævar Arnfjörð Bjarmason
2010-05-17 14:32         ` Thomas Rast
2010-05-17 14:53           ` Ævar Arnfjörð Bjarmason
2010-05-17 15:12             ` Thomas Rast
2010-05-17 17:59               ` Jan Hudec
2010-05-17 18:56                 ` Will Palmer
2010-05-18  7:51                   ` Michael J Gruber [this message]
2010-05-18  9:35                     ` Thomas Singer
2010-05-18 13:33                       ` Will Palmer
2010-05-22 11:01                         ` Jan Hudec
2010-05-19 15:43             ` demerphq
2010-05-16 16:53 ` Thomas Singer
2010-05-17 15:04 ` Marc Weber
2010-05-18  7:12 ` Peter Krefting

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=4BF246ED.3040706@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=avarab@gmail.com \
    --cc=bulb@ucw.cz \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=trast@student.ethz.ch \
    --cc=wmpalmer@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 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.