View Single Post
Old 04-18-2010, 01:29 PM   #59
charleski
Wizard
charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.
 
Posts: 1,188
Karma: 727236
Join Date: Sep 2009
Device: PRS-505
I see some people have difficulties with this hack over-riding a font that's embedded in the epub. This can easily be prevented (in the vast majority of cases) by restricting the font-family definition to the html tag only, thus:
Code:
html { font-family: serif; }
[do not include any font definitions for the body or p tags]
This way the top-level html tag will specify your replacement font. But, most epubs with embedded fonts put the font-family definition in the body or paragraph tags. These will now not be affected by the global user css file and will take precedence over the font-family attribute in the html tag.

I use this hack with PRS+, and this saves having to disable the user css for epubs with embedded fonts.
charleski is offline   Reply With Quote