Thread: Calibre issue exporting to Kobo
View Single Post
Old 12-29-2019, 12:28 AM   #11
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by JSWolf View Post
The rule here is not to help someone who is asking for help with illegally downloaded eBooks. And there are triggers that bring up red flags. If I am wrong, I'll say so. But am I wrong? I have never encountered a single commercial eBook that had a bad filename. I've encountered other errors, but never a filename that wasn't valid.
I'm sure that I have. And I just opened a random book. It has internal files that look like "tmp_dfcef919bbc4d91200ea44c8b4530284_RJ5x1i.ch.fi xed.fc.tidied.stylehacked.xfixed_split_000.html". That is 97 characters. If you added in the typical Windows temporary directory, and the name of the book plus an internal directory. Hitting the maximum file path length would be possible. I'm pretty sure that would give the error the OP is seeing. (And yes, I can see that it is probably a Mac being used, o this shouldn't be an issue, but, it is an example of a cause.)

And maybe it wasn't an invalid file name. Maybe it triggered a bug. Or the combination of characters in the file name and temp path triggered something. Or, as I have already stated, it is actually a problem in parsing the contents of the file. The drivers code parses the error and doesn't show the exact source of the error.

And Jon, it could easily have been an error made by the OP. I know that you clean up your books. What if the OP made a change while doing that and this error was triggered? There wasn't anything in the OP's post that suggested piracy to me.
davidfor is offline   Reply With Quote