From: "Matthias Rüster" <matthias.ruester@gmail.com>
To: Ralf Thielow <ralf.thielow@gmail.com>, git@vger.kernel.org
Cc: tr@thomasrast.ch, jk@jk.gs, stimming@tuhh.de,
phillip.szelat@gmail.com, magnus.goerlitz@googlemail.com
Subject: Re: [PATCH] l10n: de.po: translate 260 new messages
Date: Mon, 3 Oct 2016 00:23:46 +0200 [thread overview]
Message-ID: <0de216d5-8a47-bd1d-b9d6-8346a62bc489@gmail.com> (raw)
In-Reply-To: <20161002165946.19656-1-ralf.thielow@gmail.com>
Hi Ralf,
many thanks for your translations!
I reviewed them and only have some minor comments:
> #: bisect.c:967
> -#, fuzzy, c-format
> +#, c-format
> msgid "%s was both %s and %s\n"
> -msgstr "%s folgt sowohl %s als auch %s"
> +msgstr "%s war %s als auch %s\n"
Maybe keeping the "sowohl" here:
"%s war sowohl %s als auch %s"
> #: setup.c:989
> #, c-format
> msgid ""
> "Problem with core.sharedRepository filemode value (0%.3o).\n"
> "The owner of files must always have read and write permissions."
> msgstr ""
> +"Problem mit Wert für Dateimodus (0%.3o) von core.sharedRepository.\n"
> +"Der Besitzer der Dateien muss immer Lese- und Schreibberechtigung haben."
I would translate "read and write permissions" to:
Lese- und Schreibrechte
> #: builtin/fsck.c:606
> -#, fuzzy
> msgid "show verbose names for reachable objects"
> -msgstr "unerreichbare Objekte anzeigen"
> +msgstr "erweiterten Namen für erreichbare Objekte anzeigen"
Maybe "ausführlich" is the better choice for "verbose" here?
"ausführliche Namen ..."
> #: builtin/merge.c:960
> #, c-format
> msgid "Bad value '%s' in environment '%s'"
> -msgstr ""
> +msgstr "Fehlerhafter Wert '%s' in Umgebungsvariable '%s'"
I do not know the context but I would translate it to:
"... Umgebung '%s'"
> #: builtin/push.c:546
> -#, fuzzy
> msgid "option to transmit"
> -msgstr "nichts zu committen\n"
> +msgstr "Optionen übertragen"
Is the plural form correct in this context?
Maybe "Option übertragen" ?
> #: git-rebase--interactive.sh:147
> msgid ""
> "\n"
> "Commands:\n"
> " p, pick = use commit\n"
> " r, reword = use commit, but edit the commit message\n"
> " e, edit = use commit, but stop for amending\n"
> " s, squash = use commit, but meld into previous commit\n"
> " f, fixup = like \"squash\", but discard this commit's log message\n"
> " x, exec = run command (the rest of the line) using shell\n"
> " d, drop = remove commit\n"
> "\n"
> "These lines can be re-ordered; they are executed from top to bottom.\n"
> msgstr ""
> +"\n"
> +"Befehle:\n"
> +" p, pick = Commit verwenden\n"
> +" r, reword = Commit verwenden, aber Commit-Beschreibung bearbeiten\n"
> +" e, edit = Commit verwenden, aber zum Nachbessern anhalten\n"
> +" s, squash = Commit verwenden, aber mit vorherigem Commit vereinen\n"
> +" f, fixup = wie \"squash\", aber die Log-Nachricht des Commits verwerden\n"
> +" x, exec = Befehl (Rest der Zeile) mittels Shell ausführen\n"
> +" d, drop = Commit entfernen\n"
> +"\n"
> +"Diese Zeilen können umsortiert werden; Sie werden von oben nach unten\n"
> +"ausgeführt.\n"
In my opinion fixup needs a more detailed description here.
Something like:
"fixup: wie \"squash\", aber die Commit-Beschreibung vom Vorgänger
verwenden\n".
or:
"fixup: wie \"squash\", aber diese Commit-Beschreibung verwerfen\n".
Everything else looks great!
Kind regards,
Matthias
next prev parent reply other threads:[~2016-10-02 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 16:59 [PATCH] l10n: de.po: translate 260 new messages Ralf Thielow
2016-10-02 22:23 ` Matthias Rüster [this message]
2016-10-04 17:05 ` Ralf Thielow
2016-10-07 16:45 ` [PATCH v2] " 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=0de216d5-8a47-bd1d-b9d6-8346a62bc489@gmail.com \
--to=matthias.ruester@gmail.com \
--cc=git@vger.kernel.org \
--cc=jk@jk.gs \
--cc=magnus.goerlitz@googlemail.com \
--cc=phillip.szelat@gmail.com \
--cc=ralf.thielow@gmail.com \
--cc=stimming@tuhh.de \
--cc=tr@thomasrast.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;
as well as URLs for NNTP newsgroup(s).