View Single Post
Old 12-27-2011, 03:46 PM   #100
pssquirrel
ebooknut
pssquirrel ought to be getting tired of karma fortunes by now.pssquirrel ought to be getting tired of karma fortunes by now.pssquirrel ought to be getting tired of karma fortunes by now.pssquirrel ought to be getting tired of karma fortunes by now.pssquirrel ought to be getting tired of karma fortunes by now.pssquirrel ought to be getting tired of karma fortunes by now.pssquirrel ought to be getting tired of karma fortunes by now.pssquirrel ought to be getting tired of karma fortunes by now.pssquirrel ought to be getting tired of karma fortunes by now.pssquirrel ought to be getting tired of karma fortunes by now.pssquirrel ought to be getting tired of karma fortunes by now.
 
pssquirrel's Avatar
 
Posts: 297
Karma: 688154
Join Date: Oct 2011
Device: Kindle Voyage & Oasis
Quote:
Originally Posted by jackie_w View Post
... it's quite possible that the font-family: serif; line is redundant as all the ereaders I've owned seem to use font-family: serif as the epub default in the absence of more specific css.
I just tested this and you're right! If you use @font-face { font-family: serif; ...} you don't need to include body {font-family: serif}

I like this very much as it leaves the css cleaner and more universal, less likely to cause problems if you want to read the same epub on other devices. Also, I didn't realize using the generic "serif" will let you switch fonts on the T1. Very nice! Thanks for so many tips, jackie_w!

P.S. re:
Quote:
I always put the @font-faces at the beginning of the .css file (but I'm not sure whether this is important)
FYI, I don't think it matters. I always put the @font-faces at the end, and it still works.

Last edited by pssquirrel; 12-27-2011 at 03:55 PM. Reason: correction
pssquirrel is offline   Reply With Quote