The page-break-after:avoid rule just doesn't do its job! Can we fix it? Yes we can.
You all know it to be true. The one really annoying thing about the re-flowable ePub, is that you are often seeing those sub-titles all on their own at the bottom of the page. Just like a lonely orphan.
You can see an example in the first image here.
CSS has some rules for paged-media that try to prevent a page breaking before or after elements. Try as I might, I simply cannot get this do as expected.
So is there a way to sort this out while we wait for the ereader software to be updated to solve this? Or do we really have to use the fixed-layout option. No!No! Please not that.
My talk during the 'Love Learning' Seminars at the London Book Fair 2013, had a large audience. If any of you are reading this - apologies that I over-ran my time slot and skipped over a few slides towards the end!
So much to say on this topic - hard to fit into a 50 minite slot.
Note: I presented from a PDF inside the iBooks app on the iPad. Just sweeping through the slides but double-tapping to enlarge images within the pages. This seems a very visually rich way to present and being already inside the iBooks app means that we can demonstrate eBooks from the library easily. There is less control than with Keynote. I did use Keynote to create the presentation but then exported out to PDF.
In the iBooks app on the iPad the user has control over the justification. Well, that is, by default justification is turned on. Users can turn that off - but they probably don't! ‘cos they don‘t know where to find it.
How can eBook designers get the kind of alignment they prefer, and make the eBook stay like that?
I have updated my eBook eBook Typography for Flowable eBooks, on the iBooks store.
The recent update to the iBooks app (this arrived the same time as the announcement for the iPad Mini), was causing a few oddities in the book. On investigating and experimenting, here is what I discovered.
I have used the MAC editor Coda from Panic for a while as my preferred web site and template editor. I have recently been using it to edit ePUB innards.
Coda normally expects that you are editing a site on a server, or at least transferring onto a server after editing locally, so the configuration for a 'site' may not seem initially appropriate for editing ePUBs. Nevertheless, setting up a local folder is straightforward. In fact, you can set this up to be the root of the complete ePUB, thereby giving you the potential to edit the various XML files (package files and TOC files).