-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Stem notation support? #163
Comments
The correct attribute would be But the stem support is an integration feature, which means it relies on MathJax to actually handle the equations. All the stem attribute does is process stem blocks and macros and wrap them in markup for MathJax. That means you need to add MathJax to your page template. You can use the following as a reference: |
To tell that the stem feature is working, you should be able to observe that |
Ah, OK - I see content converted from |
This could be something nice to add to the quickstart. |
I figured out how to add it in a relatively simple way. You may have suggestions for this that are better - I just taught myself some JS last week, so nowhere close to being an expert in it. I added a new _include file "mathjax_support.html" that I cobbled together from Googling and from asciidoctor/asciidoctor.js#60. Then I added that to my "head.html" _include, and updated Here's the contents of "mathjax_support.html" in case you have feedback:
|
Nice work! I'll transfer this information to the README for others who are looking to set it up. Thank you for sharing! |
I've transferred this information to the README. |
We're using Jekyll to render our AsciiDoc files, with the jekyll-asciidoc plugin. One of our contributors needs to add content that includes stem notations, and noted that it wasn't rendered properly in his tests.
I added
:page-stem:
to my front-matter, but it does nothing. I also tried simply:stem:
with the same result. Is Asciidoctor's stem notation support also supported with jekyll-asciidoc? Should we use something else instead as a plugin or extension to Jekyll? Or, is there something I should add to my templates to allow the support?The text was updated successfully, but these errors were encountered: