I cannot disagree more: csv requires a lot of attention when importing/editing/exporting and fail to provide most of the features required by a translator.
PO files are always a standard and all translation software are far more easy to use and understand because they were made just for this scope. I have years of experience in localization including from the translator point of view and from the software publisher. By experience I've come to the conclusion that using gettext format it's the best way of doing translations. If you don't trust me please just take the most non-technical translator and put him to download the translation and a link to the translation tool (in this case I suppose it would be Poedit because it's the only on win32 platform). >From the developer point of view If you ever worked with the gettext you'll >never leave it. Due to the GPL license I've was forced to reimplement some >functionality for my commercial application. And now the good news: You can use PO files without changing anything in tinyerp server. I've already finished yesterday two python scrips: tinycsv2po and po2tinycsv - they require you to have translate-toolkit on the host but this is not a problem now because it can be installed using "yum install translate-toolkit" or apt-get. (I don't know about win32 yet) I would like to publish them on the subversion of my localization project but it's down and in the last 3 days nobody looked over my problem on tinyforge: http://tinyforge.org/tracker/?func=detail&aid=403&group_id=13&atid=129 Hope somebody will take action soon. _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
