To get the .po files updated with an svn update bin/make-messages.py -a would need to be run on every svn commit and you'd need to track differences from "the last revision I translated" to "the one I just updated to".
Running make-messages -l <my_lang> when you want allows you to do "svn diff" just after that and see what's new. So, updating .po files on svn is a bit overkill. Just my .02, Marc El vie, 29-06-2007 a las 11:32 -0400, Mario Gonzalez escribió: > On 29/06/07, Ramiro Morales <[EMAIL PROTECTED]> wrote: > > > > It's a responsability of the translator(s): > > > > Sure but I'm saying that if there's a updated translation version, a > svn updatedb must be enough. > > Does the commiter add the updated file? Maybe my English is getting > me in problems because I didn't understand why I've got to run > make-messages after a new update. > > > >
signature.asc
Description: Esta parte del mensaje está firmada digitalmente