Skip to content
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

Use CommonMark instead of loosely defined Markdown flavour #563

Closed
dumblob opened this issue Mar 27, 2015 · 5 comments
Closed

Use CommonMark instead of loosely defined Markdown flavour #563

dumblob opened this issue Mar 27, 2015 · 5 comments

Comments

@dumblob
Copy link

dumblob commented Mar 27, 2015

It seems that the precise specification of CommonMark already settled down, so I'm proposing sticking with it to be compatible with most of Markdown flavours and also be predictable.

CommonMark is backwards compatible with the original Gruber's Markdown, so it should be just internal change.

@nikolas
Copy link

nikolas commented May 29, 2015

I agree - it would be great if marked supported CommonMark! Currently I'm using Remarkable because it has a commonmark option.

@puzrin
Copy link

puzrin commented May 30, 2015

marked's strong point is it's small size.

For commonmark parser you'd better search in "official" list of implementations: https://github.com/jgm/CommonMark/wiki/List-of-CommonMark-Implementations. If you need commonmark support, i see no problem to select appropriate project.

@noraj
Copy link

noraj commented Feb 21, 2017

It seems a good idea to use commonmark.js, markdown-it or remarkable.

@howardroark
Copy link

I really enjoy how flexible this parser is. Allows for a good amount of human error. Which is what you want from a syntax designed for writers.

@joshbruce
Copy link
Member

See #956

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants