From: Thomas Rast <tr@thomasrast.ch>
To: Ralf Thielow <ralf.thielow@gmail.com>
Cc: 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 19:39:08 +0100 [thread overview]
Message-ID: <877g95motv.fsf@thomasrast.ch> (raw)
In-Reply-To: <1390511452-6553-1-git-send-email-ralf.thielow@gmail.com> (Ralf Thielow's message of "Thu, 23 Jan 2014 22:10:52 +0100")
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.)
I don't really like 'gesondert eingehängt', how about 'transplantiert'
instead? Or just say graft=Graft and use 'mit Grafts' or some similar
workaround, since it is a highly specialized term.
Ralf Thielow <ralf.thielow@gmail.com> writes:
> #: diff.c:113
> #, c-format
> @@ -975,21 +975,23 @@ msgid ""
> "There is nothing to exclude from by :(exclude) patterns.\n"
> "Perhaps you forgot to add either ':/' or '.' ?"
> msgstr ""
> +"Es gibt nichts, was durch :(exclude) Muster ausgeschlossen wird.\n"
> +"Vielleicht haben Sie vergessen entweder ':/' oder '.' hinzuzufügen?"
Doesn't sound right -- the original seems to describe the situation
where you are using :(exclude) without any non-excluded paths, whereas
the German first sentence sounds like you are using :(exclude) when it
doesn't match any paths.
Perhaps it works if translated very liberally:
":(exclude) Muster, aber keine anderen Pfadspezifikationen angegeben.\n"
"Vielleicht haben Sie vergessen entweder ':/' oder '.' hinzuzufügen?"
> #: remote.c:753
> -#, fuzzy, c-format
> +#, c-format
> msgid "Cannot fetch both %s and %s to %s"
> -msgstr "Kann keine Commit-Beschreibung für %s bekommen"
> +msgstr "Kann 'fetch' nicht für %s und %s nach %s ausführen."
[...]
> #: remote.c:761
> #, c-format
> msgid "%s tracks both %s and %s"
> -msgstr ""
> +msgstr "%s folgt %s und %s"
In both of these the key point is "both". Perhaps use "sowohl... als
auch".
> #: wt-status.c:275
> -#, fuzzy
> msgid "new file"
> -msgstr "neue Datei: %s"
> +msgstr "neue Datei:"
[...]
> #: wt-status.c:285
> -#, fuzzy
> msgid "typechange"
> -msgstr "Typänderung: %s"
> +msgstr "Typänderung:"
>
> #: wt-status.c:287
> -#, fuzzy
> msgid "unknown"
> -msgstr "unbekannt: %s"
> +msgstr "unbekannt:"
Do we still need the trailing colon?
--
Thomas Rast
tr@thomasrast.ch
next prev parent reply other threads:[~2014-02-08 18:39 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 ` Thomas Rast [this message]
2014-02-08 19:01 ` [PATCH] l10n: de.po: translate 27 " David Kastrup
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=877g95motv.fsf@thomasrast.ch \
--to=tr@thomasrast.ch \
--cc=git@vger.kernel.org \
--cc=jk@jk.gs \
--cc=ralf.thielow@gmail.com \
--cc=stimming@tuhh.de \
--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).