2012/2/13 Junio C Hamano <gitster@xxxxxxxxx>: > Jiang Xin <worldhello.net@xxxxxxxxx> writes: > >> Junio has a suggestion on how to contrib l10n for git, and you can see the >> discussion here: http://article.gmane.org/gmane.comp.version-control.git/189584. >> >> Seems that the suggested git-po repo has not been setup yet, so let me >> have a try. >> >> 1. Repositiry git-po is hosted on GitHub: https://github.com/gotgit/git-po/ >> >> 2. I made a commit on the maint branch with a initial version of 'po/git.pot' >> https://github.com/gotgit/git-po/commit/4247a7a9d39e2a74ce1d58e5eb1f5e5d87977989 This commit is based on current maint branch. Since the translated po files will first in 1.7.10, so the initial pot file should be generated from master branch. The pot file from the master branch has 10 new messages than from the maint branch. For clarity, I removed the maint and other branches except the master branch, and made a new commit. > Somebody needs to eyeball this commit before anything else happens on top > of it, so that if there is a glaring mistake it can be caught before it > spreads to affect work by translators for various languages. So please check this commit with the updated pot file: https://github.com/gotgit/git-po/commit/816049b7ec0e5f452c77a4c4e71e2cb40a0ccb45 Please note In this commit I removed one line from the 'po/.gitignore' file. As a translater for Chinese, I also made a commit with the translated po file 'po/zh_CN.po' in branch master-zh-cn (merged back to master branch). >> >> I have a question, which version of po should be maintained? master >> branch or maint branch. > > I would say for this round the git-po repository and its pot file should > pick up whatever new translatable strings are added to 'master'. > > After this is merged in 1.7.10, we may want to maintain separate tracks, > but at this moment there is no point maintaining something mergeable to > 1.7.9.x maintenance track. > -- Jiang Xin -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html