notebook icon indicating copy to clipboard operation
notebook copied to clipboard

Markdown rendering of double supscripts in .ipynb file differs from .md file on github

Open isalykke opened this issue 3 years ago • 4 comments
trafficstars

Describe the bug

  1. When I render a double subscript in an .md file (like here), it looks correct, like this: TabN2Ostald

  2. When I do the same in a markdown block in an .ipynb file, it does not render correctly on github: image See the file here: https://github.com/segesdk/SAF_dokumentation/blob/main/N2O_Stald_Lager.ipynb

  3. Sidenote: the rendering of the .ipynb file in VS code is also correct: image

To Reproduce Type in this code - the last < /sub > is not rendered correctly (see 2. above) image

Expected behavior I expect 2 to look like 1

Screenshots See above

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser Edge
  • Version 103.0.1264.77

Additional context none

isalykke avatar Aug 03 '22 14:08 isalykke

Hi @isalykke thanks for submitting this issue! I downloaded the notebook you linked and opened it but I was not able to see the </sub> tag as text like this issue. I can see this issue at the link however, so my question is, do you see this issue locally when you run jupyter notebook from a standalone terminal outside VS code? If so, would you provide the version of Notebook that you are using?

RRosio avatar Aug 17 '22 15:08 RRosio

Hi @RRosio - thanks for helping out! You are right, the issue only occurs here on github - specifically in markdown blocks in .ipynb files I have never run the notebook in a terminal, as I only use it for sharing with colleagues online as documentation...

isalykke avatar Aug 19 '22 11:08 isalykke

It seems like maybe this issue is tied to the mechanism that Github uses to render Jupyter notebooks. Maybe it's an issue best reported to them? I also tried pasting the notebook link in nbviewer website (nbviewer repo) and I can see that the issue is present there as well. I'm not entirely sure which would be the best place for this issue (maybe both?) but they seem like places where someone might be able to provide more insight.

RRosio avatar Aug 24 '22 21:08 RRosio

Alright thanks @RRosio, I'll try reporting it in those two places :)

isalykke avatar Aug 25 '22 09:08 isalykke