-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi
Am Dienstag, 15. Mai 2018, 22:19:17 schreiben Sie: > 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? I think a fundamental discussion is necessary with the question: Who should / will use GnuPG in the future? Two extremes: Only these people who need really to encrypt their emails because they are persecuted. But these people learned how to handle their email client correctly and these people will write text-only also in the future. Or is Email encrypting a need for *every* email user? But there the standard today IS that mails are HTML-written and contain links and pictures and so on. If GnuPG should be a tool for "everybody" HTML mail must be encrypted and decrypted correctly by the clients and GnuPG should give any important information, - -- Regards Martin -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE92uV/w2x7WB1p4XLsdyR185C444FAlr8NjoACgkQsdyR185C 4474IAf/VBxWlV8/r5QHblhK6wUVzZFflEJH1zrE25notn3F5SNp35hoF6JkbjNU sbej2HMAaGPaSn7zoFNs6npzw/1jR0/Y8o6jgRR2XfDjCMMhMrDvfiGceoOvDNoG FJfV5llksYKUYPXzxrxQLJ+m553MItZ2VfN0SXz4cLnH+cqEcXAt9dKHYdJPJjus CxmEDe0U+noYYn+Pr7i6Lx18OGDyPot6OGt1lJ9biQhTpfn0/WuyFkHaNSRFoe8Z LnLIjyvcKbb083nsYCQWlY59QR2Kz38ulzFajwGYx8fKXwFxSptpwEM8xbD0u/vh DlGPOnzX7W8wgzvn+2AyQ/hi9kVWPg== =Gbsn -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
