View Single Post
Old 06-17-2020, 02:46 PM   #6
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,
Quote:
Originally Posted by chaley View Post
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?

Good hypothesis, if it is calibre side, then leaving out cc and using a device browser to fetch from calibre should show the same corruption
I can't type the URL syntax for that test from memory,. But it is easily found.
stumped is offline   Reply With Quote