Message4927
Default Python charset is 'utf-8' only for version 3 as i found in many
documents.
I was trying to investigate roundup code and remove various decode and
str(). But then error appears in different place and when it was on
_socket_op(self.request.wfile.write, str(content)) in client.py i gave up.
I don't fully understand a conception of charset handling in roundup.
Things, like
- client.py (write_html)
if self.charset != self.STORAGE_CHARSET:
content = content.decode(self.STORAGE_CHARSET, 'replace')
content = content.encode(self.charset, 'xmlcharrefreplace')
- engine_jinja2.py (render)
return self._tpl.render(c).encode(client.charset, )
are implying that all output will follow a client preferred charset. But
roundup templates prepared by a roundup administrator usually contain
predefined ' <meta http-equiv="Content-Type" content="text/html;
charset=X">' in they content, as seemed to me. |
|
Date |
User |
Action |
Args |
2013-09-23 10:36:17 | antmail | set | messageid: <1379932577.72.0.314270556608.issue2550811@psf.upfronthosting.co.za> |
2013-09-23 10:36:17 | antmail | set | recipients:
+ antmail, ber, pcaulagi, shammash |
2013-09-23 10:36:17 | antmail | link | issue2550811 messages |
2013-09-23 10:36:16 | antmail | create | |
|