-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 You might have noticed that I have changed the ZopeTemplateFile implementation to work with unicode as internal representation. I think it would make sense for FSPageTemplate instance to use unicode as well - especially when ZPTs and FSPageTemplate live side by side. However FSPageTemplate inherits directly from PageTemplate.
What has to be done: - FSPageTemplate._readFile() should convert 'data' to unicode and pass it to pt_edit() instead of using write() - a filesystem-based PT should be able to specify its encoding through the .metafile like [default] encoding=utf-8 For XML files the encoding is determines by the XML preamble and for HTML file we are able to check for the 'charset' inside <meta http-equiv="content-type" ...> tag (if available) What do you think about this idea? How about the schedule? I would like to port my ZPT changes to the Zope 2.10 branch because the ZPT implementation is now partly broken and needs the fixes. However I don't know if the changes will play nicely with the upcoming CMF 2.1 release. I had no problem with a plain CMF site running on Zope 2.10.2 with my changes but we should ensure that are not big issues with the upcoming Plone 3.0 release (which requires Zope 2.10/CMF 2.1). Andreas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (Darwin) iD8DBQFFho8GCJIWIbr9KYwRAt9GAJwLS+t3vz95JUTDiB498+3YVLCCtACeNv1q aCFwpGMUg8VjlXJLXpqCKFw= =D/F6 -----END PGP SIGNATURE----- _______________________________________________ Zope-CMF maillist - [email protected] http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
