On 11/29/2012 08:20 PM, Charlie Clark wrote:
I'm forwarding this from the CMF list as I'm stumped. I worked my way up
the debug stack but couldn't find what was causing one Zope instance to
decode to unicode and the other to leave content as utf-8 (or maybe it's
the other way round?). Both instances on the same machine.

Any ideas?


------- Weitergeleitete Nachricht -------
Von: "Charlie Clark" <charlie.cl...@clark-consulting.eu>
An: zope-...@zope.org
Betreff: Re: [Zope-CMF] Weird UnicodeDecodeError with zope.formlib
Datum: Thu, 29 Nov 2012 11:52:13 +0100

Am 29.11.2012, 09:43 Uhr, schrieb Charlie Clark

No. I guess I'll have to look more closely at the wigdets data. As I
said a different site on the same machine doesn't exhibit these
problems so I should have a point of comparison.

Definitely weird. From site 1:

(Pdb) t = self.widgets['town']
(Pdb) t._getFormInput()

as expected but from site 2:

(Pdb) t = self.widgets['town']
(Pdb) t._getFormInput()

Note the similarity of the field name as one of these forms started out as
a copy of the other. Need to check what is causing this. I think I might
have set a default encoding for Zope to UTF8 ostensibly to reduce IE /
Safari errors. Oh, isn't this fun!


I think I had the same. My hunch was IE, but had no repro.
If you *have* a repro, you could log the *whole* raw request input and investigate what's the difference.

Best regards,
Quote of the day:
And I smiled to think God's greatness flowed around our incompleteness; Round our restlessness, His rest.
- Elizabeth Barrett Browning
Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope )

Reply via email to