-
Notifications
You must be signed in to change notification settings - Fork 108
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
MDsveX + Katex #113
Comments
Yeah, this is indeed the same issue as #76. Appreciate the test case! I do have a fix for this but it is a little involved. I have something in the works that will address a number of formatting/ encoding issues as well as a host of other benefits but it is quite foundational and will take some time given my limited schedule. |
@pngwn appreciate it! I'll keep my eye out. |
This comment pretty much covers this issue as well. With one difference, this case should be easier to optimise since it uses custom syntax, there is at least the possibility of escaping the conflicting characters automatically. This doesn't depend on precisely how the plugin itself generates it's output but possible is better than nothing. :D I am going to close this issue and keep the older one open to keep track. I'll reference this from that issue. |
Awesome project! I've been impressed by the expressiveness of Svelte's reactive-ness, and you've got a beautiful repl here.
I'd like to report an issure regarding integration with katex, where
<
signs result in aExpected valid tag name
error. Katex is correctly transformed. This is related to or the same root cause as #76 .I have a tidy little test case here.
svelte config:
svx input:
error:
The text was updated successfully, but these errors were encountered: