From: Michael J Gruber <git@drmicha.warpmail.net>
To: Ralf Thielow <ralf.thielow@gmail.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Christian Stimming <stimming@tuhh.de>,
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: Fri, 06 Jul 2012 20:20:32 +0200 [thread overview]
Message-ID: <4FF72C70.1010202@drmicha.warpmail.net> (raw)
In-Reply-To: <CAN0XMOJF8+iJqyiqvBxEHOVGMB17rPnO9Pnu29LY1fMDBopKGw@mail.gmail.com>
Ralf Thielow venit, vidit, dixit 05.07.2012 20:16:
>>>> Is "rebase" = "Neuaufbau"? My last thought on this wording was "rebase" =
>>>> "Umpflanzen".
>>
>> "Basisumbau"?
>>
>
> I have added both suggestions to the glossary that they don't get lost when
> we discuss about non-optimal and/or missing parts within the glossary.
Not the base is being reconstructed, but what's on top of it. So,
"Basiswechsel" would be more appropriate.
But: "Umpflanzen" is really a great term which stays within the context
of trees, roots and branches. Strictly speaking, "Umpflanzen" refers to
something you do at the root level. The corresponding action for
branches would be "Umpfropfen". I think that also conveys the effort
that is sometimes necessary ;)
Michael
next prev parent reply other threads:[~2012-07-06 18:20 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 [this message]
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
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=4FF72C70.1010202@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=jk@jk.gs \
--cc=ralf.thielow@gmail.com \
--cc=schwab@linux-m68k.org \
--cc=stimming@tuhh.de \
--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;
as well as URLs for NNTP newsgroup(s).