[Zope-dev] Non-Latin-1 properties

2006-06-08 Thread Yves Bastide
Hi! Sorry to beat a dead horse: the ZMI doesn't allow using non-Latin-1 properties. * properties are stored using the default-zpublisher-encoding (iso-8859-15); * manage_propertiesForm is input--output'ed using management_page_charset (UTF-8) ... * ... but built using join_unicode, which

[Zope-dev] Re: Non-Latin-1 properties

2006-06-08 Thread Yves Bastide
Andreas Jung wrote: --On 8. Juni 2006 15:31:09 +0200 Yves Bastide [EMAIL PROTECTED] wrote: Hi! Sorry to beat a dead horse: the ZMI doesn't allow using non-Latin-1 properties. huh? How about using the utext and ustring properties? Er. Yep, of course you're right. Except that lots

[Zope-dev] Re: Non-Latin-1 properties

2006-06-08 Thread Yves Bastide
Yves Bastide wrote: Andreas Jung wrote: --On 8. Juni 2006 15:31:09 +0200 Yves Bastide [EMAIL PROTECTED] wrote: Hi! Sorry to beat a dead horse: the ZMI doesn't allow using non-Latin-1 properties. huh? How about using the utext and ustring properties? Er. Yep, of course you're right

[Zope-dev] Zope 2.5: allow_type

2002-03-12 Thread Yves Bastide
Hi, There seems to be a bug in either AccessControl.SimpleObjectPolicies.allow_type or Products.PythonScripts.module_access_examples.py, as module_access_examples's examples such as allow_type(type(re.compile(''))) dont work. Knowing neither Python nor Zope, I patched allow_type like this: