Cilyan Olowen wrote: > French translation done (pootle). > > Just a remark : be careful not to overwrite already made translation, > because I had to redo some work I had already done (not too much, > fortunately).
Indeed. I am sorry for this but it's my fault. When the Pootle server and the repository get inconsistent I try my very best to solve conflicts. Some times it works out really nice. This time there were no way to get it to work nice and I had to overwrite some work in Pootle. The basic problem is that we haven't agreed on a way to work with the po files. If the developer resyncs the complete repository and I try to update the base files in Pootle it's more than a PITA to sort it all out. An updated POT file would be enough for me but then we have to agreee on how to work with the files. 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. -- Martin ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
