On Sun, 25 May 2014, Thorsten Glaser wrote:
Sure: When you view a raw message using ‘h’, and the message was base64 content-transfer-encoded, you do *not* want this base64 to be interpreted as if it were in the content-type/charset, because the charset only applies to the message *after* base64 decoding. Instead, you want to view the raw base64, which is ASCII, which is a UTF-8 subset.
But the "h" command does not do that, that is, you should be able to see anything literally; BASE64 should be BASE64. If you are having this problem, this is a problem that has nothing to do with this patch/feature. Submit this as a different bug, and show an example that shows this problem.
-- Eduardo http://patches dot freeiz dot com/alpine/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
