[ZCM] [ZC] 1200/ 3 Reject " non-latin1 object titles & portal properties causes UnicodeEncodeError when viewing from ZMI"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #1200 Update (Reject) " non-latin1 object titles & portal properties causes UnicodeEncodeError when viewing from ZMI"
 Status Rejected, Zope/bug medium
To followup, visit:
  http://collector.zope.org/Zope/1200

==============================================================
= Reject - Entry #3 by htrd on Jan 26, 2004 5:08 am

 Status: Pending => Rejected

> when I put an object somewhere with Title containing non
> latin-1 characters

The correct solution is to use unicode objects to store these properties, rather than a plain 8bit string.

> sitecustomize.py set to UTF-8 

This is not a supported configuration of zope.



________________________________________
= Comment - Entry #2 by bouillon on Jan 25, 2004 8:10 am

not only Zope 2.7.0b3, Zope-2.6.4-rc1-src too.
I use UTF-8(russian) and see in properties only "небольшая интернет-платформа Германии"
________________________________________
= Request - Entry #1 by kaixo on Jan 21, 2004 5:17 am


Issue 2385 of Issue Collector [Plone]
Title: 	non-latin1 object titles & portal properties causes UnicodeEncodeError
Target Version: 	Undecided
Status: 	Rejected 	Security related: 	No
Description: 	Error Type UnicodeEncodeError 'latin-1' codec can't encode characters in position 50964-50965: ordinal not in range(256) This appears every ti...
From: 	kaixo 	on 	Jan 15, 04 09:31
	Anonymous User 	Last update: 	Jan 21, 04 00:25
Topic/class: 	Unknown/bug 	Importance: 	medium
Version info: 	Plone version: 2.0-RC2, 2.0-RC3 Zope version: 2.7.0b3 Apache version: 1.3.29 CMF version (if known): 1.4.2 Browser(s...
 
Transcript for Issue 2385 (5 )
= Reject - Entry #5 by limi on Jan 21, 2004 12:25 am

 Status: Pending => Rejected

This is a Zope problem, not a Plone problem. Plone handles Unicode just fine. Please report in Zope Collector. ZMI has problems with unicode.
________________________________________
= Comment - Entry #4 by kaixo on Jan 20, 2004 3:58 pm

Sorry, I haven't got much time to test it on RC4 bugday but the problem with the description and title of the portal still remains. I could create a new plone site with non-latin1 characters, but next time when I checked it out from ZMI, returned something like őűúóüöáűé (browser set to utf-8 encoding), and wasn't able anymore to change to a non-latin1 string.

I've fetched the latest hourly build from test.plone.org (RC4) and put on top of a brand new Zope 2.7.0-rc1, using CMF-1.4.2 .

I could add standard CMF objects with non latin1 title without having problems to see them in ZMI, but I guess the problem of seeing some objects from ZMI is somehow should be related to Archetypes, but needs more testing.

________________________________________
= Comment - Entry #3 by runyaga on Jan 20, 2004 12:38 pm

could you upgrade to 2.7RC1 and see if this fixes your problems.
________________________________________
= Comment - Entry #2 by kaixo on Jan 20, 2004 12:36 pm

Traceback (innermost last):

    * Module ZPublisher.Publish, line 102, in publish
    * Module ZPublisher.HTTPResponse, line 298, in setBody
    * Module ZPublisher.HTTPResponse, line 433, in _encode_unicode

________________________________________
= Request - Entry #1 by Anonymous User on Jan 15, 2004 9:31 am

Error Type
    UnicodeEncodeError  

'latin-1' codec can't encode characters in position 50964-50965: ordinal not in range(256)

This appears every time when I put an object somewhere with Title containing non latin-1 characters, or try to set the portal properties.
When I try to enter the object's container from ZMI, this message preventing me to see the portal root for instance, if I have such object in my plone root folder.
I cannot put a non-latin character in my portal description either.

Using UTF-8 encoding, sitecustomize.py set to UTF-8 and so on, but I don't where the Latin-1 encoding comes from because I would never set it....

==============================================================