* [L10N] New po/git.pot generated for Git 1.7.10-rc1
@ 2012-03-16 13:43 Jiang Xin
[not found] ` <4F64C837.10700@in.waw.pl>
0 siblings, 1 reply; 3+ messages in thread
From: Jiang Xin @ 2012-03-16 13:43 UTC (permalink / raw)
To: Junio C Hamano, Ævar Arnfjörð Bjarmason,
Peter Krefting; +Cc: git
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
^ permalink raw reply [flat|nested] 3+ messages in thread[parent not found: <4F64C837.10700@in.waw.pl>]
* Re: [L10N] New po/git.pot generated for Git 1.7.10-rc1 [not found] ` <4F64C837.10700@in.waw.pl> @ 2012-03-18 2:20 ` Jiang Xin 2012-03-18 6:04 ` Zbigniew Jędrzejewski-Szmek 0 siblings, 1 reply; 3+ messages in thread From: Jiang Xin @ 2012-03-18 2:20 UTC (permalink / raw) To: Zbigniew Jędrzejewski-Szmek; +Cc: Git List 2012/3/18 Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>: >> https://github.com/git-l10n/git-po/ > > Hi, > the slash at the end makes this an invalid url to pull from: > > % git remote add l10n https://github.com/git-l10n/git-po/ > % git fetch l10n > error: RPC failed; result=22, HTTP code = 502 > fatal: The remote end hung up unexpectedly > > (Works fine with "https://github.com/git-l10n/git-po"). Next time I should write the url of the repo, not url of the project. git://github.com/git-l10n/git-po.git https://github.com/git-l10n/git-po.git Thanks. -- Jiang Xin ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [L10N] New po/git.pot generated for Git 1.7.10-rc1 2012-03-18 2:20 ` Jiang Xin @ 2012-03-18 6:04 ` Zbigniew Jędrzejewski-Szmek 0 siblings, 0 replies; 3+ messages in thread From: Zbigniew Jędrzejewski-Szmek @ 2012-03-18 6:04 UTC (permalink / raw) To: Jiang Xin; +Cc: Git List On 03/18/2012 03:20 AM, Jiang Xin wrote: > 2012/3/18 Zbigniew Jędrzejewski-Szmek<zbyszek@in.waw.pl>: >>> https://github.com/git-l10n/git-po/ >> >> Hi, >> the slash at the end makes this an invalid url to pull from: >> >> % git remote add l10n https://github.com/git-l10n/git-po/ >> % git fetch l10n >> error: RPC failed; result=22, HTTP code = 502 >> fatal: The remote end hung up unexpectedly >> >> (Works fine with "https://github.com/git-l10n/git-po"). > > Next time I should write the url of the repo, not url of the project. > > git://github.com/git-l10n/git-po.git > https://github.com/git-l10n/git-po.git Nope. https://github.com/git-l10n/git-po is better because it works in the browser too. https://github.com/git-l10n/git-po.git gives 404. - Zbyszek ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-03-18 6:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-16 13:43 [L10N] New po/git.pot generated for Git 1.7.10-rc1 Jiang Xin
[not found] ` <4F64C837.10700@in.waw.pl>
2012-03-18 2:20 ` Jiang Xin
2012-03-18 6:04 ` Zbigniew Jędrzejewski-Szmek
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).