I do not mind Chinese in the patch text (i.e. below), but I would have
preferred the above not to be in Chinese, which I do not read---I can
guess what 文件, 添加 and 删除 are, and I can also guess that 个 and 处
are units of counting, but nevertheless...
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.
Thanks for a patch.
[Footnote]
*1* Ah, another thing, shouldn't the title be labelled as l10n instead of
i18n?
...
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
I do not mind Chinese in the patch text (i.e. below), but I would have
preferred the above not to be in Chinese, which I do not read---I can
guess what 文件, 添加 and 删除 are, and I can also guess that 个 and 处
are units of counting, but nevertheless...
Such a stat line would be wonderful in an all-Chinese environment
though. I'm thinking perhaps it's a good idea to support
core.officialLocale (or workingLanguage). Commands that produce stuff
for outside like format-patch would prefer core.exchangeLanguage over
$LANG. Commands in blurred zone can learn --official option to ignore
$LANG.
We can then have a shared config with core.officialLocale =
en_US.UTF-8 somewhere in git.git. Developers of multi-nation companies
would be pleased, I think.
--
Duy
I do not mind Chinese in the patch text (i.e. below), but I would have
preferred the above not to be in Chinese, which I do not read---I can
guess what 文件, 添加 and 删除 are, and I can also guess that 个 and 处
are units of counting, but nevertheless...
Such a stat line would be wonderful in an all-Chinese environment
though. I'm thinking perhaps it's a good idea to support
core.officialLocale (or workingLanguage). Commands that produce stuff
for outside like format-patch would prefer core.exchangeLanguage over
$LANG. Commands in blurred zone can learn --official option to ignore
$LANG.
We can then have a shared config with core.officialLocale =
en_US.UTF-8 somewhere in git.git. Developers of multi-nation companies
would be pleased, I think.
For now we can also avoid this whole issue and just declare that
anything that's used for interchange or permanently stored
(git-format-patch output, reflogs, merge commit messages etc.) will be
in English.
For now we can also avoid this whole issue and just declare that
anything that's used for interchange or permanently stored
(git-format-patch output, reflogs, merge commit messages etc.) will be
in English.
An extreme case is: Hg translated 'hg --versoin' and broke many other software.
For example, redmine had to grep hg version properly using 'LC_ALL=C
hg --version'.
I think Duy‘s patch maybe better for such cases.
http://thread.gmane.org/gmane.comp.version-control.git/189453/focus=189509
The call of interactive_use makes translations only available for human
but not for interchange and permanently stored.
--
Jiang Xin