From: Jiang Xin <worldhello.net@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Git List" <git@vger.kernel.org>,
"Ævar Arnfjörð" <avarab@gmail.com>,
"Alexander Shopov (Александър Шопов)" <lists@kambanaria.org>
Subject: Re: Bulgarian translation of git
Date: Mon, 13 Feb 2012 15:12:50 +0800 [thread overview]
Message-ID: <CANYiYbFYmGNE09fAeHL_uk+0s+yBapTs4BeGch7iCtWR_v9LXQ@mail.gmail.com> (raw)
In-Reply-To: <7vy5s7idxb.fsf@alter.siamese.dyndns.org>
2012/2/13 Junio C Hamano <gitster@pobox.com>:
> Jiang Xin <worldhello.net@gmail.com> 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
next prev parent reply other threads:[~2012-02-13 7:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 12:26 Bulgarian translation of git Alexander Shopov (Александър Шопов)
2012-02-13 2:46 ` Jiang Xin
2012-02-13 3:56 ` Junio C Hamano
2012-02-13 7:12 ` Jiang Xin [this message]
2012-02-13 8:07 ` Junio C Hamano
2012-02-13 8:52 ` Jiang Xin
2012-02-13 14:00 ` Jonathan Nieder
2012-02-13 15:43 ` Jiang Xin
2012-02-13 15:56 ` Jonathan Nieder
2012-02-13 18:52 ` Junio C Hamano
2012-02-15 3:28 ` Jiang Xin
2012-02-15 18:09 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANYiYbFYmGNE09fAeHL_uk+0s+yBapTs4BeGch7iCtWR_v9LXQ@mail.gmail.com \
--to=worldhello.net@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=lists@kambanaria.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).