3 ms·
The worst part of those is that most of the time the HTML isn't even HTML. It's encoded in some some sort of weird email-html-specific content type. Base64 if y
by superkuh 4y ago
The worst part of those is that most of the time the HTML isn't even HTML. It's encoded in some some sort of weird email-html-specific content type. Base64 if you're lucky. Something far more obscure and email-html specific if you not.
When that happens I then have to copy the raw encoded "text" into some shady website $email-html-specific-content-type to text converter just to get the html in it's natural character set to manually find and copy the <long-url-with-lots-of-tracking-guids>.
- blueflow 4y agoDo you mean https://en.wikipedia.org/wiki/Quoted-printable https://en.wikipedia.org/wiki/Quoted-printable ? Since its a transfer encoding, the email client needs to decode it before rendering it. Its comparable to HTTP chunking.
- superkuh 4y agoAh, so not directly HTML's fault. Thanks. It's just the confluence of Quoted-printable transfer encoding and the tendency for HTML emails to embed links split up and in non-href and other tags that end up not getting rendered on my thunderbird fork in text mode which means I have to view source and deal with the Quoted-printable URLs.
- blueflow 4y agoI think you need to patch your client to decode that, in the same vein it needs to be able to decode base64-encoded bodies.