[L10N] Kickoff of translation for Git 2.6.0 round 1

[L10N] Kickoff of translation for Git 2.6.0 round 1

[Jiang Xin]

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

Re: [L10N] Kickoff of translation for Git 2.6.0 round 1

[Jean-Noël AVILA]

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.

Some strings may be difficult to translate in some languages. We need a first 
set of commits to correct these errors, before updating the translations. In a 
longer term, a style/i18n guideline and checker would be very useful.

My two cents.

Jean-Noel

Re: [L10N] Kickoff of translation for Git 2.6.0 round 1

[Jiang Xin]

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

Most of them are comes from the "die*" function call (If we check the
"die*" funtion call, we can see more inconsistent leading characters).
Because it's hardly for the normal operations to fall into these code
blocks, so most people won't find this issue.  If we care, we can fix
them, but I suspect these fixes could catch up this update window.

> Some strings may be difficult to translate in some languages.

Maybe the following is not the most difficult to translate, but I also
want to point here.  Some messages have multiple specifiers,
for this case we can order the specifiers in our translation text,
such as:

    msgid   "'%s' for '%s' is not a valid timestamp"
    msgstr  "'%2$s' 的值 '%1$s' 不是一个有效的时间戳"

I think the most difficult to translate messages you pointed for
this round are:

    +msgid   "'git bisect $TERM_BAD' can take only one argument."

    +msgid   "Invalid command: you're currently in a
$TERM_BAD/$TERM_GOOD bisect."

    +msgid   "You need to give me at least one $bad_syn and one $good_syn "
    +        "revision.\n"
    +        "(You can use \"git bisect $bad_syn\" and \"git bisect
$good_syn\" "
    +        "for that.)"

Before we can do something to make a l10n-friendly git-bisect,
we have to leave $TERM_BAD / $TERM_GOOD / $good_syn
/ $bad_syn unchanged.


-- 
Jiang Xin

Re: [L10N] Kickoff of translation for Git 2.6.0 round 1

[John Keeping]

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")

Re: [L10N] Kickoff of translation for Git 2.6.0 round 1

[Jiang Xin]

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.