Quote:
Originally Posted by JSWolf
I have Courier Prime loaded on my Kobo. I tried font-family: monospace; and it did not work with 4.33. I used to work. I have 4.29 on my H2O and it used to work. Now it works if the font is named Courier. So your renaming is not superfluous any longer. It's what works in ePub.
When I try this in KePub, I get a really small font. Smaller then 1em. It could be Georgia.
IMHO, I think if the eBook is using monopsace, use ePub if you have Courier (or a font internally named Courier) in fonts. Otherwise, you'll have to do a full font embed. Even if you don't have Courier in fonts, you can do the pseudo embed (where you can specify the font that lives in fonts) for monospace.
So basically, after the font system change, Kobo made KePub worse because using monospace just became more difficult. And if monospace is used, you'll have a basically unreadable (too small) font that's not monospace (I think it's Georgia).
A good example of where this will be a problem is in the eBook of Planetfall by Emma Newman. It specifies monospace for text messages. If you load this as KePub, it will have sections of the book that are not readable or hard to read. If it's loaded as ePub and you don't have a Courier font in font's, you'll get the same font as your selected font.
This really is a mess for those who do not know the fixes. If someone buys books from Kobo and syncs, any books that specify monospace without any embedded font, will not be happy.
|
How is that truly changed? It has always been the case, that if a book needed a specific font, it should be embedded. That is the only save way to do it. Sure, Kobo changed things to support using a sideloaded monospace font if it was installed, but, they also never advertised the fact. It was pretty much only people who visited this forum that knew about it. Plus those who read blogs by people who source their information from here.