My workaround is for unicodeconflictresolver.py.
The diff for Zope 2.13.13 is:
100,101d99
charsets.append('iso-8859-15')
But as the issue occurs with
Am 04.04.2012 16:25, schrieb Yuri:
Hi Yuri,
does this error occur with all browsers?
Yes, unfortunately.
I once had a
Il 05/04/2012 14:18, Stefan Loidl ha scritto:
I'm using a workaround similar to that in the bug report in my
environment (Zope 2.13.13 and a mixture of utf-8 and iso8859).
Without the workaround the issue does still occur for me.
can you send me your workaround? Maybe it can help :P
My
Hi Yuri,
does this error occur with all browsers?
Yes, unfortunately.
I once had a similar issue
that was caused only by some browsers because they do not send a
HTTP_ACCEPT_CHARSET header.
Maybe the following bug reports helps you in solving the issue:
