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

Re: Translation maintenance requires direct branch commits. (Doesn't it?)

From: Tobias Ringström <tobias_at_ringstrom.mine.nu>
Date: 2004-09-30 10:02:33 CEST

plasma wrote:

>I tried to follow 'Maintenance on branches' in TRANSLATING today, but
I think that summarizes the current situation quite well. :-)

The current situation is very complex, so I wrote a tool
(tools/dev/po-merge.py) to help with the maintenance of the translations
on the branches. I think Erik will update the instructions in
TRANSLATION soon, but until he does, here's a quick summary of how it's
supposed to work. The most important thing is that the main translation
work should still be done on trunk. When updating a translation on a
branch, do the following:

   1. Make locale-gnu-pot and locale-gnu-po-update on the branch.
   2. Merge in the translated strings from trunk using e.g.:
          * svn cat
            http://svn.collab.net/repos/svn/trunk/subversion/po/sv.po | \
                    po-merge.py sv.po
   3. Optionally translate strings that are not present on trunk.
   4. Commit.

Since the tool is new, it would be great if you could try it out. I know
Peter Lundblad has used it with great success to update sv.po on the
1.1.x branch.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 30 10:03:04 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.