M.-A. DARCHE a écrit : > 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
mmh I forgot this tool. It depends on unmaintained prdoduct OpenTAL and OpenPTi18n. We can use i18ndude that is a more mature tool. You can parse ZCML and Generic Setup profiles with it. > 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? Yes I can. There is two point to decide before: - how to separate legacy from each platform - how to detect and manage msgid semantic conflicts > Note: recently all the .po files have been encoded in UTF-8: > http://svn.nuxeo.org/trac/pub/ticket/1916 Cool, i18ndude is not really latin1 friendly :) Regards, -- Encolpe Degoute INGENIWEB (TM) - S.A.S 50000 Euros - RC B 438 725 632 Bureaux de la Colline 1 rue Royal 92210 Saint Cloud web : www.ingeniweb.com - « les Services Web Ingénieux » Tel : 01.78.15.24.08 / Fax : 01 47 57 39 14 _______________________________________________ cps-devel mailing list http://lists.nuxeo.com/mailman/listinfo/cps-devel
