View Single Post
Old 07-02-2012, 03:08 PM   #189
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,083
Karma: 148029447
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by ldolse View Post
@JSWolf, As I said before, the plugin code inserts @page by design - this is the only way to insert top and bottom page margins to match Calibre's preferences - this is the only way you can use modify ePub to fix the corresponding check in quality check. Inserting @page in general is not a bug and it's not going to change.

Aside from offending your sensibilities, an empty @page declaration is going to behave exactly the same as not inserting @page, but I'm ok with calling this case an issue, albeit a low priority one since it won't affect how the book renders. Whenever I get a chance to dig back into the plugin to investigate Jackie's case I'll look into not inserting empty @page statements when all margins are zero.
Could you also add in an option to delete @page? Also, if both options are checked, deleting @page should take higher priority.
JSWolf is offline   Reply With Quote