From: Thomas Rast <trast@inf.ethz.ch>
To: Ralf Thielow <ralf.thielow@gmail.com>
Cc: <jk@jk.gs>, <stimming@tuhh.de>, <git@vger.kernel.org>
Subject: Re: [PATCH] l10n: de.po: fix some minor issues
Date: Mon, 21 Jan 2013 20:21:58 +0100 [thread overview]
Message-ID: <87622ql4tl.fsf@pctrast.inf.ethz.ch> (raw)
In-Reply-To: <1358794945-4254-1-git-send-email-ralf.thielow@gmail.com> (Ralf Thielow's message of "Mon, 21 Jan 2013 20:02:25 +0100")
Ralf Thielow <ralf.thielow@gmail.com> writes:
> This fixes some minor issues and improves the
> German translation a bit. The following things
> were changed:
> - use complete sentences in option related messages
> - translate "use" consistently as "verwendet"
> - don't translate "make sense" as "macht Sinn"
>
> Signed-off-by: Ralf Thielow <ralf.thielow@gmail.com>
It would be easier on the reviewers if you could split out such
search&replace changes as s/benutzt/verwendet/ into a separate patch.
I'm not sure though which one would be more error-prone. As it stands,
it's very tiring to review because of the very similar s/// changes, and
I am unlikely to spot any other change or mistake in a message that
undergoes the substitution. With my proposal, I'd just skip reviewing
the s/// patch :-)
[No, don't change it for this patch; not worth the splitting effort.]
> #: builtin/checkout.c:964
> msgid "paths cannot be used with switching branches"
> -msgstr "Pfade können nicht mit dem Wechseln von Zweigen benutzt werden"
> +msgstr "Pfade können nicht mit dem Wechseln von Zweigen verwendet werden"
>
> #: builtin/checkout.c:967 builtin/checkout.c:971
> #, c-format
> msgid "'%s' cannot be used with switching branches"
> -msgstr "'%s' kann nicht mit dem Wechseln von Zweigen benutzt werden"
> +msgstr "'%s' kann nicht mit dem Wechseln von Zweigen verwendet werden"
Not new, but they sound a bit strange to me. Perhaps "kann nicht *beim*
Wechseln von Zweigen verwendet werden"?
> #: builtin/clone.c:734
> #, c-format
> @@ -3293,7 +3297,7 @@ msgstr "Abstand zwischen Spalten"
>
> #: builtin/column.c:51
> msgid "--command must be the first argument"
> -msgstr "Option --command muss zuerst angegeben werden"
> +msgstr "Die Option --command muss zuerst angegeben werden."
Not new either, but also took a second reading. Maybe "muss an erster
Stelle stehen"?
> #: builtin/describe.c:482
> msgid "--dirty is incompatible with committishes"
> -msgstr "--dirty ist inkompatibel mit Versionen"
> +msgstr "Die Option --dirty ist inkompatibel mit Versionen."
I think in this case it would sound nicer if you used the "Die Option
--dirty kann nicht mit Versionen verwendet werden" pattern instead of
the "inkompatibel" one.
> #: builtin/grep.c:866
> msgid "--open-files-in-pager only works on the worktree"
> -msgstr "--open-files-in-pager arbeitet nur innerhalb des Arbeitsbaums"
> +msgstr "Die Option --open-files-in-pager kann nur innerhalb des "
> +"Arbeitsbaums."
... " verwendet werden"!
> #: builtin/grep.c:897
> msgid "--[no-]exclude-standard cannot be used for tracked contents."
> -msgstr ""
> -"--[no-]exlude-standard kann nicht mit beobachteten Inhalten benutzt werden"
> +msgstr "Die Option --[no-]exlude-standard kann nicht mit beobachteten "
> +"Inhalten verwendet werden."
Typo in --no-exClude-standard. (It was in the old version, too.)
> #: builtin/log.c:1218
> msgid "--name-only does not make sense"
> -msgstr "--name-only macht keinen Sinn"
> +msgstr "Die Option --name-only kann nicht verwendet werden."
If you were curious as to the point of the message (even in English):
it's only triggered by format-patch.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2013-01-21 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 19:02 [PATCH] l10n: de.po: fix some minor issues Ralf Thielow
2013-01-21 19:21 ` Thomas Rast [this message]
2013-01-21 20:07 ` [PATCHv2] " Ralf Thielow
2013-01-21 20:28 ` Thomas Rast
2013-01-22 8:18 ` Joachim Schmitz
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=87622ql4tl.fsf@pctrast.inf.ethz.ch \
--to=trast@inf.ethz.ch \
--cc=git@vger.kernel.org \
--cc=jk@jk.gs \
--cc=ralf.thielow@gmail.com \
--cc=stimming@tuhh.de \
/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).