-
Notifications
You must be signed in to change notification settings - Fork 9
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
footnotes stop working, when using glossarify #38
Comments
I suspect what causes the references to be displayed verbatim is the fact that the markdown AST stringifier remark-stringify used internally translates the colon of the footnote into an HTML entity sequence, so instead of
it renders
I played around with the respective remark-stringify options This is not to say it's impossible to solve but just to provide a bit more context to the issue and why footnotes do not work out of the box at the moment. |
…. Support for Pandoc footnote syntax will be considered *experimental* until it becomes part of the official CommonMark Specification at https://spec.commonmark.org. See also https://pandoc.org/MANUAL.html#footnotes.
Okay turned out to be easier than expected. After a look at the source files I found that remark-parse and remark-stringify both already implement support for footnotes but the feature must be enabled explicitely with the parser and Since they are not yet officially part of the CommonMark Spec glossarify-md v2.1.0 will also require explicit feature toggling by a separate boolean config option |
* feat: New option `--experimentalFootnotes` for Markdown footnotes (#38). Support for Pandoc footnote syntax will be considered *experimental* until it becomes part of the official CommonMark Specification at https://spec.commonmark.org. See also https://pandoc.org/MANUAL.html#footnotes.
Thanks for the ultra fast fix. I'll bump up the Version on monday. |
Works! Thanks! |
Hi,
I am using vuepress 1.1.0 with markdown-it-footnote 3.0.2.
When activating glossarify (2.0.0) - footnotes stop working, i.e.
[^footnote1]
is displayed verbatim instead of being a link.The text was updated successfully, but these errors were encountered: