From: David Kastrup <dak@gnu•org>
To: Thomas Rast <tr@thomasrast•ch>
Cc: Ralf Thielow <ralf.thielow@gmail•com>,
jk@jk•gs, stimming@tuhh•de, git@vger•kernel.org,
worldhello.net@gmail•com
Subject: Re: [PATCH] l10n: de.po: translate 27 new messages
Date: Sat, 08 Feb 2014 20:01:48 +0100 [thread overview]
Message-ID: <874n49ctsz.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <877g95motv.fsf@thomasrast.ch> (Thomas Rast's message of "Sat, 08 Feb 2014 19:39:08 +0100")
Thomas Rast <tr@thomasrast•ch> writes:
> I see you are defining new glossary terms:
>
> shallow unvollständig
> grafted gesondert eingehängt
>
> I guess the first one is reasonable if we don't call anything
> "incomplete"? (I don't think we do, just checking.)
"oberflächlich" seems better: a shallow clone is not "incomplete": the
cloning process ran to completion.
> I don't really like 'gesondert eingehängt', how about 'transplantiert'
> instead?
I suggest using the actual translation here as it is perfectly fitting
for both literal and figurative meaning: "aufgepfropft".
--
David Kastrup
next prev parent reply other threads:[~2014-02-08 19:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 21:10 [PATCH] l10n: de.po: translate 27 new messages Ralf Thielow
2014-01-24 22:29 ` Jiang Xin
2014-01-27 6:18 ` [PATCH v2] " Ralf Thielow
2014-02-05 6:19 ` [PATCH v3] l10n: de.po: translate 28 " Ralf Thielow
2014-02-08 19:40 ` [PATCH v4] " Ralf Thielow
2014-02-08 20:11 ` David Kastrup
2014-02-08 20:36 ` Ralf Thielow
2014-02-08 20:41 ` [PATCH v5] " Ralf Thielow
2014-02-08 18:39 ` [PATCH] l10n: de.po: translate 27 " Thomas Rast
2014-02-08 19:01 ` David Kastrup [this message]
2014-02-08 19:07 ` Thomas Rast
2014-02-08 19:22 ` David Kastrup
2014-02-08 19:46 ` Ralf Thielow
2014-02-08 19:59 ` David Kastrup
2014-02-08 20:20 ` Ralf Thielow
2014-02-08 21:29 ` [PATCH] l10n: de.po: correct message when hiding commits by craft Ralf Thielow
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=874n49ctsz.fsf@fencepost.gnu.org \
--to=dak@gnu$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=jk@jk$(echo .)gs \
--cc=ralf.thielow@gmail$(echo .)com \
--cc=stimming@tuhh$(echo .)de \
--cc=tr@thomasrast$(echo .)ch \
--cc=worldhello.net@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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