Git development
 help / color / mirror / Atom feed
From: Christian Stimming <stimming@tuhh.de>
To: Ralf Thielow <ralf.thielow@gmail.com>
Cc: trast@student.ethz.ch, jk@jk.gs, worldhello.net@gmail.com,
	git@vger.kernel.org
Subject: Re: [RFC] l10n: de.po: translate 29 new messages
Date: Wed, 04 Jul 2012 22:14:03 +0200	[thread overview]
Message-ID: <1819393.sAuVItIfZO@cs-pc> (raw)
In-Reply-To: <CAN0XMO+R3+JiuHSZ0O46py2WbXVh8D2Z+f7t_xofsN6ZrFwnQQ@mail.gmail.com>

Hi Ralf,

Am Mittwoch, 4. Juli 2012, 09:20:40 schrieb Ralf Thielow:
> >> -msgstr "Du befindest dich auf keinem Zweig."
> >> +msgstr "Du bist gerade beim Neuaufbau."
> > 
> > Is "rebase" = "Neuaufbau"? My last thought on this wording was "rebase"
> > = "Umpflanzen".
> 
> According to the current state of the glossary on GitHub, "rebase" as a
> verb is translated as "neu aufbauen". There are already translations using
> this. For example:
> 
> #: builtin/remote.c:998
> #, c-format
> msgid "rebases onto remote %s"
> msgstr "baut neu auf externen Zweig %s auf"
> 
> In this translation, "rebase" is used as a noun for the very first time.
> So, I simply translate it with "Neuaufbau". In fact, we can use different
> translations for verbs and nouns. Not really sure whether we should do this
> for "rebase".
> 
> Using "Umpflanzen" for "rebase" as a noun, would result in
> msgstr "Du bist gerade beim Umplanzen."
> Using "Umplanzen" was a verb, would result in
> msgstr "Du planzt gerade um."
> 
> For me, "Umpflanzen" sounds a bit like "working with plants
> in the garden". I do not have a strong opinion on this, though.

That's true. The wording goes very far into gardening, which is an argument 
against it. An argument for it is that it consequently re-uses the tree and 
branch metaphor, which is indeed also related to gardening.

I thought "neu aufbauen" is probably useful in the context of the gc or fsck 
command... no strong opinion on this, too, though.

Thanks for the reminder of the glossary - indeed I forgot to check that first.

Regards,

Christian

      parent reply	other threads:[~2012-07-04 20:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03 17:04 [RFC] l10n: de.po: translate 29 new messages Ralf Thielow
2012-07-03 20:03 ` Christian Stimming
2012-07-04  7:20   ` Ralf Thielow
2012-07-04  8:22     ` Andreas Schwab
2012-07-05 18:16       ` Ralf Thielow
2012-07-06 18:20         ` Michael J Gruber
2012-07-06 18:58           ` Ralf Thielow
2012-07-06 19:18             ` Peter Baumann
2012-07-06 20:12               ` Ralf Thielow
2012-07-04 20:14     ` Christian Stimming [this message]

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=1819393.sAuVItIfZO@cs-pc \
    --to=stimming@tuhh.de \
    --cc=git@vger.kernel.org \
    --cc=jk@jk.gs \
    --cc=ralf.thielow@gmail.com \
    --cc=trast@student.ethz.ch \
    --cc=worldhello.net@gmail.com \
    /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