Quote:
Originally Posted by Zora
Thanks, Odedta. I have notified the client that version 20140530-3 of the epub is now deprecated  as well as sending him your comment. Perhaps he can just accept that the software on his iPad *will* insist on doing this. He tends to want to optimize for the device he uses and forget about the others. |
ALL clients want to do that. We get clients that will literally insist that we insert a page-break, to force a line that they are seeing as a widow, to have a companion line. Naturally, they're seeing it at ONE font size only, on one device...they don't even try to change the font sizes, or the screen orientation, or (if Kindle Previewer, for example), other "devices." The same is spectacularly true for iPad-clients; bet he hasn't even changed the font, much less the font-size. {shrug}. You shouldn't try to satisfy that type of insensibility to the environment of eBooks; they need to better understand the workings.
I've lost track of the hundreds--literally--of images and videos of this I've made for clients on this very topic. "This is what your ebook looks like. This is your ebook on drugs (font size 4). This is your ebook with a different font, at font-size 5," and so on and so forth. And do we have all this stuff in our FAQ, Resources and Handbook? YES, we do. Do they read it? NO, they don't. It's an uphill battle, but if you give in to it too much, it gets unmanageable.
If you're making the book with all the sections/chapters in their own files, as odedta said, the "page-break-before:always" is redundant. You should remove it; the chapters will all start on their own pages naturally without it, on virtually every device I've ever seen. iBooks will insert additional blanks for what SEEMS to be no apparent reason, but it's usually something, if you spend enough time tracking it down--and it's particularly noticeable in the first-gen iPads. I wouldn't spend more time on it, really.
Hitch