View Single Post
Old 06-28-2009, 09:38 AM   #18
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,856
Karma: 146918083
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 Jellby View Post
You got me!

I was thinking of that while I was writing my message, but decided it was not worth mentioning it

Yes, specifying generic font families is fine, nothing wrong with that (do current ePUB readers provide a complete set of these families, anyway?). My point was that a particular font face should not be used if it's not embedded, because there's no guarantee the readers will have that font, or even the possibility of installing it (or at least, the creator should assume that many readers will not see the intended font).
When I use CSS code to specify specific fonts, I do this for my own use and do not have to add he font files to the ePub.. If I am going to embed for others, I will embed in the ePub file itself.

I did take a recently converted ePub and specify that the headers should use the default sans-serif font and it worked perfectly.
JSWolf is offline   Reply With Quote