View Single Post
Old 02-25-2021, 11:48 AM   #12
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,133
Karma: 60406498
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by luisdent View Post
I'm not sure what you mean, i downloaded and installed the fonts from the official google fonts. i never renamed them. and the font names don't all need to be in the epub, that's the point of the device being able to pick whichever font it wants right? so where would the font have to be case sensitivly correct?

also, I've reread your messages 3 times. i don't know what you're referring to that i haven't already addressed? if you qoute your point i can try to address it again...
The message about unsupported FW. All that means in this case is the driver needs updating to recognize the new FW number, the Kobo database has not really changed in recent times.

Your book calls for Obscura.TTF, but your device has obscura.ttf <brap, fail>
We are mainly talking FILE NAME as used, Internal font (Family) name IS an issue on some devices, but I have not run into that with my Aura 2
theducks is online now   Reply With Quote