Installing woff fonts - Page 5

DiapDealer · 03-16-2024, 03:51 PM

I say we add the nodirectwrite platform argument like we do altgr (except with no user preference involved) to force the gdi font backend for now. We can revisit removing it when the DirectWrite backend proves to be more complete.

If we don't do something, we'll be chasing mystery windows crashes as more users encounter embedded woff fonts on scaled displays. And I'm for the path of least Qt patching.

EDIT: for the record... adding the "fontengine=freetype" platform option seems to accomplish the same thing as nodirectwrite. It also eliminates any of the QWindowsFontDatabase::fontEngine warnings encountered when using nodirectwrite.

KevinH · 03-16-2024, 04:19 PM

Sounds like a good plan to me. Will you push that change to master?

DiapDealer · 03-16-2024, 04:33 PM

Sure. Do we need to limit this to a certain Qt version level? Also... do you see any benefit for "nodirectwrite" over "fontengine=freetype"?

KevinH · 03-16-2024, 04:39 PM

nodirectwrite is supposed to fall back to the gdi backend. Whereas all of the unix based Qts use the freetype one.

I am just not sure how well tested the freetype backend is on Windows.

As for limiting to Qt versions, the bug has existed since 6.3 timeframes and even possibly before that. Perhaps limit the change to all Qt6 versions for now, maybe up to 6.8.0? We can then revist that for any follow-on releases.

DiapDealer · 03-16-2024, 04:51 PM

Sounds good. I'll go with nodirectwrite between 6.0 and 6.8.

DiapDealer · 03-16-2024, 07:05 PM

If anyone who's been able to reproduce the issue would like to test a version of Sigil that includes a workaround, it can be downloaded from here:

https://github.com/dougmassay/win-qt...-x64-Setup.exe

Doitsu · 03-16-2024, 07:52 PM

Quote:

Originally Posted by DiapDealer

If anyone who's been able to reproduce the issue would like to test a version of Sigil that includes a workaround, it can be downloaded from here:

The beta version worked fine when 120% custom scaling was in effect.

KevinH · 03-16-2024, 08:00 PM

Just in case here is an alternative link from my own github site to DiapDealer's test build :

https://github.com/kevinhendricks/Bu...nMac/releases/

Download: Sigil-2.1.0-Windows-x64-Setup.exe

JSWolf · 03-16-2024, 08:37 PM

My Windows 11 is set to a scaling of 125%. But I also have QT_ENABLE_HIGHDPI_SCALING=0 set and the test ePub loads no problem.

DNSB · 03-16-2024, 10:15 PM

Tested in on a laptop with the scaling set to 125% and Sigil 2.0.2 crashed, Sigil 2.1.0 did not.

DiapDealer · 03-16-2024, 10:20 PM

Great. Thanks. And thanks for the tip about checking the scaling!

BetterRed · 03-16-2024, 11:51 PM

Quote:

Originally Posted by DNSB

Tested in on a laptop with the scaling set to 125% and Sigil 2.0.2 crashed, Sigil 2.1.0 did not.

Dell XPS-8920 desktop, with scaling at 150% (Recommended), using DNSBs test epub.

Any reason why I shouldn't continue to use Diap's 2.1.0?

BR

DiapDealer · 03-17-2024, 12:13 AM

Quote:

Originally Posted by BetterRed

Any reason why I shouldn't continue to use Diap's 2.1.0?

None that I can think of. It's basically what the next Windows release will be.

BetterRed · 03-17-2024, 01:14 AM

Quote:

Originally Posted by DiapDealer

None that I can think of. It's basically what the next Windows release will be.

Then I will

I fired up Page Edit 2.0.2 on DNSB's test epub, it did not crash - is that what y'all would expect.

I call Qt "Thatcher's Curse" - There Is No Alternative

BR

DiapDealer · 03-17-2024, 08:09 AM

Quote:

Originally Posted by BetterRed

I fired up Page Edit 2.0.2 on DNSB's test epub, it did not crash - is that what y'all would expect.

I tend not to expect much of anything where Qt is concerned.

