On 2004-10-05 22:58:01 Erik Hũlsmann wrote:
> Recently Oyvind A. Holm (alias sunny256) committed a change to
> TRANSLATING adding a new section on maintaining translations on
> branches. In his piece he describes how it has to be done with the
> current restriction of committing to trunk and backporting to the
> branch. His scheme involves quite some changing, reverse merging and
> changing again. The system turns out to be quite complex.
> [...]
> 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'
This looks as a Good Thing™. Have been testing the script with ancient
versions of the files, and it seems to do the job right. No doubt this
will make life easier for the translators. +1.
Regards,
Øyvind A. Holm
---------------------
cat /dev/urandom >SCO
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 7 18:16:01 2004