View Single Post
Old 04-03-2024, 05:32 PM   #89
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: 28,699
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
It was definitely a Qt bug. They quickly fixed the crash after Kevin put together a test program that clearly produced the crash.

The crash fix still won't show the font family name of woff/woff2 fonts in book browser tooltips or font tabs. If you use woff fonts a lot, you may wish to force Sigil to use our patched qt freetype font engine by setting the SIGIL_USE_FREETYPE_FONTENGINE. You can set it to any value.

After restarting Sigil (and maybe your machine depending on how the environment variable was set), you should see the font family names of woff/woff2 fonts show up where they should.

We didn't want to force a non-default qt font backend on everyone (on Windows) for such a piddly issue that won't affect many people.
DiapDealer is offline   Reply With Quote