Earlier quoted context omitted.
I had a recent request from a product owner to style the subject line... I said we can't do that and that I don't want to live in a world where senders can change the font or size of the subject in an email.... Can you imagine the crap we would have from spam in that case?!
Y̗̳̬͍̘͚o͘u͏ ͏̬̟̩h̦̕a̰̖͍̟v̧̯̜͉͙̖͖͉e҉̳̲̙͚̗̬ ̤͚͉̀w̢̫͎̮̼͇o̷̮̙̩n̪͙͎̠͔ ̻̮a̛̭ ̡̪̤̻ͅp̵̭͇r̩͉į̬̺̭̯͍͙z̯͈͟e!͖̖͈̯ ie don't any mua let you use UTF8? 𝔻𝕠𝕖𝕤 𝕥𝕙𝕚𝕤 𝕨𝕠𝕣𝕜?
Can I Email: ‘Can I Use’ for email
151–160 of 206 posts
Re: Can I Email: ‘Can I Use’ for email
#152Earlier quoted context omitted.
Something like this? http://www.rfc-editor.org/rfc/rfc1896.txt
Thanks for the RFC link. Yes, basically. I mean, different mime versions of the same content are a possibility to do this transition: Send both plaintext, HTML and markdown, and the receiver could choose to display markdown if he otherwise would display plain text. To be honest, this won't come. Google is pushing AMP into mails, that's exactly the opposite direction.
Re: Can I Email: ‘Can I Use’ for email
#153This is really helpful - kudos! Sidenote: you can always avoid the hassle of testing HTML/CSS across email clients by just using plain text. :P https://bradleytaunt.com/plain-text-emails/
Re: Can I Email: ‘Can I Use’ for email
#154Earlier quoted context omitted.
Markdown is nice for composing, but not as a standard to be supported by many clients. CommonMark is an improvement, but there is way to many ambiguities and differences in supported features over different markdown parsers for it to be feasibly used as a standard. Markdown is also not any better than HTML in terms of security - most markdown parsers allow passing through arbitrary HTML, and then depend on sanitizing…
This is a bigger issue than most people care to admit. I post stuff to a number of different sites that support "Markdown" and not a single one agrees on even something a simple as how to format a hyperlink. I end up having to hit the help page on every site to remember which syntax they use, if they even support the feature at all. HTML might be "ugly", but at least it is consistent.
Re: Can I Email: ‘Can I Use’ for email
#155You send me anything other than plain text in an email, and I don't already have a source filter for your address, it gets sent to a folder that I might look at if I have the time some day.
99% of important transactional email I get is HTML. Kind of nice to have your boarding passes and two-factor authentication emails easily visible.
Re: Can I Email: ‘Can I Use’ for email
#156Why using plain text is better: - readable under any mail client and any text editor - smaller size files - safer - better accessibility and compatibility with screen readers
I don't get why plain text would be more accessible than a well-formed HTML email. A screen reader could say "this is a title", "this is a list item". In plain text, what do you get? "dash bla bla"? Though I hope screen reader are more intelligent than that, but it seems like a more complex problem than just using information given by a well-formed HTML text.
Re: Can I Email: ‘Can I Use’ for email
#157Re: Can I Email: ‘Can I Use’ for email
#158Earlier quoted context omitted.
Y̗̳̬͍̘͚o͘u͏ ͏̬̟̩h̦̕a̰̖͍̟v̧̯̜͉͙̖͖͉e҉̳̲̙͚̗̬ ̤͚͉̀w̢̫͎̮̼͇o̷̮̙̩n̪͙͎̠͔ ̻̮a̛̭ ̡̪̤̻ͅp̵̭͇r̩͉į̬̺̭̯͍͙z̯͈͟e!͖̖͈̯ ie don't any mua let you use UTF8? 𝔻𝕠𝕖𝕤 𝕥𝕙𝕚𝕤 𝕨𝕠𝕣𝕜?
The first one does not work great in a terminal. The words are readable but I don't get the full experience. The second one, pretty good.
Line 1:
" You have wøn a prize! "
Unincluded line; my sister got bitten by a prize once. Or a terminal. Onto line twø: two:
Line two: (2:)
" ie don't any mua let you use UTF8? "
And three:
" Does this work? "
All the lines for all the good people. The " signs " are a delimiter for each line. They're, or should be pretty verbatim, minus the unrenderability.
Have fun.