On Sun, May 09, 2004 at 03:43:47PM -0300, Gustavo R. Montesino wrote: [...] > > This is a bad idea, because when translators add or update PO files, they > > already exist or are modified on www-master which causes a CVS conflict. > > IMO the only solution is to add */po/foo.XX.po into CVS when adding > > english/po/foo.pot > > I have to go for a couple of hours and will look at it when I am back. > > > > Hmmm... Because something outside of my understanding, the .po files being > made automatically by the rule that I've added seems to be rmed after the > build process. Although I don't know what's causing this, I think it lets > the path open for the translators to add their own .po files when they > wish.
No, files under CVS control must not be modified when building pages, otherwise CVS conflict may occur on www-master. Imagine for instance that PO files contain a "PO-Revision-Date" header field, automatically updated when building pages. PO files in the working directory differ from the ones stored in CVS repository. Then a translator commits his file, and when 'cvs update' is run on www-master, there is a conflict and this PO file becomes invalid on www-master. Denis
