Forma Odd font abnormality on Forma post-upgrade 4.32 - Page 2

rtiangha · 06-21-2022, 08:46 AM

I figured out what was causing this issue for me.

Back in the day before supplemental fonts were a thing and before Kobo allowed you to install/replace system fonts in the root partition yourself (if you did, they just wouldn't show up in the menu), one way to increase the number of glyphs in the UI fonts was to replace Georgia and Avenir Next by taking a different font (ex. Noto Serif/Sans), renaming them as Georgia/Avenir Next in the font metadata, and placing them in /mnt/onboard/fonts. When you opened a book, those versions of the fonts would be loaded and from then on, the UI would use those instead until the next reboot. The system was smart enough not to show duplicates in the font drop down menu.

I did this using Georgia Pro and the W1G version of Avenir Next because they had pan-European support including Cyrillic characters, and I've had it set up this way for years.

When supplemental font support arrived, I noticed that if I had a specific sideloaded font selected for a book, the next time I opened that book, while it would still display the correct font in the book text, the font name displayed in the font menu would always be off by two. It didn't used to happen, but it was always consistent.

I eventually had a hunch that maybe the indexing was off by two because of those two extra hidden fonts, so I deleted my sideloaded custom versions of Georgia and Avenir Next and the indexing problem went away (I now just install them directly to the root partition via kobopatch and have duplicate copies of them in the Plato and Koreader internal font directories so I can use them there too).

But it also had the side effect of fixing the problem of the UI falling back and displaying the Kakugo font upon USB disconnect as well.

So maybe that was the problem. Because the user partition becomes unavailable to the system when it's mounted on a computer, and at that time the UI is using the fonts from there instead of the root partition, it gets confused and falls back to displaying Kakugo when those fonts suddenly disappear and it doesn't reload them once they become available again (which didn't used to be a problem pre font engine rewrite).

That's my guess, anyway.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
I added a new font and my Forma is letting me use advanced options (!)	Wallace Lee	Kobo Reader	7	06-10-2020 08:55 AM
Odd font regression in Kindle Previewer, and online	dgatwood	Kindle Formats	4	02-06-2015 01:06 AM
The #1 Big-Data Detective is Back, in Abnormality #2	pigeonweather	Self-Promotions by Authors and Publishers	2	03-13-2014 04:12 PM
mobi to epub conversion - odd font size...	richrock	Conversion	3	03-06-2013 05:30 PM
PDF with odd text/font	Atagahi	Sony Reader	0	04-28-2011 11:03 AM

06-21-2022, 08:46 AM	#16
rtiangha Evangelist Posts: 495 Karma: 356531 Join Date: Jul 2016 Location: 'burta, Canada Device: Kobo Glo HD	I figured out what was causing this issue for me. Back in the day before supplemental fonts were a thing and before Kobo allowed you to install/replace system fonts in the root partition yourself (if you did, they just wouldn't show up in the menu), one way to increase the number of glyphs in the UI fonts was to replace Georgia and Avenir Next by taking a different font (ex. Noto Serif/Sans), renaming them as Georgia/Avenir Next in the font metadata, and placing them in /mnt/onboard/fonts. When you opened a book, those versions of the fonts would be loaded and from then on, the UI would use those instead until the next reboot. The system was smart enough not to show duplicates in the font drop down menu. I did this using Georgia Pro and the W1G version of Avenir Next because they had pan-European support including Cyrillic characters, and I've had it set up this way for years. When supplemental font support arrived, I noticed that if I had a specific sideloaded font selected for a book, the next time I opened that book, while it would still display the correct font in the book text, the font name displayed in the font menu would always be off by two. It didn't used to happen, but it was always consistent. I eventually had a hunch that maybe the indexing was off by two because of those two extra hidden fonts, so I deleted my sideloaded custom versions of Georgia and Avenir Next and the indexing problem went away (I now just install them directly to the root partition via kobopatch and have duplicate copies of them in the Plato and Koreader internal font directories so I can use them there too). But it also had the side effect of fixing the problem of the UI falling back and displaying the Kakugo font upon USB disconnect as well. So maybe that was the problem. Because the user partition becomes unavailable to the system when it's mounted on a computer, and at that time the UI is using the fonts from there instead of the root partition, it gets confused and falls back to displaying Kakugo when those fonts suddenly disappear and it doesn't reload them once they become available again (which didn't used to be a problem pre font engine rewrite). That's my guess, anyway.