git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ralf Thielow <ralf.thielow@gmail.com>
To: Phillip Sz <phillip.szelat@gmail.com>
Cc: 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 3/7] part3: l10n: de.po: use imperative form for command options
Date: Thu, 25 Sep 2014 20:04:51 +0200	[thread overview]
Message-ID: <CAN0XMO+z-PbcLWO-OS04LeALzDvS5kXsnEB=hZTRGAWhTBVC0g@mail.gmail.com> (raw)
In-Reply-To: <54214A4D.8080904@gmail.com>

Hi,

2014-09-23 12:24 GMT+02:00 Phillip Sz <phillip.szelat@gmail.com>:
> Hi,
>
>>  #: builtin/describe.c:395
>>  msgid "find the tag that comes after the commit"
>> -msgstr "findet das Tag, das nach Commit kommt"
>> +msgstr "das Tag finden, das nach Commit kommt"
>>
>
> "das Tag finden, das nach dem Commit kommt"
>
>>  #: builtin/fast-export.c:718
>>  msgid "Use the done feature to terminate the stream"
>> -msgstr "Benutzt die \"done\"-Funktion um den Strom abzuschließen"
>> +msgstr "die \"done\"-Funktion benutzen um den Strom abzuschließen"
>>
>
> "die \"done\"-Funktion benutzen, um den Strom abzuschließen"

You send a patch for the comma before "um" (thanks for that). I'll rebase
these patches on top of that before applying, so the comma will be added
then.

>
> Maybe its better to use »Stream» instead of »Strom« in general?
>

What about "Datenstrom"?

> Phillip
>
>

  reply	other threads:[~2014-09-25 18:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 17:12 [PATCH 0/7] l10n: de.po: use imperative form for command options Ralf Thielow
2014-09-19 17:12 ` [PATCH 1/7] part1: " Ralf Thielow
2014-09-19 19:11   ` Phillip Sz
2014-09-19 20:43     ` Ralf Thielow
2014-10-24 18:02       ` [PATCH v2] " Ralf Thielow
2014-10-25  8:53         ` phillip
2014-09-19 17:12 ` [PATCH 2/7] part2: " Ralf Thielow
2014-09-19 17:12 ` [PATCH 3/7] part3: " Ralf Thielow
2014-09-23 10:24   ` Phillip Sz
2014-09-25 18:04     ` Ralf Thielow [this message]
2014-09-25 19:45       ` phillip
2014-10-24 18:02         ` [PATCH v2] " Ralf Thielow
2014-09-19 17:12 ` [PATCH 4/7] part4: " Ralf Thielow
2014-09-19 17:12 ` [PATCH 5/7] part5: " Ralf Thielow
2014-09-19 17:12 ` [PATCH 6/7] part6: " Ralf Thielow
2014-09-19 17:12 ` [PATCH 7/7] part7: " Ralf Thielow
2014-11-07 20:11 ` [PATCH v3 0/7] use imperative form for command Ralf Thielow
2014-11-07 20:11   ` [PATCH v3 1/7] part1: l10n: de.po: use imperative form for command options Ralf Thielow
2014-11-07 20:11   ` [PATCH v3 2/7] part2: " Ralf Thielow
2014-11-07 20:11   ` [PATCH v3 3/7] part3: " Ralf Thielow
2014-11-07 20:11   ` [PATCH v3 4/7] part4: " Ralf Thielow
2014-11-07 20:11   ` [PATCH v3 5/7] part5: " Ralf Thielow
2014-11-07 20:11   ` [PATCH v3 6/7] part6: " Ralf Thielow
2014-11-07 20:11   ` [PATCH v3 7/7] part7: " 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAN0XMO+z-PbcLWO-OS04LeALzDvS5kXsnEB=hZTRGAWhTBVC0g@mail.gmail.com' \
    --to=ralf.thielow@gmail.com \
    --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).