Valve has pushed out what they're calling Proton 9.0 (Release Candidate 2), with a whole bunch of improvements for gaming on Linux Desktop and Steam Deck.
Yes, I was. I checked in F-Droid and the reason it didn’t automatically update was something to do with an incompatible signature. But I updated it manually and it’s looking fine now.
Seems like clients vary wildly in how they interpret this markup. This is how it shows on Sync:
Yeah it looks like the subscript and superscript fonts are not being supported on third party android/apple clients properly, but only the Lemmy web client.
My goal was actually just to make the font smaller, and not so much subscript/superscript.
I may have to revert the change, and just make the font for the link regular sized.
Either that, or just wait for the android/apple clients to catch up to the Lemmy web client.
Its a manual copy/paste of the following text…
[~CC~ ~BY-NC-SA~ ~4.0~](https://creativecommons.org/licenses/by-nc-sa/4.0/)I use the Lemmy web client, and they don’t have a signature section on the account to set once and forget.
CC BY-NC-SA 4.0
Why do you put strikethrough the text though?
The single ~ reduces the font size.
For example
CC BY-NC-SA 4.0
Not on my client.
Strange.
On the Lemmy web client its two tildes ~ for strikeout.
One tilde is the subset font size.
Before superset After
^superset^Before subset After
~subset~Before
strikeoutAfter~~strikeout~~What client are you using?
CC BY-NC-SA 4.0
Voyager. And this is how it looks, by the way.
What formatting text do they use for subscript/superscript?
The Lemmy help page for formatting has the formatting text I’m using.
Seems like others are having the same problem. Looks like the non-web clients need to add support for subscript and superscript to themselves.
CC BY-NC-SA 4.0
Are you running outdated version of voyager? Because it looks fine to me
Yes, I was. I checked in F-Droid and the reason it didn’t automatically update was something to do with an incompatible signature. But I updated it manually and it’s looking fine now.
Seems like clients vary wildly in how they interpret this markup. This is how it shows on Sync:
Yeah it looks like the subscript and superscript fonts are not being supported on third party android/apple clients properly, but only the Lemmy web client.
My goal was actually just to make the font smaller, and not so much subscript/superscript.
I may have to revert the change, and just make the font for the link regular sized.
Either that, or just wait for the android/apple clients to catch up to the Lemmy web client.
CC BY-NC-SA 4.0