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
mathjax with slideous does not update formulae #966
Comments
I've never noticed a problem with mathjax in slidy or revealjs. Can you confirm that this problem only affects slideous? |
Indeed, it is OK with revealjs and other http://johnmacfarlane.net/pandoc/demo/example16[a-c].html, but not with |
Just a proposal. Since slideous replaces the Would you be able to just insert the following whenever slideous is chosen as an output? Perhaps inject within
This would ensure that the typeset is forced right after slideous is finished processing. |
Actually it should be easy enough to insert it directly in the <script> tag as before, but only when slideous output is selected. +++ Alberto Leal [Oct 12 13 05:17 ]: > Just a proposal. > > Since slideous replaces the `body.html` with its modified version of the original `body.html`, it would re-execute any javascript that may be within the scope of `body`. > > Would you be able to just insert the following whenever slideous is chosen as an output? Perhaps inject within `include-after`? > > ``` > <script type="text/javascript"> > MathJax.Hub.Queue(["Typeset",MathJax.Hub]); > </script>
|
http://johnmacfarlane.net/pandoc/demo/example16d.html produced with
does not render the maths formula correctly even after reloads (true for stable and for the git versions of pandoc, I tried these locally). The following change in SLIDES source for the last page fixes this issue:
I suppose this has to do with MathJax treating the pages as dynamic, and this is known to need a call to MathJax.Hub.Queue(). So a proper fix would insert these calls -- it seems that one such call on the last page suffices --to render all the mathjax maths in the document correctly.
The text was updated successfully, but these errors were encountered: