On Friday, 26 January 2007 13:58, Chris Cannam wrote: > On Thursday 25 Jan 2007 22:41, Pedro Lopez-Cabanillas wrote: > > If you have updated the .po file from the 1.4 release, it could be used > > for an hypothetical 1.4.1 release but not for 1.5, sorry. > > Is that really true? I hadn't realised that. I'm sorry -- I should have > stepped in sooner, as I think Jasper has mentioned before that he was > working from 1.4.0. > > So what happens if you just drop in the nl.po from 1.4.0 or wherever into > the 1.5.0 tree and update using messages.sh? I would have expected it to > use the existing translations correctly wherever the source strings > matched, perhaps marking them fuzzy if their origins (in terms of file name > etc) had changed. I'm pretty naive about these things, but if it doesn't do > that, why not?
If the translator does it as part of his job (knowing what he is doing) it is perfectly safe. He knows that the current translation residing on the SVN repository is obsolete, and he process a new merge from the latest sources, checking that the new total number of messages is equal to the latest from SVN. He can test the new resulting translation, iterate several times the kbabel/install/test cycle and finally he commits the results (only his own translation) to the repository to be included in the next release. Fine. I've done it myself, and I have to say that the whole business of xgettext / msgmerge / msgfmt is pretty solid and you have good chances of success. But now, let's look to the other side: the release administrator (Chris). You have processed the latest sources, generated a new .pot template (that can be picked by the upcoming translators) and merged the existing translations with this new template. You have committed everything to the SVN repo and decreed a string freeze (or have you missed this step?). The merry squad of translators have started to pick the .po files and update it for the next release. If you repeat the msgmerge process and commit all the translations again, when the squad return their translations to the SVN, it may flag collisions. It may require a svn merge. If there are strings added/removed/changed in the sources it can be even worse, of course. And the administrator can't usually review all the translations to verify that everything is OK. Regards, Pedro ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
