3 ms·
Not going to happen. If you look at the CommonMark discussions, you will find people adamant that X features not be included for varying reasons. I think the b
by 0cf8612b2e1e 4y ago
Not going to happen. If you look at the CommonMark discussions, you will find people adamant that X features not be included for varying reasons.
I think the best future option is going to be djot[0]. It is being created by the author of pandoc, who might possibly be the most qualified person in the world to appreciate all if the nuances of marking up text and parsing it.
[0] https://www.djot.net/ https://www.djot.net/
- leephillips 4y agodjot syntax looks just like Pandoc’s markdown. What’s the difference?
- 0cf8612b2e1e 4y agoClean slate design. I think pandoc markdown is a superset of markdown, which must parse the ambiguous parts of the spec. Djot has a goal to eliminate the corner cases and be able to represent all things without requiring the html escape hatch (eg bold text within a word). The rationale page can do a better job than myself. https://github.com/jgm/djot#rationale https://github.com/jgm/djot#rationale
- leephillips 4y agoThanks, that makes sense. Although I’d like to point out that one of the listed problems with commonmark, and the problem you mention, are not problems with Pandoc markdown: : echo "word**withboldtext**inside" | pandoc <p>word<strong>withboldtext</strong>inside</p> : echo "a*?*b" | pandoc <p>a<em>?</em>b</p>