Re: plone4: how to override translations in plone.app.locales?

On Tue, Aug 24, 2010 at 6:00 PM, Maurits van Rees
<[email protected]> wrote:
> But if you want to override some translations for a third party product
> that still uses an i18n folder, then an i18n folder in the instance home
> would still work, right?

No. You would use the same approach as for a locales folder. In Plone
4 both these folder structures internally produce the same sort of
standard zope.i18n translation domain utilities. You can mix and match
between the two structures as you like now.

Nothing will read an i18n folder in the instance home anymore, though.

> Getting slightly off-topic, but does it still make sense for a third
> party product (let's say one for Plone 4 only) to use i18n instead of
> locales.  As far as I know, both work.  For a new package I would surely
> use locales, but I'm not sure it makes sense to restructure an existing
> package.
>
> I expect that the old i18n way won't work anymore in Plone 5 (perhaps
> pending on okay from the framework team), is that correct?  That might
> be a good enough reason.

The idea is of course to remove the i18n folder support for good in
Plone 5. Consider the i18n folder format to be deprecated with Plone
4.0.

If you have an add-on that only targets Plone 4, you should only use
locales folders.

If you target Plone 3 and 4 at the same time, you should use a locales
folder for your own domain and an i18n folder for the plone domain.

Hanno

------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Plone-i18n mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-i18n