Quote:
Originally Posted by Doitsu
@JustinThought: To exclude problems with the external binary, change the following following two lines in the FlightCrew plugin.py file:
From:
/snip!/
Implement these changes on the machine where FlightCrew doesn't work and post your results.
AFAIK, it's not possible to create valid epub2 books with embedded multimedia files. (Here's a valid epub3 book with audio files in them.)
|
Sorry, you guys are being so helpful, and I had lost track of this thread.
So I implemented the changes you suggested, ran FlightCrew against my sample file, as well as a different file which, as far as I know, has no problems, on the problematic machine, and here's what came back on both files:
Status: failed
Running FlightCrew ... please wait
res_out: b'' res_err: b'' retcode: 3221225781
I hope that means something to you.
In the meantime, while I was ignoring you guys' helpful advice, I had taken matters into my own hands, just as an experiment. What i did was to un-install Sigil and the associated Microsoft C++ runtime; then I went in and changed the name of the Sigil preferences folder (I didn't want to lose my saved searches or dictionary); deleted every other reference to Sigil that I could possibly find on my machine, and then re-installed the entire thing. Pulled up a valid Epub that I knew had some unused graphics in it, ran Flight Crew--and it came back immediately with "No Problems Found."
I was laughing hysterically because it felt so good when I quit pounding my head on the keyboard. (Note to self: buy a new keyboard. Gonna need that "R" key someday.)
Really, this isn't that great of an issue. The
only problems that FlightCrew ever found that EpubCheck didn't
was the unused media files. I can
easily just use the function Tools/Delete Unused Media Files instead.
And yes, I am aware that putting MP3 and MP4 files into an Epub2 file invalidates that file. Those files are my quick'n'dirty files that I use in my classes, and won't ever be published. Limited use, and only by myself.
As I've said before, but can't say enough, I really
do appreciate all the skull-sweat you are putting into this issue.