Another usecase where Zope does not play nicely: You can create a ZPT with XHTML content where the content is encoded as UTF-8 (which the corresponding encoding declaration within the XML preamble). When you redefine the zpublisher_default_encoding Zope might convert the UTF8 body of the ZPT to some other encoding. This leads to twopossible problems: a) the new encoding is not available from the content-type header and b) the encoding inside the XML preamble still contains the original encoding...both is wrong...any ideas how to deal with that problem
(perhaps the problem is only a constructed problem?)
-aj
pgpmYiDxbvl4o.pgp
Description: PGP signature
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
