View Single Post
Old 08-22-2017, 10:08 PM   #4
tomsem
Grand Sorcerer
tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.
 
Posts: 6,959
Karma: 27060153
Join Date: Apr 2009
Location: USA
Device: iPhone 15PM, Kindle Scribe, iPad mini 6, PocketBook InkPad Color 3
It used to be that Kindle re-paginated all the time when you jumped to a new location. That was a problem, because it is a waste of computing power, and can be dis-orienting to readers. No doubt it still does this on older Kindles. Now jumps do not generally force re-pagination. You're only guaranteed that the location you are jumping to is somewhere on the page you wind up on.

One downside of the newer behavior is that there is no way to coerce repagination, e.g., to un-orphan an orphaned header or image caption (short of changing font or something like that). I used to do this by selecting the orphan, then 'Search this book' and select it in the search results, thereby jumping to the thing I'd selected, which would then be at the top of the page. But that in turn was just a workaround for the lack of orphan control. I don't think Kindle platform supports 'orphan' CSS, and certainly does not have heuristics to prevent orphans. Maybe some ePub systems do.

Last edited by tomsem; 08-22-2017 at 10:24 PM.
tomsem is offline   Reply With Quote