Am 13.01.2011, 14:01 Uhr, schrieb Godefroid Chapelle <got...@bubblenet.be>:
>> Aren't you risking double encoding now? That patch looks like it makes
>> things worse, not better.
> I am not sure I understand what you mean.
the unpatched code checks to see whether a self.Title() or
self.Description() are unicode in which case they can be encoded. Your
patch will force encoding even on strings, ie. double-encoding.
Regarding the procedure: changes to the CMF should be tested on CMF
buildouts, with CMF specific tests. You should probably run the
exportimport with pdb to see what self.Title() is returning but, yes, I
suspect the problem you are experiencing is Plone and not CMF related.
Clark Consulting & Research
Zope-CMF maillist - Zope-CMF@zope.org
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests