You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related to #1745 (and somewhat to #3171), I wish K9 Mail had an option to send and receive mails that are explicitly labeled as using Markdown (preferably in the Commonmark variant) as specified in RFC 7763 and its companion RFC 7764.
Not many mail user agents do implement these yet, unfortunately, and there would need to be some tests whether sending as text/markdowninstead of rather than in addition totext/plain yields any serious compatibility problems. The expected result is that receiving MUAs just display the Markdown text verbatim.
Receiving such mails and parsing them for enriched displaying should be implemented regardless.
Related to #1745 (and somewhat to #3171), I wish K9 Mail had an option to send and receive mails that are explicitly labeled as using Markdown (preferably in the Commonmark variant) as specified in RFC 7763 and its companion RFC 7764.
Not many mail user agents do implement these yet, unfortunately, and there would need to be some tests whether sending as
text/markdown
instead of rather than in addition totext/plain
yields any serious compatibility problems. The expected result is that receiving MUAs just display the Markdown text verbatim.Receiving such mails and parsing them for enriched displaying should be implemented regardless.
Expected behavior
text/markdown
instead oftext/html
ortext/enriched
(RFC 1563/1896) ortext/richtext
(RFC 1341/1521).text/markdown
.Actual behavior
text/plain
(ortext/html
?).The text was updated successfully, but these errors were encountered: