Quote:
Originally Posted by Trollheart
It's okay; it finally came to me, and thanks for the reply. What I need to do is put all the documents in one, then use H1 headers to mark each separate story, like the chapters in a book. The system then recognises each H1 header and assigns it, or it can be assigned, a place on the TOC which enables me to go directly to that story.
Thanks again. I knew it was possible, just could not remember how I did it.
TH
|
This is something I've had to do a lot of over the years. The main stumbling block is often internal filenames -- especially cover.jpg/.jpeg/.svg, stylesheet.css, and page_styles.css. If any/all of them are under that name in more than one component of the anthology, some readers and some conversions can muck up the references, so that story
x's stylesheets end up controlling the entire anthology. This can be problematic for automatically-named styles (e.g., calibre_7) that aren't necessarily even referring to the same type of element.
If you're not going to go to the effort of preestablishing all of the file and style names before adding anything to the anthology (admittedly an annoyance), at least change the filenames in the epub you're about to add in before you actually add it in so that they're unique.