From: Stephan Beyer <s-beyer@gmx.net>
To: Christian Stimming <stimming@tuhh.de>
Cc: Paul Mackerras <paulus@samba.org>, git@vger.kernel.org
Subject: Re: [PATCH] gitk: Update German translation
Date: Thu, 1 May 2008 23:10:04 +0200 [thread overview]
Message-ID: <20080501211004.GE7868@leksak.fem-net> (raw)
In-Reply-To: <200805012142.10151.stimming@tuhh.de>
[-- Attachment #1: Type: text/plain, Size: 4679 bytes --]
> I'd propose to talk about the newest or topmost commit,
> but rather not about the "first".
I agree, but s/newest/latest/ :)
Well.
Although your patch does not cover the translations itself (and although
I neither use the German translation of gitk and use gitk very seldom at
all), I've taken a look at the given translations and want to drop some
comments/corrections.
> -#: gitk:141 gitk:2143
> +#: gitk:151 gitk:2191
> msgid "Reading commits..."
> msgstr "Versionen lesen..."
Is "Version" really the German translation for "commit" throughout the
whole git suite?
(Ehh, is git translated at all?)
I'd recommend "Commit" or "Eintragung"...
"Version" is so CVS/SVN-like.
> -#: gitk:264
> +#: gitk:275
> msgid "Can't parse git log output:"
> msgstr "Git log Ausgabe kann nicht erkannt werden:"
"git-log-Ausgabe" oder "Ausgabe von git-log"
> -#: gitk:650
> +#: gitk:665
> msgid "List references"
> msgstr "Zweige auflisten"
Hm, the button lists branches and tags.
Is then "Zweige" (= branches) only correct?
What about "Referenzen auflisten" or "Zweige/Markierungen auflisten"
(or however "tags" is translated).
> -#: gitk:782 gitk:784 gitk:2308 gitk:2331 gitk:2355 gitk:4257 gitk:4320
> +#: gitk:797 gitk:799 gitk:2356 gitk:2379 gitk:2403 gitk:4306 gitk:4369
> msgid "containing:"
> msgstr "enthaltend:"
"enthält:"
> -#: gitk:785 gitk:1741 gitk:1746 gitk:2383
> +#: gitk:800 gitk:1778 gitk:1783 gitk:2431
> msgid "touching paths:"
> msgstr "Pfad betreffend:"
"betrifft Pfad:"
> -#: gitk:786 gitk:2388
> +#: gitk:801 gitk:2436
> msgid "adding/removing string:"
> msgstr "String dazu/l??schen:"
"ändert Zeichenkette:"
> -#: gitk:797 gitk:2466 gitk:4225
> +#: gitk:812 gitk:2514 gitk:4274
> msgid "IgnCase"
> msgstr "Kein Gro??/Klein"
The translation is rather ambiguous. Or is it just me? ;)
"Ignoriere Groß-/Kleinschreibung" or
"Groß-/Kleinschreibung ignorieren"
> -#: gitk:801 gitk:2483 gitk:4287 gitk:4713
> +#: gitk:816 gitk:2531 gitk:4336 gitk:4765
> msgid "Committer"
> msgstr "Eintragender"
"Versionierender" ... No, just a bad joke ;-)
The translation is good.
> -#: gitk:1026
> +#: gitk:1061
> msgid "Cherry-pick this commit"
> msgstr "Diese Version pfl??cken"
If I didn't knew that it means "cherry-pick", I'd have no idea
what the function behind that German words does. ;-)
(That's why I don't have locales set to my mother tongue. Just because I
only have to understand the programmer and not the translator first.)
"Diesen Commit übernehmen"
"Diesen Commit kopieren"
"Diese Eintragung übernehmen"
> +#: gitk:1354
> +msgid "<Left>, z, j\tGo back in history list"
> +msgstr "<Links>, z, j\tEine Version zur??ck gehen"
I think it's still "zurückgehen" and not "zurück gehen" in the latest
German spelling.
> +#: gitk:1355
> +msgid "<Right>, x, l\tGo forward in history list"
> +msgstr "<Rechts>, x, l\tEine Version nach vorne gehen"
"nach vorne gehen" sounds so colloquial.
Better, perhaps: "weitergehen"?
> -#: gitk:5719
> +#: gitk:5781
> msgid "SHA1 ID:"
> msgstr "SHA1 Kennung:"
Somewhere else it has been translated to "SHA1:", which is imho better.
Otherwise it'd be "SHA1-Kennung".
> -#: gitk:5744
> +#: gitk:5806
> #, tcl-format
> msgid "Short SHA1 id %s is ambiguous"
> msgstr "Kurze SHA1-Kennung ??%s?? ist mehrdeutig"
Here it's correct.
> -#: gitk:6081
> +#: gitk:6143
> msgid "Error creating patch:"
> msgstr "Fehler beim Patch erzeugen:"
"Fehler bei der Erzeugung des Patches"
> -#: gitk:6233
> +#: gitk:6291
> msgid "Error writing commit:"
> msgstr "Fehler beim Version eintragen:"
"Fehler bei der Eintragung:"
"Fehler beim Schreiben der Eintragung:" (or "Version", if really used in
other places)
> -#: gitk:7966
> +#: gitk:8024
> +msgid "Auto-select SHA1"
> +msgstr "SHA1 Hashwert automatisch markieren"
"SHA1-Hashwert"
> -#: gitk:7985
> +#: gitk:8048
> msgid "Background"
> msgstr "Vordergrund"
>
> -#: gitk:7989
> +#: gitk:8052
> msgid "Foreground"
> msgstr "Hintergrund"
Funny. It's vice versa!
msgid "Background"
msgstr "Hintergrund"
msgid "Foreground"
msgstr "Vordergrund"
> -#: gitk:8587
> +#: gitk:8656
> msgid ""
> "No files selected: --merge specified but no unmerged files are within file "
> "limit."
> @@ -720,6 +891,6 @@ msgstr ""
> "Keine Dateien ausgew??hle: --merge angegeben, aber keine nicht-"
^
t
> "zusammengef??hrten Dateien sind in der Dateiauswahl."
Regards,
Stephan
--
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-05-01 21:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 19:42 [PATCH] gitk: Update German translation Christian Stimming
2008-05-01 21:10 ` Stephan Beyer [this message]
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 19:36 ` [PATCH] gitk: German translation again updated Christian Stimming
2008-05-02 11:49 ` [PATCH] gitk: Update German translation 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
-- strict thread matches above, loose matches on Subject: below --
2016-02-12 18:40 [PATCH] gitk: update " Ralf Thielow
2016-02-12 18:56 ` Stefan Beller
2016-02-12 19:17 ` Ralf Thielow
2016-03-19 6:56 ` Paul Mackerras
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-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=20080501211004.GE7868@leksak.fem-net \
--to=s-beyer@gmx.net \
--cc=git@vger.kernel.org \
--cc=paulus@samba.org \
--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).