Richard Heck wrote: > I'm not sure what's causing the error. It looks as if maybe unicode is > being used in some cases, but then it isn't properly handled after the > switch.
But this would apply to all cases where the encoding is switched (not only the backend). Jürgen