View Single Post
Old 06-15-2016, 08:49 AM   #374
sherman
Guru
sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.
 
Posts: 876
Karma: 2676800
Join Date: Aug 2008
Location: Taranaki - NZ
Device: Kobo Aura H2O, Kobo Forma
To be honest, while I'm no expert, I'm leaning towards the conclusion that Qt is the main issue with font problems. Qt + non-system fonts = pain.

Some here may remember last year I created a script to modify font files for our Kobos. Over the summer, I worked at slapping a GUI on top, and after a while after playing with wxPython and Tkinter, I settled on learning the basics of PyQt.

Well, I have a mostly working GUI, however there is one problem...

I wanted to be able to offer a preview of what the font changes look like, however I still have not managed to get it working. To put it simply, Qt font handling is downright weird, especially once you start adding the various styles for one font.

I bring this up, because I'm pretty sure that Nickel uses Qt (please correct me if I'm wrong!), and I would in no way be surprised if ACCESS also uses Qt (on the Kobo at least - I assume the underlying engine is not tied to any specific UI toolkit)
sherman is offline   Reply With Quote