With the information you provided I'd first try this on a python prompt on a working machine : "Köln" == u"Bonn" If this does not throw the same error, somebody changed the python default encoding. Then I'd look if some of my validators get constraints with umlauts. But I guess, you tried that already?
On Wed, Nov 28, 2012 at 7:12 PM, Charlie Clark < [email protected]> wrote: > Hi, > > one of my sites has (hopefully) started behaving funny. I have a formlib > driven contact form that is rejecting any input that is not ascii as part > of the validation step of the form: > > UnicodeWarning: Unicode equal comparison failed to convert both arguments > to Unicode - interpreting them as being unequal > > I may have got this wrong but I thought inputs into forms could be > considered as unicode and we only had to worry about them when storing them > in case they were being accessed by non-unicode-aware code. > > What's really puzzling is that I have almost identical forms on other > sites that don't exhibit this behaviour which makes me think it must be a > configuration error such as the default encoding which is set to utf-8 for > this site. > > Any ideas? > > Charlie > -- > Charlie Clark > Managing Director > Clark Consulting & Research > German Office > Kronenstr. 27a > Düsseldorf > D- 40217 > Tel: +49-211-600-3657 > Mobile: +49-178-782-6226 > ______________________________**_________________ > Zope-CMF maillist - [email protected] > https://mail.zope.org/mailman/**listinfo/zope-cmf<https://mail.zope.org/mailman/listinfo/zope-cmf> > > See > https://bugs.launchpad.net/**zope-cmf/<https://bugs.launchpad.net/zope-cmf/>for > bug reports and feature requests >
_______________________________________________ Zope-CMF maillist - [email protected] https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
