was fixed in Zope 3.3 proper.

zope.tal.xmlparser.XMLParser.parseString()

o Forward-port from 2.8 branch.

        zope.security.management.checkPermission aren't rerouted to
        Zope 2's security policy.

        NOTE: If you already have a Zope 2.10 instance running, you
        will either have to recreate it or add the following lines to
        the end of the etc/site.zcml file::

          <securityPolicy
                component="Products.Five.security.FiveSecurityPolicy" />

-This line, and those below, will be ignored--

M    doc/CHANGES.txt
_M   lib/python/Products
M    lib/python/ZPublisher/Publish.py
M    skel/etc/site.zcml

That consisted of forwardporting r70918 and r71797 from the 2.9 branch and providing
a fix.

properly with the UnicodeEncodingConflictResolver configured through ZCML

No commit message

- configuration through ZCML
- additional useful logging

No commit message

in order to make the sniffing a bit configurable for instances
working with encodings other than iso-8859-15 or utf-8

- the ZMI edit view now *always* uses 'utf-8' and no longer uses self.output_encoding (which is only relevant for FTP/WebDAV)
- 'output_encoding' is now a property

/Zope/branches/ajung-zpt-encoding-fixes

This branch fixes several encoding issues with the ZopePageTemplate
implementation, some webdav issues and now uses unicode internally
for ZPT instances (but not for the PageTemplate(File) classes)