[z3-five] Re: Extended characters in forms

Tarek Ziadé tziade at nuxeo.com
Thu May 12 13:59:54 CEST 2005


Lennart Regebro wrote:

>>>1. Force people to change the default encoing in site.py.
>>>2. Monkey-patch Zope3 to stop it from converting everything to unicode.
>>>3. Do some magic so everything in these forms is converted to unicode
>>>with the charset encoding in the for request.
>>>      
>>>
>>I tried #3, and you get problems with things that are for example
>>lists of strings, so that didn't work.
>>    
>>
>
>There is also of course 4: Stop using Zope3 forms and schemas all together.
>
>  
>
That what I did at first place, before my Product was moved to five. I 
added a mechanism that controls user input by safely translating it to 
unicode.

Isn't there any existing mechanism in z3 forms where a function can be 
hooked to verify and transform user input ?

z3 widgets waits for pure unicode or pure ascii feeding, and our CPS3 
forms are always iso8859-15.

Tarek

-- 
Tarek ZIADE, Nuxeo SARL: Zope Service Provider.
Mail: tz at nuxeo.com - Tel: +33 (0)6 30 37 02 63
Nuxeo Collaborative Portal Server: http://www.nuxeo.com/cps
Gestion de contenu web / portail collaboratif / groupware / open source



More information about the z3-five mailing list