From: Jonathan Nieder <jrnieder@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "Cyrus.Evans" <cyrus_evans@163.com>, git <git@vger.kernel.org>,
Erik Faye-Lund <kusmabite@gmail.com>
Subject: Re: Applicatioin of contribution for Git Chinese version
Date: Sat, 16 Apr 2011 17:33:10 -0500 [thread overview]
Message-ID: <20110416223310.GA5149@elie> (raw)
In-Reply-To: <BANLkTi=29fvnLYVnsjpYXfaB20=H6D6fcg@mail.gmail.com>
Hi Cyrus,
Ævar Arnfjörð Bjarmason wrote:
> It's great that you want to translate Git into chinese. Currently Git
> is in a state where we're preparing to accept translations, but
> there's no reason why you can't start now.
>
> What you can do to start now is:
>
> git clone git://git.kernel.org/pub/scm/git/git.git
> cd git
> make pot
> cd po
> msginit --locale=zh
From talking on irc, it looks like you're on Windows and the bandwidth
when talking to servers like git.kernel.org is not so great, and that
you want to be keeping the translation up to date day-to-day as git
is developed. So here are some hints to start out.
As Ævar mentioned, we were just starting to get our act together to
accept translations. So you are a pioneer and we will be working out
some of this as we go (thank you!).
1. The first step, which you have already done, is to install msysgit
(which includes a C compiler and some other useful tools). With it
you can easily test your changes.
Start MsysGit, as described here:
https://git.wiki.kernel.org/index.php/MSysGit:InstallMSysGit
under "How to restart msysGit".
If you installed using the fullinstaller, initialize it by running
/share/msysGit/initialize.sh
2. Msysgit does not include a pre-compiled copy of gettext yet, but
Erik Faye-Lund has done the necessary work. Make use of it like
so:
cd /
git checkout devel
cd /src/gettext
sh release.sh
Now "gettext --help" should work.
3. Build a translation template:
cd /git
git checkout -t origin/master
make pot
cd po
msginit --locale=zh_CN
4. Start translating, at last.
> That'l generate a template zh.po that you can translate. You can
> translate the text with any PO editor, e.g. Poedit:
> http://www.poedit.net/
That's the end of chapter 1. I am leaving how to test and publish
your translation and how to update when messages in git change for a
later mail.
> Please let me know if you have any questions, or if there's anything
> that can be improved in this process.
Yes.
Thanks, and hope that helps.
Jonathan
next prev parent reply other threads:[~2011-04-16 22:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <559debc.6920e.12f5f0bdfc0.Coremail.cyrus_evans@163.com>
2011-04-16 16:34 ` Applicatioin of contribution for Git Chinese version Ævar Arnfjörð Bjarmason
2011-04-16 16:55 ` Ævar Arnfjörð Bjarmason
2011-04-16 17:22 ` Jakub Narebski
2011-04-18 7:57 ` Ævar Arnfjörð Bjarmason
2011-04-16 22:33 ` Jonathan Nieder [this message]
[not found] ` <6e8d0165.486.12f608bb3de.Coremail.cyrus@drupalgate.com>
2011-04-16 23:07 ` Jonathan Nieder
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=20110416223310.GA5149@elie \
--to=jrnieder@gmail.com \
--cc=avarab@gmail.com \
--cc=cyrus_evans@163.com \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
/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).