View Single Post
Old 10-26-2012, 09:14 PM   #5
pholy
Booklegger
pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.
 
pholy's Avatar
 
Posts: 1,783
Karma: 7999034
Join Date: Jun 2009
Location: Toronto, Ontario, Canada
Device: BeBook(1 & 2010), PEZ, PRS-505, Kobo BT, PRS-T1, Playbook, Kobo Touch
If you think of the @font-face { } as a declaration of a font, realize that only a single font can be declared at a time. So your declaraion above needs to be broken up into three @font-face declarations. So if @font-face {} is a declaration, then the font-family: name; in a CSS rule is a reference; at that point you can have a series of font names separated by commas. The first name mentioned is the preferred font, each following name (a fallback) is less preferred. The ereader software uses the first on it can find.
Adobe-based ereaders can get very confused with multiple font-names in an @font-face declaration; one of the few times it doesn't totally reject the stylesheet, as far as I can tell.
Oh, and those font names are not for a family, they are a specific style and weight.
pholy is offline   Reply With Quote