Re: Using Transifex in git.git
- From
Andreas Ericsson <ae@op5.se>
- Date
- Jun 15, 2011, 08:22 UTC
- Message-ID
- <4DF86BB3.4070906@op5.se>
- In-Reply-To
- <BANLkTikCB7t4DhCxjLT-JABsUuksPBhkLw@mail.gmail.com>
On 06/15/2011 09:33 AM, Ramkumar Ramachandra wrote:
Show 12 quoted lines
> 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.
Show 7 quoted lines
> 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.