From: Christian Stimming <stimming@tuhh.de>
To: "Stephan Beyer" <s-beyer@gmx.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitk: Update German translation
Date: Wed, 7 May 2008 22:56:50 +0200 [thread overview]
Message-ID: <200805072256.50520.stimming@tuhh.de> (raw)
In-Reply-To: <20080503012419.327120@gmx.net>
Hi Stephan,
thanks for your feedback. I won't have time to answer this in detail until end
of next week. I'll just highlight a few things:
* Translation "commit" - "Version": Indeed this depends on the target
audience. Those who prefer the english terms IMHO are by definition no longer
the target audience. That's why I prefer this German word in the translation.
By the way, I strongly suggest reading the German TortoiseSVN documentation -
IMHO they've created a really good translation.
Am Samstag, 3. Mai 2008 03:24 schrieb Stephan Beyer:
> > In fact this word is used as the part of a full sentence
> > (which in itself is very bad i18n style, but that's another discussion),
> > and the sentence reads "Suche nächste/vorige Version enthaltend:".
>
> My mistake was that I began reading at "Version"... ;)
>
> > The sentence is already quite "holprig"
>
> The original
> "Find next/prev commit _containing:_ [insert]"
> should be translated to
> "Suche nächste/vorige Version, die [insert] enthält."
> But this is beyond the used techniques for software translation ;-)
Yes. But maybe even without GUI modifications this can be translated in a
better way. Eventually, I would expect something like this:
Suchen: Nächste / vorige Fundstelle mit Kriterium 'Enthält Zeichenkette':
[insert]
IMHO this shouldn't be one single sentence which is what the current english
GUI tries to mimic. Instead, this should be something with a heading and a
choicebox for the criteria and appropriate labels for those. Maybe we can
come up with a translation that already does this - the above sentence was a
quick thought but there are surely better ways to do this.
> > > > msgid "Cherry-pick this commit"
> > > > msgstr "Diese Version pflücken"
>
> > In other words: Git invented a new word here anyway.
>
> No, "cherry picking" is a commonly used term.
>
> I wonder what a commonly used German phrase with a similar meaning is...
> Something like "sich die Rosine(n) herauspicken"? (Is this a common
> phrase?) But a translation to "Diese Rosine herauspicken" is also
> confusing. ("Warum ist dieser Commit eine Rosine?
> Was passiert, wenn ich sie herauspicke?
> Ist er dann weg?")
Good point. We shouldn't come up with "Rosinen" here. Maybe "herauspicken",
but then "pflücken" can work as well. Branches are called "Zweige", so it's
not too far-fetched to have an action for "etwas von einem Zweig pflücken".
> Btw, 'man git-cherry-pick' says
> "Apply the change introduced by an existing commit".
> So why not take this and use
> "Durch diese Version eingeführte Änderungen übernehmen" or
> "Durch diese Version eingeführte Änderungen anwenden"?
This is indeed a case where a better translation can still be found. However,
all of "kopieren, übernehmen, anwenden" IMHO sound too similar to actions
that already appear here or there in the version control GUI. Cherry-picking
is a specialized action and should thus get a specialized German word.
Regards,
Christian
next prev parent reply other threads:[~2008-05-07 20:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 19:42 [PATCH] gitk: Update German translation Christian Stimming
2008-05-01 21:10 ` Stephan Beyer
2008-05-02 19:23 ` Christian Stimming
2008-05-03 1:24 ` Stephan Beyer
2008-05-07 20:56 ` Christian Stimming [this message]
2008-05-15 16:20 ` Stephan Beyer
2008-05-24 20:48 ` Christian Stimming
2008-05-25 21:57 ` Stephan Beyer
2008-05-02 19:36 ` [PATCH] gitk: German translation again updated Christian Stimming
2008-05-02 11:49 ` [PATCH] gitk: Update German translation Paul Mackerras
2008-05-02 18:33 ` Christian Stimming
2008-05-03 7:53 ` Paul Mackerras
2008-05-03 8:03 ` Christian Stimming
2008-05-02 12:56 ` Paul Mackerras
2008-05-02 18:30 ` Christian Stimming
-- strict thread matches above, loose matches on Subject: below --
2016-02-12 18:40 [PATCH] gitk: update " Ralf Thielow
2016-02-12 18:56 ` Stefan Beller
2016-02-12 19:17 ` Ralf Thielow
2016-03-19 6:56 ` Paul Mackerras
2010-01-27 19:30 [PATCH] gitk: Update " Christian Stimming
2009-09-25 20:41 Christian Stimming
2009-05-12 20:20 Christian Stimming
2008-01-09 21:24 Christian Stimming
2008-01-15 11:54 ` Paul Mackerras
2008-01-15 12:49 ` Christian Stimming
2008-01-08 20:56 Christian Stimming
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=200805072256.50520.stimming@tuhh.de \
--to=stimming@tuhh.de \
--cc=git@vger.kernel.org \
--cc=s-beyer@gmx.net \
/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).