Am 01.07.2010, 16:16 Uhr, schrieb yuppie <y.2...@wcm-solutions.de>:

> Well. It works for me. Do you have registrations like these in your  
> product?
>   <i18n:registerTranslations directory="locales"/>
>    <configure package="zope.app.locales">
>      <i18n:registerTranslations directory="."/>
>    </configure>

ah, that, along with the necessary  
xmlns:i18n="http://namespaces.zope.org/i18n"; declaration was missing.  
Working great now.

To clarify: localisation requires *one* declaration per site. Either as  
above or adding zope.app.locales to a the buildout zcml list?

Each package that needs localisation resources must have its own  
registered "locales" resource directory?

Charlie
-- 
Charlie Clark
Managing Director
Clark Consulting & Research
German Office
Helmholtzstr. 20
Düsseldorf
D- 40215
Tel: +49-211-600-3657
Mobile: +49-178-782-6226
_______________________________________________
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

Reply via email to