Thread: Kepub erratic numbering
View Single Post
Old 05-08-2021, 12:06 AM   #6
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Pjama View Post
Update - just moved on to the next chapter, and it also skipped three pages! I’m going to see if it does this for all my Kepubs. I don’t recall noticing it before though. I purchased it on my kobo, so no conversion at any stage.
The full book page numbering for kepubs is supposed to be one page per screen. And it changes with the font settings. But, there are a couple of bugs. The main one I notice is that the last page in a chapter doesn't always increment. The other one seen is that in longer chapters, the page numbering doesn't always increment for each turn. This happens about one in eight pages. This seems to get worse with more complex page coding or with images.

I haven't noticed what you are reporting with kepubs. For epubs, skipping a page at the end of a chapter does happen. And if you page backward, the page does show. It has something to do with exactly where on the screen the page break would happen. For kepubs, some of the page calculation is done when the book is added to the device, some is done the first time it is opened and the rest as the book is read. I have an idea that the problem is something to do with the relative size of the internal files in the book. There is also an issue with what is in the ToC. In the past, when there was not a one-to-one relationship between the ToC and the internal files, there were some interesting problems. Most have been fixed, but, I think there are still some problems.

Unfortunately, without seeing the book, it is hard to work out what is actually happening.
davidfor is offline   Reply With Quote