Thread: [Device Plugin] Kobo Touch Extended Driver
View Single Post
Old 04-13-2015, 10:01 AM   #1248
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 monry View Post
I understand that. What I meant is that it displays pages/percentages/time left to the next image instead of next chapter. I've downloaded book once again from the store to see if maybe this was resolved inside of it but nothing changed.

This is quite funny cause I've tried to change what is displayed later yesterday and pages and percentages are correct but time is still 0 minutes. Some of my books are perfectly fine and some are affected. This wouldn't bother me if the chart was good cause I'm using pages numbering in footer but there are flat chapters on it and I can't see how long is the next one for example. Any ideas?
Edit: OK I now validated this epub with W3C validator and it has no problems..
As jgoguen said, the per chapter timing, percent and page numbers are to the next chapter in the book. For a kepub, chapter is defined in two ways: the ToC and the files within the kepub. The value displayed depends on how big the chapter is. If it is only one page, the time remaining will be zero.

From what you say, the book has images in it. I think each image is in a separate file. So, it is probably the chapter heading with text in one file, then the image in the next and then some more text in the next. The per chapter stats is based on those files. I have just done an experiment with an epub that was constructed like this and it worked how you described it.

As I said before, every file in a kepub is supposed to have a ToC entry. If they don't it works, but you get strange things like this. The extended driver doesn't fix the ToC. Doing a conversion to kepub can update the ToC. That uses the full conversion pipeline rather than the much simpler processing the driver does. This works for most books, but this demonstrates there are some short comings.
davidfor is offline   Reply With Quote