-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Adeodato,
Am Sa den 7. Mai 2005 um 19:11 schrieb Adeodato Simó: > (Right, I forgot to reopen the bug in Sep 2nd, when I finally > understood what the issue was, and now the bug is archived. Sorry for > the inconvencience.) Oh, ah, I see. I also did lost the discussion I think or missed a mail. However... > (Actually, my mail on Sep 2nd implicitly contained "a patch".) :-) Yes > No, before considering adding that patch I nead clear answers to the > questions that I made on Sep 2nd [1]. I do understand what the problem > is for you, and as you say, it used to work in previous versions. > However, a change in that behavior was introduced by upstream, and I > won't overrule that decision, because they may have had good reasons > to make the change. OTOH, perhaps the change was not intentional, but > I need them to tell if that was the case. Sorry, my english is leaving me. Did you mean that the upstream author force you to change this back to the buggy way and ignore the usersettings? Well, I know the opinion about non-UTF-8 charset of the upstream author; I did discuss it with him years ago. For him there is no other than UTF-8. But that's exactely the reason why many people did develop these patches to fix this hardcoded stuff. > What I want you to understand, Klaus, is that I must listen to both > sides of the discussion before taking a decision. I asked already > once, if you're particularly interested, then you can ask again and > nag for an answer. In the meantime I'll do nothing, __specially__ > because Mutt is creating perfectly valid messages that most sane MUAs > can handle. If your mail is going through a program (tracker?) that > changes the content-type, fix that program to add stuff in the > original charset. But this is exactely the point, I use iso-8859-1 as charset and also say gpg that this is my charset. But now mutt do set the wrong charset in the outgoing mail! (The Mailbody is iso-8859-1 and all filters can handle it properly but mutt then change it to UTF-8 which is wrong as I sayed it other to the application.) It dosn't mather for me that it might be eventuality display fine in sane MUAs. The world is foll of non-sane ones. This point and the point that the upstream author think that inline is deprecated is fine for a completely sane environment but not for the real world. (Morover mime-signatures are bad in many cases and only inline signatures can be checked everytime; also if you use a web mailer. But this is a other point and not directely related to the bug as in debian there are the right patches for it.) Gruß Klaus Ps. As I told, my english is leaving me. So I hope I could make the poinds understandable. Why could the world language not be german... ;-) - -- 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.0 (GNU/Linux) iQEVAwUBQn0BaJ+OKpjRpO3lAQKiXQf+Ku2sWxG0YQoqbxLJcV+UpYj4xWibTogj 1QW9ecqzPfMODJVGtLqu83US5w1pE+O+UTWmHQlTpcylSo+ob2EFI2z4WcVplfAX cprBTWBfoq3J+/Ovd5YD75iGberQTfh6z602YmiV3/Ky+vTYg6OpUAk4wl82c5AW 1EnmpxE4nwl+2oOAqQJrqv0115D0LGKxxpCGHYVFh8FsAvp3iP3PJhAvpm/28Mvi u6sWq+Ogz8djWYM4wndmDnKaEJkKk0GF0C3TMiEWZCXd2rErnDVvpK2o2PTqtEjD sPtIkjNHNxKRih+BOSRwCDyLYgkVOCA9EV9Haa10t8WGQQV2lWD6Gw== =IVyy -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
