Thread: Unwated Page Breaks
View Single Post
Old 04-11-2018, 06:11 PM   #6
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,111
Karma: 60406498
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by LeoD View Post
Hey guys, thanks for the tips. I tried them all and they didn't work. Also, I noticed that there was no code for "page-break-before" or "page-break-after". The page is being broken by the presence of separate index_split files, nothing else.

I had the width and height settings of the pictures set to "auto." I noticed that when I set width and height to something arbitrary and tiny, like 100px by 100px, the unwanted blank pages disappeared. Is it possible that the "auto" setting is creating the unwanted blank pages by sizing the picture too big? So far, I've only checked this in the ebook viewer that comes with Calibre. Any idea if this will be a problem on an actual ebook reader?

Thanks!
New file = implied pagebraek
I tend to us splits AS new chapters, where I want a break.
The only other time, is a forced-to-split case, to stay under 260K for older ADE based devices.
I like splits.I believe the performance improves with small chunks
theducks is online now   Reply With Quote