Support Standard Markdown

[KyleAMathews]

https://github.com/jgm/stmd

[scottgonzalez]

Do you care to elaborate on what isn't supported?

[KyleAMathews]

I haven't done any investigation. I assume there's some discrepancies and that either those be resolved or it be another supported "mode" like Github-flavored Markdown.

First step I'd assume would be to run marked.js against the spec to see where marked.js differs.

This all, of course, assumes that the maintainers of this library agree with the modifications proposed by the group behind Standard Markdown.

[commenthol]

Just running the tests of the stmd suite:

marked

stmd$ perl runtests.pl spec.txt marked
169 tests passed, 272 failed, 0 skipped.

stmd

stmd$ perl runtests.pl spec.txt js/markdown
437 tests passed, 4 failed, 0 skipped.

[chjj]

I'm going to be looking at this over the weekend I think. Personally I'd like to get involved with the spec itself, particularly with Lists. I'm almost certain List tests are most likely failing there due to my own biased logical/more-intuitive implementation of them. While standard markdown is robust in that area, I think it still misses some things.

Aside from gfm and the behavior muted by pedantic=false, marked tries to follow markdown.pl exactly, if the standard isn't doing that it will be incompatible with marked (I have a feeling markdown.pl would fail even more of those tests: i.e. would you really want raw markdown.pl "replacement tags" in your markup?). This will be a new design decision for marked and we'll have to figure out where to go with it.

(This is also not the first time a markdown spec has been tried before, If I remember right. Like Wayland is the king of a dozen would-be X11-killers over the course of a decade and a half, this might be the one spec that finally dethrones markdown.pl. Who knows?).

[joshbruce]

Closing for now as stale. See #956 and the two targeted specifications.