From: Thomas Rast <tr@thomasrast.ch>
To: Ralf Thielow <ralf.thielow@gmail.com>
Cc: jk@jk.gs, stimming@tuhh.de, worldhello.net@gmail.com,
git@vger.kernel.org
Subject: Re: [PATCHv2] l10n: de.po: translate 68 new messages
Date: Sat, 09 Nov 2013 13:10:14 +0100 [thread overview]
Message-ID: <877gchu66x.fsf@thomasrast.ch> (raw)
In-Reply-To: <1383942139-10536-1-git-send-email-ralf.thielow@gmail.com> (Ralf Thielow's message of "Fri, 8 Nov 2013 21:22:19 +0100")
Ralf Thielow <ralf.thielow@gmail.com> writes:
> #: remote.c:1837
> -#, fuzzy
> msgid " (use \"git branch --unset-upstream\" to fixup)\n"
> -msgstr " git branch --set-upstream-to %s\n"
> +msgstr " (benutzen Sie \"git branch --unset-upstream\" zum Beheben)\n"
Minor nit: the indent (it's simply a continuation indent for the "your
upstream is gone" message) is not consistent with other continuation
indents in the same vein, e.g.
#: remote.c:1794
msgid " (use \"git push\" to publish your local commits)\n"
msgstr " (benutzen Sie \"git push\" um lokale Commits zu publizieren)\n"
> #. Maybe the user already did that, don't error out here
> #: submodule.c:76
> -#, fuzzy, c-format
> +#, c-format
> msgid "Could not update .gitmodules entry %s"
> -msgstr "Konnte git-Verweis %s nicht erstellen"
> +msgstr "Konnte Eintrag '%s' in .gitmodules nicht aktualisieren"
>
> #. Maybe the user already did that, don't error out here
> #: submodule.c:109
> -#, fuzzy, c-format
> +#, c-format
> msgid "Could not remove .gitmodules entry for %s"
> -msgstr "Konnte Sektion '%s' nicht aus Konfiguration entfernen"
> +msgstr "Konnte Sektion '%s' nicht aus .gitmodules entfernen"
Here you translate 'entry' once as Eintrag, and once as Sektion? Is the
latter just a mistake from the fuzzy translation?
> #: builtin/gc.c:265
> msgid "force running gc even if there may be another gc running"
> -msgstr ""
> +msgstr "erzwingt Ausführung des Garbage Collectors selbst wenn ein anderer\n"
> +"Gargabe Collector bereits ausgeführt wird"
>
> #: builtin/gc.c:305
> #, c-format
> @@ -5502,6 +5493,8 @@ msgstr ""
> msgid ""
> "gc is already running on machine '%s' pid %<PRIuMAX> (use --force if not)"
> msgstr ""
> +"Gargabe Collector wird bereits auf Maschine '%s' pid %<PRIuMAX> ausgeführt\n"
> +"(benutzen Sie --force falls nicht)"
According to the glossary:
When a message is referring to the command, e.g. in error messages, we
do not translate the term.
Isn't this an instance of this rule? You could translate gc to git-gc
to avoid some confusion, but I think it specifically refers to running
the command.
> #: builtin/repack.c:143
> -#, fuzzy
> msgid "pack everything in a single pack"
> -msgstr "packt alles"
> +msgstr "packt alles in ein einzelnes Paket"
"ein einziges Paket" -- or is that my Swiss German again?
Also, the glossary says pack -> Pack-Datei. So it'd end up at "eine
einzige Pack-Datei".
> #: builtin/repack.c:145
> -#, fuzzy
> msgid "same as -a, and turn unreachable objects loose"
> -msgstr "zeigt unerreichbare Objekte"
> +msgstr "genau wie -a, unerreichbare Objekte werden aber nicht gelöscht"
Clever :-)
> #: builtin/repack.c:150
> msgid "pass --no-reuse-delta to git-pack-objects"
> -msgstr ""
> +msgstr "übergibt --no-reuse-delta nach git-pack-objects"
>
> #: builtin/repack.c:152
> msgid "pass --no-reuse-object to git-pack-objects"
> -msgstr ""
> +msgstr "übergibt --no-reuse-object nach git-pack-objects"
>
> #: builtin/repack.c:157
> msgid "pass --local to git-pack-objects"
> -msgstr ""
> +msgstr "übergibt --local nach git-pack-objects"
s/nach/an/?
> #: builtin/repack.c:158
> msgid "approxidate"
> -msgstr ""
> +msgstr "Datumsangabe"
On an entirely different note, we don't parse German approxidates, do
we?
--
Thomas Rast
tr@thomasrast.ch
next prev parent reply other threads:[~2013-11-09 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 18:57 [PATCH] l10n: de.po: translate 68 new messages Ralf Thielow
2013-11-08 20:22 ` [PATCHv2] " Ralf Thielow
2013-11-09 12:10 ` Thomas Rast [this message]
2013-11-10 17:55 ` [PATCH v3] " Ralf Thielow
2013-11-11 20:54 ` Thomas Rast
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=877gchu66x.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.