-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Antonio,
Am Mi den 17. Jun 2009 um 20:56 schrieb Antonio Radici: > I'm sorry that the patch does not fix your bug, please reopen it, absolutely! > We > have a bug upstream linked with that bug which was resolved with the following > explanation: Ok, I did reopen it and set found to 1.5.20-1. [...] > The sending side is not touched, we unconditionally send UTF-8. > ---- > > So they just fixed the receiving side and not the sending side, Seems so. > is this still an issue to you? Yes. It is. It is that hard issue that without patching that crap out of mutt I would not use it at all. (As I told I always patch it and compile my own version locally. The patch is taken from a very very old debian release I think around 2004. But the patch is still fine (with some small merging issues).) > I think that there is another bug in the queue about the send_charset > defaulted to utf-8 and upstream refused to change it (Based on the RFC > I suppose); can you please have a look at 441950 and see if it's more > appropriate to follow up there? As I understand it the user wants to have exact the opposite of me. And he told by the default. The problem I have is that the send_charset is completely ignored if and only if the mail is signed inline (like I do allways). Gruß Klaus - -- Klaus Ethgen http://www.ethgen.de/ pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <[email protected]> Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iQEVAwUBSjlRwJ+OKpjRpO3lAQrcNwf+LDGNv2mfd5H3OLTXewvC+RkW9sfAzoro gV/mHIhtoE1y3vzTBf4gUIXqvzNKo8zHxA/0RZXEgVAK2yoOX8kzrsVAG1bMZhFd OEfzO65PcSZqfCgB4ddECE9WVnJyXn76uwKHi37O+ShIg61LLvSaAR6JZCUheXIf ibJ/arVWJ2Xwu/ezXVZOH9diq+QKnxO5ncyrVQnvSAzB85aU56XnRLShurGvcqMl 0ZTrGoSuRXXd9M5jT140zHBmOcm0KrX+sGCKNFhFf5TsBoQAejd3lI93anw6GRp0 fja2QqnamcbvFFbBfGZ2PCYaHWKI/Jf6HoVqTggvS8TZS125gv8v2A== =v6y+ -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
