Git development
 help / color / mirror / Atom feed
From: Sascha Cunz <sascha-ml@babbelbox.org>
To: Ralf Thielow <ralf.thielow@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
	"Thomas Rast" <trast@student.ethz.ch>, "Jan Krüger" <jk@jk.gs>,
	"Christian Stimming" <stimming@tuhh.de>
Subject: Re: Message from 'git-rebase'; German translation
Date: Sun, 23 Sep 2012 17:41:55 +0200	[thread overview]
Message-ID: <224751243.JXpXFWu6vV@blacky> (raw)
In-Reply-To: <CAN0XMO+Dd9S7j9Ujudcy+O3GwwBX1CvRPQTYWxymmEu=2bg7ww@mail.gmail.com>

Am Sonntag, 23. September 2012, 17:04:15 schrieb Ralf Thielow:
> On Sat, Sep 22, 2012 at 11:57 PM, Sascha Cunz <sascha-ml@babbelbox.org> 
wrote:
> > As I know how hard translations can be, esp. with that much technical
> > terms
> > inside, I'm usually expecting _not_ to yield the same result when
> > translating a software's translation back to English.
> 
> Yeah, I think the goal is not making translations which are looking nearly
> the same when somebody translates them back to English in the first place.

Exactly. The meaning is more important then the exact wording. Please consider 
this:

	Es wurden Neuaufbau- / Zusammenführungs-Informationen gefunden.
	Falls ein Neuaufbau bereits im Gange ist, versuche bitte:
		git rebase (--continue | --abort | --skip)
	Sollte dies nicht der Fall sein, können die Informationen durch
		rm -fr "$(GIT_DIR)/rebase-merge"
	entfernt werden. Es wird angehalten, falls etwas Schützenswertes
	gefunden werden sollte.

It sounds way cleaner (to me at least) and transports all of the meaning. Esp. 
for  the last sentence, it's very hard to find something in German that 
doesn't sound 'destructive'.

Btw: In the past I've seen quite a few topics on translation on this list - is 
this at all the right place for that kind of discussion?

Sascha

> > However, git-rebase just threw these two sentences at me (And though i
> > know
> > their meaning, i couldn't get the meaning from the message, it gave). Both
> > are in context of starting a rebase while one is already in progress.
> > 
> > first is:
> > 
> > Original:
> > ... and I wonder if you are in the middle of another rebase.
> > 
> > German git translation:
> > ... und es wäre verwunderlich, wenn ein Neuaufbau bereits im Gange ist.
> > 
> > And a re-translation back to English from my understanding as native
> > German
> > speaker:
> > ... and it would be astonishing (=i'd be surprised), if a rebase was
> > already in progress.
> 
> We try to avoid translating terms like "I wonder if.." and similar as
> "ich wundere mich", because it's very unusual in German messages
> of computer programs. Translators should have the freedom to reword
> terms a bit to make a more optimal translation, but the meaning must
> not be lost, and I can't say that this is the case.
> Translate the term "in the middle of"  word-by-word would result in
> "in der Mitte eines", which can be interpreted as a place somewhere
> or that an action is in progress. To avoid a possible confusion, we
> decided to translate this term as "im Gange sein" ("be in progress") in
> the whole translation. I also think that "in der Mitte einer Zusammenführung
> sein" doesn't sound really good. It tends to mean a place, not an action.
> > And second:
> > 
> > Original:
> > I am stopping in case you still have something valuable there.
> > 
> > German git translation:
> > Es wird angehalten, falls bereits etwas Nützliches vorhanden ist.
> > 
> > I wanted to point out that "etwas Nützliches" is more "something useful"
> > that "something valuable". But the more I thought about it, the more it
> > started to
> I've been thinking about possible different translations, and the only
> one I have in
> mind is "wertvoll". But translating "valuable" as "wertvoll" ("bereits
> etwas Wertvolles
> vorhanden") sounds a bit like "we've found a treasure", instead of
> something which
> has a value in the meaning of content. I think having a translation
> which is more
> like "useful" than "valuable" does also hit the point of the message,
> doesn't it?
> 
> > confuse me (even the original text) - and now I feel like I don't
> > understand the meaning of the last sentence at all; neither in English
> > nor in the German translation:
> > After removing the directory with all rebase-information inside it, WHERE
> > should something valuable still be left over? Is it referring to my
> > working
> > tree?
> 
> Yeah, I think it means the working tree and/or the index which would make
> sense.
> 
> Ralf
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2012-09-23 15:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-22 21:57 Message from 'git-rebase'; German translation Sascha Cunz
2012-09-23 15:04 ` Ralf Thielow
2012-09-23 15:36   ` knittl
2012-09-23 15:52     ` Sascha Cunz
2012-09-23 15:41   ` Sascha Cunz [this message]
2012-09-23 17:34     ` Ralf Thielow
2012-09-23 17:57       ` Sascha Cunz
2012-09-23 17:29   ` Jan Engelhardt
2012-09-24 12:15   ` Greg Troxel
2012-09-24 19:45   ` Thomas Hochstein
2012-09-24  7:33 ` 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=224751243.JXpXFWu6vV@blacky \
    --to=sascha-ml@babbelbox.org \
    --cc=git@vger.kernel.org \
    --cc=jk@jk.gs \
    --cc=ralf.thielow@gmail.com \
    --cc=stimming@tuhh.de \
    --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