From: "Sören Krecker" <soekkle@freenet•de>
To: "brian m. carlson" <sandals@crustytoothpaste•net>,
git@vger•kernel.org, Ralf Thielow <ralf.thielow@gmail•com>
Subject: Re: Possible German translation bug
Date: Fri, 28 Nov 2025 06:14:18 +0100 [thread overview]
Message-ID: <1a65fcbb-0a44-41f2-bba5-e0670a312ee1@freenet.de> (raw)
In-Reply-To: <aSjehThPX8-WeQR7@fruit.crustytoothpaste.net>
Hi,
for me as a native speeker the translation revison as "Revision" seems
much better to me.
Best regards,
Sören Krecker
Am 28.11.25 um 00:28 schrieb brian m. carlson:
> We have the following string in Git, which is translated as follows in
> Spanish, French, and German:
>
> ----
> % git rev-parse --verify nonexistent
> fatal: Needed a single revision
> % LC_ALL=es_MX.UTF-8 git rev-parse --verify nonexistent
> fatal: Se necesitó una revisión singular
> % LC_ALL=fr_CA.UTF-8 git rev-parse --verify nonexistent
> fatal : Une seule révision attendue
> % LC_ALL=de_DE.UTF-8 git rev-parse --verify nonexistent
> Schwerwiegend: Benötigte einen einzelnen Commit
> ----
>
> In Spanish and French, we use the translation of the word "revision"
> because `git rev-parse --verify` can permit referring to an object of
> any type: blob, tree, commit, or tag. For instance, this is a blob:
>
> ----
> % git rev-parse --verify v2.0.0:strbuf.c
> ee96dcfb816625436582833d812a7156513d5d39
> ----
>
> But in German, we use the noun "Commit". I admit my German is not very
> good[0] and my technical German is effectively nonexistent, but I
> presume "Commit" means "commit" and if so, that's simply not accurate in
> this case.
>
> It looks like in other places in the translation we use "Revisionsgang"
> for "revision walk" and "Revisionsliste" for "revision list", so maybe
> "Revision" is a possible option here, but that would be better decided
> by someone with a much better command of German than I have. Of course,
> I could be wrong altogether, in which case please accept my apologies
> for the noise.
>
> [0] I do hope to improve it in the new year, though.
prev parent reply other threads:[~2025-11-28 5:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 23:28 Possible German translation bug brian m. carlson
2025-11-28 5:14 ` Sören Krecker [this message]
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=1a65fcbb-0a44-41f2-bba5-e0670a312ee1@freenet.de \
--to=soekkle@freenet$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=ralf.thielow@gmail$(echo .)com \
--cc=sandals@crustytoothpaste$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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