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
Figure out MathJax 2 support #1313
Comments
http://www.mathjax.org/docs/2.0/tex.html#tex-eq-numbers We need to decide how to configure this. It should be simple to enable, but we need someone to test this with Markdown and sympy rendered math. Here is our MathJax config code: |
So I tracked down the problem.
Someone needs to track this down further to see what is going on. |
I take that back you have to do a full clearing of the browser cache when you update mathjax. But v2.0 is still borked. |
Question here: this is marked as 'blocker' but has no milestone attached to it, which to me is kind of contradictory. If it's really considered a blocker, then it is a blocker for the next release (hence it should have milestone 0.13). Otherwise, we should lower its priority... |
Targeted to 0.13. I am not even sure how bad the problem is today. It be magically fix itself if the download link to v2.0 is updated to the 2.0.2 version. |
I've been using the default MathJax from CDN (currently 2.0.3), and it appears to be working just fine. I also did |
It looks like they have updated the version to something that is On Fri, Apr 27, 2012 at 1:14 PM, Min RK
Brian E. Granger |
okay, closing. |
I'm still getting [Math Processing Error] with IPython 0.13.2 for simple expressions like |
as discussed on the user list, we should incorporate/expose MathJax equation numbering functionality when it available in the stable version of mathjax. This looks like the relevant issue to keep track of the status of that functionality: mathjax/MathJax#71
It also appears that MathJax 2 is completely broken in the notebook. I am getting [Math Processing Error] instead of nice math. You can get MathJax 2 by doing:
But you will have to reload your browser a few times to make sure you are not getting the v1.1 version.
The text was updated successfully, but these errors were encountered: