Summary: | KMail cannot correctly display subjects with UTF-8 characters encoded in quoted-printable fomat | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | gambas <g4mba5> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Mandriva RPMs | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
gambas
2009-07-21 18:33:10 UTC
Sorry, but the example you have given is invalid. According to RFC 2047, section 4.2. 'The "Q" encoding', part (3), it is not allowed to represent the '?' as itself. This means =?utf-8?q?es_bizarres_?_[...] should be =?utf-8?q?es_bizarres_=3F_[...] File a bug report against the mail client that produced this message. SVN commit 1002322 by tmcguire: Be more robust against invalid encoded strings that have a stray '?' in them Glad we have unit tests here, otherwise I would have introduced many regressions here. CCBUG: 201017 M +17 -14 kmime_header_parsing.cpp M +6 -6 kmime_warning.h M +32 -0 tests/headertest.cpp M +3 -0 tests/headertest.h M +3 -0 tests/rfc2047test.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1002322 You are right, this is my fault, I didn't read the RFC carefully enough when I wrote my quoted routine. I was thinking KMail was false because KMail/KDE3 and GMail were more tolerant! Shame on me :-) |