Bill Kendrick <[EMAIL PROTECTED]> wrote in news:[EMAIL PROTECTED]:
>> Modified Files: >> po2txt.py tuxpaint-stamps-af.po tuxpaint-stamps-be.po >> tuxpaint-stamps-br.po tuxpaint-stamps-ca.po >> tuxpaint-stamps-da.po tuxpaint-stamps-de.po >> tuxpaint-stamps-el.po tuxpaint-stamps-en_gb.po >> tuxpaint-stamps-es.po >> tuxpaint-stamps-eu.po > <snip> > > Okay, what the heck did those scripts do, and is it BAD? :^) Always run 'cvs diff' before 'cvs commit'. ALWAYS! > It _looks_ like the order of the strings in the PO files > merely got shuffled, Yes, I don't think anything else changed. I believe the order they are written in the file depends on the order they're 'listed' on your filesystem. I guess this might be easy (or not) to fix (e.g. to get the scripts to to insert stamps sorted alphabetically by directory, and then by filename). Unfortunately I don't know any Python ... > Then I did a regualr "cvs commit" in the PO file. I didn't > expect EVERY file to have been touched, but figured maybe > timestamps had changed in the comments, or something benign... > Apparently not. :^) If you do a 'cvs update', all 'touched' but not changed files are reset to 'not changed' state by CVS (a second 'cvs update' then tells you which files are *really* changed). -- Karl Ove Hufthammer _______________________________________________ Tuxpaint-dev mailing list [EMAIL PROTECTED] http://tux4kids.net/mailman/listinfo/tuxpaint-dev
