We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
+
We ran into a very specific scenario using a + in superscript or subscript that appears to fail parsing correctly.
Superscript^+^ or Subscript~+~
The above renders as...
If a space is added before the ^+^, then it parses correctly:
^+^
Superscript ^+^ or Subscript ~+~
Interestingly, using ^+^ also fails:
^+^
Superscript^+^ or Subscript~+~
The parsing issue only happens when using a single + char. If revised to a - char, then the subscript and subscript parse and render correctly.
-
Can anyone else reproduce?
Hope this helps.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We ran into a very specific scenario using a
+
in superscript or subscript that appears to fail parsing correctly.Sample 1
The above renders as...
Sample 2
If a space is added before the
^+^
, then it parses correctly:The above renders as...
Sample 3
Interestingly, using
^+^
also fails:The above renders as...
The parsing issue only happens when using a single
+
char. If revised to a-
char, then the subscript and subscript parse and render correctly.Can anyone else reproduce?
Hope this helps.
The text was updated successfully, but these errors were encountered: