Encolpe Degoute a écrit : > M.-A. DARCHE a écrit : >> Encolpe Degoute a écrit : >> >>> 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. > > Here come a script that depend only on the latest egg of i18ndude: > [...] >
Super thanks Encolpe! Could you put it in http://svn.nuxeo.org/trac/pub/browser/CPS3/products/CPSI18n/trunk/bin please? I'll try it once the commit is done. >>> - how to detect and manage msgid semantic conflicts >>> >> Do you mean duplicate msgids? > > The same msgid that is present in several products with a > different meaning. > For example workflow states and transitions have rather simple > msgids due to the UI but their translations can be very different. > Thanks for the explanations. At the moment in the CPS products found in http://svn.nuxeo.org/ there are no such duplicates as far as I know. So the first obvious and immediate solution is to simply do nothing :-) We just go on in the same manner, that is when one needs a new msig, be sure to not use an existing one. That has worked for a long time and produce good results :-) What would be a better solution, I can only guess ... maybe using different domains? That is using a specific "i18n:domain" for each CPS product. CPSSkins already does that. This would imply to change the *.pt files of all products. Such a change would not break customized *.pt files, since the old translations would still exist. So this could go into the next CPS release. What do you advise? 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
