[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 calls PyUnicode_DecodeLatin1.

To see the problem:

* with the default default-zpublisher-encoding (Latin-9),
  - set a property's value to '€' (not in Latin-1)
  - Save Changes: it will be displayed as '¤' (the corresponding character)
  - Save Changes again: 'charmap' codec can't encode character u'\xa4' 
in position 0: character maps to undefined (because '¤' is not in 
(Latin-9).


* with default-zpublisher-encoding set to UTF-8
  - set a property's value to '€'
  - Save Changes: it will be displayed as '€'
  - Save Changes again: it becomes '€'


Note that this has repercussions not only on the ZMI but on other 
products, such as GenericSetup.



Some possible fixes:

* do nothing. This will please those wishing to deprecate the ZMI, but 
not the rest of us :-)


* rewrite properties.dtml as a ZPT?

* change join_unicode to use either default-zpublisher-encoding or yet 
another setting (which would default to Latin-1 to stay compatible)?



Flames, comments?

Thanks!

Yves

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


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

2006-06-08 Thread Andreas Jung



--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?

-aj

--
ZOPYX Ltd.  Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany
Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376
E-Publishing, Python, Zope  Plone development, Consulting


pgpW6M9DKjz08.pgp
Description: PGP signature
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


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

2006-06-08 Thread Tino Wildenhain

Andreas Jung schrieb:



--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?


they (sorry ;) suck :-) And they arent available in
manage_page_charset=utf8 (for whatever bd reason ;)

Regards
Tino
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


[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 of products hardwire 
their properties types.


I told this was an ex-horse, anyways :)



-aj



yves

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


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

2006-06-08 Thread Andreas Jung



--On 8. Juni 2006 15:40:59 +0200 Tino Wildenhain [EMAIL PROTECTED] wrote:


Andreas Jung schrieb:



--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?


they (sorry ;) suck :-) And they arent available in
manage_page_charset=utf8 (for whatever bd reason ;)


You have to use 'UTF-8' (everything in uppercase)...the related code in
properties.dtml is just horrible and stupid :-/

-aj


--
ZOPYX Ltd.  Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany
Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376
E-Publishing, Python, Zope  Plone development, Consulting


pgp01tz4miIWE.pgp
Description: PGP signature
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


[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. Except that lots of products hardwire 
their properties types.




... And that string and text properties are encoded using 
default-zpublisher-encoding, which is not Latin-1.  So in practice 
string and text can't much be used for anything but ASCII.


yves

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )