All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Lehmann <Jens.Lehmann@web.de>
To: Thomas Rast <trast@student.ethz.ch>
Cc: avarab@gmail.com, git@vger.kernel.org,
	"Junio C Hamano" <gitster@pobox.com>, "Jan Krüger" <jk@jk.gs>,
	"Sam Reed" <sam@reedyboy.net>, "Jeff King" <peff@peff.net>
Subject: Re: [PATCH 1/2] po/de.po: add German translation
Date: Mon, 06 Sep 2010 18:24:58 +0200	[thread overview]
Message-ID: <4C8515DA.9010109@web.de> (raw)
In-Reply-To: <201009061741.27840.trast@student.ethz.ch>

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.

But however, translations should be consistent between gitk/git-gui
and the command line, no? E.g. tracking branch is "Übernahmezweig"
(whatever that means) there and "verfolgter Branch" here ... :-/


> [probably out of order, I found it while compiling the glossary]
>> +msgid "detached HEAD"
>> +msgstr "von HEAD abgetrennt"
> 
> That's not strictly speaking true; HEAD always points to a commit
> except in an unborn branch, and in any case (this is from commit.c)
> points to a commit after this message is output.  You could try
> "abgetrennter HEAD", "entkoppelter HEAD" or so...

Yup, maybe "abgelöster HEAD" or "loser HEAD" (even if the latter may
sound funny when parsed in English ;-)

  parent reply	other threads:[~2010-09-06 16:25 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 [this message]
2010-09-06 19:58       ` Tilo Schwarz
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=4C8515DA.9010109@web.de \
    --to=jens.lehmann@web.de \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jk@jk.gs \
    --cc=peff@peff.net \
    --cc=sam@reedyboy.net \
    --cc=trast@student.ethz.ch \
    /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.