Windows Terminal seems to have its own font renderer, and sometimes it's just plain worse than what's built in.
Compare these two prompts from CONHOST (darker, left) and Windows Terminal (lighter, right). Same text, same font, but the Windows Terminal rendering frequently gets the shape and size of the diagonal blocks wrong, which causes artifacts like color bleed and/or misaligned edges. Worse, which artifacts you see changes with the font size.
The alignment issues are supposedly solved in 1.18 (I'm using 1.19): "In the screenshots above, you can see how our AtlasEngine rewrite in 1.18 Preview fixed powerline rendering. We now have no weird gaps, no cut off glyphs, and no shrunken glyphs."
Are you KIDDING ME RIGHT NOW? Zoom up of their supposed golden screenshot, which shows both a glyph that is both too tall and has an edge rendering problem:
Honest question: Am I expecting too much? Are people by and large just ignoring these things because they are either blind to them and/or don't care about them?
@nicholashead I don't do high dpi on this monitor (32" 4K). The screenshots are just zoomed to a ridiculous level to highlight the issues and make them easier to see, but I can see them even at relatively small rendering, too.
@nicholashead Sorry about that, accidentally posted from my phone when I wanted to send a screenshot along with.
I was checking the config file, but I see this in the config UI. Checking vs. unchecking it, I don't see any difference (not just the diagonal blocks, I mean I don't see any text rendering difference at all). I even tried restarting Terminal just in case.
@bradwilson@nicholashead That option is actually going away in 1.21, but only because we're removing the old renderer it replaced^1. The new renderer is now so very much better than the old one, that it doesn't make sense to keep the old one around anymore.
@bradwilson oops, realized these are what you meant. I thought originally the rendering/antialiasing on the 'sh' is not the same in both, but of course the diagonal artifacts are a bigger problem
@KirillOsenkov The anti aliasing doesn't affect the problem (Windows uses ClearType but I enabled the grayscale rendering in Windows Terminal). I tried all three anti aliasing modes in WT and the problem is present in all of them. It's definitely the core font rendering that's the problem.
Add comment