-
Notifications
You must be signed in to change notification settings - Fork 45
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
Incorrect handling of inline AsciiMath #84
Comments
It is also worth noting that the |
This issue could be avoided in the future with the introduction of tests targeting the rendering of the |
We need to refactor the code now. After a lot of edits, the code is messay. |
Fixed on 050841e. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This a follow up to #82 (comment). I recently implemented AsciiMath support. It has just been released.
However, I now realize the
asciimath
inline macro is incorrectly handled. Basically, it is handled in exact the same way thelatexmath
inline macro is. That means the macro is not processing AsciiMath code, it's actually processing LaTeX directly. In other words, currently theasciimath
inline macro is functionally equivalent to thelatexmath
inline macro. This is an error.I'm working on a patch, but I may need some help on it. This issue was cause by my inability to comprehend how inline stem blocks are currently handled. I think I've now got things figured out, but I'd like someone to review the patch in detail to make sure the implementation is not broken again.
The text was updated successfully, but these errors were encountered: