From: Philip Oakley Date: Mon, 03 Aug 2015 13:49:37 GMT Subject: Re: [PATCH 1/1] po/README: split out the different contribution types Message-ID: <66FDED7A4D18442A8DF6A35A22B256CC@PhilipOakley> In-Reply-To: From: "Jiang Xin" > 2015-08-02 21:42 GMT+08:00 Philip Oakley : >> Separate out the three different contribution styles for existing, >> new, >> and wider mis-translation contributions, with suitable headings for >> easy >> reference. >> >> In particular highlight the appropriate action should a Git >> mis-translation be from a different distribution. i.e. initially >> report >> to that usptream, but also consider if it could be coordinated here. >> >> While here, add surrounding headings, and reference the lanaguage >> codes. >> >> Signed-off-by: Philip Oakley >> --- >> po/README | 24 ++++++++++++++++++++++++ >> 1 file changed, 24 insertions(+) >> >> diff --git a/po/README b/po/README >> index d8c9111..b54b3c6 100644 >> --- a/po/README >> +++ b/po/README >> @@ -10,19 +10,43 @@ 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. >> >> + >> +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. >> >> + >> +Reporting mis-translations >> +-------------------------- >> +First, confirm that your language translation is managed by this >> group. >> +Initially any translation mistake should be reported to the >> appropriate >> +upstream team. If not managed by this group, and the translation has >> a >> +suitable licence, consider suggesting that the translation could be >> +included here (see 'new language translation' above). >> + > First, find the right place to report. If there is a YourLanguage.po > here, > and you can find the bug in it, then here is the right place for you > to > report. But if not, maybe your Git distribution (such as from Ubuntu) > may have its own l10n workflow, and not work well with our git > upstream. For this case, you should report bug to them... > > (I'm not a native English speaker, so correct me) > Thanks. I'll work up your comments and try sending a formal V2 patch to the list. I'll also include about other workflows for other distributions. Would I be right that there were no issues with the splitting into the separate headings? >> + >> +Forming a Team >> +-------------- >> If there are multiple contributors for the same language, please >> first >> 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.3.1 >> > > -- > Jiang Xin > -- Philip