comrak
comrak copied to clipboard
kivikakk
CommonMark + GFM compatible Markdown parser and renderer
What the title says! `ComrakOptions::default()` sets the `header_ids` option of `extensions` to `""`; this means that, by default, headers are always given anchor tags (with an ID matching the text...
The GFM spec [states](https://github.github.com/gfm/#strikethrough-extension-) that > Strikethrough text is any text wrapped in two tildes (~). But as I show in this failing text, a single tilde is enough to...
Need to actually populate and propagate the source positions everywhere upstream does, now.
From the title you can probably tell that this is related to #58. The [documentation for `ext_footnotes`](https://docs.rs/comrak/newest/comrak/struct.ComrakOptions.html#structfield.ext_footnotes) has this example: ```rust let options = ComrakOptions { ext_footnotes: true, ..ComrakOptions::default() };...
It's kind of impossible to get nested lists to render in a regular and predictable way due to the tight/loose list distinction. Paragraphs generally have padding. One of the list...
comrak currently parses `**A*B*C*` as `**ABC*` the [common-mark dingus](https://spec.commonmark.org/dingus/?text=%60%0A%60%0A) gives the result `*ABC"`. (My implementation agrees with the dingus)
Hi! Thanks for working on Comrak and sharing it with us. I'm new to Rust and I'm having trouble figuring out how to manipulate the Comrak AST. Here's a snippet...
I'm writing a program that needs to translate the comrak AST into a different AST, that a WYSIWYG editor (prosemirror) understands, and back again. I was about to write some...
https://docs.rs/crate/latex2mathml/ is very easy to use. And cmark-syntax has integrated it https://github.com/grego/cmark-syntax/blob/057ed25507735aa013b55a0650845da5ff2c368e/src/lib.rs#L74, I hope comrak can support it.
I hope to do a bidirectional link jump based on `Ast`, but it seems that there is not enough information. https://github.com/kivikakk/comrak/blob/7b1f19f2be0de1abf26dbf93ddcba9b653e11fae/src/nodes.rs#L365-L366 How about store position with start and end offset`(usize,...
