-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

as mentioned in an earlier I was working on several encoding and webdav
issues related to the Zope 3 ZPT integration in Zope 2.10. I backported
the changes to the 2.10 branch.

The changes include an in-place migration of all ZopePageTemplate instances 
to unicode (through a custom __setstate__() implemenetation). The migration 
code tries to sniff the encoding (it knows about ISO-8859-15 and UTF-8). A 
custom "preferred" encoding can be specified through the environment 
variable $ZPT_PREFERRED_ENCODING.

I know that this migration is a big hammer (for a minor release) however I 
have not found another solution to deal with the outstanding issues in a 
reasonable and sane way. Therefore this migration must be tested. I am 
thinking about a beta release for 2.10.2 in order to get the stuff tested
(I am also aware of the fact that most people don't test betas :-))

Thoughts? Objections?

Andreas

- -- 
ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany
Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376
E-Publishing, Python, Zope & Plone development, Consulting
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)

iD8DBQFFk81+CJIWIbr9KYwRAhF9AKCTgzufb/v5VUBxQvHNbL/1GcfcfACdG9Wo
Ti+S/skHE79SXJfnjjI8gAM=
=QKf4
-----END 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 )

Reply via email to