#217 — Unicode Error when creating Snapshot

by (anonymous) — last modified Jul 06, 2009 09:40 PM
Contributors: Ingo Wolfmayr
State Resolved
Version:
Area Functionality
Issue type Bug
Severity Medium
Submitted by (anonymous)
Submitted on Jul 06, 2009
Responsible Maurits van Rees
Target release: 1.2
Hi,

am having unicode encoding issues when creating a snapshot of the system.

"Module ConfigParser, line 366, in write
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 0: ordinal not in range(128) "

The exception is fired after entering an "Umlaut" into the issue body. There is no problem entering an "Umlaut" into the
 - issue head,
 - issue response and
 - steps to reproduce.

It would be great if someone could give me a hint on what I can do.

Cheers,
Ingo

Steps to reproduce:
To exclude every problem caused by a dirty install/configuration of plone, I setup a completly clean installation:

Plone 3.2.2. windows installer
Poi 1.2.4

Standard configuration, no KUPU support for POI. Just creating an issue tracker, creating one issue having for example "ä" as issue body text.

The issue is stored and the issue tracker is fully functional. When I go to ZMI --> Portal Setup --> Snapshot --> create Snapshot: I receive the error message. Changing the Issue body text from "ä" to "a" it works fine.
Added by Maurits van Rees on Jul 06, 2009 09:40 PM
Issue state: UnconfirmedResolved
Responsible manager: (UNASSIGNED)maurits
Target release: None1.2
Hm, one of the steps done when creating a snapshot is to export the content, but only the title and description are taken. This makes no sense to me, but there is no option to turn this off...

The problem at the Poi side is that the Description of an issue returns unicode and may contain accented characters. This is related to issue #135.

A workaround is to go to the edit form of all issues that have this problem, go to the metadata tab and add an explicit description there (without accented or other non-ascii characters).

Hm, I see I can register an own handler for exporting issues. I can use that to simply do nothing when exporting, instead of trying to do something silly and failing at that. Okay, done in r89351. Should be in version 1.2.5 once that comes out.

No responses can be added.