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 two
possible 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?)


Attachment: pgpmYiDxbvl4o.pgp
Description: PGP signature

Zope-Dev maillist  -
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to