git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ralf Thielow <ralf.thielow@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git <git@vger.kernel.org>, Ralf Thielow <ralf.thielow@googlemail.com>
Subject: Re: [PATCH] l10n: de: lower case after semi-colon
Date: Fri, 17 Mar 2017 18:11:27 +0100	[thread overview]
Message-ID: <CAN0XMOKrm7BOx5RUD5ki1DF-WieVAmOmx5=eAOnJcaFB+iQxwg@mail.gmail.com> (raw)
In-Reply-To: <ae12d1eaac8cec63bbfe0eae3b428b781fd34d30.1489762895.git.git@drmicha.warpmail.net>

Thanks for both patches to de.po!

2017-03-17 16:04 GMT+01:00 Michael J Gruber <git@drmicha.warpmail.net>:
> Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
> ---
> Just a minor thing. I'm wondering about lower/upper case
> at the beginning of the line, though. Do we have a rule for de.po?
>

There is no rule nor is there consistency. :/ Some messages start with
lower case because the original english message is doing so, some do
not.

I do not think it makes sense to adopt rules like "error messages should
start with lower case" or something like that in translations so it's an error
to do so.

I will add this issue to my TODO list to fix this in the whole translation.

Thanks

>  po/de.po | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/po/de.po b/po/de.po
> index e9c86f5488..f8215945e7 100644
> --- a/po/de.po
> +++ b/po/de.po
> @@ -7599,7 +7599,7 @@ msgid ""
>  "more than %i tags found; listed %i most recent\n"
>  "gave up search at %s\n"
>  msgstr ""
> -"mehr als %i Tags gefunden; Führe die ersten %i auf\n"
> +"mehr als %i Tags gefunden; führe die ersten %i auf\n"
>  "Suche bei %s aufgegeben\n"
>
>  #: builtin/describe.c:396
> --
> 2.12.0.484.g92f9ab2bc1
>

      reply	other threads:[~2017-03-17 17:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-17 15:04 [PATCH] l10n: de: lower case after semi-colon Michael J Gruber
2017-03-17 17:11 ` Ralf Thielow [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='CAN0XMOKrm7BOx5RUD5ki1DF-WieVAmOmx5=eAOnJcaFB+iQxwg@mail.gmail.com' \
    --to=ralf.thielow@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=ralf.thielow@googlemail.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.
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).