# Re: [PATCH v2 0/1] handling mistranslation reports 4 messages from 2015-08-16 to 2015-08-16. Participants: Jiang Xin, Philip Oakley. Thread: https://gitlist.dev/t/40110 ## Jiang Xin, 2015-08-16 05:46 Subject: Re: [PATCH v2 0/1] handling mistranslation reports Message-ID: URL: https://gitlist.dev/e/CANYiYbEKoF6GhezPmR1fGxRqTvZAE4L2xguvvwFEWqWBkOp9tw%40mail.gmail.com In-Reply-To: <1438640973-1452-1-git-send-email-philipoakley@iee.org> ``` 2015-08-04 6:29 GMT+08:00 Philip Oakley : > 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. -- Jiang Xin ``` ## Jiang Xin, 2015-08-16 07:56 Subject: [PATCH v3] po/README: Update directions for l10n contributors Message-ID: <30198223977cc51444ce3c3a61833fa9d7619dc7.1439704077.git.worldhello.net@gmail.com> URL: https://gitlist.dev/e/30198223977cc51444ce3c3a61833fa9d7619dc7.1439704077.git.worldhello.net%40gmail.com In-Reply-To: ``` From: Philip Oakley 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 Signed-off-by: Jiang Xin --- 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: +-------------------+ +------------------+ -- 2.5.0.rc2.34.gfbdeabf.dirty ``` ## Philip Oakley, 2015-08-16 18:54 Subject: Re: [PATCH v2 0/1] handling mistranslation reports Message-ID: <134837D8A3EE41ECBE65D228CC57818B@PhilipOakley> URL: https://gitlist.dev/e/134837D8A3EE41ECBE65D228CC57818B%40PhilipOakley In-Reply-To: ``` From: "Jiang Xin" > 2015-08-04 6:29 GMT+08:00 Philip Oakley : >> 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. Yes 0/1 was the cover letter and 1/1 was the actual patch. I have not found a way of sending, via my 'git send-email' (*), a single patch with its integrated cover-letter at the beginning. I can easily add short notes after a 3-dashes in the commit, but it is not the same as a cover-letter ... Hopefully, you got the 1/1. Unfortunately, the Git list is rejecting my patches (and just my patches), as sent via send-email, and at the moment I have no way of debugging and diagnosing that issue. >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. Thanks. Will review. > > -- > Jiang Xin > -- (*) https://groups.google.com/forum/#!topic/msysgit/U85cSXd-Uv0 ``` ## Philip Oakley, 2015-08-16 18:59 Subject: Re: [PATCH v3] po/README: Update directions for l10n contributors Message-ID: <766F16CA94884DEBAEFC7A594DE64529@PhilipOakley> URL: https://gitlist.dev/e/766F16CA94884DEBAEFC7A594DE64529%40PhilipOakley In-Reply-To: <30198223977cc51444ce3c3a61833fa9d7619dc7.1439704077.git.worldhello.net@gmail.com> ``` From: "Jiang Xin" > From: Philip Oakley > > 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 > Signed-off-by: Jiang Xin > --- > 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. > + OK. That's a reasonable summary of what the reader should do. > + > +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: > > +-------------------+ +------------------+ > -- Confirmed-by: Philip Oakley -- ```