View Single Post
Old 09-22-2025, 11:03 AM   #5
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,982
Karma: 6361444
Join Date: Nov 2009
Device: many
BTW, that same bug hit me but the problem was not a bad font, but a duplicate font which seems to confuse Qt. It turns out I had a local Arial font file and a local Times New Roman font file but Sequoia installed a system version of Arial and of Times New Roman with lots of unicode code points added to each of their versions.

With Apple's FontBook I was able to detect the duplicates and remove/disable my own local copies of Arial and Times New Roman and everything Qt started to work again.

So look out for font duplicates as well. If in doubt, disable your local font files.
KevinH is online now   Reply With Quote