New paragraph - default to a different font

So, I have a body style for my text. I have also made the style the default for my documents.

Scrivener insists on changing the style on the next paragraph - every time.

Do you have “Next Style” set to “None” in the style properties? If so, change it to the style you want. Section 17 of the user manual talks about it.

Can I say, as a long-time Scrivener-user, that setting yourself up with a “Body” style potentially makes your life much more complicated when it comes to compiling. If you are using different section types, then you need to check that each section type will use your “Body” style for the text. The point about “No Style” is that when you compile, it is exported as “Body” or “Normal”.

The “philosophy” behind Scrivener is that only paragraphs that differ from the body text—headings, block quotes, etc.—should be assigned a style.This means you can write the text using any font, size, colour combination you like and the compile process exports it in standard format to print, PDF, DOCX, RTF, ePUB etc. without the need to spend time modifying compile formats.

Just saying; it’s your call how you want to work.



Thanks, xiamenese. I have come to the same realization that you outline above.

In my initial testing of how S3’s styles worked with Word, I focused on Heading styles and also on a “Normal” style. What I think I came to realize is that for most purposes in most cases, “No Style” functions in S3 as the equivalent of “Normal.”

I created a “Normal” para+char style, and tried to ensure it was used consistently throughout the project, which proved difficult it not impossible. But it turned out that deleting this style altogether had no apparent impact at all project formatting. And as you point out, “No Style” gets output as (or gets interpreted as) “Normal” when, for example, a complied docx file a synced rtf is opened in Word. And, depending on how you go about doing it, there is now some functional compatibility between S3 styles and Word that was not there in S1.

That said, there are definitely serious problems with how styles in S3 behave within S3 itself, fully independent of their compatibility with Word, which make we wary of depending on them as more than local formatting. See this thread, for example. (In the screenshots in that thread, I was still using a “Normal” style, but they issue described still happens when regular “No Style” is used.).