[Zope-CMF] [CMF 2.1] FSPageTemplate & Unicode

[Andreas Jung]

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



- --On 21. Dezember 2006 20:14:59 +0100 Dieter Maurer <dieter at handshake.de> 
wrote:

> Andreas Jung wrote at 2006-12-20 19:34 +0100:
>> ...
>> Right. The pt_render() should return unicode only. Let's assume
>> FSPageTemplates would use unicode internally and a customized copy (an
>> instance of ZopePageTemplate) wouldn't then we would definitely run
>> into UnicodeDecode errors. That's why we should use unicode as internal
>> representation where possibly. However applications will likely run into
>> UnicodeDecode error for example with scripts returning non-unicode...
>
> Yes, you need "all text is unicode" or non-unicode encoded in a
> default encoding. Its up to you, how you define "default encoding".
>
> I would use Python's default encoding.

I think there are too many place in Zope where we would have to convert 
non-unicode strings into unicode for legacy applications. Therefore 
changing Python's default encoding might be a legitimate choice for legacy 
code. But I don't think that it would be a good idea to have some global 
encoding to perform explicit conversions to unicode.

Andreas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)

iD8DBQFFiuEaCJIWIbr9KYwRAqByAKCYrWmwhbWL8xXs+VzOtlBGkGEPugCeN/T0
Ry3QtjYtBMEKxaofIAQfoMQ=
=lYQC
-----END PGP SIGNATURE-----