Re: [PATCH] i18n: po for zh_cn
- From
Jiang Xin <worldhello.net@gmail.com>
- Date
- Feb 2, 2012, 04:47 UTC
- Message-ID
- <CANYiYbFM3U=z5z-BTj3F51wjBQ4naS00jsGYKWFXUysfzVJs2Q@mail.gmail.com>
- In-Reply-To
- <7vr4ye15kr.fsf@alter.siamese.dyndns.org>
2012/2/2 Junio C Hamano <gitster@pobox.com>:
Show 9 quoted lines
>> Git can speak Chinese now. > ... > I haven't decided what to do with this, though. If we are going to get > tons of l10n patches[*1*], it may make sense to have a separate clone of > git.git, with possibly a maintainer other than myself, forked at v1.7.9 > and updates _only_ files in po/ hierarchy. > > Let me think about how to manage the l10n patches a bit. >
It's really a problem. Nobody knowns all languages, so a seperate mail list may also have troble.
Since current format-patch -> send-email -> am not suitable for l10n, pull-request and outside seperate bug report maybe better.
- One langage, one l10n team with one repo on GitHub. - Project homepage write into the header of PO file, such as: "Language-Team: GitHub <https://github.com/gotgit/git/>\n" - Bug report not directly to this list, but use GitHub as an alternate for example. - As to the branch management, the same as Git or can be easily matched. as a example: master-zh-cn <-> master, maint-zh-cn <-> maint - Pull Request send to this mailing list.
> *1* Ah, another thing, shouldn't the title be labelled as l10n instead of > i18n?
yeah. not only should I update the brief commit log, but also filename should be zh_CN.po, not zh_cn.po.
-- Jiang Xin