In Ripcord, for some reason, spaces directly after commas and periods are not being shown. A comma and a space is showing as just a comma, a comma and two spaces is showing as a comma with one space. Same behavior for periods. The same posts, viewed in normal Discord, appear with the correct number of spaces. I have only noticed this behavior within the last day or so, around when I upgraded to 0.4.27. I also upgraded to Big Sur around the same time.

That's really weird. I didn't change any code related to that. I think this must be a Big Sur issue? Hmm.

I can confirm this is a Big Sur issue. I've been dealing with it for months. I now wish I'd logged it earlier, but I upgraded in one of the early betas so it seemed too early to log and since then I've just gotten used to it and forgot.

It happens across the entire app; typing a message, displaying a message (both Slack and Discord), and in the preferences window (e.g. slack preferences has a comma in two of the "avatars in chat" options).

Looks like this is an unfixed, unacknowledged Qt bug: https://bugreports.qt.io/projects/QTBUG/issues/QTBUG-88495

This isn't surprising, I guess. Mac OS releases, in the last few years, are on an aggressive schedule and come with lots of broken, buggy, or changed behavior. It will probably take a while to get fixed. Immediately updating to a new OS is something I would suggest avoiding. There's not much I can do about this. I'd suggest upgrading back to Catalina for now.

If you can't do that, well, I don't know what to say. This isn't something I can fix, and it looks like it affects every Qt program.

That's more or less what I expected. I upgraded because I'm willing and able to deal with the problems and help apps with bug reports.

Alright. I'll keep a look out for a patch or fix. I might have to backport it to Qt 5.9 or 5.12, because I don't want to drop support for 10.12. We'll see.

Hello, I had this bug too, I would not consider it as minor it is very annoying, but it is a font problem: Change your display font and everything is alright 👍. Yep, I been very surprised too.

Looks like this is acknowledged now. And it looks like they will publish a fix for Qt 5.15, but it will be some time before Ripcord is able to use Qt 5.15, because Qt 5.15 drops support for macOS 10.12. So, I may have to release two versions of Ripcord for Mac, or something. Or, I might try to backport the fix from Qt 5.15 to Qt 5.9 or 5.12.

In the meantime, changing the font in Ripcord from default to something else will fix it, because the San Francisco (system default) font on Big Sur is missing some kind of metadata, causing the text shaper in Qt to get confused. Maybe I can add a hotfix to Ripcord on Mac to use Helvetica instead of San Francisco by default on Big Sur.

I use Arial on my side and it look good 👍.

A hotfix to switch the default font would be welcome.

Still present in Monterey. Was able to fix it by changing the font to Arial.