New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Markdown support compliant with CommonMark #142

Open
elazar opened this Issue Sep 3, 2014 · 6 comments

Comments

Projects
None yet
5 participants
@elazar
Copy link

elazar commented Sep 3, 2014

Markdown now has an official standard. It would likely be a prudent long-term goal of this project, since it appears to maintain its own implementation/superset of Markdown, to confirm or establish compliance with the standard.

@mb21

This comment has been minimized.

Copy link

mb21 commented Oct 9, 2014

+1
Also, there's a discussion about a consistent attribute syntax which's similar to what Pandoc, Markdown Extra and Kramdown use: {#id .class key=val key2="val 2"}, for example:

## my header {#myId}

my [span]{.myClass}

@elazar elazar changed the title Make Markdown support compliant with Standard Markdown Make Markdown support compliant with CommonMark Oct 9, 2014

@gnab

This comment has been minimized.

Copy link
Owner

gnab commented Dec 24, 2014

I'm a big fan of standards, and as long as the current feature set of remark may be retained, using CommonMark instead of Marked to do the vanilla Markdown conversion may be a better solution.

Also, in relation to #103 and #134, it seems using CommonMark even seems to resolve the issues.

@gnab

This comment has been minimized.

Copy link
Owner

gnab commented Dec 24, 2014

#161 also seems to get fixed by using CommonMark.

gnab added a commit that referenced this issue Feb 7, 2015

@gnab gnab added the commonmark label May 8, 2015

@gnab gnab modified the milestone: CommonMark Jul 27, 2015

@utdrmac

This comment has been minimized.

Copy link

utdrmac commented Jul 28, 2015

Well, honestly, I retracted my +1 vote. In CommonMark, there is no native support for tables. You have to do <tables> the old fashioned way. I'm disappointed in CommonMark by this. The multi-level nested <li> was nice but I think I use tables more.

@gnab

This comment has been minimized.

Copy link
Owner

gnab commented Jul 29, 2015

It would be possible to implement extra support for tables. I'm going to start an implementation based on CommonMark at some point, primarily to fix all the Markdown errors in Marked (the library currently used by remark to convert from Markdown to HTML). If table support is high on the list, then that has to be implemented on top of CommonMark at some point.

@gnab gnab removed this from the CommonMark milestone Jan 22, 2016

@jbaber

This comment has been minimized.

Copy link

jbaber commented Jan 29, 2016

Commonmark in remark.js would mean a lot to me. I've started a bounty with a tiny initial amount.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment