View Single Post
Old 07-16-2011, 03:25 PM   #12
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,196
Karma: 1281258
Join Date: Sep 2009
Device: PRS-505
Quote:
Originally Posted by kartu View Post
Custom CSS works in all books, but some might have style that overrides yours, which is a generic CSS "issue".
Actually, that's the goal: modify the defaults, but allow the book's own css to override these as needed so its design is preserved. If the ePub's design is faulty, then it's the ePub that needs to be fixed, since mucking around with !important properties that will mess things up in other books.

But you have a point about redefining the base font classes, that will catch cases where the book (unnecessarily) has something like body { font-family: serif ... }.
charleski is offline   Reply With Quote