-----BEGIN PGP SIGNED MESSAGE-----
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
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).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)
-----END PGP SIGNATURE-----
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests