Bug 402189 - Introduce Y-axis text antialiasing in Krita UI
Summary: Introduce Y-axis text antialiasing in Krita UI
Status: REPORTED
Alias: None
Product: krita
Classification: Applications
Component: Usability (show other bugs)
Version: 4.1.5
Platform: Microsoft Windows Microsoft Windows
: NOR wishlist
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-16 12:43 UTC by Be5invis
Modified: 2019-04-09 19:19 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Be5invis 2018-12-16 12:43:23 UTC
Starting from RS2, GDI on Windows gained Y-axis text antialiasing and is set to "on" for almost all Windows app (like Notepad). However Krita does not follow this pattern.

Considering modern typography would introduced more and more please enable that for better text display.

https://i.loli.net/2018/12/16/5c16478b1f07c.png
(Related bugs for other products including Visual Studio are already filed.)
Comment 1 Halla Rempt 2018-12-16 12:47:15 UTC
Um, we render the text using Qt, so this probably should be reported for the Qt toolkit. Unless Qt exposes that as a property, there isn't anything we can do.
Comment 2 Be5invis 2018-12-16 12:58:28 UTC
Well some other applications like Snipaste is built using Qt too, but it has proper Y-axis AA and GASP table respect.
Comment 3 Be5invis 2018-12-16 13:02:52 UTC
Also Qt supports DWRITE, so you can try that?
Comment 4 Halla Rempt 2018-12-16 14:24:09 UTC
Where did you find that in the Qt documentation?
Comment 5 wolthera 2019-04-08 15:49:02 UTC
I am... setting this as wishlist.
Comment 6 Alvin Wong 2019-04-09 19:19:57 UTC
I believe Qt _is_ using DirectWrite on Windows by default and we haven't done anything to change it. (The only other option is FreeType and trust me, it looks awful on Windows.)

I can't tell if Qt has enabled vertical anti-aliasing for the menus. From your screenshot it looks like maybe it doesn't but it's a bit hard to tell for sure. The best way would be to check the source code of Qt.

It's a very minor issue for Krita though, so it'd be low priority. And it'll still need to be reported on Qt's bug tracker.