View Single Post
Old 06-17-2020, 12:20 PM   #3
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
JimmXinu's Avatar
 
Posts: 6,999
Karma: 4604635
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
Quote:
Originally Posted by ottischwenk View Post
Why should this error be in CC?
Standard routines from the operating system are used here.
If so, then the problem lies there, or else in a hardware defect.
I don't know that it is. Which is why I described this as a problem I am having, not a bug. I'm hoping that this is something seen before in the CC community with a ready fix. I will be perfectly happy if it's something I'm doing wrong, but I would like to get it fixed.

I have seen the same epub sent without issue through the other parts of the path (Calibre) and if it was a hardware defect on the phone I would expect to see low level read errors, not just zip file errors.

The fact Calibre can still read these and silently fixes them suggests to me that it may be a differing OS/library thing of some kind. I will be looking at the Calibre code for inspiration, but obviously I can't do that with CC.
JimmXinu is offline   Reply With Quote