From: Jiang Xin <worldhello.net@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Peter Krefting" <peter@softwolves.pp.se>
Cc: git@vger.kernel.org
Subject: [L10N] New po/git.pot generated for Git 1.7.10-rc1
Date: Fri, 16 Mar 2012 21:43:01 +0800 [thread overview]
Message-ID: <CANYiYbGZ7mQaqyAxOiHOdMfDSy0VsDgLaWiBTTaZ30asiSU0nQ@mail.gmail.com> (raw)
L10n team leaders,
It time to update your translations to the new git.pot for Git 1.7.10-rc1.
A new "po/git.pot" file is generated in the l10 coordinator repository:
https://github.com/git-l10n/git-po/
Updates of "po/git.pot" for this new revision since last update:
* 1 new l10n message at line: 3361
In order to update your translations, l10n team leaders should:
1. Pull from the l10 coordinator repository;
2. update your locale file, make a commit;
3. and then push your commit to the repository of your l10n team.
You can update locale file use this command:
msgmerge --add-location --backup=off -U XX.po git.pot
After push the commits with new translations to your forked repository
of your l10n team, please send a pull request to the 10n coordinator
repository on GitHub. But before that it is helpful to check your locale
file and new commits as follows:
* Do a syntax check on XX.po
msgfmt -o /dev/null --check --statistics XX.po
* Check your commit logs, and make sure that if there are non-ascii
characters, the commit logs must have a proper encode setting.
A helper script can help:
po-helper.sh check commits
The helper script can be found at:
* https://github.com/gotgit/git-po-zh_CN/raw/po-helper/po/po-helper.sh
--
Jiang Xin
next reply other threads:[~2012-03-16 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 13:43 Jiang Xin [this message]
[not found] ` <4F64C837.10700@in.waw.pl>
2012-03-18 2:20 ` [L10N] New po/git.pot generated for Git 1.7.10-rc1 Jiang Xin
2012-03-18 6:04 ` Zbigniew Jędrzejewski-Szmek
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=CANYiYbGZ7mQaqyAxOiHOdMfDSy0VsDgLaWiBTTaZ30asiSU0nQ@mail.gmail.com \
--to=worldhello.net@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peter@softwolves.pp.se \
/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).