Re: svn commit: r11126 - branches/1.1.x/subversion/po

Another thought... a branch PO file can be created with the
following steps:

  1) copy original PO file from trunk to branch;
  2) run locale update in branch;
  3) remove obsolete messages;
  4) run 'svn add' and 'svn commit';

Maybe a similar approach could be used to maintain the PO file in
branch:

  1) run locale update in trunk;
  2) update PO file in trunk and DO NOT remove obsolete messages;
  3) copy the PO file from trunk over the PO file in branch;
  4) run locale update in branch;

I think that there shouldn't be untranslated messages, maybe just
fewer obsolete ones. If there are untranslated messages in branch,
let's try another approach... Just a thought - not tested.

What do you think?

_________________________________________________________________
MSN Messenger: converse com os seus amigos online.
http://messenger.msn.com.br

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Sep 26 00:05:12 2004