03-16-2024, 03:51 PM	#61
DiapDealer Grand Sorcerer Posts: 28,897 Karma: 207182180 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	I say we add the nodirectwrite platform argument like we do altgr (except with no user preference involved) to force the gdi font backend for now. We can revisit removing it when the DirectWrite backend proves to be more complete. If we don't do something, we'll be chasing mystery windows crashes as more users encounter embedded woff fonts on scaled displays. And I'm for the path of least Qt patching. EDIT: for the record... adding the "fontengine=freetype" platform option seems to accomplish the same thing as nodirectwrite. It also eliminates any of the QWindowsFontDatabase::fontEngine warnings encountered when using nodirectwrite. Last edited by DiapDealer; 03-16-2024 at 04:22 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Libra 2 Installing Custom Fonts	BookCat	Kobo Reader	41	04-05-2022 10:01 AM
Installing fonts	Pajamaman	KOReader	6	09-05-2020 03:06 PM
Installing Tamil Fonts on SnPRS - T2	Raman	Sony Reader	3	01-12-2013 12:54 PM
Installing Tamil Fonts on Kindle 4.1.0	sriramvenkatesan	Amazon Kindle	14	10-22-2012 11:45 AM
PRS-T1 Still have a problem with installing fonts in my device	hamedavatar	Sony Reader	5	06-21-2012 06:46 PM

03-16-2024, 04:19 PM	#62
KevinH Sigil Developer Posts: 9,073 Karma: 6361556 Join Date: Nov 2009 Device: many	Sounds like a good plan to me. Will you push that change to master?

03-16-2024, 04:33 PM	#63
DiapDealer Grand Sorcerer Posts: 28,897 Karma: 207182180 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Sure. Do we need to limit this to a certain Qt version level? Also... do you see any benefit for "nodirectwrite" over "fontengine=freetype"?

03-16-2024, 04:39 PM	#64
KevinH Sigil Developer Posts: 9,073 Karma: 6361556 Join Date: Nov 2009 Device: many	nodirectwrite is supposed to fall back to the gdi backend. Whereas all of the unix based Qts use the freetype one. I am just not sure how well tested the freetype backend is on Windows. As for limiting to Qt versions, the bug has existed since 6.3 timeframes and even possibly before that. Perhaps limit the change to all Qt6 versions for now, maybe up to 6.8.0? We can then revist that for any follow-on releases.

03-16-2024, 04:51 PM	#65
DiapDealer Grand Sorcerer Posts: 28,897 Karma: 207182180 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Sounds good. I'll go with nodirectwrite between 6.0 and 6.8.

03-16-2024, 07:05 PM	#66
DiapDealer Grand Sorcerer Posts: 28,897 Karma: 207182180 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	If anyone who's been able to reproduce the issue would like to test a version of Sigil that includes a workaround, it can be downloaded from here: https://github.com/dougmassay/win-qt...-x64-Setup.exe

03-16-2024, 08:00 PM	#68
KevinH Sigil Developer Posts: 9,073 Karma: 6361556 Join Date: Nov 2009 Device: many	Just in case here is an alternative link from my own github site to DiapDealer's test build : https://github.com/kevinhendricks/Bu...nMac/releases/ Download: Sigil-2.1.0-Windows-x64-Setup.exe

03-16-2024, 08:37 PM	#69
JSWolf Resident Curmudgeon Posts: 80,832 Karma: 150249619 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	My Windows 11 is set to a scaling of 125%. But I also have QT_ENABLE_HIGHDPI_SCALING=0 set and the test ePub loads no problem.

03-16-2024, 10:15 PM	#70
DNSB Bibliophagist Posts: 48,276 Karma: 174315444 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	Tested in on a laptop with the scaling set to 125% and Sigil 2.0.2 crashed, Sigil 2.1.0 did not.

03-16-2024, 10:20 PM	#71
DiapDealer Grand Sorcerer Posts: 28,897 Karma: 207182180 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Great. Thanks. And thanks for the tip about checking the scaling!

Advert

Advert