-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Withers wrote:
On 22/09/2010 09:58, Andreas Jung wrote:
If you think it is crap then I cam happy to accept that (and I don't mind much because Zope 2 is not my radar right now). You are committer and you can fix my crap. Blame me for having written this crap but you could also blame me for having on this whole Zope 3 ZPT engine integration :-)
Can you please answer me one thing though: in what way could it ever be a good idea to consult the browser's list of acceptable character sets to decide how to decode python strings into python unicode objects in a database that the browser has never had anything to do with?
Check with Launchpad - neither I can remember the details nor am I interested right now thinking about. There were reasons *and* real-world tests with browsers obviously required that. As said: the encoding handling is a game you can only lose inside Zope 2. - -aj -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJMmcfoAAoJEADcfz7u4AZjQ90LwLQoiWZzKwnLhYJBaO/j4Hs5 RXxURlWAPX2VB1iNbzmzZgadffYdF4Tigmh/kuZFZwZLizJw+SnYwPwJJgAHM/dn aq2Q9JV3atjlu0p/OGe/54BY5ZfMWSE/AjS2gKSJExNdp9rKZbvOdKWg/J+utzq3 M/U7E2AXvOtG3YWZYggQF1QZlY3PZu08XlXHUCNdiK3fAu9dtJQstRGGdggdxhuQ QiheKAs2Tu/hKWsVPURlxes9zGtylpDAQxt5ycRxTxYToJyCQtFdSzBsbLC1rkGG fMDOOL/fPR3UlTzyhvB87ugaiBH7owng+n8tia3Ro06LzGp0oy5PdytrhfQ2BGn2 RzPre7tGavUFn6sxYSEZ6akIuHwk1KQgvMFN2ngsa/F1N1xqZpQUXwF1ALrEFzWc qg4CeO4UDdkh1V8ZlawbKgbih/0eaNYKreCg0vCb2xNqXvsl5OL0QERj0v4u/gWp pJ1zGB+BVHbtZifhHSHkKYmx9Dgpl3I= =EwM7 -----END PGP SIGNATURE-----