Encolpe Degoute a écrit : > 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. >
Yes :-( > We can use i18ndude that is a more mature tool. > You can parse ZCML and Generic Setup profiles with it. > I would be glad to not depend on those products anymore and switch to i18ndude. >> 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. > :-D > There is two point to decide before: > - how to separate legacy from each platform Only the newer CPS will have .po files in UTF-8. Would that be a good enough way to do the detection? > - how to detect and manage msgid semantic conflicts > Do you mean duplicate msgids? Presently the update_pos script http://svn.nuxeo.org/trac/pub/browser/CPS3/products/CPSI18n/trunk/bin/update_pos prevents any duplicate msgids through the use of i18n/.blacklist_pot files, for example: http://svn.nuxeo.org/trac/pub/browser/CPS3/products/CPSWiki/trunk/i18n/.blacklist_pot 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
