-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Issue with absolute values #16
Comments
This happens at the parser level. I think the node level that we are currently working at is too late in the process. Even if we could reconstruct it from the node, the warning will already be omitted. So I think we need to modify the extension to work at the parser level. The node level may also be necessary to prevent math from being used inside of code blocks. |
I guess we can make a parser subclass and register it. https://www.sphinx-doc.org/en/master/extdev/parserapi.html |
I don't know how easy this will be to fix. For now, if you get a warning like this from using dollar math, you should just use the :math: role as a workaround. |
Have you tried it like this |
That doesn't work. The problem is that Sphinx parses out the |
I think that it is possible to make a workaround like
|
The math
$|y| \geq |x^e|$
produces an errorChanging the transformer priority to lower than that of substitutions doesn't seem to fix it. http://docutils.sourceforge.net/docs/ref/transforms.html
The text was updated successfully, but these errors were encountered: