Skip to content
This repository has been archived by the owner on Aug 29, 2018. It is now read-only.

Use CommonMark instead of some loosely defined Markdown flavour #6

Open
dumblob opened this issue Jun 21, 2015 · 1 comment · May be fixed by #19
Open

Use CommonMark instead of some loosely defined Markdown flavour #6

dumblob opened this issue Jun 21, 2015 · 1 comment · May be fixed by #19

Comments

@dumblob
Copy link

dumblob commented Jun 21, 2015

Would it be possible to switch to a well-defined "flavour" of the original Markdown called CommonMark? There are very good JS implementations and I'd recommend markdown-it.

CommonMark continues in the spirit of well-defined typing (which is one of the greatest advantages of Elm) and brings it to the domain of syntax.

@jvoigtlaender
Copy link
Contributor

Indeed, it seems that marked.js does not follow Markdown "rules". For example, it will apply markup to Markdown blocks inside literal HTML blocks. Like in this:

import Markdown

main =
  Markdown.toHtml markdown

markdown = """
<div>
<p>Codes are "p_2014__"* for balance sheet and  "p_2014_2000_"**  for income statement.
....Notes: *as of year end, **span of 14 years.</p></div>
"""

Also consider: markedjs/marked#236 (comment)

And it seems a bit unclear whether marked.js is still being maintained: markedjs/marked#724

@liamcurry liamcurry linked a pull request May 19, 2016 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants