Quote:
Originally Posted by davidfor
Isn't that unwieldy? It means that there are somewhere between 250 and 900 extra lines in the fonts menu. How can you find one to use?
|
I have such number of fonts just because I was testing fonts. I don't plan to do that permanently.
I don't use the menu to change the fonts. KOReader can generate a "test font document" which contains some text which is set to show in every single font installed in the device. This document is in plain HTML format. It is the document RMSDK failed to open.
I trimmed the text to fit in one screen, imported the document into Calibre and converted it to ebook format. This way I just go to the next page to see the next font. Don't need to use the menu at all. I just set the font to "Publisher default".
The kepub I generated works ok in Nickel, but RMSDK couldn't handle the epub. I was interested in seeing the RMSDK output because Nickel is pretty bad at handling kerning and it does funny things with most fonts when displaying the "[leoˈnardo diˌsɛr ˈpjɛːro da (v)ˈvintʃi]" part of the text. See the difference between Baskerville 10 Pro and IBM Plex Serif in the attached screenshots.
BTW, Calibre and the rendering engines in the devices mess it up when the font name contains a word made solely of numbers. Calibre converts every single
Code:
<div style='font-family: whatever'>
declaration into a CSS style, but for some reason the numbers are ignored if they are not attached to a letter. I had to manually fix "Aldine 721 BT", "Baskerville 10 Pro" or "Coranto 2" and a few others in the epub by enclosing the font name in quotes. There where just a few, luckily.
Quote:
Originally Posted by davidfor
I was told by a Kobo developer that the RMSDK was inefficient in how it loads fonts, though I would not have thought it would load all the fonts. But, maybe it is loading them to get the details so they can be used when needed. That would make sense with a sickel timeout reboot and it working when the number of fonts was reduced.
|
Very interesting info. It explains why RMSDK struggles so much with that document. It seems that it loads all the fonts regardless of whether they are used in the document it is handling or not, because I couldn't load any epub at all.
I guess I can just test the fonts in RMSDK in small batches, so problem solved. The problem I have now is to keep just 50 fonts or so. There are very very good fonts out there.