On 18/03/2020 02:40, Anton Rieger wrote: > On Wed, Mar 18, 2020 at 02:51:45AM +0100, Wesley Peng wrote: >> Hello > Hello > >> >> Following this guide: >> https://useplaintext.email/ > I don't like it's tone but it's mostly ok > >> >> Shall we use plaintext message in regular email communication? > I use it regulary, except if I give tutorials in support mails with > more than two images. > It's way easier to refer to inline images than say: > > Do xyz like you see in image1.png. > Lorem Ipsum.... look at image2.png. > > Or like[1] to look something[2] up.
The problem there is that you've just re-invented markup. Cross-referencing some text to an image? Isn't that just <a href="#link">txt</a> or whatever? There is clearly a desire among users for something more than plain text. You often want *emphasis* in flame wars. You want a table in reporting your financial results or when listing various things. However, I think everyone can agree that "Responsive emails", trackers, frameworks and so on and so on is just TOO MUCH. I'd argue then, that a middle ground is the way forward. Emails should be written in a markup language which is both relatively simple (yet flexible enough to handle the basic formatting commands) and human readable before (and after) rendering. Markdown is a very good step towards this, IMO. > >> >> Thanks > > Regards > Anton Rieger > -------------------- > [1] image1.png > [2] image2.png
signature.asc
Description: OpenPGP digital signature
