View Single Post
Old 03-21-2020, 04:57 PM   #35
jackie_w
Grand Sorcerer
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 6,257
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
Quote:
Originally Posted by konstantinus View Post
I have not installed 4.20.XXXXX yet. Does the quote mean that the user will no longer be able to set his font family
In fw 4.20.xxxxx Kobo changed quite a bit about how kepub pop-up footnotes are handled. The old font-family patch no longer works and there isn't any obvious patchable nickel CSS dedicated to footnote font-family.

Having said that, although not a kobopatch, there is a way forward if you have the inclination and the technical skills. It will affect the whole Kobo GUI, which may or may not be acceptable to you. In outline it involves using a font editor to internally/externally rename your font-of-choice to Georgia before sideloading it to the standard /fonts directory. The new font will then be used for the pop-up footnotes and everywhere else in the GUI that used to use Georgia.

If you plan to attempt this I suggest you first read through this thread, particularly the Summary linked at the bottom of post #1 and especially post #2.

Quote:
Originally Posted by konstantinus View Post
... and the font size of the pop-up footnotes?
The old font-size patch no longer works in 4.20.xxxxx but see this post and it's link to GitHub for a workaround. Not as flexible as the old patch but it does work (at least for now).

ETA: Please note the workaround is now a libnickel.so.1.0.0.yaml patch not a nickel.yaml patch.

Last edited by jackie_w; 03-21-2020 at 05:04 PM. Reason: ETA
jackie_w is offline   Reply With Quote