Re: Bulgarian translation of git

Jiang Xin [off-list ref] 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

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.

3. As l10n coordinator for Chinese, I translate against the pot file, and
    the translated po file 'po/zh_CN.po' is commited in my own branch:
maint-zh-cn.
    You can find the commit in:
https://github.com/gotgit/git-po/commits/maint-zh-cn

4. I will merge the commit in branch maint-zh-cn back or other l10n
coordinators' contributes
    to maint 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.