Comment 22 for bug 613721

Guys,

we had this trouble in found that in v6 too: https://bugs.launchpad.net/openobject-server/+bug/617484

Now, I would say: Python stuff definitely needs to be English. But for XML in views, as Borja says, it looks like it's much less RAD now, much less user friendly: all that slideware http://www.slideshare.net/tiny07/openobject-intro goes now to trash as now the noob users are supposed to know master all the tricks of Openobject translation system (even advanced integrators here don't know them as reported in that thread, how cool and smart is that to require beginners to know them?)

But more importantly, what is the the purpose of that whole code that blows up when encountering non UTF-8 in XML ???

Look, the patch I propose is even simpler: https://bugs.launchpad.net/openobject-server/+bug/617484/+attachment/1488450/+files/unicode.patch

It seems to me that OpenERP is trying to convert string into unicode twice currently which makes overhead and that new bug what is the purpose of that? Is my patch wrong?

I mean, if that whole encoding here is useless and pure overhead, then are we sure we want to make that bug occur just to make Openobject more cumbersome ??? Or am I getting it wrong is there a bug in my patch https://bugs.launchpad.net/openobject-server/+bug/617484/+attachment/1488450/+files/unicode.patch ?

Please explain...