From: "Tilo Schwarz" <tilo@tilo-schwarz.de>
To: git@vger.kernel.org
Subject: Re: [PATCH 1/2] po/de.po: add German translation
Date: Mon, 06 Sep 2010 21:58:44 +0200 [thread overview]
Message-ID: <op.vimm36yma8ed4e@dellschleppa.fritz.box> (raw)
In-Reply-To: <4C8515DA.9010109@web.de>
On Mon, 06 Sep 2010 18:24:58 +0200, Jens Lehmann <Jens.Lehmann@web.de>
wrote:
> Am 06.09.2010 17:41, schrieb Thomas Rast:
>> I already like the translation way better than the one that
>> gitk/git-gui have, because it doesn't try so hard to translate *every*
>> term.
>
> Full Ack, I can't find my way through git-gui or gitk when I forget
> to start them with "LC_ALL=C" (And when you use git mainly via these
> guis, you will have to learn /every/ git command again when you
> start using the command line). IMHO terms that have a special in git
> should not be translated, so I would even vote for leaving terms like
> "fetch", "fast-forward" and maybe even "tracking-branch" as they are.
Full Ack again! Many german IT people use many english special terms daily
(like compiler, linker, terminal, interrupt). Normally the translation of
the special terms generates confusion all over the place. That's why I
also start git-gui or gitk only in english (and the manpages too, by the
way).
Thus the git special terms should not be translated, even though I might
be helpful to have a glossary which explains, what a "fast-forward" is.
--
Regards,
Tilo
next prev parent reply other threads:[~2010-09-06 19:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 18:22 [GIT PULL] New ab/i18n series and builtin fixes Ævar Arnfjörð Bjarmason
2010-09-03 23:24 ` [PATCH 0/3] ab/i18n: README and GETTEXT_POISON support Ævar Arnfjörð Bjarmason
2010-09-03 23:24 ` [PATCH 1/3] gettext: Add po/README file documenting Git's gettext Ævar Arnfjörð Bjarmason
2010-09-03 23:24 ` [PATCH 2/3] gettext: Add GETTEXT_POISON=YesPlease Makefile parameter Ævar Arnfjörð Bjarmason
2010-09-03 23:24 ` [PATCH 3/3] gettext: add NO_GETTEXT_POISON prerequisite to tests Ævar Arnfjörð Bjarmason
2010-09-03 23:41 ` Ævar Arnfjörð Bjarmason
2010-09-04 0:49 ` [PATCH 0/2] [PULL] ab/i18n-gettextize & translations avarab
2010-09-04 0:49 ` [PATCH 1/2] po/de.po: add German translation avarab
2010-09-06 15:41 ` Thomas Rast
2010-09-06 16:09 ` Jan Krüger
2010-09-06 17:06 ` Ævar Arnfjörð Bjarmason
2010-09-06 16:24 ` Jens Lehmann
2010-09-06 19:58 ` Tilo Schwarz [this message]
2010-09-06 17:15 ` Ævar Arnfjörð Bjarmason
2010-09-04 0:49 ` [PATCH 2/2] po/en_GB.po: add British English Translation avarab
-- strict thread matches above, loose matches on Subject: below --
2010-09-15 7:33 [PATCH 1/2] po/de.po: add German translation Christian Stimming
2010-09-15 9:47 ` Thomas Rast
2010-09-15 11:51 ` Michael J Gruber
2010-09-15 11:10 ` Michael J Gruber
2010-09-15 16:54 ` Andreas Schwab
2010-09-15 11:44 ` Thomas Hochstein
2010-09-16 10:57 ` Jan Krüger
2010-09-16 11:09 ` Ævar Arnfjörð Bjarmason
2010-09-16 11:29 ` Jens Lehmann
2010-09-16 11:51 ` Ævar Arnfjörð Bjarmason
2010-09-16 14:52 ` Junio C Hamano
2010-09-16 15:05 ` Jens Lehmann
2010-09-16 11:51 ` Michael J Gruber
2010-09-16 16:48 ` Jan Krüger
2010-09-17 7:23 ` Michael J Gruber
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=op.vimm36yma8ed4e@dellschleppa.fritz.box \
--to=tilo@tilo-schwarz.de \
--cc=git@vger.kernel.org \
/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).