[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: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2004-09-09 22:46:30 CEST

On Thu, 9 Sep 2004, Erik Huelsmann wrote:

> Several translation maintainers have mentioned this and I have promised to
> write about it. In this mail I'm trying to find out if I understand the
> issue correctly. Please feel free to comment. (Or rather: please comment!
> :-)
Interesting that you wrote this right after I decided to get the sv.po up
to date on the branch. My strategy is to:
a) run locale-gnu-po-update on the branch
b) go through sv.po on the branch and on trunk in parallell, fixing the
messages that need fixing on trunk and commit trunk
c) Merge that to the po-updated branch, remove obsolete messages, resolve
conflicts and commit.

I will do step c) above when r10860 is merged. Then I'll see how tedious
the conflict resolution is. We have no removed messages on trunk yet, so
that's not a problem at the moment. OTOH, there is no reason to remove
obsolete messages on the trunk while there are active branches.

I'll come back when I know how this worked out for me.


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