From: Jakub Narebski <jnareb@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "Cyrus.Evans" <cyrus_evans@163.com>, git <git@vger.kernel.org>
Subject: Re: Applicatioin of contribution for Git Chinese version
Date: Sat, 16 Apr 2011 10:22:42 -0700 (PDT) [thread overview]
Message-ID: <m362qexgb1.fsf@localhost.localdomain> (raw)
In-Reply-To: <BANLkTintJ6FsYAQ1iV1kygwOdtsFtCs3EA@mail.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> On Sat, Apr 16, 2011 at 18:34, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
>
> > In particular I was thinking of using some web interface for
> > translation, but that would probably be hard to work out with
> > accounting for who did what, which would play badly with Git's signoff
> > policies.
>
> It was clear from talking on IRC that having them use PO wouldn't get
> anywhere.
>
> So I've created https://translations.launchpad.net/git-i18n
>
> It has strings from git's master + the shellscript translations.
>
> I've set the translation policy to "open", so anyone can contribute
> there. We can figure out the legal mumbo-jumbo later.
>
> Translating there will work once the Launchpad people review & accept
> the POT file I uploaded. I have no idea how long that takes.
Why not use Pootle?
http://translate.sourceforge.net/wiki/
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2011-04-16 17:22 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 [this message]
2011-04-18 7:57 ` Ævar Arnfjörð Bjarmason
2011-04-16 22:33 ` Jonathan Nieder
[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=m362qexgb1.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=avarab@gmail.com \
--cc=cyrus_evans@163.com \
--cc=git@vger.kernel.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).