Repository navigation
|
I know I'm beating a dead horse, but this is not about "right" or "wrong"; it's just peculiar. Please check the attached screenshot. Notice how the equal sign on the left (Ghostty) using different antialising techniques in different lines. Line 93 looks reasonable, darker on top and bottom and only two lines. Line 88 and 92 looks like different characters. Lines 90 and 87 uses three pixels only for the bottom part. As I said, this is not about what's "wrong", but it actually calls my attention (or obsession) how this symbol that is usually surrounded by space can look so off compared to others of its surrounding it. 
For reference (even if comparisons are unpolite), Gnome Terminal (aka Ptyxis) renders the symbol the same way everywhere. 
For context, I'm using Iosevka Term SS15 (so no ligatures) on a 1920x1080 screen (Lenovo Thinkpad) Ghostty 1.2.3-1.fc43 config: |
Replies: 1 comment 6 replies
Ghostty 1.3 was just released and includes changes to font hinting, precisely to be more aligned with ptyxis and other gnome/GTK apps. How does the comparison look if you update? |
|
I was waiting for it to be published on the COPR; fortunately it was just published so I've updated. But unfortunately, the rendering still looks off. Check how on three different lines, I got three different renderings. 
This is the equivalent to my previous screenshots. 
|
|
Do you use fractional DPI scaling in your display configuration? If so, this is #1938 (which is closed, but should arguably be reopened since the problem reappeared due to upstream changes). Ghostty only rasterizes a glyph once and reuses that bitmap in every cell containing that glyph, so it will always be pixel identical on the virtual screen that Ghostty renders to. But fractional upscaling from virtual to physical pixels may break this. The solution is to figure out how to once again make Ghostty render directly to physical pixels regardless of DPI scaling. |
|
That was the issue! Fractional scaling was set to 125% as default by Fedora Silverblue, and I just went with it due to my poor sight. I have reverted to 100% and everything looks fine. Even setting "Large text" in accesibility options. Even so, it's a bummer that fractional scaling breaks rendering. For reference, these screenshots are at scale 100%, and with large text enabled. 
|
Definitely! This one needs fixing, it shouldn't be like this (and it wasn't, but then GTK made some changes/deprecations and no one has taken the time to figure out how to catch up). |
Should I report a proper issue or is this conversation enough? |
|
The issue is #1938, which I've argued should be reopened, but that would be a maintainer's call. |
Do you use fractional DPI scaling in your display configuration? If so, this is #1938 (which is closed, but should arguably be reopened since the problem reappeared due to upstream changes).
Ghostty only rasterizes a glyph once and reuses that bitmap in every cell containing that glyph, so it will always be pixel identical on the virtual screen that Ghostty renders to. But fractional upscaling from virtual to physical pixels may break this. The solution is to figure out how to once again make Ghostty render directly to physical pixels regardless of DPI scaling.