Single characters in super- and subscript

[activivan]

While subscript can be achieved using ~im below~, superscript with ^up^ (as recommended in https://www.markdownguide.org/extended-syntax/#superscript) is not working.

[geoffreymcgill]

For me, both appear to be working correctly. Here is a sample I'm testing with...

Normal ^superscript^ and ~subscript~

[activivan]

Ok, I figured it's the plus character that doesn't work, neither in subscript or superscript:

NAD^+^ or Disney~+~

[activivan]

It's not only +, also +,.#&%$? don't work. - does work though

[geoffreymcgill]

Thanks for the sample. There does appear to be an issue with the Markdown parser during that exact ^+^ scenario.

I found that if you add a space in front of the ^+^, then it does render correctly. Maybe that is at least a temp work-around for the issue.

// FAIL
NAD^+^ or Disney~+~

// PASS (add a space)
NAD ^+^ or Disney ~+~

Interestingly, using ^+^ also fails:

NAD^+^ or Disney~+~

Another work-around could be using a dagger with ^†^ instead of a +:

NAD^†^

I don't think the ^+^ is going to be a quick fix, but we will certainly look into getting this fixed for a future release.