Re: Glossary for bootstrapping Git translations

From: Jiang Xin <worldhello.net@gmail.com>
Date: Apr 30, 2012, 13:17 UTC
Message-ID: <CANYiYbH7g5JRvEQ_b9sEP72zR+yrAj+cQbemi_nsFTSa+QRgEw@mail.gmail.com>
In-Reply-To: <CACBZZX7H8qB05qc+ovaeFJ_qR3bF7=uWq6bjOHq8+_YNDLTu2g@mail.gmail.com>

2012/4/30 Ævar Arnfjörð Bjarmason <avarab@gmail.com>:

> Over the weekend I started the Icelandic translation of Git beyond the
> current test messages that are there in po/is.po already.

I just created new branch 'maint' in git-po repository on GitHub, and generated two different 'git.pot' files yesterday. The recommended workflow for a new language:

1. After fork the git-l10n/git-po on GitHub, checkout the 'maint'
    branch, or create a new tracking branch based on it.

2. Create your initial XX.po file, tranlate, commit, and push to
    your own fork.

3. Send a GitHub pull request to the 'maint' branch of git-l10n/git-po.

4. The l10n coordinator merge your commit to the 'maint' branch,
    so your translation may appear in git next maintainence version,
    i. e. 1.7.10.1.

5. The l10n coordinator will do a second merge, so new commit in
    'maint' branch will merge back to the 'master' branch.

6. Update your XX.po in 'master' branch, translate, commit, and
     send new pull request.

7. The l10n coordinator will merge your updates to 'master' branch,
     and your translations will come with git 1.7.11.

L10N team leaders may already noticed these changes, as I @ all team leaders in the commit comments.

* https://github.com/git-l10n/git-po/commit/cd1e74874049c8ba8e510f2fae064e510cccd32b#commitcomment-1271645
* https://github.com/git-l10n/git-po/commit/df3ef6fb98a276fa62bbcf129d40307b00253588#commitcomment-1271639

-- Jiang Xin