View Single Post
Old 04-24-2015, 09:48 AM   #920
Rev. Bob
Wizard
Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.
 
Rev. Bob's Avatar
 
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
Quote:
Originally Posted by cybmole View Post
I'd settle for removal only of matches for

<div class="mbppagebreak" id="calibre_pb_\d+"></div>
I wouldn't, for the reason I gave above: that would catch matches in the middle of a document, instead of only at the beginning and/or end. I've already explained why that's a terrible idea. You can do so manually if you wish, but I will not.

Now, if it's confined to right after <body *> or right before </body>, that's a different story - but what you describe is not limited in that way, and therefore I will not do it. I may or may not elect to build any sort of mbppagebreak processing into the plugin, but I have already decided that much.
Rev. Bob is offline   Reply With Quote