Thread: Kobo Forma database problems
View Single Post
Old 11-01-2018, 09:37 AM   #23
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 bongorash View Post
So after much time copying files over in small batches I have now established that the problems have been caused by one 'rogue' book. I have loaded my entire library (some 500+ books) minus the 'rogue' book onto both mine and my friends Forma and everything went smoothly and all books copied fine. (I use calibre to side load them as kepubs). The strange thing is the rogue book loaded fine onto my Aura One so I can only think that the firmware for the Forma is more particular about which books it will load ?

davidfor:
I will pm you with a dropbox link to the offending file as you requested.

Although I have used calibre regularly I am not an expert on all the options available within it - is there any way that calibre can check a book for compatibility before I send it to my device ? This experience has shown me that when an ereader crashes over loading a rogue book it will not load any further books and a factory reset is necessary meaning reloading your full library again, not something I want to do regularly !
I have had a look at the book, and the problem was easy to find. I dropped it on my Clara HD as an epub and it loaded OK. Then I simply renamed as a kepub, and the device rebooted during the import.

Opening it in the calibre editor and running the check there, it shows a lot of CSS errors. But also:

Code:
OEBPS/Content.opf (line: 18)
The meta cover tag points to an item with id="images/pic_1.jpg" which does not exist in the manifest
The line in the OPF was:

Code:
<meta name="cover" content="images/pic_1.jpg"/>
The value of the content attribute should be an id defined in the manifest part of the OPF. This should have just been "pic_1.jpg" as the manifest has the entry:

Code:
<item id="pic_1.jpg" href="images/pic_1.jpg" media-type="image/jpeg"/>
The way I fixed this was to right-click on the cover in the file list and select the option to mark it as a cover. That rewrote the first line above.

I tried the kepub version on my Touch which has firmware version 4.10.11586. The book imported OK there, but didn't have a cover. Look like there was a change in how kepubs are handled that breaks on this error.
davidfor is offline   Reply With Quote