All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Thielow <ralf.thielow@gmail.com>
To: Simon Ruderich <simon@ruderich.org>
Cc: git <git@vger.kernel.org>, "Thomas Rast" <tr@thomasrast.ch>,
	"Jan Krüger" <jk@jk.gs>, "Christian Stimming" <stimming@tuhh.de>,
	"Phillip Szelat" <phillip.szelat@gmail.com>,
	"Matthias Rüster" <matthias.ruester@gmail.com>,
	"Magnus Görlitz" <magnus.goerlitz@googlemail.com>
Subject: Re: [PATCH v2] l10n: de.po: update German translation
Date: Tue, 2 May 2017 18:34:26 +0200	[thread overview]
Message-ID: <CAN0XMOLW8J9vYWY8wgMPwZoDX6FHJQZqpwHf6VA-uBeN-00PwQ@mail.gmail.com> (raw)
In-Reply-To: <20170501121930.jsbooranvc2il7s2@ruderich.org>

2017-05-01 14:19 GMT+02:00 Simon Ruderich <simon@ruderich.org>:
> On Sun, Apr 30, 2017 at 09:11:49PM +0200, Ralf Thielow wrote:
>>  #: config.c:1952
>>  #, c-format
>>  msgid "unknown core.untrackedCache value '%s'; using 'keep' default value"
>> -msgstr ""
>> +msgstr "Unbekannter Wert '%s' in core.untrackedCache; benutze Stardardwert 'keep'"
>                                                                  ^^^^^^^^^^^^
> Standardwert
>
>>  #: entry.c:280
>> -#, fuzzy, c-format
>> +#, c-format
>>  msgid "could not stat file '%s'"
>> -msgstr "konnte Datei '%s' nicht erstellen"
>> +msgstr "konnte Datei '%s' nicht lesen"
>
> Read is not quite stat (there are situations where you can stat
> but not read a file), but I can't think of a better translation.
>
>>  #: builtin/describe.c:551
>> -#, fuzzy
>>  msgid "--broken is incompatible with commit-ishes"
>> -msgstr "Die Option --dirty kann nicht mit Commits verwendet werden."
>> +msgstr "Die Option --broken kann nicht nit Commits verwendet werden."
>                                           ^^^
> mit
>
>>  #: builtin/tag.c:312
>>  msgid "tag: tagging "
>> -msgstr ""
>> +msgstr "Tag: tagge "
>
> Lowercase Tag because it's used as command prefix? In other
> places in this patch the lowercase version was used for commands.
>
> Regards
> Simon
> --

Thanks!

> + privacy is necessary
> + using gnupg http://gnupg.org
> + public key id: 0x92FEFDB7E44C32F9

  reply	other threads:[~2017-05-02 16:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-30 18:47 [PATCH] l10n: de.po: update German translation Ralf Thielow
2017-04-30 19:11 ` [PATCH v2] " Ralf Thielow
2017-05-01 12:19   ` Simon Ruderich
2017-05-02 16:34     ` Ralf Thielow [this message]
2017-05-02 16:36   ` [PATCH v3] " Ralf Thielow
2017-05-03 12:38     ` Christian Brabandt
2017-05-03 16:38       ` Ralf Thielow
2017-05-03 19:27         ` Christian Brabandt
2017-05-04 12:55           ` Ralf Thielow
2017-05-03 16:40     ` [PATCH v4] " Ralf Thielow
2017-05-03 17:29       ` Matthias Rüster
2017-05-04 12:53         ` Ralf Thielow
2017-05-04 17:08       ` [PATCH v5] " Ralf Thielow
2017-05-04 18:14         ` Matthias Rüster
2017-07-20 18:36 [PATCH] " Matthias Rüster
2017-07-21 15:11 ` [PATCH v2] " Ralf Thielow
2017-07-21 16:10   ` Junio C Hamano
2017-07-21 16:32     ` Ralf Thielow
2017-07-21 17:21       ` Junio C Hamano

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=CAN0XMOLW8J9vYWY8wgMPwZoDX6FHJQZqpwHf6VA-uBeN-00PwQ@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=simon@ruderich.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.