Is there are way to split at selection but not have it show in the TOC on epubs?
You can “split at selection” whenever you like without necessarily forcing a new ToC entry, because the compile process allows you to control the documents/folders that will appear in the table of contents. To do this, you will need to use the expanded compile options, so after you have selected File > Compile, click on the blue arrow next to the “Format As” field to display these.
When you compile for ePub format, a ToC entry is created for each document/folder which is marked as being a new section (i.e. has a page break before it). You can therefore use the “Pg Break Before” column in the Contents pane of the Compile options to mark those documents/folders which you want to list in the table of contents. I have just tried this out, specifying “Pg Break Before” for random documents/folders in the tutorial project, then compiling to ePub and opening the resultant file in Calibre, and it seems to work fine. For clarity, if you are manually specifying sections like this, it might be best to go to the Separators pane and make sure that no page breaks are going to be created automatically (based on the relationships between consecutive documents/folders).
I hope this helps.
Thanks. I think I get it. Unfortunately, I can’t make a ebook to test it right now (https://forum.literatureandlatte.com/t/error-generating-the-epub-book/17601/1).
I unchecked the page break before the files and they don’t show up in the table of contents. Unfortunately, they don’t begin on a new page either.
It is a recipe book and what I would like to do is something like…
For example in the In the ToC
but the book
Salsa Deviled Eggs
Holiday Deviled Eggs (etc)
The individual recipes look better when they start at the top of the page and I don’t end up with dangling sentences. But I don’t want them in the ToC.
Can this be done?
Not currently. The problem is that the section break in an e-book is more than just a cosmetic function (and that extends outside of Scrivener; it’s just how they work; they actually break things up into new files, internally). So what one needs to do is craft their own ToC that doesn’t follow the internal structure of the book as designed by the appearance of section breaks, which at least provides for a visible ToC that follows your goal, but might not necessarily be what is always shown if the e-book reader uses a special ToC function that looks at section breaks. For example, on the Kindle, section breaks become visible “tick marks” in the progress bar at the bottom of the reader, no matter what your visual ToC looks like. It uses top-level NCX entries for that, so nesting NCX entries can obscure sub-section breaks.
At any rate, we’re talking about stuff there is no front-end for in the compiler as yet. Fine tuning the end result of the e-book in an e-book editor is often a necessary step to take, even with a lot of front-end options. I wish more mainstream publishers did that, matter of fact. They publish e-books they would fire people over if they went to print looking the way they do!
That’s what I was thinking you were gonna say, but thought I’d double check.