Quote:
Originally Posted by DNSB
While I'd agree that Kobo's error checking is about as useful as a screendoor on a submarine, any commercially produced epubs should pass Flightcrew and/or epubcheck without major errors. For non-commercial epubs, I'll allow a bit of leniency though many of them are more standards compliant than many of the commercial epubs. I have not found an epub that validated with no major errors and caused my Kobo reader to hang during processing.
|
I agree the major choking is probably due to bad formatting. But if you can't parse it within a reasonable time frame, how about failing gracefully? Give me a message saying "book xyz's fomatting isn't up to our high quality standards. Please fix or do sumpm." And then move on to processing the next book instead of just sitting there, blocking the device and burning CPU cycles.
As is, we get the worst of both options. The device is unusable,
and the software won't even tell us which of the books it finds offensive.
The other aspect is a question of priorities. The normal book-reading with turning a page every other minute can't be all that CPU-intensive. Seems like a no-brainer to let the user do that while you do whatever processing you think you have to do in the background? Then give them a message about the results of your processing?