git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Ralf Thielow <ralf.thielow@googlemail.com>
Cc: <trast@student.ethz.ch>, <jk@jk.gs>, <stimming@tuhh.de>,
	<worldhello.net@gmail.com>, <git@vger.kernel.org>
Subject: Re: [PATCH v2] l10n: de.po: translate 41 new messages
Date: Thu, 31 May 2012 11:56:16 +0200	[thread overview]
Message-ID: <87zk8o3c8v.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <1338412586-12116-1-git-send-email-ralf.thielow@googlemail.com> (Ralf Thielow's message of "Wed, 30 May 2012 23:16:26 +0200")

Ralf Thielow <ralf.thielow@googlemail.com> writes:

> +#. TRANSLATORS: the colon here should align with the
> +#. one in "usage: %s" translation
> +#: parse-options.c:515
> +#, c-format
> +msgid "   or: %s"
> +msgstr "      oder: %s"
> +
> +#: parse-options.c:518
> +#, c-format
> +msgid "    %s"
> +msgstr "    %s"

On IRC I indicated that this might be intended to line up with the " or:
%s" snippet.  This was a false alarm; it indents followup material, as
in

$ git blame -h
usage: git blame [options] [rev-opts] [rev] [--] file

    [rev-opts] are documented in git-rev-list(1)

    --incremental         Show blame entries as we find them, incrementally
[snip]

> +#: builtin/apply.c:3974
> +msgid "instead of applying the patch, output diffstat for the input"
> +msgstr "anstatt der Anwendung des Patches, wird die Differenz für die Eingabe "
> +"ausgegeben"

diffstat has no precedent, so we get to bikeshed (yay).  I added a
placeholder to your glossary.  (I also added some other diff-related
terms.)  My current best suggestion, sadly, is "diffstat" simply because
it matches the option name.

> +#: builtin/apply.c:4000 builtin/apply.c:4003
> +msgid "ignore changes in whitespace when finding context"
> +msgstr "ignoriert Änderungen in Leerzeichen bei der Suche des Kontextes"

I interpret "Leerzeichen" as being (specifically) the ASCII space
character.  Is it just me?  Otherwise I suggest we find a more general
translation for whitespace.

>  #: builtin/index-pack.c:458
>  msgid "delta base offset is out of bound"
> -msgstr "Wert für Versatz bei Differenzobjekt liegt außerhalb des gültigen "
> -"Bereichs"
> +msgstr ""
> +"Wert für Versatz bei Differenzobjekt liegt außerhalb des gültigen Bereichs"

This is a case where I really wonder how useful a translation is.  The
user won't be any wiser (just as with the English one), the developers
will just grep de.po for the "real" message to look for :-)

> +#: parse-options.h:156
> +msgid "no-op (backward compatibility)"
> +msgstr "Keine Operation (Rückwärtskompatibilität)"

"Kein Effekt" might be less confusing?

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2012-05-31  9:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30 16:39 [PATCH] l10n: de.po: translate 41 new messages Ralf Thielow
2012-05-30 21:16 ` [PATCH v2] " Ralf Thielow
2012-05-31  9:56   ` Thomas Rast [this message]
2012-05-31 14:49     ` Ralf Thielow
2012-06-01 14:55       ` [PATCH v3] " 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=87zk8o3c8v.fsf@thomas.inf.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=jk@jk.gs \
    --cc=ralf.thielow@googlemail.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).