From: Ralf Thielow <ralf.thielow@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: "Phillip Sz" <phillip.szelat@gmail.com>,
git <git@vger.kernel.org>, "Thomas Rast" <tr@thomasrast.ch>,
"Jan Krüger" <jk@jk.gs>, "Christian Stimming" <stimming@tuhh.de>,
"Matthias Rüster" <matthias.ruester@gmail.com>,
"Magnus Görlitz" <magnus.goerlitz@googlemail.com>
Subject: Re: [PATCH 1/1] l10n: de.po: use "bla …" instead of "bla..."
Date: Tue, 24 Mar 2015 18:10:44 +0100 [thread overview]
Message-ID: <20150324171044.GA4414@ralf-ubuntu> (raw)
In-Reply-To: <551190F2.10808@drmicha.warpmail.net>
Michael J Gruber <git@drmicha.warpmail.net> wrote:
> Ralf Thielow venit, vidit, dixit 21.03.2015 22:21:
> > Am 21. März 2015 um 13:52 schrieb Phillip Sz <phillip.szelat@gmail.com>:
> >>
> >> I think we should use it like this, as most open-source projects do.
> >> Also we should use a space before the three dots as per http://www.duden.de/sprachwissen/rechtschreibregeln/auslassungspunkte
> >>
> >
> > I don't think this rule of ellipsis applies here as the dots are meant
> > to be a pattern to tell users that an argument can be passed multiple
> > times.
> >
>
> "..." is used in (at least) 2 cases:
>
> * ellipsis
> * continuation arguments
>
> The patch changes both, but the Duden rule applies to the first case
> only (and is different from "legacy rules", I think).
>
> Also, you might want to check the format of other commit messages and
> reword yours accordingly.
>
Let's apply this instead.
-- >8 --
From: Phillip Sz <phillip.szelat@gmail.com>
Date: Sat, 21 Mar 2015 13:52:37 +0100
Subject: [PATCH] l10n: de.po: add space before ellipsis
Signed-off-by: Phillip Sz <phillip.szelat@gmail.com>
Signed-off-by: Ralf Thielow <ralf.thielow@gmail.com>
---
po/de.po | 32 ++++++++++++++++----------------
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/po/de.po b/po/de.po
index 11fbd0f..9fa3f4c 100644
--- a/po/de.po
+++ b/po/de.po
@@ -616,7 +616,7 @@ msgstr ""
#: help.c:373
#, c-format
msgid "in %0.1f seconds automatically..."
-msgstr "Automatische Ausführung in %0.1f Sekunden..."
+msgstr "Automatische Ausführung in %0.1f Sekunden ..."
#: help.c:380
#, c-format
@@ -1271,12 +1271,12 @@ msgstr "Kann keine Commit-Beschreibung für %s bekommen"
#: sequencer.c:611
#, c-format
msgid "could not revert %s... %s"
-msgstr "Konnte \"revert\" nicht auf %s ausführen... %s"
+msgstr "Konnte \"revert\" nicht auf %s ausführen ... %s"
#: sequencer.c:612
#, c-format
msgid "could not apply %s... %s"
-msgstr "Konnte %s nicht anwenden... %s"
+msgstr "Konnte %s nicht anwenden ... %s"
#: sequencer.c:648
msgid "empty commit set passed"
@@ -2436,7 +2436,7 @@ msgstr "%s: Patch konnte nicht angewendet werden"
#: builtin/apply.c:3653
#, c-format
msgid "Checking patch %s..."
-msgstr "Prüfe Patch %s..."
+msgstr "Prüfe Patch %s ..."
#: builtin/apply.c:3746 builtin/checkout.c:231 builtin/reset.c:135
#, c-format
@@ -4091,7 +4091,7 @@ msgstr "Konnte zu klonenden Remote-Branch %s nicht finden."
#: builtin/clone.c:561
#, c-format
msgid "Checking connectivity... "
-msgstr "Prüfe Konnektivität... "
+msgstr "Prüfe Konnektivität ... "
#: builtin/clone.c:564
msgid "remote did not send all necessary objects"
@@ -4165,12 +4165,12 @@ msgstr "Konnte Arbeitsverzeichnis '%s' nicht erstellen."
#: builtin/clone.c:870
#, c-format
msgid "Cloning into bare repository '%s'...\n"
-msgstr "Klone in Bare-Repository '%s'...\n"
+msgstr "Klone in Bare-Repository '%s' ...\n"
#: builtin/clone.c:872
#, c-format
msgid "Cloning into '%s'...\n"
-msgstr "Klone nach '%s'...\n"
+msgstr "Klone nach '%s' ...\n"
#: builtin/clone.c:897
msgid "--dissociate given, but there is no --reference"
@@ -4600,7 +4600,7 @@ msgstr ""
#: builtin/commit.c:1199
msgid "Clever... amending the last one with dirty index."
msgstr ""
-"Klug... den letzten Commit mit einer geänderten Staging-Area nachbessern."
+"Klug ... den letzten Commit mit einer geänderten Staging-Area nachbessern."
#: builtin/commit.c:1201
msgid "Explicit paths specified without -i or -o; assuming --only paths..."
@@ -7335,7 +7335,7 @@ msgstr "Aktualisiere %s..%s\n"
#: builtin/merge.c:1388
#, c-format
msgid "Trying really trivial in-index merge...\n"
-msgstr "Probiere wirklich trivialen \"in-index\"-Merge...\n"
+msgstr "Probiere wirklich trivialen \"in-index\"-Merge ...\n"
#: builtin/merge.c:1395
#, c-format
@@ -7349,12 +7349,12 @@ msgstr "Vorspulen nicht möglich, breche ab."
#: builtin/merge.c:1450 builtin/merge.c:1529
#, c-format
msgid "Rewinding the tree to pristine...\n"
-msgstr "Rücklauf des Verzeichnisses bis zum Ursprung...\n"
+msgstr "Rücklauf des Verzeichnisses bis zum Ursprung ...\n"
#: builtin/merge.c:1454
#, c-format
msgid "Trying merge strategy %s...\n"
-msgstr "Probiere Merge-Strategie %s...\n"
+msgstr "Probiere Merge-Strategie %s ...\n"
#: builtin/merge.c:1520
#, c-format
@@ -7682,7 +7682,7 @@ msgstr "git notes copy [<Optionen>] <von-Objekt> <nach-Objekt>"
#: builtin/notes.c:51
msgid "git notes copy --stdin [<from-object> <to-object>]..."
-msgstr "git notes copy --stdin [<von-Objekt> <nach-Objekt>]..."
+msgstr "git notes copy --stdin [<von-Objekt> <nach-Objekt>] ..."
#: builtin/notes.c:56
msgid "git notes append [<options>] [<object>]"
@@ -8689,7 +8689,7 @@ msgstr "git remote prune [<Optionen>] <Name>"
#: builtin/remote.c:64
msgid "git remote update [<options>] [<group> | <remote>]..."
-msgstr "git remote update [<Optionen>] [<Gruppe> | <externesRepository>]..."
+msgstr "git remote update [<Optionen>] [<Gruppe> | <externesRepository>] ..."
#: builtin/remote.c:88
#, c-format
@@ -9865,7 +9865,7 @@ msgstr "fehlerhaftes Objekt bei '%s'"
#: builtin/tag.c:301
#, c-format
msgid "tag name too long: %.*s..."
-msgstr "Tagname zu lang: %.*s..."
+msgstr "Tagname zu lang: %.*s ..."
#: builtin/tag.c:306
#, c-format
@@ -10450,7 +10450,7 @@ msgstr ""
#: git-am.sh:166
msgid "Falling back to patching base and 3-way merge..."
-msgstr "Falle zurück zum Patchen der Basis und des 3-Wege-Merges..."
+msgstr "Falle zurück zum Patchen der Basis und des 3-Wege-Merges ..."
#: git-am.sh:182
msgid "Failed to merge in the changes."
@@ -10943,7 +10943,7 @@ msgstr "Änderungen von $mb zu $onto:"
msgid "First, rewinding head to replay your work on top of it..."
msgstr ""
"Zunächst wird der Branch zurückgespult, um Ihre Änderungen\n"
-"darauf neu anzuwenden..."
+"darauf neu anzuwenden ..."
#: git-rebase.sh:620
#, sh-format
--
2.3.3.434.g642b19b
next prev parent reply other threads:[~2015-03-24 17:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 12:52 [PATCH 1/1] l10n: de.po: use "bla …" instead of "bla..." Phillip Sz
2015-03-21 14:07 ` Matthias Rüster
2015-03-21 21:21 ` Ralf Thielow
2015-03-24 16:29 ` Michael J Gruber
2015-03-24 17:10 ` Ralf Thielow [this message]
2015-03-24 17:34 ` Ralf Thielow
[not found] ` <xmqqlhim713w.fsf@gitster.dls.corp.google.com>
2015-03-24 17:51 ` Ralf Thielow
2015-03-24 18:42 ` [PATCH 1/2] l10n: de.po: add space before ellipsis Ralf Thielow
2015-03-24 18:42 ` [PATCH 2/2] l10n: de.po: fix messages with abbreviated hashs Ralf Thielow
2015-03-25 16:42 ` [PATCH v2] " Ralf Thielow
2015-03-24 20:29 ` [PATCH 1/1] l10n: de.po: use "bla …" instead of "bla..." phillip
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=20150324171044.GA4414@ralf-ubuntu \
--to=ralf.thielow@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=jk@jk.gs \
--cc=magnus.goerlitz@googlemail.com \
--cc=matthias.ruester@gmail.com \
--cc=phillip.szelat@gmail.com \
--cc=stimming@tuhh.de \
--cc=tr@thomasrast.ch \
/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).