-
Notifications
You must be signed in to change notification settings - Fork 1
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
Consistent Rule name and token meta information #3
Comments
Yep I can the see the thinking here; seems reasonable 👍 If we do this, a the thing to bear in mind is that these changes also need to be made in mdit-py-plugins, and then in myst-parser, to keep parity (see e.g. executablebooks/mdit-py-plugins#26)
hmm, not sure about that: I think having the package start to actually interpret the LaTeX (or reassemble it) is difficult to do in a robust way, without implementing/depending on a proper parser. I would rather leave that to katex/mathjax |
Note you would also have to bear in mind how myst-parser would need to be changed, to accommodate the different token structures:
(obviously just changing renders, like in #1, will not affect myst-parser in any way, since it works directly from the tokens) |
For the default rule name, it would be great if we could have some consistency with dollarmath package? Maybe
math_block_amsmath
? Or simply make it amath_block
and add some metadata to the token to indicate that it is AMS?It would be great to have consistency between:
and
and
and
In terms of downstream packages not having to know the intricacies of how the math was parsed, this would mean the tokens in all cases would be something close to:
Maybe optionally strip out
equation
environments and parse simple label information. In the future as well, as packages may want to label things on their own.The text was updated successfully, but these errors were encountered: