How can I keep my interface translations separate and upgradable?

I need to keep my own translations of some parts of the Plone User interface. How can I keep these separate from the Plone translation files, so they don't get deleted when I upgrade?

« Back to Table of Contents

Put your translations in a separate .po file with the domain plone in the header.

This way, you will have a mytranslations-xy.po with your own translations that will be added to the Plone translation name space on load, and you can update the normal plone-xy.po files without affecting your translations.

If you keep your files in a directory called i18n in your INSTANCE_HOME directory, they will always have priority over the ones shipping inside Products.

by Alexander Limi — last modified Dec 30, 2008 03:00 PM All content is copyright Plone Foundation and the individual contributors.

How to do this on multiple sites?

Posted by Francesco Ricciardi at Nov 09, 2005 10:29 AM
If my instance hosts multiple sites, and each site wants a specific word for a given msgid (e.g. one wants "user" and another wants "member"), where shall I put the customized 'plone-en.po' files?

Just specifying a new i18n:domain for each site does not work, because:
1) Rework on many templates is needed, and must be done for each site
2) This rework is again needed whenever a new version of Plone is installed

Separate Zope instances needed

Posted by Alexander Limi at Nov 09, 2005 05:49 PM
You'll need separate Zope instances to do this. This is the way a global translation service like PTS works.