Skip to content
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

Single + in superscript or subscript #791

Open
geoffreymcgill opened this issue Apr 16, 2024 · 0 comments
Open

Single + in superscript or subscript #791

geoffreymcgill opened this issue Apr 16, 2024 · 0 comments

Comments

@geoffreymcgill
Copy link

We ran into a very specific scenario using a + in superscript or subscript that appears to fail parsing correctly.

Sample 1

Superscript^+^ or Subscript~+~

The above renders as...

Screen Shot 2024-04-16 at 11 09 26 AM

Sample 2

If a space is added before the ^+^, then it parses correctly:

Superscript ^+^ or Subscript ~+~

The above renders as...

Screen Shot 2024-04-16 at 11 09 35 AM

Sample 3

Interestingly, using ^+^ also fails:

Superscript^+^ or Subscript~+~

The above renders as...

Screen Shot 2024-04-16 at 11 09 40 AM

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant