From: Thomas Braun <thomas.braun@virtuell-zuhause.de>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: git@vger.kernel.org, ralf.thielow@gmail.com
Subject: german language fix: Generierung vs. Generation [was: Re: Parallel fetch and commit graph writing results in locking failure (even on linux)]
Date: Sun, 15 Dec 2019 18:35:48 +0100 (CET) [thread overview]
Message-ID: <2099929548.270607.1576431348524@ox.hosteurope.de> (raw)
In-Reply-To: <20191213201522.GM6527@szeder.dev>
> SZEDER Gábor <szeder.dev@gmail.com> hat am 13. Dezember 2019 um 21:15 geschrieben:
>
>
> On Fri, Dec 13, 2019 at 08:20:42PM +0100, Thomas Braun wrote:
> > Commit-Graph Generierungsnummern berechnen: 100% (13/13), Fertig.
> >
> > (Sorry for the german text, this is not easily reproducible.)
>
> It's unrelated to your issue, and I'm not a native German or English
> speaker... but that translation doesn't look quite right to me.
>
> The original is:
>
> _("Computing commit graph generation numbers"),
>
> where the word "generation" isn't used in the sense of "creation"
> (erzeugen, generieren), but rather as in "generation gap" or "my
> parents are one generation older than me". So I don't think that
> "Generierung..." is the right word to use here, but perhaps
> "Generationsnummer".
>
> But who am I to argue about German software ranslation?! :)
Your hunch is right I would say (not that it matters much but I'm a native speaker).
So how about the following patch (CC'ing the original translator)
commit 724bf68da28b75e04a9fda34b08e95259ade9ec3 (HEAD -> master)
Author: Thomas Braun <thomas.braun@virtuell-zuhause.de>
Date: Sun Dec 15 18:28:42 2019 +0100
lang de: Reword generation numbers
The english term generation is here not used in the sense of "to
generate" but in the sense of "generations of beings".
This corrects the initial translation from cf4c0c25 (l10n: update German
translation, 2018-12-06).
Fixed-by: "SZEDER Gábor" <szeder.dev@gmail.com>
diff --git a/po/de.po b/po/de.po
index 066326a687..773e361f6f 100644
--- a/po/de.po
+++ b/po/de.po
@@ -1535,7 +1535,7 @@ msgstr "Lösche Commit-Markierungen in Commit-Graph"
#: commit-graph.c:1104
msgid "Computing commit graph generation numbers"
-msgstr "Commit-Graph Generierungsnummern berechnen"
+msgstr "Commit-Graph Generationsnummern berechnen"
#: commit-graph.c:1179
#, c-format
next prev parent reply other threads:[~2019-12-15 17:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 19:20 Parallel fetch and commit graph writing results in locking failure (even on linux) Thomas Braun
2019-12-13 19:35 ` Derrick Stolee
2019-12-13 19:52 ` Jeff King
2019-12-13 19:58 ` Derrick Stolee
2019-12-15 17:19 ` Thomas Braun
2019-12-13 20:15 ` SZEDER Gábor
2019-12-15 17:35 ` Thomas Braun [this message]
2019-12-15 19:44 ` [PATCH] l10n: de.po: Reword generation numbers 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2099929548.270607.1576431348524@ox.hosteurope.de \
--to=thomas.braun@virtuell-zuhause.de \
--cc=git@vger.kernel.org \
--cc=ralf.thielow@gmail.com \
--cc=szeder.dev@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).