earmark_parser
earmark_parser copied to clipboard
RobertDober
The Markdown to AST part of Earmark.
Should behave like e.g. https://babelmark.github.io/?text=+%3Cstrong%3Evalue%3C%2Fstrong%3E now only behaves like this if no spaces preceed the HTML tag (which is not documented and might be a regression, ...)
As discovered in https://github.com/elixir-lang/ex_doc/pull/1400 fenced codeblocks should render IAL annotation (and also annotations, to be checked) verbatim. However the IAL annotation disappears.
This would superseed [Earmark#356](https://github.com/pragdave/earmark/issues/356) and is inspired by [Earmark#353](https://github.com/pragdave/earmark/issues/353). Basic idea let the scanner be a little be more intelligent and scan the following line ```markdown hello αλφα ``` as...
```markdown hello[^1] world[^1] [^1]: A common greeting ``` produces the following ```elixir [ {"p", [], [ "hello", {"a", [ {"href", "#fn:1"}, {"id", "fnref:1"}, {"class", "footnote"}, {"title", "see footnote"} ], ["1"],...
This will implement the deprecation in #86
Right now IAL annotations for list items are silently ignored here are some ideas how to make that better ## Best implement them as for other elements ```markdown - `li`...
fix or refute https://github.com/pragdave/earmark/issues/361 ```elixir iex(10)> Earmark.as_ast " anything that follows the comment is lost " {:ok, [comment: [" Replace with better image "]], []} iex(11)> Earmark.as_ast " this is...
https://github.com/pragdave/earmark/issues/171 depends on this
I was doing some markdown of inline C code and noticed that the parser interprets ** inside `` ` `` as the end of the emphasis. ```elixir iex(1)> EarmarkParser.as_ast "**`**`**"...
