View Single Post
Old 06-17-2020, 02:21 PM   #5
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,453
Karma: 8012886
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by stumped View Post
But cc does not open the zip( the epub). It simply files it and hands a copy to reader app as needed. So it can't be the cause of the corruption.
Unless something has changed, this is true. CC doesn't ever "process" the epub. It simply copies the network stream to the file. If that reliably didn't work then CC would have far greater problems than you are seeing.

I suspect that something on the calibre side is borking the epub when it is created to be copied. When sending via a device, calibre creates a new copy, applies plugboards and cover changes, embeds new metadata, then hands it to the device driver (the wireless device). Do you use any plugins that could get in the middle of that, such as an epub metadata writer?
chaley is offline   Reply With Quote