View Single Post
Old 05-01-2013, 04:21 PM   #7
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,796
Karma: 146391129
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by katl View Post
I used the list of included fonts for various readers from this website to come up with my font family fall backs, so hopefully most people will be happy.
It won't work. there is no way to access fonts on a reader just by using the font-family name of the font. You can use the generic serif, sans-serif, and monospace. But that's it. All it's doing it preventing font changes if the device supports such.

Quote:
I'm actually considering removing the font-family from all of the text in the book. My thinking is this: If I don't know what "normal" text font the user will choose, how can I really choose a header to compliment it? I'll dig around a little more to see if that's the best way to proceed,and if anyone has any advise on that matter I would love to hear it.
You can do something like sans-serif for the headers. That's acceptable. Unless you actually embed the fonts, leave the body as whatever the device displays.
JSWolf is offline   Reply With Quote