From: Jiang Xin <worldhello.net@gmail.com>
To: John Keeping <john@keeping.me.uk>
Cc: "Jean-Noël AVILA" <jn.avila@free.fr>,
"Alexander Shopov" <ash@kambanaria.org>,
"Alex Henrie" <alexhenrie24@gmail.com>,
"Ralf Thielow" <ralf.thielow@googlemail.com>,
"Marco Paolone" <marcopaolone@gmail.com>,
"Marco Sousa" <marcomsousa@gmail.com>,
"Dimitriy Ryazantcev" <DJm00n@mail.ru>,
"Peter Krefting" <peter@softwolves.pp.se>,
"Trần Ngọc Quân" <vnwildman@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Git List" <git@vger.kernel.org>
Subject: Re: [L10N] Kickoff of translation for Git 2.6.0 round 1
Date: Sat, 5 Sep 2015 21:30:23 +0800 [thread overview]
Message-ID: <CANYiYbHknxRnDXLBwwj9-kB4JvciP3C0aQiCptL=hqWC-_1CVA@mail.gmail.com> (raw)
In-Reply-To: <20150905132148.GC27660@serenity.lan>
2015-09-05 21:21 GMT+08:00 John Keeping <john@keeping.me.uk>:
> On Sat, Sep 05, 2015 at 09:14:18PM +0800, Jiang Xin wrote:
>> 2015-09-05 18:02 GMT+08:00 Jean-Noël AVILA <jn.avila@free.fr>:
>> > Le samedi 5 septembre 2015, 10:17:54 Jiang Xin a écrit :
>> >> Hi,
>> >>
>> >> Git v2.6.0-rc0 has been released, and it's time to start new round of git
>> >> l10n. This time there are 123 updated messages need to be translated since
>> >> last update:
>> >>
>> >> l10n: git.pot: v2.6.0 round 1 (123 new, 41 removed)
>> >>
>> >> Generate po/git.pot from v2.6.0-rc0-24-gec371ff for git v2.6.0 l10n
>> >> round 1.
>> >>
>> >> Signed-off-by: Jiang Xin <worldhello.net@gmail.com>
>> >>
>> >> You can get it from the usual place:
>> >>
>> >> https://github.com/git-l10n/git-po/
>> >>
>> >> As how to update your XX.po and help to translate Git, please see
>> >> "Updating a XX.po file" and other sections in “po/README" file.
>> >>
>> >> --
>> >> Jiang Xin
>> >
>> >
>> > Some new strings are not consistent with the actual set.
>> >
>> > For instance, in the "Could not ..." strings were all with capitals, and some
>> > new ones are not. Last time, I remarked strings which were almost exactly the
>> > same (only difference was a final dot, if I remember). Some help strings were
>> > mixing different styles.
>>
>> Before this update, "Could not" vs "could not" is 50:40, and now it's 50:50.
>>
>> $ grep 'Could not' po/git.pot | wc -l
>> 50
>>
>> $ grep 'could not' po/git.pot | wc -l
>> 50
>
> Note that Documentation/CodingGuidelines has a section on error messages
> which says:
>
> - Do not end error messages with a full stop.
>
> - Do not capitalize ("unable to open %s", not "Unable to open %s")
>
> - Say what the error is first ("cannot open %s", not "%s: cannot open")
Wow, we know how to fix.
prev parent reply other threads:[~2015-09-05 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-05 2:17 [L10N] Kickoff of translation for Git 2.6.0 round 1 Jiang Xin
2015-09-05 10:02 ` Jean-Noël AVILA
2015-09-05 13:14 ` Jiang Xin
2015-09-05 13:21 ` John Keeping
2015-09-05 13:30 ` Jiang Xin [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='CANYiYbHknxRnDXLBwwj9-kB4JvciP3C0aQiCptL=hqWC-_1CVA@mail.gmail.com' \
--to=worldhello.net@gmail.com \
--cc=DJm00n@mail.ru \
--cc=alexhenrie24@gmail.com \
--cc=ash@kambanaria.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jn.avila@free.fr \
--cc=john@keeping.me.uk \
--cc=marcomsousa@gmail.com \
--cc=marcopaolone@gmail.com \
--cc=peter@softwolves.pp.se \
--cc=ralf.thielow@googlemail.com \
--cc=vnwildman@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).