View Single Post
Old 06-09-2025, 04:13 PM   #19
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,796
Karma: 146391129
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by Slevin#7 View Post
That's pretty the way it should look like, thanks for checking.

So I think, since nobody seems to have stumbled across a similar issue during their eBook coding time, I will leave it at that - although I have to confess, I'd still prefer to know the reason why^^.

Thanks to everyone for helping.

And for documentation's sake, the issue visually as attachment.
I have an idea for something you can try. QT sometimes has problems with your video driver. There is a way around it that may work. Set the following code as an environment variable in Windows and then reboot and see what happens.

Code:
QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu"
If it still fails and the view shows the font incorrectly, try booting into safe mode and try the viewer again. If it then works, then it's something that runs on startup that's the problem.
JSWolf is offline   Reply With Quote