a desktop arcane chat would be nice for the md support. until then we’re stuck w dchat client
lucarne
September 1, 2026, 7:52pm
26
link2xt:
foo ***bar **baz * foo is not parsed by this forum (it displays foo ***bar **baz * foo), same for CommonMark, but pandoc converts it to <p>foo <em><strong>bar </strong>baz </em> foo</p> (when not in CommonMark mode). And there are lots of cases where you want to just type literal * and escaping rules for * differ among implementations too. You can’t just escape everything, because it will be unreadable in plaintext, and the longer the text, the higher the chance that some unescaped * will be treated as a closing symbol. Add unicode character classification to the mix, with differences in how punctuation characters and so on are dectected depending on the version of unicode supported. pandoc has round-trip test for markdown disabled for this reason, and it is very difficult to make it work
Everything has been said. Chatmail core should not support Markdown. Html is a wiser path (or something else equivalent).
Then, nothing prevent the clients to implement Markdown realtime interpretation (meaning you write in markdown and it is immediately converted to WYSIWYG).