View Single Post
Old 10-11-2014, 09:49 AM   #10
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,140
Karma: 148951761
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 arspr View Post
NO, JSWolf, you don't need to do that, although, of course, that's the way you guarantee it will always work.

page-break-before (or even -after) CSS property can be used either. But it might not work in some kind of defective/old/simple? renderers. As examples: the aforementioned Editor Preview, and more over, and quite incomprehensibly, Kobo ACCESS renderer for their "advanced" kepubs. (Beware, future H2O buyers...)
The other issue that's not been mentioned is if chapters are split between XML files. If that's the case, then splitting at chapter breaks and making sure each chapter is complete is the best solution that will work best of all.
JSWolf is online now   Reply With Quote