Quote:
Originally Posted by mastroalex
I'll give Sigil a try. I'm new to ebooks, as I've been given a PRS-650 for Christmas. Maybe I should use rtf as standard instead of epub.
|
epub is probably a better standard if your device is a prs-650. It doesn't read rtf, so you would need to convert from rtf to epub anyway and run into the same problem.
There are a lot of ways to get the book to split based on the actual chapters instead of arbitrarily. If the source format is well defined this should happen automatically with no intervention from you. If it's not well defined then you need to go through a bit of effort.
I'm not sure what you mean by the 'optimize my epubs' feature - this isn't one I've come across.
If your original book source is epub and it's already split at random places in the book it means the original publisher of that version did a quick conversion and didn't bother with editing/inserting appropriate chapter breaks - instead they let the conversion utility split at the 260 or 300 bytes which is what's supported by a lot of the readers. There isn't much you can do for a book like that except fix it by hand in Sigil as already mentioned.
If the book is some other format then you have more options. The 'preprocess html' option under structure detection will look for common headings and mark them so that the book is later split at appropriate points. Alternatively you can do a bit of investigation into the actual html and figure out what an appropriate chapter detection xpath is - it's in the same structure detection dialog as the preprocess option.
Lastly page breaks are inserted by default at ever <h1> and <h2> header in the document. You can control/disable this by editing/deleting the 'insert page breaks before' xpath, which is also under structure detection.