From: Andreas Ericsson <ae@op5.se>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@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: Wed, 15 Jun 2011 10:22:11 +0200 [thread overview]
Message-ID: <4DF86BB3.4070906@op5.se> (raw)
In-Reply-To: <BANLkTikCB7t4DhCxjLT-JABsUuksPBhkLw@mail.gmail.com>
On 06/15/2011 09:33 AM, Ramkumar Ramachandra wrote:
> Hi Andreas,
>
> Andreas Ericsson writes:
>> 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.
>
> Fair point. How do we work around this?
> 1. Can we relax the requirements for contributing translations? To what extent?
Probably at least a bit. It doesn't affect core functionality in any
way so it's unlikely it will cause bugs that requires deep diving in
the history, so changes needn't be so isolated and commit messages
are less important than for code changes.
> 2. It think one commit per edit-session per language sounds sane.
Yup.
> If
> people just go around translating some random strings that they like
> (which is often the case), what is the sense in asking them to write a
> commit message? Maybe we can write one ourselves before committing it,
> provided they signoff on all the commits? Maybe there should be an
> auto-signoff option too?
>
No and no. No auto-signoff, and no auto-message. That will just leave
us with a long string of auto-signoffs and automatic messages, and
that's horrible.
The "no auto-signoff" rule is from Junio btw, and I doubt he's changed
his mind regarding that. The "no auto-message" is just my gut feeling
that everyone will really hate to see changes without an explanation.
Something simple like "5 out of 6 of the large scm's (in terms of
userbase) uses 'blarg' instead of 'fnurg' for commits, so let's call
it that in our examplinitian translation too" is enough and will be
quite helpful when it comes to explaining why a change is made.
Otoh, "Updated translations for new release" will probably be the
most common message, and that's fine too if that's what happened.
--
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-15 8:22 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
2011-06-15 7:33 ` Ramkumar Ramachandra
2011-06-15 8:22 ` Andreas Ericsson [this message]
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=4DF86BB3.4070906@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 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).