The body text of this paragraph(2) has different formatting than the section number (1).
Why aren’t they separated out then?
They are, as we can see in the screenshot.
I dunno, #2 looks different than #1, but there is no way to control one without controlling the other.
In LaTeX 1 woud be:
\section{One} %%% with section formatting
While 2 would be standard body text. I don’t see a way here to change #1 and not change 2, or vice-versa.
Click in the one you want to change. Then change it. (After opening the format.)
I’ll give that a try.
Reading the (extensive) documentation on the Compile command might save you a great deal of time and frustration. Every question you’ve asked so far is answered there.
As @drmajorbob said, to change the section numbering, the text, or both, edit the Section Layout.
Also, note that this particular Layout gives you the Synopsis, not the body text.
1 Like
A fair criticism. Though I have looked, and in some cases what I looked for was buried or used uncommon terms.
It seems to me nevertheless that there is a conflict between identified (or sought to be identified) structural elements of a text and Compile options that fail to identify them. You can write in, say, Courier, identify a block quote in the editor–“As Is” isn’t an option because you need Compile to convert text as to other elements–and Scrivener will ignore, or perhaps it isn’t told what to do, with the identified text labeled as a block quote.
Here is the preview mentioned in the manual that I was looking for. The feature doesn’t do what I wanted it to do (a post compile print preview) but I am sure that others appreciate its existing functionality.
If you want to see what the compile will look like, you can Compile it in less than a minute.
What elements do you mean? You can compile as-is and still add a title prefix and suffix. You can format all three separately. The Prefix can be the chapter number, the suffix the title. Both can contain any text and any placeholders.
My workflows make it very simple.
A completely different result from the same contents:
Even the video shows both Prefix and Suffix, at time = 4:10, with chapter number in the Prefix and title in the Suffix:
Here I was referring to block quotes:
But I just added a table and the table fonts on compiling do not have a separate format: Compile treats them as plain text. So the current rabbit hole is trying to get Compile to format textual elements like block quotes and tables (and lists) in a fashion other than merely treating them as 11/13 text.
According to your screenshot, Block Quote is a style. Compile compiles styles as determined by the style, whether you compile as-is or not. If you changed the margins and other things in one or more paragraphs with that style, those changes have no effect unless you redefine the style after making the change. That is, change your margins, etc., then right-click on the style name in the styles panel (cntl-S) and redefine the style.
Likewise, if you want to override most text (hence not compiling as-is) but you want list formatting, etc. to carry through to compile, you may have to give them styles.
I’ll give it a try! There is no built-in “Tables” element in styles, so I should add that element as well?
If you added tab stops, changed the margins, changed the font, etc., you’ll probably need a style.
So a Style overrides the “override” settings? Wow.
Yes, and it’s sometimes necessary. You can still override a style in Compile, though, by adding it in the Styles pane (of Compile, not the Editor styles panel) and modifying the style there.
This is a key difference between No style and a style, by the way.
Somewhere I read it wasn’t a good practice to use Styles since it restricts Compile, but I never would have concluded that they override the override setting.
I’m getting closer thanks to you and other posters. Thanks again.
It’s not a good practice to use a “normal” or “body” style like you would in Word or other WYSIWYG applications, in part because you then need to ensure you have the corresponding compile style set up as well in order to override the settings during compile.
1 Like
A Style acts as a Preserve Formatting command. That is, the formatting will pass straight through the Compile command unchanged unless you explicitly change it.
Whether that’s desirable or not depends on your application. For body text, usually it’s just additional complexity that you don’t need. But applying Styles to “special” text, such as headers, block quotes, and so on, is exactly the intended application.
2 Likes
The style override isn’t working. Here I’ve defined a block quote with narrower margins than the body text and a smaller font:
And (unfortunately) here’s the Compile result. The defined style did not override the text settings.
Here are the Compile settings:
And digging deeper, though this shouldn’t matter because the style overrides the text settings, right?
Except that it doesn’t. Here’s the result:
No change whatsoever.
Suggestions? At this point I’ve blown a deadline and am thinking of biting the bullet and exporting to LaTeX (where I can see what’s going on) or Vellum, where the defaults are good enough for government work and a block quote is a block quote.
I very much appreciate everyone’s help. It’s frustrating to have to repastinate an issue I thought was solved: styles override even overridden text. But they don’t.