Thread: Device Communication Errors
View Single Post
Old 11-11-2014, 06:21 PM   #3
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
As theducks said, it appears to be a broken epub. Fixing that should fix the problem. If it doesn't, can you post in the thread for the driver. That will get the attention of anyone who might want to look at it. Also, there is an option in the driver to "Silently Ignore Failed Conversions". This should allow the rest of the books to be sent and I think it sends the epub version of failed books.

As to going back to the standard driver, that is up to you. If you want to read books as kepubs, they need to be converted. The extended driver does this, or you can do a conversion using the kepub output plugin and send using the standard driver.
davidfor is offline   Reply With Quote