Problem with encoding (cherrypy)

[Paul Korotkov]

I run webclient. Main screen appears with unreadable characters. When I check encoding of page in Chromium it says that cp1251 is selected. When i select UTF8 all seems correct. But when i create database after creaton error occurs.
<type 'exceptions.TypeError'>: character mapping must return integer, None or unicode
      args = ('character mapping must return integer, None or unicode',)
      message = 'character mapping must return integer, None or unicode'

[Cyril MORISSE (cmorisse)]

Run webclient on a french computer.
Chrome reports welcome page is encoded as ISO8859-1 but display is garbaged.
If I manually set encoding to UTF8 Chrome reloads page and display it correctly.

But I enter in the customer creation screen display is garbaged again even with chrome encoding set to UTF8.

Note : This behaviour makes the web-client currently unusable for french users.

[Cyril MORISSE (cmorisse)]

This bug is related to cherrypy 3.2.0 which is installed by default on my mac with python 2.7.2.

If I uninstall cherrypy 3.2.0 and install cherrypy 3.1.2 it's ok.

Cyril

[Vishal Parmar(Open ERP) (vpa-openerp)]

Hello,

I have checked your issue as per your specification and I also tyr with different language but I did't face any problem.

I have use cherrypy 3.1.2 and python 2.6 It is working as expected.

Thanks.

[Vinay Rana (OpenERP) (vra-openerp)]

Thanks a lot for reporting this bug and contributing to OpenERP. Unfortunately the OpenERP Web Client project is not going to be developed further after the 6.0 series. As of 6.1 a newer and better web frontend known as the OpenERP Web project[1] will be available.
Our R&D developers normally work in Launchpad to fix bugs for the next release, but there will be no next release for the current OpenERP Web Client. As our resources are limited, all further R&D efforts from the Web team are dedicated to finish the new 6.1 OpenERP Web project[1].
This bug will be closed as "Won't Fix" to show that R&D won't be able to work on it.

Bugs affecting customers in production of course continue to be handled via the OpenERP Enterprise (OPW) maintenance service, and this is the recommended way to have them corrected directly in the 6.0 LTS stable branch.
You can find more details about all of this in the FAQ of our Bug Management Policy documentation[2].

If you are interested, you should soon be able to beta-test the new OpenERP Web 6.1 (this will be announced on OpenERP Community channels).

Thank you for your contributions and for your understanding!

[1] https://launchpad.net/openerp-web
[2] http://bit.ly/openerp-bugs-faq (FAQ #4)