From: Stefan Beller <sbeller@google.com>
To: Ralf Thielow <ralf.thielow@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
"Christian Stimming" <stimming@tuhh.de>,
"Paul Mackerras" <paulus@samba.org>,
"Phillip Sz" <phillip.szelat@gmail.com>,
"Matthias Rüster" <matthias.ruester@gmail.com>
Subject: Re: [PATCH] gitk: update German translation
Date: Fri, 12 Feb 2016 10:56:29 -0800 [thread overview]
Message-ID: <CAGZ79kY8aSD-T-pcqeBBA-Rv9FwSeqAT2k2+OSyEsiPcF-AWOA@mail.gmail.com> (raw)
In-Reply-To: <1455302439-9290-1-git-send-email-ralf.thielow@gmail.com>
2016-02-12 10:40 GMT-08:00 Ralf Thielow <ralf.thielow@gmail.com>:
> Signed-off-by: Ralf Thielow <ralf.thielow@gmail.com>
> ---
> Note:
> Some translations in gitk may differ from translations in git-core
> since gitk uses another glossary which I tried to follow here.
>
> po/de.po | 79 +++++++++++++++++++++++++++-------------------------------------
> 1 file changed, 33 insertions(+), 46 deletions(-)
>
> diff --git a/po/de.po b/po/de.po
> index d9ba405..bde749e 100644
> --- a/po/de.po
> +++ b/po/de.po
> @@ -21,15 +21,15 @@ msgstr ""
> msgid "Couldn't get list of unmerged files:"
> msgstr "Liste der nicht zusammengeführten Dateien nicht gefunden:"
>
> #: gitk:212 gitk:2381
> msgid "Color words"
> -msgstr ""
> +msgstr "Wörter einfärben"
>
> #: gitk:217 gitk:2381 gitk:8220 gitk:8253
> msgid "Markup words"
> -msgstr ""
> +msgstr "Wörter kennzeichnen"
>
> #: gitk:324
> msgid "Error parsing revisions:"
> msgstr "Fehler beim Laden der Versionen:"
"Laden" (loading) is not the most correct translation for parsing,
but maybe good for the user. What about one of "analysieren, (zer)gliedern,
parsen, bestimmen" ?
Thanks,
Stefan
next prev parent reply other threads:[~2016-02-12 18:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 18:40 [PATCH] gitk: update German translation Ralf Thielow
2016-02-12 18:56 ` Stefan Beller [this message]
2016-02-12 19:17 ` Ralf Thielow
2016-03-19 6:56 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2010-01-27 19:30 [PATCH] gitk: Update " Christian Stimming
2009-09-25 20:41 Christian Stimming
2009-05-12 20:20 Christian Stimming
2008-05-01 19:42 Christian Stimming
2008-05-01 21:10 ` Stephan Beyer
2008-05-02 19:23 ` Christian Stimming
2008-05-03 1:24 ` Stephan Beyer
2008-05-07 20:56 ` Christian Stimming
2008-05-15 16:20 ` Stephan Beyer
2008-05-24 20:48 ` Christian Stimming
2008-05-25 21:57 ` Stephan Beyer
2008-05-02 11:49 ` Paul Mackerras
2008-05-02 18:33 ` Christian Stimming
2008-05-03 7:53 ` Paul Mackerras
2008-05-03 8:03 ` Christian Stimming
2008-05-02 12:56 ` Paul Mackerras
2008-05-02 18:30 ` Christian Stimming
2008-01-09 21:24 Christian Stimming
2008-01-15 11:54 ` Paul Mackerras
2008-01-15 12:49 ` Christian Stimming
2008-01-08 20:56 Christian Stimming
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=CAGZ79kY8aSD-T-pcqeBBA-Rv9FwSeqAT2k2+OSyEsiPcF-AWOA@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=matthias.ruester@gmail.com \
--cc=paulus@samba.org \
--cc=phillip.szelat@gmail.com \
--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).