From: Ralf Thielow <ralf.thielow@gmail.com>
To: trast@student.ethz.ch, jk@jk.gs, stimming@tuhh.de
Cc: git@vger.kernel.org, Jiang Xin <worldhello.net@gmail.com>
Subject: Re: [PATCH/RFC] l10n: de.po: translate 2 new messages
Date: Fri, 7 Sep 2012 19:12:30 +0200 [thread overview]
Message-ID: <CAN0XMOLUpt+fdT-=wsTg_+m_VGaKpvHuC8H-h7rBozN+iFfVMQ@mail.gmail.com> (raw)
In-Reply-To: <CAN0XMOL9cxy8noicF-P-cjLkw76Zf3Uyu4C2RqbcTYrug5+w8Q@mail.gmail.com>
On Fri, Sep 7, 2012 at 7:05 PM, Ralf Thielow <ralf.thielow@gmail.com> wrote:
> On Fri, Sep 7, 2012 at 6:36 PM, Ralf Thielow <ralf.thielow@gmail.com> wrote:
>> On Fri, Sep 7, 2012 at 12:31 PM, Jiang Xin <worldhello.net@gmail.com> wrote:
>>> I just notice that the 1st line of the orignal message below has
>>> only 56 characters, much shorter than other lines. It is because
>>> this is a warning message, and would add a prefix: "warning: ".
>>>
>>> #: builtin/push.c:151
>>> msgid ""
>>> "push.default is unset; its implicit value is changing in\n"
>>> "Git 2.0 from 'matching' to 'simple'. To squelch this message\n"
>>> "and maintain the current behavior after the default changes, use:\n"
>>> "\n"
>>> " git config --global push.default matching\n"
>>>
>>> For this reason, translations as follows are not well-formed.
>>> So I rewind git-po, and your commits may need a bit amend.
>>>
>>
>> I admit that I don't really understand what you mean. I can't
>> see a big difference in line lengths. It's not more than others
>
> I got it. This "warning: " is added automatically.
> Sorry
The update would looks like this:
msgstr ""
"'push.default' ist nicht gesetzt; der implizit gesetzte Wert\n"
"wird in Git 2.0 von 'matching' nach 'simple' geändert. Um diese Meldung zu\n"
"unterdrücken und das aktuelle Verhalten nach Änderung des Standardwertes\n"
...
next prev parent reply other threads:[~2012-09-07 17:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 17:11 [PATCH/RFC] l10n: de.po: translate 2 new messages Ralf Thielow
2012-09-05 17:21 ` Ralf Thielow
2012-09-06 16:44 ` Thomas Rast
2012-09-06 17:15 ` Ralf Thielow
2012-09-07 10:31 ` Jiang Xin
2012-09-07 16:36 ` Ralf Thielow
2012-09-07 17:05 ` Ralf Thielow
2012-09-07 17:12 ` Ralf Thielow [this message]
2012-09-07 17:44 ` Junio C Hamano
2012-09-07 19:05 ` [PATCH 0/2] multiline prefixes on messages Ralf Thielow
2012-09-07 19:05 ` [PATCH 1/2] advice: extract function to print messages with prefix Ralf Thielow
2012-09-07 19:32 ` Junio C Hamano
2012-09-07 19:56 ` Ralf Thielow
2012-09-07 20:52 ` Junio C Hamano
2012-09-07 21:09 ` Ralf Thielow
2012-09-07 21:16 ` Junio C Hamano
2012-09-07 21:20 ` Junio C Hamano
2012-09-07 19:05 ` [PATCH 2/2] i18n: mark prefix "warning:" for translation 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='CAN0XMOLUpt+fdT-=wsTg_+m_VGaKpvHuC8H-h7rBozN+iFfVMQ@mail.gmail.com' \
--to=ralf.thielow@gmail.com \
--cc=git@vger.kernel.org \
--cc=jk@jk.gs \
--cc=stimming@tuhh.de \
--cc=trast@student.ethz.ch \
--cc=worldhello.net@gmail.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).