Message150459
I've been bitten by this too (in python up to 2.7 in roundup the bug-tracker). We're currently using a workaround that re-inserts spaces, see git on roundup.sourceforge.net file mailgw.py method _decode_header_to_utf8
RFC2047 even has a test-case at the end, it specifies:
encoded form displayed as
(=?ISO-8859-1?Q?a?= b) (a b)
note the space between 'a' and 'b' above. Spaces between non-encoded and encoded parts should be preserved. And it's probably a good idea to put the examples from the RFC into the regression test. |
|
Date |
User |
Action |
Args |
2012-01-02 15:50:44 | runtux | set | recipients:
+ runtux, barry, georg.brandl, alexanderweb, mgoutell, r.david.murray, BreamoreBoy |
2012-01-02 15:50:44 | runtux | set | messageid: <1325519444.69.0.779454686273.issue1467619@psf.upfronthosting.co.za> |
2012-01-02 15:50:44 | runtux | link | issue1467619 messages |
2012-01-02 15:50:43 | runtux | create | |
|