-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 06.08.13 19:38, Kreuvf wrote: > 08/01/2013 03:26 PM, Patrick Brunschwig wrote: >> On 01.08.13 15:04, Kreuvf wrote: >>> 07/29/2013 08:29 AM, Patrick Brunschwig wrote: >>>> As Thunderbird will do an additional line wrapping after >>>> Enigmail has created the signed message, the two additional >>>> characters would cause line wrapping after the signature was >>>> created - which would destroy the signature. > >>> So, everything I described, especially examples #3 to #5, >>> actually is not a bug, but a feature? > >> Not entirely. Thunderbird line wrapping (which is what Enigmail >> uses) is not ideal. But it's better than no rewrapping ... > > Could you please be clearer about which behaviour should be > considered a bug of Enigmail, a bug of Thunderbird, or a feature?
I consider: * the fact that TB does line rewrapping: a feature * the fact that TB uses two different implementations of line wrapping (one in the editor and a different one later during the send process): not ideal * the way how the TB mail editor does line wrapping (which is what Enigmail uses): buggy * what Enigmail does to avoid issues with too ling lines: a hack - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEVAwUBUgIIWMk25cDiHiw+AQjArAgAqlZ54LCOFvK8KbRkHMWBtIOrpmCCT9zC dKyKSQhOTUjFwTJrMFyTR6qopoLNdCrqGG2U4U3pVKNFedblzBGqEwpCoxdJ7tn5 G/RzampKSpWvow57xACLvCvWkkwsctmHxnMLfbW9w6MH3TF5Xn81cbcOaZXw2UY/ V6JGQdHGS5NoZ0ZQzxv58RX9hRWjsrwMJK5UohlbgndBSU6ULhRPGZ15OhOASTgI Niki2mkx38zE/cUGKFlKGQsSJBNh63R0mg5WhbxtlvQqiBJAimuRqloNIRKRnBnx 8tPxigJk/gV16uJGTYVAInhc5g7Dk3nYLaxByvnjtEUXcI++EXVqIQ== =fJiJ -----END PGP SIGNATURE----- _______________________________________________ enigmail-users mailing list [email protected] https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
