[Zope] zope/pone dies without traceback:cant uplaod data with umlauts anymore

Chris Withers chris at simplistix.co.uk
Wed Nov 9 07:49:52 EST 2005


robert rottermann wrote:
> *Error Type: UnicodeDecodeError*
> *Error Value: 'ascii' codec can't decode byte 0xc3 in position 0: 
> ordinal not in range(128)*

I would be extremely suprised is this actually killed the Zope process. 
What database adapter are you using? If Zope was dying, how did it 
render the above message?!

Unicode errors can be tricky to read, but if you do so carefully, you'll 
see that something is trying to turn a string into a unicode, and that 
string contains data which the default ascii codec can't handle. This 
will happen most often when you should be manually decoding a unicode 
encoded string...

cheers,

Chris

-- 
Simplistix - Content Management, Zope & Python Consulting
            - http://www.simplistix.co.uk



More information about the Zope mailing list