From: Andreas Ericsson <ae@op5.se>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
Dimitris Glezos <glezos@indifex.com>,
Git List <git@vger.kernel.org>,
Jonathan Nieder <jrnieder@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: Using Transifex in git.git
Date: Tue, 14 Jun 2011 14:07:08 +0200 [thread overview]
Message-ID: <4DF74EEC.1050506@op5.se> (raw)
In-Reply-To: <BANLkTikLJJwfGJp_nshRXGSb-yGOshwzTg@mail.gmail.com>
On 06/14/2011 11:37 AM, Ævar Arnfjörð Bjarmason wrote:
> On Tue, Jun 14, 2011 at 07:57, Ramkumar Ramachandra<artagnon@gmail.com> wrote:
>> Hi Dimitris et al,
>>
>> [+CC: Git List; for wider exposure]
>> [+CC: Jonathan Nieder; he has been involved with translations in the past]
>> [+CC: Junio C Hamano; for authoritative policy advice]
>>
>> I think it's a good idea to use a system like Transifex to manage
>> translations for git.git, so that we can attract a large number of
>> non-technical translators. Further, I think it's a good time to start
>> off on this now, since many of the i18n bits from Ævar's series are in
>> 'master'. So, I'm looking to start off a discussion about how to
>> adapt a translation system into our current patch workflow. Dimitris
>> is the lead developer of Transifex, and can help with the details.
>
> Turns out I have two E-Mails related to this in my inbox. Below
> follows the reply I sent to the other one in private mail, but applies
> here too:
>
> * Any way of editing the translations will have to comply with git's
> normal patch submission process.
>
> When you normally submit a patch to Git you have to write a
> sensible commit message for it, change one logical thing at a time,
> and you have to agree to the contributor's agreement by adding a
> Signed-off-by to your Git commit.
>
Historically, a translation for one language has been considered "one
logical change" in that respect. I think it's safe to assume that if
we want translators to stick around they shouldn't need to divide their
changes on a per-message or per-command basis. Especially since such
divisions wouldn't be very easy to do if all you've got to go on is
a pot-file.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
next prev parent reply other threads:[~2011-06-14 12:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 5:57 Using Transifex in git.git Ramkumar Ramachandra
2011-06-14 9:16 ` Andreas Ericsson
2011-06-14 10:12 ` Ramkumar Ramachandra
2011-06-14 9:37 ` Ævar Arnfjörð Bjarmason
2011-06-14 11:02 ` Ramkumar Ramachandra
2011-06-14 12:07 ` Andreas Ericsson [this message]
2011-06-15 7:33 ` Ramkumar Ramachandra
2011-06-15 8:22 ` Andreas Ericsson
2011-06-15 10:10 ` Ramkumar Ramachandra
2011-06-15 20:40 ` Ævar Arnfjörð Bjarmason
2011-06-15 20:58 ` Ævar Arnfjörð Bjarmason
2011-06-15 13:21 ` Erik Faye-Lund
2011-06-15 13:45 ` Michael Witten
2011-06-15 20:43 ` Ævar Arnfjörð Bjarmason
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=4DF74EEC.1050506@op5.se \
--to=ae@op5.se \
--cc=artagnon@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=glezos@indifex.com \
--cc=jrnieder@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.