Bulgarian translation of git

Hello,

I am Alexander Shopov and would like to volunteer for the Bulgarian translation of git po file if no one else is doing this. How should I contribute it back? Via this email list, via fork-push from github, or a patch?

Kind regards: al_shopov

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

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.

2012/2/10 "Alexander Shopov (Александър Шопов)" <lists@kambanaria.org>:

Jiang Xin <worldhello.net@gmail.com> writes:

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.

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.

2012/2/13 Junio C Hamano <gitster@pobox.com>:

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.

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).

Jiang Xin <worldhello.net@gmail.com> writes:

Thanks.

As far as I can tell, this adds git.pot while removes the entry to remove it from po/.gitignore (because now it is a tracked file), but there is no description on how this file was generated in the log message.

Please give a short description to the effect that it was mechanically created by running xgettext on the sources as of b6b3b6a (Update draft release notes to 1.7.10, 2012-02-10), or something like that.

Other than that, I do not immediately see anything objectionable in this commit; I would still appreciate an extra set of eyeballs or two from people who have worked on gitk and/or git-gui i18n/l10n infrastructure in the past, just in case I forgot to check some obvious/trivial gotchas.

I am also Cc'ing people who participated in git-gui and gitk l10n with more than a couple of commits to their po/ part, found by:

    $ cd git-gui/po &&
      git rev-list --parents HEAD . |
      while read commit parent
      do
        git log --pretty=short $parent..$commit^2 -- :/po
      done | git shortlog -n -e

(same for gitk-git)

Thanks.

2012/2/13 Junio C Hamano <gitster@pobox.com>:

Please check this commit with the updated pot file: https://github.com/gotgit/git-po/commit/master%5E ( The commit with the amended commit message can be access using the above URL, no longer how this commit is ammended latter.)

I add a prefix 'l10n:' to the new amended commit log, is it OK?

$ git show --stat master^
commit b55102542911326e8191500ff6f53a2e1d52e504
Author: Jiang Xin <worldhello.net@gmail.com>
Date:   Mon Feb 13 14:37:59 2012 +0800

    l10n: initial git.pot for 1.7.10 upcoming release

    The file 'po/git.pot' is generated using the command 'make pot'
    against git v1.7.9-209-gb6b3b (Update draft release notes to 1.7.10).

    Also removed the entry po/git.pot from po/.gitignore, since it is a
    tracked file.

    Signed-off-by: Jiang Xin <worldhello.net@gmail.com>

 po/.gitignore |    1 -
 po/git.pot    | 3431 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 3431 insertions(+), 1 deletions(-)

Junio C Hamano wrote:

I wonder if there's a simple to ask the gettext tools to make a po template including strings from both 'maint' and 'master'. (Hackish way demonstrated below.)

Hopefully that would make it easier for translators to keep both tracks well maintained at the same time. If a problem in the translation of a string shared by 'master' and 'maint' is only noticed while working on 'master', there would be no need to go through the "switch branches; make the change; switch back; merge" dance.

What do you think? Jonathan

2012/2/13 Jonathan Nieder <jrnieder@gmail.com>:

Translators on a new language may not like this. Translating the obsolete messages in pot file is boring and waste of time.

Failed if po/git.pot does not exist. touch one first?

Jiang Xin wrote:

[...]

Right, doing this for real require somehow removing stale messages, too, so the pot file would only contain messages from actively maintained releases (the tip of 'master' and 'maint').

Will experiment privately a little more.

Jonathan Nieder <jrnieder@gmail.com> writes:

I somehow think it is not such a big deal if l10n messages are not maintained for maintenance tracks at all, actually, given that our cycles for the master track have been 8-10 weeks long, which is not a long time to wait, compared to 5 years people survived without any ;-).

I squash the following in the pot initial commit, and update the commit log. commit: https://github.com/gotgit/git-po/commit/master%5E

Jiang Xin <worldhello.net@gmail.com> writes:

Yeah, that change is very sensible. I am surprised that nobody noticed it so far while this topic was discussed.