Thread: [Device Plugin] Kobo Touch Extended Driver
View Single Post
Old 11-26-2016, 08:14 AM   #1652
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 Handsome2000 View Post
Thank you very much for your reply.
The origin of the file is epub file. I convert this epub file to kepub with calibre using extended driver and send to the device. But still have this problem. Can you give me more info about checking this file? What should I focus on when checking? Also I have no problem with the original epub file reading on my device.. thank you.
When you do the check, you are looking for errors. Any error could be causing the problem. As to running a check, as you are using calibre, the simplest thing you can do is open the epub in the calibre editor and run the "Check book" tool. If there are problems, they will be listed and you can use the editor to fix them.

As to what errors you are looking for, I don't really know. I usually clean my books and do so reformatting before sending them to the device. With that, I rarely see problems. This has to be either an error in the code of the book, or something very unusual that the kepub renderer cannot handle.

The only other thing I can think of is if it is a very large book with a very large ToC. That might be enough to trigger the firmware thinking that the renderer has hung and force a restart.
davidfor is offline   Reply With Quote