View Single Post
Old 06-18-2015, 05:30 PM   #88
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,160
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by leftright View Post
I also have a large collection of books which stalled at 80% during Kobo Processing of the entire collection.

I discovered via Sigil and Calibre that several books had major errors in their TOC and structural errors in the code, I first cleaned them in Sigil, then fixed the TOC in Calibre and bug checked in calibre.

With a large unverified collection I would batch load the books.
Whenever I do a clean install of my entire collection to my Glo I batch load then, 200 per batch, let the Glo process 200 at a time and it works fine.
With a bit of batch file magic, you can use epubcheck and/or Flightcrew (the same checker currently used in Sigil) to check a large batch of epubs with any errors being recorded in a log file. I've done this on a couple of occasions and it does make locating the troublemakers much easier.

Once the ebooks are cleaned up and transferred sucessfully to a Kobo, I don't worry about smaller batches for those ebooks.
DNSB is offline   Reply With Quote