[kmail2] [Bug 248058] Message preview pane character encoding issue (utf-8, unicode)
Sandro Knauß
knauss at kolabsys.com
Sat Apr 18 16:46:09 BST 2015
https://bugs.kde.org/show_bug.cgi?id=248058
Sandro Knauß <knauss at kolabsys.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|message list |crypto
Status|REOPENED |ASSIGNED
Assignee|kdepim-bugs at kde.org |knauss at kolabsys.com
CC| |knauss at kolabsys.com
--- Comment #5 from Sandro Knauß <knauss at kolabsys.com> ---
The problem is that PGP inline is not a standard at all and it is not definded
what charset is to use when displaying the mail. For kmail we said that the
charset field in the mail indicate, what charset the decrypted message have.
Because the encrypted part is everytime ascii. This is mostly that what the
most email clients does.
RFC 2440 only says:
"Charset", a description of the character set that the plaintext
is in. Please note that OpenPGP defines text to be in UTF-8 by
default. An implementation will get best results by translating
into and out of UTF-8. However, there are many instances where
this is easier said than done. Also, there are communities of
users who have no need for UTF-8 because they are all happy with
a character set like ISO Latin-5 or a Japanese character set. In
such instances, an implementation MAY override the UTF-8 default
by using this header key. An implementation MAY implement this
key and any translations it cares to; an implementation MAY
ignore it and assume all text is UTF-8.
-> The best would be if apine would have used the Armor Header Key "Charset".
To not break the existing way, i would only switch to default utf8 decoding if
the surrounding charset is ascii :) Because every ascii text is the same in
utf8...
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Kdepim-bugs
mailing list