{"thread":{"id":"40279","subject":"[L10N] Kickoff of translation for Git 2.6.0 round 1","startedAt":"2015-09-05T02:17:54Z","lastAt":"2015-09-05T13:30:23Z","messageCount":5,"participants":["Jiang Xin","Jean-Noël AVILA","John Keeping"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"269470","messageId":"CANYiYbEVU7A2w999jqLQ=V35WM0WTo--RHJHW7Ocw0FfsmqmLg@mail.gmail.com","threadId":"40279","inReplyTo":null,"subject":"[L10N] Kickoff of translation for Git 2.6.0 round 1","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2015-09-05T02:17:54Z","receivedAt":"2015-09-05T02:17:54Z","isPatch":false,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"Hi,\n\nGit v2.6.0-rc0 has been released, and it's time to start new round of git l10n.\nThis time there are 123 updated messages need to be translated since last\nupdate:\n\n    l10n: git.pot: v2.6.0 round 1 (123 new, 41 removed)\n\n    Generate po/git.pot from v2.6.0-rc0-24-gec371ff for git v2.6.0 l10n\n    round 1.\n\n    Signed-off-by: Jiang Xin <worldhello.net@gmail.com>\n\nYou can get it from the usual place:\n\n    https://github.com/git-l10n/git-po/\n\nAs how to update your XX.po and help to translate Git, please see\n\"Updating a XX.po file\" and other sections in “po/README\" file.\n\n--\nJiang Xin\n"},{"id":"269476","messageId":"2019620.IQg8023dli@cayenne","threadId":"40279","inReplyTo":"CANYiYbEVU7A2w999jqLQ=V35WM0WTo--RHJHW7Ocw0FfsmqmLg@mail.gmail.com","subject":"Re: [L10N] Kickoff of translation for Git 2.6.0 round 1","fromName":"Jean-Noël AVILA","fromEmail":"jn.avila@free.fr","sentAt":"2015-09-05T10:02:00Z","receivedAt":"2015-09-05T10:02:00Z","isPatch":false,"sender":{"key":"jn.avila@free.fr","avatar":"https://avatars.githubusercontent.com/u/156172?v=4"},"body":"Le samedi 5 septembre 2015, 10:17:54 Jiang Xin a écrit :\n> Hi,\n> \n> Git v2.6.0-rc0 has been released, and it's time to start new round of git\n> l10n. This time there are 123 updated messages need to be translated since\n> last update:\n> \n>     l10n: git.pot: v2.6.0 round 1 (123 new, 41 removed)\n> \n>     Generate po/git.pot from v2.6.0-rc0-24-gec371ff for git v2.6.0 l10n\n>     round 1.\n> \n>     Signed-off-by: Jiang Xin <worldhello.net@gmail.com>\n> \n> You can get it from the usual place:\n> \n>     https://github.com/git-l10n/git-po/\n> \n> As how to update your XX.po and help to translate Git, please see\n> \"Updating a XX.po file\" and other sections in “po/README\" file.\n> \n> --\n> Jiang Xin\n\n\nSome new strings are not consistent with the actual set.\n\nFor instance, in the \"Could not ...\" strings were all with capitals, and some \nnew ones are not. Last time, I remarked strings which were almost exactly the \nsame (only difference was a final dot, if I remember). Some help strings were \nmixing different styles.\n\nSome strings may be difficult to translate in some languages. We need a first \nset of commits to correct these errors, before updating the translations. In a \nlonger term, a style/i18n guideline and checker would be very useful.\n\nMy two cents.\n\nJean-Noel\n"},{"id":"269485","messageId":"CANYiYbF3p-yHBhzyfU1WQhjRZEqjXotsQS+x5K2EbatnAGuJrw@mail.gmail.com","threadId":"40279","inReplyTo":"2019620.IQg8023dli@cayenne","subject":"Re: [L10N] Kickoff of translation for Git 2.6.0 round 1","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2015-09-05T13:14:18Z","receivedAt":"2015-09-05T13:14:18Z","isPatch":false,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"2015-09-05 18:02 GMT+08:00 Jean-Noël AVILA <jn.avila@free.fr>:\n> Le samedi 5 septembre 2015, 10:17:54 Jiang Xin a écrit :\n>> Hi,\n>>\n>> Git v2.6.0-rc0 has been released, and it's time to start new round of git\n>> l10n. This time there are 123 updated messages need to be translated since\n>> last update:\n>>\n>>     l10n: git.pot: v2.6.0 round 1 (123 new, 41 removed)\n>>\n>>     Generate po/git.pot from v2.6.0-rc0-24-gec371ff for git v2.6.0 l10n\n>>     round 1.\n>>\n>>     Signed-off-by: Jiang Xin <worldhello.net@gmail.com>\n>>\n>> You can get it from the usual place:\n>>\n>>     https://github.com/git-l10n/git-po/\n>>\n>> As how to update your XX.po and help to translate Git, please see\n>> \"Updating a XX.po file\" and other sections in “po/README\" file.\n>>\n>> --\n>> Jiang Xin\n>\n>\n> Some new strings are not consistent with the actual set.\n>\n> For instance, in the \"Could not ...\" strings were all with capitals, and some\n> new ones are not. Last time, I remarked strings which were almost exactly the\n> same (only difference was a final dot, if I remember). Some help strings were\n> mixing different styles.\n\nBefore this update, \"Could not\" vs \"could not\" is 50:40, and now it's 50:50.\n\n    $ grep 'Could not' po/git.pot  | wc -l\n    50\n\n    $ grep 'could not' po/git.pot  | wc -l\n    50\n\nMost of them are comes from the \"die*\" function call (If we check the\n\"die*\" funtion call, we can see more inconsistent leading characters).\nBecause it's hardly for the normal operations to fall into these code\nblocks, so most people won't find this issue.  If we care, we can fix\nthem, but I suspect these fixes could catch up this update window.\n\n> Some strings may be difficult to translate in some languages.\n\nMaybe the following is not the most difficult to translate, but I also\nwant to point here.  Some messages have multiple specifiers,\nfor this case we can order the specifiers in our translation text,\nsuch as:\n\n    msgid   \"'%s' for '%s' is not a valid timestamp\"\n    msgstr  \"'%2$s' 的值 '%1$s' 不是一个有效的时间戳\"\n\nI think the most difficult to translate messages you pointed for\nthis round are:\n\n    +msgid   \"'git bisect $TERM_BAD' can take only one argument.\"\n\n    +msgid   \"Invalid command: you're currently in a\n$TERM_BAD/$TERM_GOOD bisect.\"\n\n    +msgid   \"You need to give me at least one $bad_syn and one $good_syn \"\n    +        \"revision.\\n\"\n    +        \"(You can use \\\"git bisect $bad_syn\\\" and \\\"git bisect\n$good_syn\\\" \"\n    +        \"for that.)\"\n\nBefore we can do something to make a l10n-friendly git-bisect,\nwe have to leave $TERM_BAD / $TERM_GOOD / $good_syn\n/ $bad_syn unchanged.\n\n\n-- \nJiang Xin\n"},{"id":"269486","messageId":"20150905132148.GC27660@serenity.lan","threadId":"40279","inReplyTo":"CANYiYbF3p-yHBhzyfU1WQhjRZEqjXotsQS+x5K2EbatnAGuJrw@mail.gmail.com","subject":"Re: [L10N] Kickoff of translation for Git 2.6.0 round 1","fromName":"John Keeping","fromEmail":"john@keeping.me.uk","sentAt":"2015-09-05T13:21:48Z","receivedAt":"2015-09-05T13:21:48Z","isPatch":false,"sender":{"key":"john@keeping.me.uk","avatar":"https://avatars.githubusercontent.com/u/1702081?v=4"},"body":"On Sat, Sep 05, 2015 at 09:14:18PM +0800, Jiang Xin wrote:\n> 2015-09-05 18:02 GMT+08:00 Jean-Noël AVILA <jn.avila@free.fr>:\n> > Le samedi 5 septembre 2015, 10:17:54 Jiang Xin a écrit :\n> >> Hi,\n> >>\n> >> Git v2.6.0-rc0 has been released, and it's time to start new round of git\n> >> l10n. This time there are 123 updated messages need to be translated since\n> >> last update:\n> >>\n> >>     l10n: git.pot: v2.6.0 round 1 (123 new, 41 removed)\n> >>\n> >>     Generate po/git.pot from v2.6.0-rc0-24-gec371ff for git v2.6.0 l10n\n> >>     round 1.\n> >>\n> >>     Signed-off-by: Jiang Xin <worldhello.net@gmail.com>\n> >>\n> >> You can get it from the usual place:\n> >>\n> >>     https://github.com/git-l10n/git-po/\n> >>\n> >> As how to update your XX.po and help to translate Git, please see\n> >> \"Updating a XX.po file\" and other sections in “po/README\" file.\n> >>\n> >> --\n> >> Jiang Xin\n> >\n> >\n> > Some new strings are not consistent with the actual set.\n> >\n> > For instance, in the \"Could not ...\" strings were all with capitals, and some\n> > new ones are not. Last time, I remarked strings which were almost exactly the\n> > same (only difference was a final dot, if I remember). Some help strings were\n> > mixing different styles.\n> \n> Before this update, \"Could not\" vs \"could not\" is 50:40, and now it's 50:50.\n> \n>     $ grep 'Could not' po/git.pot  | wc -l\n>     50\n> \n>     $ grep 'could not' po/git.pot  | wc -l\n>     50\n\nNote that Documentation/CodingGuidelines has a section on error messages\nwhich says:\n\n - Do not end error messages with a full stop.\n\n - Do not capitalize (\"unable to open %s\", not \"Unable to open %s\")\n\n - Say what the error is first (\"cannot open %s\", not \"%s: cannot open\")\n"},{"id":"269487","messageId":"CANYiYbHknxRnDXLBwwj9-kB4JvciP3C0aQiCptL=hqWC-_1CVA@mail.gmail.com","threadId":"40279","inReplyTo":"20150905132148.GC27660@serenity.lan","subject":"Re: [L10N] Kickoff of translation for Git 2.6.0 round 1","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2015-09-05T13:30:23Z","receivedAt":"2015-09-05T13:30:23Z","isPatch":false,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"2015-09-05 21:21 GMT+08:00 John Keeping <john@keeping.me.uk>:\n> On Sat, Sep 05, 2015 at 09:14:18PM +0800, Jiang Xin wrote:\n>> 2015-09-05 18:02 GMT+08:00 Jean-Noël AVILA <jn.avila@free.fr>:\n>> > Le samedi 5 septembre 2015, 10:17:54 Jiang Xin a écrit :\n>> >> Hi,\n>> >>\n>> >> Git v2.6.0-rc0 has been released, and it's time to start new round of git\n>> >> l10n. This time there are 123 updated messages need to be translated since\n>> >> last update:\n>> >>\n>> >>     l10n: git.pot: v2.6.0 round 1 (123 new, 41 removed)\n>> >>\n>> >>     Generate po/git.pot from v2.6.0-rc0-24-gec371ff for git v2.6.0 l10n\n>> >>     round 1.\n>> >>\n>> >>     Signed-off-by: Jiang Xin <worldhello.net@gmail.com>\n>> >>\n>> >> You can get it from the usual place:\n>> >>\n>> >>     https://github.com/git-l10n/git-po/\n>> >>\n>> >> As how to update your XX.po and help to translate Git, please see\n>> >> \"Updating a XX.po file\" and other sections in “po/README\" file.\n>> >>\n>> >> --\n>> >> Jiang Xin\n>> >\n>> >\n>> > Some new strings are not consistent with the actual set.\n>> >\n>> > For instance, in the \"Could not ...\" strings were all with capitals, and some\n>> > new ones are not. Last time, I remarked strings which were almost exactly the\n>> > same (only difference was a final dot, if I remember). Some help strings were\n>> > mixing different styles.\n>>\n>> Before this update, \"Could not\" vs \"could not\" is 50:40, and now it's 50:50.\n>>\n>>     $ grep 'Could not' po/git.pot  | wc -l\n>>     50\n>>\n>>     $ grep 'could not' po/git.pot  | wc -l\n>>     50\n>\n> Note that Documentation/CodingGuidelines has a section on error messages\n> which says:\n>\n>  - Do not end error messages with a full stop.\n>\n>  - Do not capitalize (\"unable to open %s\", not \"Unable to open %s\")\n>\n>  - Say what the error is first (\"cannot open %s\", not \"%s: cannot open\")\n\nWow, we know how to fix.\n"}]}