v2Re: [PATCH v2 0/1] handling mistranslation reports

> Hi Jiang,
>
> This is my updated patch based on your feedback at $gmane/275141
> and $gmane/275142.
>
> I've used most of your wording, though have retained a comment on
> considering if the translation could be held here.
>
> My original commentary is below, along with the inter-diff between versions.
>
> -
> Recently, on the 'Git for human beings' list, a user reported a
> mistranslation and asked if/what could be done, with a suggested
> alternate text [1].
>
> I pointed the user at the po/README for general guidance.
> Unfortunately the user was noting a Spanish (es) translation error which
> is not held in your tree, but the README does include how to start a new
> translation. This led to a misunderstanding with regard to which aspect
> of the README was being referred to (private discussion with Junio).
>
> This patch separates out the three different aspects that caused confusion
> and explicitly brings out what to do for translations not currently held here.
>
> I hope my suggested patch will fit with your approach and ask for comments
> (or Ack / Nack).
>
> regards
>
> Philip
>
> [1] https://groups.google.com/forum/#!topic/git-users/rK5oU6k8Tzw
>
> Interdiff:

> From: Philip Oakley <philipoakley@iee.org>
>
> Some Linux distributions (such as Ubuntu) have their own l10n 
> workflows,
> and their translations may be different.  Add notes for this case for
> l10n translators.
>
> Signed-off-by: Philip Oakley <philipoakley@iee.org>
> Signed-off-by: Jiang Xin <worldhello.net@gmail.com>
> ---
> po/README | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/po/README b/po/README
> index d8c9111..fef4c0f 100644
> --- a/po/README
> +++ b/po/README
> @@ -10,10 +10,26 @@ coordinates our localization effort in the l10 
> coordinator repository:
>
>         https://github.com/git-l10n/git-po/
>
> +The two character language translation codes are defined by 
> ISO_639-1, as
> +stated in the gettext(1) full manual, appendix A.1, Usual Language 
> Codes.
> +
> +
> +Contributing to an existing translation
> +---------------------------------------
> As a contributor for a language XX, you should first check TEAMS file 
> in
> this directory to see whether a dedicated repository for your language 
> XX
> exists. Fork the dedicated repository and start to work if it exists.
>
> +Sometime, contributors may find that the translations of their Git
> +distributions are quite different with the translations of the
> +corresponding version from Git official. This is because some Git
> +distributions (such as from Ubuntu, etc.) have their own l10n 
> workflow.
> +For this case, wrong translations should be reported and fixed 
> through
> +their workflows.
> +

> +
> +Creating a new language translation
> +-----------------------------------
> If you are the first contributor for the language XX, please fork this
> repository, prepare and/or update the translated message file po/XX.po
> (described later), and ask the l10n coordinator to pull your work.
> @@ -23,6 +39,9 @@ coordinate among yourselves and nominate the team 
> leader for your
> language, so that the l10n coordinator only needs to interact with one
> person per language.
>
> +
> +Translation Process Flow
> +------------------------
> The overall data-flow looks like this:
>
>     +-------------------+            +------------------+
> -- 

> 2015-08-04 6:29 GMT+08:00 Philip Oakley <philipoakley@iee.org>:
>> Hi Jiang,
>>
>> This is my updated patch based on your feedback at $gmane/275141
>> and $gmane/275142.
>>
>> I've used most of your wording, though have retained a comment on
>> considering if the translation could be held here.
>>
>> My original commentary is below, along with the inter-diff between 
>> versions.
>>
>> -
>> Recently, on the 'Git for human beings' list, a user reported a
>> mistranslation and asked if/what could be done, with a suggested
>> alternate text [1].
>>
>> I pointed the user at the po/README for general guidance.
>> Unfortunately the user was noting a Spanish (es) translation error 
>> which
>> is not held in your tree, but the README does include how to start a 
>> new
>> translation. This led to a misunderstanding with regard to which 
>> aspect
>> of the README was being referred to (private discussion with Junio).
>>
>> This patch separates out the three different aspects that caused 
>> confusion
>> and explicitly brings out what to do for translations not currently 
>> held here.
>>
>> I hope my suggested patch will fit with your approach and ask for 
>> comments
>> (or Ack / Nack).
>>
>> regards
>>
>> Philip
>>
>> [1] https://groups.google.com/forum/#!topic/git-users/rK5oU6k8Tzw
>>
>> Interdiff:
>
> The subject is "[PATCH v2 0/1]" and I wonder where is the real patch
> file ("v2 1/1")
> aside of this  cover letter.

>But today I have time to read it
> carefully, and I know
> this is a fixup commit.
>
> I squash this reroll to last commit for this series, and simplify both
> the commit
> and the commit log.  See patch v3 in the next email.