[Zope-dev] Should PageTemplate._text be a unicode or an encoded string in Zope 2.9.3?

[Andreas Jung]

--On 17. Juli 2006 16:55:42 +0100 Chris Withers <chris at simplistix.co.uk> 
wrote:

> Andreas Jung wrote:
>>
>>> I've had problems when it's an encoded string, but that seems to be what
>>> is stored when you save a ZPT via the ZMI or WebDAV...
>>>
>> ZPT in pre-Zope 2.10 knows nothing about unicode...it can be anything :-)
>
> And what about 2.10?

Zope 2.10 comes with the ZPT implementation of Zope 3 which works nicely 
with unicode strings. However the 2.10 won't enforce the use of unicode 
strings for backward compatibility. However (at least)  the 
ZopePageTemplate
class constructor has a flag 'strict' to enforce the use of unicode.

-aj

>
> FWIW, this seems to be problematic due to Zope 3's i18n stuff returning
> unicodes.
>
> Prior to that, everything was a happy utf-8 encoded string.
>
> What does Zope 2.10 do with all of this?
>
> cheers,
>
> Chris
>
> --
> Simplistix - Content Management, Zope & Python Consulting
>             - http://www.simplistix.co.uk



-- 
ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany
Web: www.zopyx.com - Email: info at zopyx.com - Phone +49 - 7071 - 793376
E-Publishing, Python, Zope & Plone development, Consulting
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
Url : http://mail.zope.org/pipermail/zope-dev/attachments/20060717/216119e2/attachment.bin