Yes. That is expected. As I explained roughly in my earlier post (the one with the screenshots), you’ll have to set things so that the documents for which you don’t want a title go through a section-layout with the title disabled.
Right now, both titled and untitled (wished so) documents go through the same section-layout at compile.
I believe I’ve finally sorted it out–two days and many hours later. The project now seems to be compiling how I would like it to. I discovered that the key problem was working with old files in v3 that were taken from v1. Some things simply get lost in the translation. So I tried redoing the project files natively in v3 and then working from that, and that solved various issues (not just the titling issue).
Thanks again for your help and patience!
EDIT: Maybe I spoke too soon, lol. There are some remaining oddities like hashtags appearing in strange places. I may try retyping those parts from scratch and see what happens.
Check for empty lines that aren’t meant to be scene breaks, or if there aren’t meant to be any scene breaks within individual chunks of text, you could use the Edit ▸ Text Tidying ▸ Remove Empty Lines Between Paragraphs menu command in these areas where you spot them, without having to hunt things down. You can search for such breaks by pressing Ctrl+Enter in the Find field twice.
Default settings, as you may have gathered from the wording above, is to treat them as breaks, and for the manuscript formats, make them visible so that they can be more easily spotted in double-spaced text.
If, on the contrary, those blank lines are intended, you could insert a nonbreaking-space on them, so that they are not empty. (They will still look as empty afterwards, but without the # after compile.)
You could also remove it (#) from within your compile format, but if you plan on ever producing an ebook, you must use a nonbreaking-space nontheless, as html doesn’t recognize empty lines and will remove them.
I use — ⮛ ⮛ ⮛ — which is my code (very visual) for an empty line during the writing process, which my compile format replaces with a nonbreaking-space. (For quick inserting – because that’s not a common character – I’ve set a replacement in the options. === → — ⮛ ⮛ ⮛ —)
You can find your empty lines in your project by searching for return-return.
If it’s on purpose, that’s a way of doing it, though I would say that very often, if there is supposed to be an intentional vertical space for some cosmetic purpose, the optimal tool to use is paragraph padding on the style that triggers it. Often in the manuscript they will want a style for that kind of formatting hint anyway, probably with some garish look to help it stand out in editing. The style is so that the designer can more easily do their job with it.
(This approach also works with ebooks, if that is a thing.)
Hmm, nothing happens when I hit CTRL+ENTER twice in the Find box. …
What’s a “non-breaking space” and how do I enter it? (In the instances I’m looking at there’s a quote that begins before the chapter text so I DO want a space there, but not a hashtag. I suspect the hashtag is being generated as part of the style I’m applying to the quote so that the quote will be properly set off from the text but single-spaced instead of double-spaced.)
A nonbreak-space is just like a regular space, except that it prevents the words that are on each side from ending up on different lines.
The # comes from the compile format.
It has nothing to do with a style.
EDIT: Never mind, I see it now.
OK. Isn’t there a “default” compile format that has no style (e.g. Times New Roman, etc.) associated with it? Because I’ve seen another post from 2021 (evidently an older version of Scrivener) that says there is but when I check my compiler options there is nothing like a “default” that will let me just compile the entire thing as “as is.”
Either that, or don’t assign any section-type to any section-layout (as per my above screenshot), so that this orange text/square appears at the top of the middle section :
(It appears the first time. I’m not sure you can “recall” it once you’ve assigned layouts. In which case, do as per my first screenshot.)


