-
Notifications
You must be signed in to change notification settings - Fork 196
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
Support CommonMark syntax #253
Comments
Out of curiosity: what the the syntax features that are present in CommonMark that you miss with the current implementation? I am quite sure there are Python-Markdown extensions that implement the syntax you need. That said, I can add the CommonMark markup, but I am not going to reassign the standard file extensions ( |
It's not so much mssing syntax feature, rather than having a standard syntax across several systems. There are lots of different markdown flavor, based on website and parsers, and CommonMark actually have a spec on how to write syntax. I understand the problem with the file extension, maybe you could add a user preference to choose between python markdown / common mark ? |
I agree with xgouchet, that would be nice, a lot of other applications also support both. |
Some additional comments (just putting these links here for reference):
|
In some cases CommonsMark and ReText gives different rendering, so I need to make changes like colouring-cities/colouring-core@b07de22 just because ReText is displaying it brokenly. Specifically:
is shown as list on GitHub that is using CommonsMark and not in ReText that is using MarkDown. |
As I said earlier,
And here is an extension for your case: |
@mitya57 How one may use them in ReText? I see no obvious way to achieve this. |
There are multiple ways to enable extensions, as described in the wiki: https://github.com/retext-project/retext/wiki/Markdown-extensions.
And of course you need to install the extension, in this case |
Currently ReText gives the option to use Markdown, Textile and reStructured Text. It would be great to be compliant with CommonMark (which is a kind of standardized version of Markdown)
The text was updated successfully, but these errors were encountered: