Hanno Schlichting-2 wrote: > > This is needed to provide a successor for PTS's ability to overwrite > already existing translations for a site, which is currently offered > through a INSTANCE_HOME global i18n folder on the file system. > > What PTS on Plone trunk still does is to register all translations found > in i18n folders in the Zope 3 way, including compiling them to mo files > inplace, so you won't need to convert all translations to the new layout > at once. It also compiles all po files in locales folders to mo files > inplace, so you don't need to ship these in your distribution tarballs. >
What is the current status for this successor in Plone 3 ? I've just seen this response so my post about i18ndude in the i18n ML is a bit about this: until we have it, we need to compile those locales .mo inplace today so we need a simple tool to generate them ( a new feature in i18ndude for example) _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers -- View this message in context: http://www.nabble.com/i18n-in-Plone-3-products-tf4943621s20094.html#a14160189 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
