Quote:
Originally Posted by DNSB
What I've had to do on several occasions is to select all the chapter files and then right-click and merge. Then go back through and split at the chapter markers. A bit of pain but it does give you a much better looking result than mindlessly splitting files at fixed file sizes which seems to be popular with some publishers. So yes, this does give 1 chapter/1 file.
|
Yes, that is what I meant - I also take the opportunity to rename the .html files from the ridiculously long names Gutenberg uses to shorter ones.
The only real problem with doing this is that it can mangle internal hyperlinks used for footnotes etc but a bit of judicious examination and the use of regex S&R will sort that out.
There are two ways to split - either manually or again by examining the files and using regex S&R to "insert" the needed split markers before each chapter (if you are lucky they may be h1 or h2 - if someone has done it based on class then it can be a bit more messy) then tell Sigil to "Split on markers". If you have a book with 117 chapters like one I did this week the second way is definitely best.
The reason I use merge then split it to "heal" any already split chapters before performing the chapter split, you could just split the existing stuff then go through manually and merge any "broken" chapters.
I've found Sigil an excellent tool for simply examining and understanding the structure of EPUBS. I used to stay away from them, preferring .fb2 format files which are monolithic in structure but incredibly easy to edit with any old text editor, but needed to get my head round EPUBs when I bought a Glo.
Your early breaking pages may just be a widows and orphans issue. I usually add :
Code:
body {widows : 0 ; orphans: 0;}
to my css to help with this.
BobC