{"thread":{"id":"40110","subject":"Re: [PATCH v2 0/1] handling mistranslation reports","startedAt":"2015-08-16T05:46:07Z","lastAt":"2015-08-16T18:59:04Z","messageCount":4,"participants":["Jiang Xin","Philip Oakley"],"isPatch":true,"patchVersion":2,"patchTotal":1},"messages":[{"id":"268144","messageId":"CANYiYbEKoF6GhezPmR1fGxRqTvZAE4L2xguvvwFEWqWBkOp9tw@mail.gmail.com","threadId":"40110","inReplyTo":"1438640973-1452-1-git-send-email-philipoakley@iee.org","subject":"Re: [PATCH v2 0/1] handling mistranslation reports","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2015-08-16T05:46:07Z","receivedAt":"2015-08-16T05:46:07Z","isPatch":true,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"2015-08-04 6:29 GMT+08:00 Philip Oakley :\n> Hi Jiang,\n>\n> This is my updated patch based on your feedback at $gmane/275141\n> and $gmane/275142.\n>\n> I've used most of your wording, though have retained a comment on\n> considering if the translation could be held here.\n>\n> My original commentary is below, along with the inter-diff between versions.\n>\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> This patch separates out the three different aspects that caused confusion\n> and explicitly brings out what to do for translations not currently held here.\n>\n> I hope my suggested patch will fit with your approach and ask for comments\n> (or Ack / Nack).\n>\n> regards\n>\n> Philip\n>\n> [1] https://groups.google.com/forum/#!topic/git-users/rK5oU6k8Tzw\n>\n> Interdiff:\n\nThe subject is \"[PATCH v2 0/1]\" and I wonder where is the real patch\nfile (\"v2 1/1\")\naside of this cover letter. But today I have time to read it\ncarefully, and I know\nthis is a fixup commit.\n\nI squash this reroll to last commit for this series, and simplify both\nthe commit\nand the commit log. See patch v3 in the next email.\n\n-- \nJiang Xin\n"},{"id":"268147","messageId":"30198223977cc51444ce3c3a61833fa9d7619dc7.1439704077.git.worldhello.net@gmail.com","threadId":"40110","inReplyTo":"CANYiYbEKoF6GhezPmR1fGxRqTvZAE4L2xguvvwFEWqWBkOp9tw@mail.gmail.com","subject":"[PATCH v3] po/README: Update directions for l10n contributors","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2015-08-16T07:56:56Z","receivedAt":"2015-08-16T07:56:56Z","isPatch":true,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"From: Philip Oakley \n\nSome Linux distributions (such as Ubuntu) have their own l10n workflows,\nand their translations may be different. Add notes for this case for\nl10n translators.\n\nSigned-off-by: Philip Oakley \nSigned-off-by: Jiang Xin \n---\n po/README | 19 +++++++++++++++++++\n 1 file changed, 19 insertions(+)\n\ndiff --git a/po/README b/po/README\nindex d8c9111..fef4c0f 100644\n--- a/po/README\n+++ b/po/README\n@@ -10,10 +10,26 @@ 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+Sometime, contributors may find that the translations of their Git\n+distributions are quite different with the translations of the\n+corresponding version from Git official. This is because some Git\n+distributions (such as from Ubuntu, etc.) have their own l10n workflow.\n+For this case, wrong translations should be reported and fixed through\n+their workflows.\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@@ -23,6 +39,9 @@ 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-- \n2.5.0.rc2.34.gfbdeabf.dirty\n"},{"id":"268153","messageId":"134837D8A3EE41ECBE65D228CC57818B@PhilipOakley","threadId":"40110","inReplyTo":"CANYiYbEKoF6GhezPmR1fGxRqTvZAE4L2xguvvwFEWqWBkOp9tw@mail.gmail.com","subject":"Re: [PATCH v2 0/1] handling mistranslation reports","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.org","sentAt":"2015-08-16T18:54:27Z","receivedAt":"2015-08-16T18:54:27Z","isPatch":true,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"From: \"Jiang Xin\" \n> 2015-08-04 6:29 GMT+08:00 Philip Oakley :\n>> Hi Jiang,\n>>\n>> This is my updated patch based on your feedback at $gmane/275141\n>> and $gmane/275142.\n>>\n>> I've used most of your wording, though have retained a comment on\n>> considering if the translation could be held here.\n>>\n>> My original commentary is below, along with the inter-diff between \n>> versions.\n>>\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 \n>> which\n>> is not held in your tree, but the README does include how to start a \n>> new\n>> translation. This led to a misunderstanding with regard to which \n>> aspect\n>> of the README was being referred to (private discussion with Junio).\n>>\n>> This patch separates out the three different aspects that caused \n>> confusion\n>> and explicitly brings out what to do for translations not currently \n>> held here.\n>>\n>> I hope my suggested patch will fit with your approach and ask for \n>> comments\n>> (or Ack / Nack).\n>>\n>> regards\n>>\n>> Philip\n>>\n>> [1] https://groups.google.com/forum/#!topic/git-users/rK5oU6k8Tzw\n>>\n>> Interdiff:\n>\n> The subject is \"[PATCH v2 0/1]\" and I wonder where is the real patch\n> file (\"v2 1/1\")\n> aside of this cover letter.\n\nYes 0/1 was the cover letter and 1/1 was the actual patch.\n\nI have not found a way of sending, via my 'git send-email' (*), a single \npatch with its integrated cover-letter at the beginning. I can easily \nadd short notes after a 3-dashes in the commit, but it is not the same \nas a cover-letter ...\n\nHopefully, you got the 1/1. Unfortunately, the Git list is rejecting my \npatches (and just my patches), as sent via send-email, and at the moment \nI have no way of debugging and diagnosing that issue.\n\n>But today I have time to read it\n> carefully, and I know\n> this is a fixup commit.\n>\n> I squash this reroll to last commit for this series, and simplify both\n> the commit\n> and the commit log. See patch v3 in the next email.\n\nThanks. Will review.\n\n>\n> -- \n> Jiang Xin\n> --\n(*) https://groups.google.com/forum/#!topic/msysgit/U85cSXd-Uv0 \n"},{"id":"268154","messageId":"766F16CA94884DEBAEFC7A594DE64529@PhilipOakley","threadId":"40110","inReplyTo":"30198223977cc51444ce3c3a61833fa9d7619dc7.1439704077.git.worldhello.net@gmail.com","subject":"Re: [PATCH v3] po/README: Update directions for l10n contributors","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.org","sentAt":"2015-08-16T18:59:04Z","receivedAt":"2015-08-16T18:59:04Z","isPatch":true,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"From: \"Jiang Xin\" \n> From: Philip Oakley \n>\n> Some Linux distributions (such as Ubuntu) have their own l10n \n> workflows,\n> and their translations may be different. Add notes for this case for\n> l10n translators.\n>\n> Signed-off-by: Philip Oakley \n> Signed-off-by: Jiang Xin \n> ---\n> po/README | 19 +++++++++++++++++++\n> 1 file changed, 19 insertions(+)\n>\n> diff --git a/po/README b/po/README\n> index d8c9111..fef4c0f 100644\n> --- a/po/README\n> +++ b/po/README\n> @@ -10,10 +10,26 @@ 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 file \n> in\n> this directory to see whether a dedicated repository for your language \n> XX\n> exists. Fork the dedicated repository and start to work if it exists.\n>\n> +Sometime, contributors may find that the translations of their Git\n> +distributions are quite different with the translations of the\n> +corresponding version from Git official. This is because some Git\n> +distributions (such as from Ubuntu, etc.) have their own l10n \n> workflow.\n> +For this case, wrong translations should be reported and fixed \n> through\n> +their workflows.\n> +\n\nOK. That's a reasonable summary of what the reader should do.\n\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> @@ -23,6 +39,9 @@ coordinate among yourselves and nominate the team \n> 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\nConfirmed-by: Philip Oakley \n-- \n"}]}