--On 5. Januar 2007 21:22:24 +0100 Jens Vagelpohl [EMAIL PROTECTED]
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5 Jan 2007, at 20:51, Andreas Jung wrote:
I finished my work (including some test).
Any objections merging the changes back to the trunk?
If the tests pass, no.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6 Jan 2007, at 12:57, Andreas Jung wrote:
On 5 Jan 2007, at 20:51, Andreas Jung wrote:
I finished my work (including some test).
Any objections merging the changes back to the trunk?
If the tests pass, no. At least from me ;)
I merged the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On 20. Dezember 2006 19:34:22 +0100 Andreas Jung
[EMAIL PROTECTED]
wrote:
If you look at the current FSPageTemplate code, there was already an
attempt to find and transfer enoding information with the response by way
of adding it to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5 Jan 2007, at 20:51, Andreas Jung wrote:
I finished my work (including some test).
Any objections merging the changes back to the trunk?
If the tests pass, no. At least from me ;)
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On 19. Dezember 2006 09:58:37 +0100 Jens Vagelpohl [EMAIL PROTECTED]
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Dec 2006, at 09:45, Andreas Jung wrote:
Jup. However I am not completely sure about all impacts :-)
If I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On 19. Dezember 2006 09:34:13 +0100 Jens Vagelpohl [EMAIL PROTECTED]
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18 Dec 2006, at 13:52, Andreas Jung wrote:
What has to be done:
- FSPageTemplate._readFile() should convert
-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
