On 05/15/2018 04:44 AM, Patrick Brunschwig wrote: <SNIP>
> I think the correct solution must be to treat each MIME part > independently, i.e. it needs to be parsed independently by the HTML > engine and produce its own DOM tree. At the end, you can concatenate > these DOM trees and create a single correct HTML document. > > -Patrick So why use HTML with gnupg? For many years, by default I compose only text, view only text, display no inline images, and never fetch remote content. On the rare occasion that I've tested a fresh Thunderbird install, and accidentally composed HTML, Enigmail has always warned about the need to fold long lines. _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
