The philosophy is this: If your site is mono linguistic, why bother to load dozens of translations that you're not using at all?
It is quite easy to use. Just give the environment variable PTS_LANGUAGES a list of translation domains you are interested in. An example. I prefer a site to speak Danish, so I include this in the zope.conf of an instance:
<environment>It works with Plone 3.1.1 - I don't know about earlier releases.
PTS_LANGUAGES da
</environment>
1 comment:
It's a feature of PTS version 1.4.11. That version should work with any Plone 3 or 3.1 version.
We use it in production on 3.0.6 and 3.1 sites.
Besides a better startup time, it also avoids creating a few hundred persistent objects in the ZODB which in turn end up in the ZODB cache.
One effect you could see is some actual larger memory footprint of the instance, as now some real content objects make it into the ZODB cache and stay there for a while. With all languages loaded you will always have a couple of hundred tiny message catalogs in the cache.
Post a Comment