The italic variant of the font used for body text in the “Less” theme—I think it’s Source Serif Pro—has a very strange behaviour for me, at the moment, on my laptop running Windows 10. Here is a screengrab at 170% size in Firefox. Look at the serifs and at lowercase “t” and “f”! (And, I guess, everywhere where two strokes somehow run into or across one another.)
If I crank the zoom up one notch more to 200% then the weirdness goes away. In Chrome, it’s weird up to 150% size but normal from 175% up. (My laptop has a “4k” screen, with Windows’ global scaling set to 200%.)
This seems like it must be a text-rendering bug, but I’ve never seen it happen before; I guess something in the Source Serif Pro font is triggering it.
I don’t have a Windows 10 machine, so I can’t replicate this at the moment (I have never seen this bug on Mac/Linux, though it’s possible it occurs in some setup I’ve missed testing). That said, yes, it’s almost certainly something in Source Serif Pro.
Details for font geeks or the curious:
Source Serif Pro is a free, open source font from Adobe. At the time I added this font to my font server, the italic version was not yet part of the official release, as it was still being worked on; I built the font from source (using the tools Adobe provides at the linked repository). Since then, as Adobe has pushed updates, I’ve pulled the new source and rebuilt the font files a couple of times.
There do seem to have been some commits to the codebase since my last update, so it’s possible that this rendering bug has been solved. I will update the font server and post a follow-up comment if the update fixes things.
Update: I’ve updated Source Serif Pro to the latest version, but (I am told) the bug remains. I regret to suggest that, if you experience this glitch, and it seriously bothers you, you may want to use a different theme until Adobe releases a fix.
Cool! I have to say, I’m even more grateful for the comments / bug reports, in that case—regularly taking the time to try out, and give useful feedback on, a site you don’t yourself use, is pretty rare. Thank you!!
(We of course appreciate feedback from anyone—whether they use GW or not. It’s just extra-impressive when coming from someone who has no, so to speak, vested interest in the site working well!)
The italic variant of the font used for body text in the “Less” theme—I think it’s Source Serif Pro—has a very strange behaviour for me, at the moment, on my laptop running Windows 10. Here is a screengrab at 170% size in Firefox. Look at the serifs and at lowercase “t” and “f”! (And, I guess, everywhere where two strokes somehow run into or across one another.)
If I crank the zoom up one notch more to 200% then the weirdness goes away. In Chrome, it’s weird up to 150% size but normal from 175% up. (My laptop has a “4k” screen, with Windows’ global scaling set to 200%.)
This seems like it must be a text-rendering bug, but I’ve never seen it happen before; I guess something in the Source Serif Pro font is triggering it.
Fascinating!
I don’t have a Windows 10 machine, so I can’t replicate this at the moment (I have never seen this bug on Mac/Linux, though it’s possible it occurs in some setup I’ve missed testing). That said, yes, it’s almost certainly something in Source Serif Pro.
Details for font geeks or the curious:
Source Serif Pro is a free, open source font from Adobe. At the time I added this font to my font server, the italic version was not yet part of the official release, as it was still being worked on; I built the font from source (using the tools Adobe provides at the linked repository). Since then, as Adobe has pushed updates, I’ve pulled the new source and rebuilt the font files a couple of times.
There do seem to have been some commits to the codebase since my last update, so it’s possible that this rendering bug has been solved. I will update the font server and post a follow-up comment if the update fixes things.
Update: I’ve updated Source Serif Pro to the latest version, but (I am told) the bug remains. I regret to suggest that, if you experience this glitch, and it seriously bothers you, you may want to use a different theme until Adobe releases a fix.
It doesn’t seriously bother me, because I use plain ol’ Less Wrong rather than GW :-). But when a new update drops I like to see how GW is getting on.
Cool! I have to say, I’m even more grateful for the comments / bug reports, in that case—regularly taking the time to try out, and give useful feedback on, a site you don’t yourself use, is pretty rare. Thank you!!
(We of course appreciate feedback from anyone—whether they use GW or not. It’s just extra-impressive when coming from someone who has no, so to speak, vested interest in the site working well!)