View Single Post
Old 07-03-2012, 02:12 PM   #208
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: 147983159
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 kiwidude View Post
@JSWolf - nice find and thanks for the PM. The issue is caused by there being multiple children in that svg container area of the xhtml page. I'm including the fix in this attachment.

To anyone - can someone please have a quick sanity check of the attachment to make sure you are happy with the changes made to the margins handling. As noted it still does not do anything about margins for named body classes, but all the other behaviour discussed recently should be in place.
Yes, it worked. It did not delete the cover image but did correctly delete the cover thumbnail. Now, when a cover thumbnail exists, does the plugin delete it if it is not used in any of the XML files and if it does, does it also get rid of any spine entries for it? That would be a good thing. If it's not used in any XML, then it's not needed even in the spine.

As for the @page, it seems to be working now. So we can add or remove as desired based on the margin settings. This work well.
JSWolf is offline   Reply With Quote