Thread: Kobo future firmware feature request thread
View Single Post
Old 10-10-2013, 07:25 AM   #829
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
John,

The problem is that what you want can't be done without rendering the complete book. Or at least not for all books.

The other David specified how page numbers are calculated for epubs. It is also described in https://wiki.mobileread.com/wiki/Adob...s#Page_numbers.

All that means it is easy to calculate a page number for the start of each file in the epub. And if each file represents a chapter, then it is easy to calculate the page number.

But, if the chapters are not at the file breaks, you need to render all files to work out which page the chapters are on. That is a lot more work. Of course it is possible, but it could take a long time for a big book.

And for what it is worth, I would say that at least 25% of my books are of the latter type.
davidfor is offline   Reply With Quote