View Single Post
Old 02-09-2021, 07:09 PM   #2472
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 Strether View Post
Just so you know that this wasn't an isolated problem, I had my fourth book with this problem this morning. Books don't seem to have much in common, otherwise. Different publishers. Converting the books to epub and thence to kepub solves the problem and then they load normally. I don't know how to get any of these books to you, unfortunately.
Just to be clear, the driver expects a valid book. If the book has errors in it, the driver will have problems and reject the book.

The conversion to epub works as it will (almost always) produce a valid book. And the conversion to kepub using the Kepub Output plugin worked as it is largely a wrapper around the epub conversion. It basically does a conversion to epub and then does the kepub work.

Not supporting errors in books was a deliberate decision when the driver was written. The driver does have an option to allow the books to be sent as epubs if there are any errors in the kepubification process. Whether the epub will work on the device will depend on the error in the book.
davidfor is offline   Reply With Quote