Comment by cdmckay
1 day ago
You could still support a subset of the most common features like bold, italic, strike, bullets, links, etc.
Isn’t the beauty of MD supposed to be that if you can’t render it it should still look fine as plaintext?
1 day ago
You could still support a subset of the most common features like bold, italic, strike, bullets, links, etc.
Isn’t the beauty of MD supposed to be that if you can’t render it it should still look fine as plaintext?
Even these basics are not consistent. See my Markdown Monster:
https://git.sr.ht/~xigoi/markdown-monster/blob/master/monste...
The problem for web browsers is that markdown is technically a superset of HTML.
Why is this a problem? To me it sounds like a it would be an advantage because you have everything you need to render it already built into the software.
Rendering is trivial. The issue is standards, and the DOM. No-one can write a Markdown implementation for the core of any major web browser in a form that is simultaneously acceptable to both their technical and political governance.
Best you’ll get is a plugin. Strictly arm’s reach. Translation only.
Why is it a problem for web browsers?