Le 11 mai 2010 à 13:18, toutpt a écrit : > > Hi,
Hi, > > Most of translation are not synchronized because PloneFormGen doesn't use > i18ndude. > > I have add a rebuild pot script to synch translation but most of > translations are removed: I always add this to my personal components to automate i18n update/sync : https://svn.plone.org/svn/collective/aws.pdfbook/trunk/aws/pdfbook/locales/updatelocales.py https://svn.plone.org/svn/collective/aws.pdfbook/trunk/aws/pdfbook/locales/README.txt Generally you just need to change DOMAIN in the script to fit your component. > > http://pastebin.com/KMZAHs48 > > I have inspect translations in pfg code. Schemata use label_msgid and > description_msgid, and this seems not supported by i18ndude. > > So what is the best choice: > > * refactor pfg schemas to use _(u"") syntax ? +1 : AFAIK, most "old" Archetypes public content types have been refactored that way. > * update i18ndude to support the old way -1 : We can't ask to the i18ndude type to add support for such or such specific i18n markup. > > ----- > Jean-Michel François aka toutpt > http://toutpt.wordpress.com > http://twitter.com/toutpt > > -- > View this message in context: > http://plone.293351.n2.nabble.com/PloneFormGen-vs-i18ndude-need-help-tp5035466p5035466.html > Sent from the Product Developers mailing list archive at Nabble.com. > _______________________________________________ > Product-Developers mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/product-developers _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
