On Tue, May 19, 2009 at 9:12 AM, <brot...@bsnet.se> wrote: > As long as we use Pootle as a main stage for translation coordination my > proposal will be to choose between these two ways > a) developers never touches po/pot files. > b) developers only updates the POT files. > > I prefer B because then I (or anyone else doing this) would notice the > change and we can resynchronize the files in a safe way. In A some one > have to monitor the source changes and as the developers already know > when a PO resync is needed it would be a slim job to include an update > POT file in the commit.
I completely agree with you Martin. :) -- Og B. Maciel omac...@foresightlinux.org ogmac...@gnome.org ogmac...@ubuntu.com GPG Keys: D5CFC202 http://www.ogmaciel.com (en_US) http://blog.ogmaciel.com (pt_BR) ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Lxde-list mailing list Lxde-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxde-list