mirror of
https://github.com/xoofx/markdig.git
synced 2026-02-04 05:44:50 +00:00
What do I need to do for Math equations? #234
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bjthomson on GitHub (Oct 25, 2018).
Firstly, nice parser. Thank you. I'm struggling to get the Mathematics extension working, however.
I dont know Latex (I'm a markdown novice too), but I tried the test example,
and it didn't show the integral symbol
I also tried the StackEdit samples:
StackEdit shows this:


I saw that Markdown Monster used MarkDig, but that doesn't render the equation either.
StackEdit mentions KaTeX, but I cant see a reference to that in the source. Looking at the page source in StackEdit, there is a bunch of HTML markup referring to KaTeX, but in my small test page, all I see is a div of class math?
I guess I'm missing something.
TIA
@xoofx commented on GitHub (Oct 29, 2018):
So as you checked, markdig only generate a proper class/tag to detect math blocks. but it won't provide the rendering infrastructure. You need to plug an existing javascript Math framework for this (like KaTeX) and plug it into your final rendering page. Markdig doesn't generate a HTML page, it just generates a fragment of it.
Using with Katex, it should be something like this to process it (haven't tried this, but it should not be far from a version working):
@bjthomson commented on GitHub (Oct 29, 2018):
Ah I see, Thanks, i'll investigate.
@jonkas2211 commented on GitHub (Dec 20, 2018):
Hallo @xoofx,
shouldn't that be documented in the spec file?
For example something like:
Note that you have to use a rendering engine like
@xoofx commented on GitHub (Dec 21, 2018):
I would prefer this in a proper documentation page instead, but I haven't any spare time to bring documentation setup for markdig. I will leave this issue open until then.
@xoofx commented on GitHub (Mar 12, 2019):
Likely fixed by #311