-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Comments
I agree - it would be great if marked supported CommonMark! Currently I'm using Remarkable because it has a commonmark option. |
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. |
It seems a good idea to use commonmark.js, markdown-it or remarkable. |
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. |
See #956 |
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.
The text was updated successfully, but these errors were encountered: