Thread: Using calibre.ebooks.oeb.polish.container in a driver
View Single Post
Old 07-26-2013, 01:49 AM   #8
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by kovidgoyal View Post
Polish books does not modify existing css (only adds new css if needed), therefore the css parsing is intended to be used read-only. The existing css preprocessor is designed for the conversion pipeline, not polishing. You should be fine with using a dummy version.
In that case there is a problem. I couldn't think of why Polish books would modify the CSS, so I had a look. Subsetting embedded fonts was the first spot that I found. When I used that, it removed the @page rules from my stylesheet. I also checked by doing a conversion and adding margins to the page. Again, Polish books removed the @page rules when I subsetted the fonts.

I got caught when doing the above tests. I was surprised that Polish books processed the original_epub. I understand why the conversion does this, but I was expecting Polish books to polish the final product.
davidfor is offline   Reply With Quote