View Single Post
Old 10-01-2018, 10:23 AM   #570
stumped
Wizard
stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.
 
Posts: 3,305
Karma: 10259306
Join Date: May 2016
Device: kobo forma, Kobo Libra, Huawei media Tab, fire HD10, PW3 HDX8.9,
ps that 10% failure rate for bookari seems high. my issue with Bookari was that app updates kept introducing bugs, but I don't recall books NOT working. It was essential to keep old copies via app backup/restore utilities, in case google store pushed out a disasterous overnight update
the app would often crash on the initial licences check/ T&C screen if you rolled back a version, unless you deleted all previous traces of the buggy newer version.
& the page count by chapter adding up to t total pages per book would go haywire if there was not a 1:1 match between chapters and html files. having mutilple chapters in a single file or having a chapter split over muitiple html did upset it, so I would manually fix that with calibre or sigil before reading
Bookari used to have a reasonable support function where you could send them the problem book and ask why?
i would check the affected books in Sigil , using its tools to see if it thinks the epubs are error free, if it says yes, then send copies to bookari as bug reports
stumped is offline   Reply With Quote