View Single Post
Old 03-16-2024, 02:37 PM   #59
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 7,733
Karma: 5444398
Join Date: Nov 2009
Device: many
FWIW, Qt 6 dev and 6.8 will default to always using the DirectWrite backend for fonts on Windows. But DirectWrite backend support is incomplete as of Qt 6.6.x as it is missing the following changes that dev provides:

https://github.com/qt/qtbase/commit/...9280ae524482b7

So the only thing that will workaround this issue to to force fallback to the gdi font backend on Windows.

Alternatively we could try to backport the directwrite backend fixes from dev back to Qt 6.6.2 and hope that does the trick as it completes support for more font types. I have no idea if that is doable or not.
KevinH is offline   Reply With Quote