Quote:
Originally Posted by joebob2a
I tried Merging them within Sigil and my e-reader choked saying the file was corrupt.
|
You need a more specific error report
First try the built-in "Well formed check" on the Tools menu, or F7.
It will open a window listing errors and if you click on the error it will open the offending file at the line it found the error.
Often this is enough to find an error severe enough to choke a reader, though the errors can be cryptic. Try Googling the error message if you don't understand it and see some examples.
You should also use epubcheck for a comprehensive and sometimes nitpicking examination.
You can do it by submitting the epub to
http://validator.idpf.org/
But better to install
the plugin so you can do it inside Sigil, then its error report is linked to the code as the F7 check.
Otherwise, one thing that might be causing problems is if styles are defined in the header of each HTML file, rather than a separate CSS file.
That can cause conflict when they are merged if each file uses the same style names but with different definitions, as often happens with automatic conversions.
I found that Calibre can fix this: do an epub to epub conversion and it will pull all the locally defined styles into one CSS file with unique names.
The CSS will be pretty silly, with many similar or identical styles with different names, but it will work and you can make them more orderly in Sigil.