Daniel Tellez a écrit : > The best of having few translation files is that each one is for each > product, so the products can be independent. > > I prefer this way. >
I also prefer it this way, which makes the CPS products less coupled. The solution I would prefer would be to provide more means to ease the work of translators. Those tools should go in the CPSI18n product: http://svn.nuxeo.org/trac/pub/browser/CPS3/products/CPSI18n/trunk A nice tool to have would merge all .po files into one .po file to translate, and then when the translator is done with his job, redispatch the translations in their respective original .po file. Encolpe, do you think you could do such as tool? Note: recently all the .po files have been encoded in UTF-8: http://svn.nuxeo.org/trac/pub/ticket/1916 Cheers, -- Marc-Aurèle DARCHE Open Source Enterprise Content Management (ECM) http://www.nuxeo.org/ NUXEO (Paris, France) http://nuxeo.com/ _______________________________________________ cps-devel mailing list http://lists.nuxeo.com/mailman/listinfo/cps-devel
