Closed
Conversation
Member
|
@daniel3735928559 thanks for the pull request. I won't be merging this b/c we'd like to avoid non standard commands in katex-core. I would like to eventually have a plugin system. This change highlights the need for plugins to have access to specific renderers. |
Member
|
Blocked on #762. |
4 tasks
Member
|
I know this is non-standard according to LaTeX standards, but I do feel like this could represent a core feature for KaTeX. MathJax has a similar feature, which can be found here: http://docs.mathjax.org/en/latest/tex.html#html I think it could be difficult to implement without access to the KaTeX core. |
Member
|
Superseded by #1074. |
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In a similar spirit to #506 (and for the same reason--this time as part of the plan to add mouse support to the editor), adds an
\xmlClassfunction that adds adds its first argument as a class to whatever its second argument is. For example,\xmlClass{foo}{x}+2will renderx+2like normal, but the span for thexwill have class.fooin addition to all its other usual classes.This change ended up being a little bit invasive, and I am also interested in any methods of doing the same thing more simply.