View Single Post
Old 12-26-2011, 10:51 AM   #86
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: 80,070
Karma: 147983159
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 jackie_w View Post
I think that as long as you use the generic font-family names (serif, sans-serif, monospace) in your @font-face statements rather than specific font name labels (e.g. Charis, Fontin, "Times New Roman", Amasis) then the standard select-a-font feature should work as well (or as badly ) as it's always worked.

Personally, I've always done it this way, even in PRS+. I never could see the point in using those specific font name labels, it's just one more thing that needs changing when you clone an old PRS+ css file to try out a new font.
I'll have to give that a try and see what happens. I'll report back after I try it.
JSWolf is offline   Reply With Quote