View Single Post
Old 04-29-2012, 08:52 AM   #60
kiwidude
Calibre Plugins Developer
kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.
 
Posts: 4,637
Karma: 2162064
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
@paulfiera - I don't really want to do that, as it means parsing and rewriting the css file, which is not in the "ethos" of this plugin of minimal changes.

If I remember this topic came up in the modify epub plugin development thread when I first considered the option of removing fonts. And I seem to recall that someone said leaving such orphaned declarations in the css file does absolutely no harm, and the reader will just fall back to using its default font which is what people wanted.
kiwidude is offline   Reply With Quote