# Formatting Bug with superscripted text being ignored?

in a recent answer, I used the following (simplified) code snippet:

[cleartext argumentation] <sup>4, 6, 8</sup>

> [Blockquote from source] <sup>6</sup>


However, for some reason it parses into

In later generations, the outspoken rule becomes that only at character generation one can obtain rites with background or freebie points, in 1st edition that is only implicit. 4, 6, 8

Subsequently [to character generation], however, rites can be learned only through roleplaying; they may not be purchased with experience points. 6

and the command console makes it evident, that the second set of superscripted text in the quoted area is seemingly ignored:

In a similar fashion, another section of superscripted text after the blockquote is likewise just normalized.

However, for some odd reason, the very same snippet of code does work here on the meta... did I type some strange extra character in there that got lost in copying or something?!

## investigation

Adding another <sup></sup> to turn it into <sup>6</sup><sup></sup> does make the first 6 into superscripted text, but this does not work for the second instance of non-parsed superscript text - there <sup>4, 6, 8</sup><sup></sup><sup></sup> was needed to display as superscripted text.

Apparently, just having the latter code bit also somehow fixes the first formatting issue.

Also, closing each portion of superscripted text does seems to fix the issue. <sup>6</sup></sup>

• It seems like you just forgot to close a sup tag Sep 10 '21 at 10:47
• @Medix2 yes... one I did not look at. Sep 10 '21 at 10:47
• @doppel I'm really not sure code formatting is a great idea here but I'm not sure of a good alternative. It's a lot of actual text in there Sep 10 '21 at 10:52
• @Medix2 it can be helped... let me try something Sep 10 '21 at 10:52
• We're trying to show the plaintext version of markdown, that's entirely what a code block is for. There was already sufficient word wrap that both sups are in view. Sep 10 '21 at 10:54
• though the text can be cut in the top example, cleaning up the apparent problem area. not entirely sure which solution look cleaner Sep 10 '21 at 10:56
• @doppel Then I guess mobile uses different formatting since it didn't wrap at all but had a scrollbar due to the lengthier lines Sep 10 '21 at 10:57
• @Medix2 it had 3 lines and 2 lines, but wasn't really "mobile friendly" as mobile only has much less of a column width. Sep 10 '21 at 10:59
• @Medix2 Oh, no, I mean there were already word breaks in those lines. Desktop doesn't word wrap either. Sep 10 '21 at 11:10
• Is the text in the question that is supposed to be in error written correctly? All of your sup tags are correct... Sep 10 '21 at 12:19
• @ThomasMarkov read the answer: one was off. Sep 10 '21 at 12:23
• Ah, so you typed it wrong in your original post, then typed it right in the question here? Sep 10 '21 at 12:37
• @ThomasMarko yes and no: if you look at the linked old version, it was a line before the quoted part, that resulted in the error. Sep 10 '21 at 13:08

I'm a doofus!

There is a roll and time spent with the teacher, that's it. <sup>2, 4, 6, 8<sup>

Of course with no closed supertext, all kinds of errors are to be expected... The fix was therefore adding the needed /:
There is a roll and time spent with the teacher, that's it. <sup>2, 4, 6, 8</sup>