Here’s what it looks like from the default web interface.
Jerboa, the first-party Android app, shows the same. Not sure which app you’re using, but it displays markdown incorrectly. Out of interest, how does it handle subscript and
I’m using Arctic on iOS. I can’t remember offhand which md library it uses but will check if it’s been tweaked. I guess the real fix should be with the connections site in what they copy when you click ‘share’.
Unfortunately yeah there’s a lot of inconsistency with how different Lemmy clients display markdown. Even on the first-party platforms, ^multiple words of superscript^ or ~multiple words of subscript~ works some (Jerboa) but not others (lemmy-ui web interface).
The problem with this specifically though is with neither the Connections site nor with any of the Lemmy clients…it’s with the interplay between Connections and the basic markdown specification.
The markdown spec very specifically allows you to break one paragraph down into multiple lines,
so that you can write like I am right now, and keep individual lines small
while having it all display as a single paragraph.
If your client is showing this as separate lines, it is misapplying the markdown spec.
If you want a new line in markdown, you can add a blank line in between (like I did just before this sentence), to create a whole new paragraph.
Or you can end your line with two spaces (like I did the line before this)
or with a backslash, to escape the newline and tell the markdown parser “treat this newline as an actual newline”. Both the double space and the backslash methods insert a “line break”.
Here’s how this comment should display (apart from the superscript and subscript parts):
Here’s what it looks like from the default web interface.
Jerboa, the first-party Android app, shows the same. Not sure which app you’re using, but it displays markdown incorrectly. Out of interest, how does it handle subscript and
Spoilers
like this
?
I’m using Arctic on iOS. I can’t remember offhand which md library it uses but will check if it’s been tweaked. I guess the real fix should be with the connections site in what they copy when you click ‘share’.
Subscript and spoilers:
Ah interesting.
Unfortunately yeah there’s a lot of inconsistency with how different Lemmy clients display markdown. Even on the first-party platforms, ^multiple words of superscript^ or ~multiple words of subscript~ works some (Jerboa) but not others (lemmy-ui web interface).
The problem with this specifically though is with neither the Connections site nor with any of the Lemmy clients…it’s with the interplay between Connections and the basic markdown specification. The markdown spec very specifically allows you to break one paragraph down into multiple lines, so that you can write like I am right now, and keep individual lines small while having it all display as a single paragraph. If your client is showing this as separate lines, it is misapplying the markdown spec.
If you want a new line in markdown, you can add a blank line in between (like I did just before this sentence), to create a whole new paragraph.
Or you can end your line with two spaces (like I did the line before this)
or with a backslash, to escape the newline and tell the markdown parser “treat this newline as an actual newline”. Both the double space and the backslash methods insert a “line break”.
Here’s how this comment should display (apart from the superscript and subscript parts):
And how its script looks: