-
-
Notifications
You must be signed in to change notification settings - Fork 141
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
Mathematics #23
Comments
I have indeed seen this feature request a number of times across a number of channels! My primary goal for I don't have the time to implement such an extension myself, but I would welcome a PR. |
I think that when math is enabled, we should use something like |
No other parser uses this syntax. Is it really worth introducing something nonstandard? The pandoc author claims that, with some simple heuristics, false positives are simply not an issue: https://talk.commonmark.org/t/ignore-latex-like-math-mode-or-parse-it/1926/6. My experience has matched his so far. |
@jeanm You are probably correct. In that case Comrak will need to wrap |
Working on support for this in #366 |
#366 is merged, implementing regular dollar math as well as code math. Closing this issue. |
A commonly requested feature is the ability to input mathematics using LaTeX syntax without the markdown parser getting confused and messing it all up. All the parser needs to do is leave the maths alone, without interpreting underscores/askerisks/escapes, and rendering can then be delegated to something like MathJax or KaTeX. It would certainly be a nice feature for scientists, or people needing to describe algorithms etc.
A while ago I made a summary table of all the ways this syntax extension has been implemented in other markdown software, available here: https://github.com/cben/mathdown/wiki/Math-in-MarkDown#appendix-summary-table. I'd say probably the right answer is to do what pandoc does, and have
$ ... $
to delimit inline formulae, and$$ ... $$
for display-mode.The text was updated successfully, but these errors were encountered: