From: "Jan Krüger" <jk@jk.gs>
To: Thomas Rast <trast@student.ethz.ch>
Cc: avarab@gmail.com, git@vger.kernel.org,
Junio C Hamano <gitster@pobox.com>, Sam Reed <sam@reedyboy.net>,
Jeff King <peff@peff.net>
Subject: Re: [PATCH 1/2] po/de.po: add German translation
Date: Mon, 6 Sep 2010 18:09:35 +0200 [thread overview]
Message-ID: <20100906180935.4881dbb8@jk.gs> (raw)
In-Reply-To: <201009061741.27840.trast@student.ethz.ch>
Hi Thomas,
thanks for your comments so far. I pretty much agree with all of your
thoughts, so below I'm going to focus on those where I have something
to say in addition to that.
> > +#, c-format
> > +msgid "nothing added to commit but untracked files present%s\n"
> > +msgstr "keine Änderungen für den Commit vorgemerkt, aber
> > unberücksichtigte Dateien vorhanden\n"
>
> Loses the %s (which is used for advice).
That's me being careless. I will add an additional check to my workflow
to prevent format string bugs from happening again.
> [way earlier, and same goes for "by us" -> "hier" [lit. "here"]]
> > +msgid "deleted by them:"
> > +msgstr "dort gelöscht:"
> [lit. "deleted there"]
> > +
> [...]
> > +#, c-format
> > +msgid "behind %d] "
> > +msgstr "nur dort %d] "
> [lit. "only there"]
>
> This had me pause for a moment. The concepts of "[merge side] theirs"
> and "behind" are quite different; is it a good idea to translate these
> to the same?
>
> Especially so since later on you translate
>
> > +#, c-format
> > +msgid "path '%s' does not have our version"
> > +msgstr "Pfad '%s' hat keine Version 'von uns' im Index"
> [lit. "... 'of us' ..."]
>
> I do agree that the best I can come up with, "von den anderen
> gelöscht", would be quite awkward.
This was one of the more difficult things to decide on while
translating. Both are difficult to translate into something that
"flows", and individually I think both work okay the way I decided to
translate them (but see the next paragraph), but of course it would be
preferrable to distinguish the two different concepts better. I'll be
grateful for any suggestions.
The real problem, I think, is that "ours" and "theirs" are misnomers in
the original terminology. A good translation, I think, will not try
to translate them literally... that would get us from misnomers to
misnomers that also don't lend themselves well to the target
language. :) The question, then, is how to rephrase the messages
elegantly without removing them all too far from the original idea.
This would be easier if "ours" and "theirs" always referred to the same
concept... but they mean different things for merge vs. rebase, for
instance.
> [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...
Good catch. I think I might go with something a bit more verbose.
Perhaps something along the lines of "nicht Teil eines definierten
Branches", though obviously that exact phrase is a bit clunky...
-Jan
next prev parent reply other threads:[~2010-09-06 16:09 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 [this message]
2010-09-06 17:06 ` Ævar Arnfjörð Bjarmason
2010-09-06 16:24 ` Jens Lehmann
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=20100906180935.4881dbb8@jk.gs \
--to=jk@jk.gs \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 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).