MobileRead Forums - View Single Post

KamenoHayasa · 10-07-2017, 07:52 AM

Hi,
I just had the same issue with Sigil 0.9.8.
° Reinstalling did not fix the issue.
° Rebooting did not fix the issue.

Due to the remark above I attempted to Rebuilt my Font Cache.
There is a script that does it for Windows 10
https://www.tenforums.com/tutorials/...dows-10-a.html
After reboot Sigil did work again.
Just to complete because the above message while pointing out a possible issue, do not give a clear solution on how to fix it.
Regards,

P.S. :
I just started Sigil and I got the message again. Last time it could have been something to do with a corrupted Fontcache for I installed fonts the day before. That time it should not happen for such reason. Yet I saw the message again but unlike last time Sigil started anyway.

Regards,

P.S. 2:
OK so the thing that causes this message is actually not necessarily due to font cache. It seems to be happening when you customize the fonts of the GUI and use Google Fonts in particular.
Either something goes wrong with Google Fonts, Either the API that Sigil uses or a part of its own code is buggy.
I did a screen cast. You don't need to watch it entirely. It is just showing how it behaves. By the middle of the video I suggest Google Font may be what causes the issue and try to find fonts that were here before I installed them. using those fonts just work like a charm. However the drop down menu is also buggy because it needs to deal with Google Fonts likely.
I'm wondering if the real cause is Google Font or non robust font management should it be Sigil or Qt API. But at least we have a sample of the bug no matter where it comes from.
https://youtu.be/P8GqsO17aQY

10-07-2017, 07:52 AM	#3
KamenoHayasa Junior Member Posts: 2 Karma: 43620 Join Date: Oct 2017 Location: They'd call me froggy but I hate eating frogs... T_T Yuck ! Device: PC and I'd love a kobo later on.	Hi, I just had the same issue with Sigil 0.9.8. ° Reinstalling did not fix the issue. ° Rebooting did not fix the issue. Due to the remark above I attempted to Rebuilt my Font Cache. There is a script that does it for Windows 10 https://www.tenforums.com/tutorials/...dows-10-a.html After reboot Sigil did work again. Just to complete because the above message while pointing out a possible issue, do not give a clear solution on how to fix it. Regards, P.S. : I just started Sigil and I got the message again. Last time it could have been something to do with a corrupted Fontcache for I installed fonts the day before. That time it should not happen for such reason. Yet I saw the message again but unlike last time Sigil started anyway. Regards, P.S. 2: OK so the thing that causes this message is actually not necessarily due to font cache. It seems to be happening when you customize the fonts of the GUI and use Google Fonts in particular. Either something goes wrong with Google Fonts, Either the API that Sigil uses or a part of its own code is buggy. I did a screen cast. You don't need to watch it entirely. It is just showing how it behaves. By the middle of the video I suggest Google Font may be what causes the issue and try to find fonts that were here before I installed them. using those fonts just work like a charm. However the drop down menu is also buggy because it needs to deal with Google Fonts likely. I'm wondering if the real cause is Google Font or non robust font management should it be Sigil or Qt API. But at least we have a sample of the bug no matter where it comes from. https://youtu.be/P8GqsO17aQY https://youtu.be/P8GqsO17aQY</a>?wmode=opaque&origin=https://www.mobileread.com" frameborder="0" allowfullscreen> Last edited by KamenoHayasa; 10-08-2017 at 02:14 PM.