View Single Post
Old 03-16-2024, 01:34 PM   #54
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 27,614
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by KevinH View Post
Well that sucks! The number of Windows font handling bugs listed in the qtbug database is quite large with many closed automatically after a time with no fixes.

There was one font bug related to dpi scaling that may be related but they found a workaround by disableing Windows directwrite as follows:

application.exe -platform windows:nodirectwrite


Does adding that prevent the crash?

If not, I am out of ideas.
That DOES, in fact, prevent the crash! I added it via the QT_QPA_PLATFORM environment variable. The Sigil debug output verifies that the platform argument is being implemented:
Code:
Debug: Current windows platform args:  QList("nomousefromtouch", "nodirectwrite")
Debug: New windows platform args:  "windows:nomousefromtouch:nodirectwrite:altgr"
After launching the epub in question (successfully), the debug output includes:
Code:
Warning: QWindowsFontDatabase::fontEngine: Can't change family name of font
Once for each of the 8 woff2 fonts included in the test epub.
DiapDealer is offline   Reply With Quote