{"thread":{"id":"39995","subject":"Re: [PATCH 0/1] handling mistranslation reports (resend)","startedAt":"2015-08-02T15:50:58Z","lastAt":"2015-08-03T13:49:37Z","messageCount":3,"participants":["Jiang Xin","Philip Oakley"],"isPatch":true,"patchVersion":1,"patchTotal":1},"messages":[{"id":"267287","messageId":"CANYiYbGbMvPOerwQHSKRzqR8HfsTm-6fV6R+gefiX4hr1d4=SA@mail.gmail.com","threadId":"39995","inReplyTo":"1438522955-6076-1-git-send-email-philipoakley@iee.org","subject":"Re: [PATCH 0/1] handling mistranslation reports (resend)","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2015-08-02T15:50:58Z","receivedAt":"2015-08-02T15:50:58Z","isPatch":true,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"2015-08-02 21:42 GMT+08:00 Philip Oakley <philipoakley@iee.org>:\n> [Resent as first email was not picked up by vger, apologies for any duplicates]\n>\n> Hi Jiang,\n>\n> Recently, on the 'Git for human beings' list, a user reported a\n> mistranslation and asked if/what could be done, with a suggested\n> alternate text [1].\n>\n> I pointed the user at the po/README for general guidance.\n> Unfortunately the user was noting a Spanish (es) translation error which\n> is not held in your tree, but the README does include how to start a new\n> translation. This led to a misunderstanding with regard to which aspect\n> of the README was being referred to (private discussion with Junio).\n>\n\nSome linux distribution, such as Ubuntu, has its own l10n workflow for\neach package (including git.git), and not works well with the upstream.\nFor example, Ubuntu makes a one-time import from our Git translations\n(from some obsoleted version) into their l10n databases, and their\ncontributors will start to translate using their web UI, and never sync\nwith our upstream again.  They ubuntu may have more languages\nsupport, but they may also have more bugs.  Sometime,  their bugs\nwill be reported to our upstream, for example:\n\n* http://thread.gmane.org/gmane.comp.version-control.git/239130/focus=239130\n\nWe could add some clues for this case if the user can not find\nthe resource to contribute.\n\n--\nJiang Xin\n"},{"id":"267288","messageId":"CANYiYbFvackgJnqR4yahUPT2zE-kTAhQJnvzeUp-FsC-U24-dw@mail.gmail.com","threadId":"39995","inReplyTo":"1438522955-6076-2-git-send-email-philipoakley@iee.org","subject":"Re: [PATCH 1/1] po/README: split out the different contribution types","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2015-08-02T16:05:46Z","receivedAt":"2015-08-02T16:05:46Z","isPatch":true,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"2015-08-02 21:42 GMT+08:00 Philip Oakley <philipoakley@iee.org>:\n> Separate out the three different contribution styles for existing, new,\n> and wider mis-translation contributions, with suitable headings for easy\n> reference.\n>\n> In particular highlight the appropriate action should a Git\n> mis-translation be from a different distribution. i.e. initially report\n> to that usptream, but also consider if it could be coordinated here.\n>\n> While here, add surrounding headings, and reference the lanaguage codes.\n>\n> Signed-off-by: Philip Oakley <philipoakley@iee.org>\n> ---\n>  po/README | 24 ++++++++++++++++++++++++\n>  1 file changed, 24 insertions(+)\n>\n> diff --git a/po/README b/po/README\n> index d8c9111..b54b3c6 100644\n> --- a/po/README\n> +++ b/po/README\n> @@ -10,19 +10,43 @@ coordinates our localization effort in the l10 coordinator repository:\n>\n>          https://github.com/git-l10n/git-po/\n>\n> +The two character language translation codes are defined by ISO_639-1, as\n> +stated in the gettext(1) full manual, appendix A.1, Usual Language Codes.\n> +\n> +\n> +Contributing to an existing translation\n> +---------------------------------------\n>  As a contributor for a language XX, you should first check TEAMS file in\n>  this directory to see whether a dedicated repository for your language XX\n>  exists. Fork the dedicated repository and start to work if it exists.\n>\n> +\n> +Creating a new language translation\n> +-----------------------------------\n>  If you are the first contributor for the language XX, please fork this\n>  repository, prepare and/or update the translated message file po/XX.po\n>  (described later), and ask the l10n coordinator to pull your work.\n>\n> +\n> +Reporting mis-translations\n> +--------------------------\n> +First, confirm that your language translation is managed by this group.\n> +Initially any translation mistake should be reported to the appropriate\n> +upstream team. If not managed by this group, and the translation has a\n> +suitable licence, consider suggesting that the translation could be\n> +included here (see 'new language translation' above).\n> +\nFirst, find the right place to report.  If there is a YourLanguage.po here,\nand you can find the bug in it, then here is the right place for you to\nreport.  But if not, maybe your Git distribution (such as from Ubuntu)\nmay have its own l10n workflow, and not work well with our git\nupstream. For this case, you should report bug to them...\n\n(I'm not a native English speaker, so correct me)\n\n> +\n> +Forming a Team\n> +--------------\n>  If there are multiple contributors for the same language, please first\n>  coordinate among yourselves and nominate the team leader for your\n>  language, so that the l10n coordinator only needs to interact with one\n>  person per language.\n>\n> +\n> +Translation Process Flow\n> +------------------------\n>  The overall data-flow looks like this:\n>\n>      +-------------------+            +------------------+\n> --\n> 2.3.1\n>\n\n-- \nJiang Xin\n"},{"id":"267312","messageId":"66FDED7A4D18442A8DF6A35A22B256CC@PhilipOakley","threadId":"39995","inReplyTo":"CANYiYbFvackgJnqR4yahUPT2zE-kTAhQJnvzeUp-FsC-U24-dw@mail.gmail.com","subject":"Re: [PATCH 1/1] po/README: split out the different contribution types","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.org","sentAt":"2015-08-03T13:49:37Z","receivedAt":"2015-08-03T13:49:37Z","isPatch":true,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"From: \"Jiang Xin\" <worldhello.net@gmail.com>\n> 2015-08-02 21:42 GMT+08:00 Philip Oakley <philipoakley@iee.org>:\n>> Separate out the three different contribution styles for existing, \n>> new,\n>> and wider mis-translation contributions, with suitable headings for \n>> easy\n>> reference.\n>>\n>> In particular highlight the appropriate action should a Git\n>> mis-translation be from a different distribution. i.e. initially \n>> report\n>> to that usptream, but also consider if it could be coordinated here.\n>>\n>> While here, add surrounding headings, and reference the lanaguage \n>> codes.\n>>\n>> Signed-off-by: Philip Oakley <philipoakley@iee.org>\n>> ---\n>>  po/README | 24 ++++++++++++++++++++++++\n>>  1 file changed, 24 insertions(+)\n>>\n>> diff --git a/po/README b/po/README\n>> index d8c9111..b54b3c6 100644\n>> --- a/po/README\n>> +++ b/po/README\n>> @@ -10,19 +10,43 @@ coordinates our localization effort in the l10 \n>> coordinator repository:\n>>\n>>          https://github.com/git-l10n/git-po/\n>>\n>> +The two character language translation codes are defined by \n>> ISO_639-1, as\n>> +stated in the gettext(1) full manual, appendix A.1, Usual Language \n>> Codes.\n>> +\n>> +\n>> +Contributing to an existing translation\n>> +---------------------------------------\n>>  As a contributor for a language XX, you should first check TEAMS \n>> file in\n>>  this directory to see whether a dedicated repository for your \n>> language XX\n>>  exists. Fork the dedicated repository and start to work if it \n>> exists.\n>>\n>> +\n>> +Creating a new language translation\n>> +-----------------------------------\n>>  If you are the first contributor for the language XX, please fork \n>> this\n>>  repository, prepare and/or update the translated message file \n>> po/XX.po\n>>  (described later), and ask the l10n coordinator to pull your work.\n>>\n>> +\n>> +Reporting mis-translations\n>> +--------------------------\n>> +First, confirm that your language translation is managed by this \n>> group.\n>> +Initially any translation mistake should be reported to the \n>> appropriate\n>> +upstream team. If not managed by this group, and the translation has \n>> a\n>> +suitable licence, consider suggesting that the translation could be\n>> +included here (see 'new language translation' above).\n>> +\n> First, find the right place to report.  If there is a YourLanguage.po \n> here,\n> and you can find the bug in it, then here is the right place for you \n> to\n> report.  But if not, maybe your Git distribution (such as from Ubuntu)\n> may have its own l10n workflow, and not work well with our git\n> upstream. For this case, you should report bug to them...\n>\n> (I'm not a native English speaker, so correct me)\n>\n\nThanks. I'll work up your comments and try sending a formal V2 patch\n to the list. I'll also include about other workflows for other \ndistributions.\n\nWould I be right that there were no issues with the splitting into the \nseparate headings?\n\n>> +\n>> +Forming a Team\n>> +--------------\n>>  If there are multiple contributors for the same language, please \n>> first\n>>  coordinate among yourselves and nominate the team leader for your\n>>  language, so that the l10n coordinator only needs to interact with \n>> one\n>>  person per language.\n>>\n>> +\n>> +Translation Process Flow\n>> +------------------------\n>>  The overall data-flow looks like this:\n>>\n>>      +-------------------+            +------------------+\n>> --\n>> 2.3.1\n>>\n>\n> -- \n> Jiang Xin\n>\n--\nPhilip \n"}]}