Thanks a lot for the detailed reply.
You are correct, a lot of the friction comes from the fact that I plan to use Scrivener to generate the final interior PDF, not just the proof.
I couldn’t have done this with my last book (470 pages, lots of infographs etc), so I exported to .rtf and did the interior design in InDesign, so none of this was really an issue.
But my next book is only 200 page, no infographs, and Scrivener does a VERY good job as handling 99% of what I need it to do to be able to create my interior directly.
This is very useful because it allows to have just one master file (the scrivener project) for ebooks and print, have Scrivener to generate the PDF interiors, and upload them to KDP directly.
I do update/correct my books often and I’m really trying to streamline the workflow, especially for print (ebook is super simple and very efficient, as only Scrivener is involved).
I don’t need a fancy formatting of the TOC, and I don’t mind bolding manually a few chapters headings in the TOC whenever I update it, which isn’t that often.
However, I can’t output these trailing dots, they don’t look professional enough. Maybe if they were underscores (a continuous line) it would work.
So if Keith would kindly consider adding an option when pasting the TOC, so that we could select trailing dots, trailing underscores or nothing, that would be fantastic.
The only showstopper I have apart from this is that when you select a headed section in compile, you can only select the font style for the main header and the text. If there are header2 or header3 styles applied in the text, there is no way to specify their style in the compile section, and the style selected in the text editor isn’t used either.
For example, my main header in the section is centered, but I need the header2 to be left justified, so they are formatted like this in the text editor, but when I compile a random style is applied to header 2 (different font and size) and they appear centered, not in the font I want.
I guess an option would be to select “as is” in the compile options for this section, but that defeats the flexibility of the new compile section styles, which I really like.
I understand what you are suggesting re formatting an exported RTF file, but that’s exactly what I want to avoid .
I don’t think you should assume that Scrivener should only be used to generate proofs, even for print editions. Given that you can select the correct paper size (6" x 9" in my case), that you have a wide variety of formatting and design options, having a single master file (the Scrivener project) for both print and ebook is a very appealing prospect.
I wasted a lot of time with my last book having to maintain two master files: the Scrivener project for ebooks and my exported word file for print editions, and then I had to use my designer to make all the corrections from a word file showing the differences into InDesign. Apart from the cost, it was a logistical nightmare, it was slow and error prone. I decided that I’d do everything I could to avoid that in the future.
So hopefully we’ll get there, given that there are only a few minor things that would prevent this at the moment.
I think it would be a real USP for Scrivener if you could pull this off. I’m sure I’m not the only one who wishes they could have a single masterfile for all their editions and to be able to generate with Scrivener the final PDFs for both ebook and print interiors. The workflow is so efficient with ebooks that I just want the same with print books .