git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] l10n: de.po: translate 41 new messages

From
Thomas Rast <trast@student.ethz.ch>
Date
May 31, 2012, 09:56 UTC
Message-ID
<87zk8o3c8v.fsf@thomas.inf.ethz.ch>
In-Reply-To
<1338412586-12116-1-git-send-email-ralf.thielow@googlemail.com>
Ralf Thielow <ralf.thielow@googlemail.com> writes:
Show 11 quoted lines
> +#. 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.

Show 6 quoted lines
>  #: 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
Previous: Ralf ThielowNext: Ralf Thielow
Message 3 of 5 in “l10n: de.po: translate 41 new messages”
  1. l10n: de.po: translate 41 new messagesRalf Thielow, May 30, 2012
  2. l10n: de.po: translate 41 new messagesRalf Thielow, May 30, 2012
  3. Thomas RastMay 31, 2012
  4. Ralf ThielowMay 31, 2012
  5. l10n: de.po: translate 41 new messagesRalf Thielow, Jun 1, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.