The message 200510150154.51134.runlevelten@gmail.com from Ten runlevelten@gmail.com contains these words:
On Friday 14 October 2005 20:09, MJ Ray wrote:
Ten's mail client (KMail) is using quoted-printable for plain text emails, which seems broken.
What, just the idea of using quoted-printable?
IMO, yes.
If so, KMail has been using qp in signed messages, and IIRC the PGP/MIME sp= ec has the use of quoted-printable or base64 in such signed messages as a=20 required/must.
Well, does that excuse M$'s introduction and (mis)use of HTML and embedded Word in e-mails and news?
Mail and news together are a text-only medium. (AUP and various protocols.)
It's a bit harsh to see that behaviour as "broken", I think.
From the angle of what my mailreader (which does in fact read qp if
properly presented) it *IS* seriously borked.
(Not only that, it is *SERIOUSLY* borked..)
I'd be more inclined to call it intentional and standards-compliant than=20 broken.
No, it is completely standards non-compliant.
Now, if you want to talk about whether the _standard_ is borken or whether = I=20 can help list harmony by doing it a different way, that's a different matte= r,=20 but broken seems a bit unfair, tbh.
It should only be necessary if there's 8bit text and a known dud mailserver, or lines of more than 1000 characters. Otherwise please use Content-Transfer-Encoding: 8bit and everyone's happy, give or take a few spare headers.
I'm not clear on what this would achieve, would you mind elaborating please= ?=20 Thanks.
Well, it would mean that everyone, techie or beginner, endowed of loads of round tuits or tuit-challenged would be able to read what appears in e-mails (and news).