On 21/09/2010 21:18, Andreas Jung wrote:
> I can not recall all details but at the time of the integration of the
> Zope 3 ZPT engine the unicode resolver approach was the best thinkable
> solution for dealing all possible edgecase where encoding issues may pop
> *for the sake of backwards compatibility*

...where it miserably failed. The projects I've hit this on have all 
been running flawlessly on Zope 2.1(ish) through to Zope 2.9.
Zope 2.11 onwards, in my experience, phail, spectacularly...


Simplistix - Content Management, Batch Processing & Python Consulting
            - http://www.simplistix.co.uk
Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope )

Reply via email to