[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: RFC: Revised translations on branch maintenance scheme

From: Lübbe Onken <l.onken_at_rac.de>
Date: 2004-10-06 09:49:25 CEST

Erik Huelsmann wrote:
> The new procedure (to be added to TRANSLATING after discussion)
> =================
> I propose - in light of making things work with translators instead of
> against them - a new scheme for updating translations on branches. These
> are the rules / steps involved in my proposed scheme:
> 1) All (major) translation development happens on trunk
> Only after a translation has been completely (100%) translated on
> trunk, can it
> be considered for copying to a release branch.
> 2) Updating branch translations is done with the new po-merge
> 2 operations are allowed on branch translations which allow mass
> file updates: po-merge and 'make locale-gnu-po-update'
In principle I like this solution, but I've got a few things to add.

Since I translate on windows boxes, 'make locale-gnu-pot' (the find
stuff) doesn't work for me. Maybe I should try to hack my current script
into python so that an alternative exists for windows users.

I think it would be a good idea to put subversion.pot under version
control. I know that it can be created easily, but on the other hand
this would solve the above mentioned problem for people who do not
translate on Unixes.
That's what we do in TortoiseSVN. We've got an official reference .pot
file for everyone and people can translate without having to check out
the entire source tree! They just grab the current po and pot for their
language and go ahead.
Take a look at: http://tortoisesvn.tigris.org/translations.html.

We've got eighteen languages including english and I think the main
reason is that the translation procedure for TortoiseSVN is a lot easier
than for Subversion.
Take a look at:
for our translation procedure.

To run 'make locale-gnu-po-update' requires me to check out (or switch)
the entire source tree twice, once for trunk and once for the branch.
This is a nightmare at home where I only got a 64K line...

Put Subversion.pot under version control:
+ Life is easier for translators (no huge checkouts)
+ works on every platform
+ po-merge will still work the way you suggested
- Subversion.pot may be out of date, but since you run the translation
status checks daily already, you could also run 'update-pot' once a week

> I think that in this special instance branch commits are alright, since:
> - there is a pre-commit hook to catch the worst failures
> - the number of messages on a branch which have no translation (ever) on
> trunk is typically quite low
Could you also add a check for people (like me) who forget to change the
"Last-Translator" line in the .po file :-)?

- Lübbe

   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 6 09:50:22 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.