Closing this on OpenERP server, sorry but tools.ustr() is not the magic answer
too all encoding issues, despite what you might think.
You still need to properly know/detect what encoding you are reading strings
in, in order to know if tools.ustr() will be able to help you.
BTW the convention is for tools.ustr() to raise an exception when
something cannot be converted to unicode, this is much better than
silently returning None or u''. In this case it apparently helps
highlight an upstream issue, so that's Good!
** Changed in: openobject-server
Status: Confirmed => Invalid
--
Error in accented characters encoding in received mail
https://bugs.launchpad.net/bugs/493997
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
Status in OpenObject Server: Invalid
Status in Power e-Mail for Open ERP: Incomplete
Bug description:
* Display problem with accented characters, here is an example of mail
downloaded:
Je l'ai d=E9ja envoy=E9 un e-mail et j'attends encore sa r=E9ponse.
D=E9sol=E9 pour le d=E9lai mis pour r=E9pondre =E0 vos mails, je
suis trop= pris par la charge de travail que j'ai
(=E9 is é ; =E0 is à)
_______________________________________________
Mailing list: https://launchpad.net/~c2c-oerpscenario
Post to : [email protected]
Unsubscribe : https://launchpad.net/~c2c-oerpscenario
More help : https://help.launchpad.net/ListHelp
