Sorry if this is an obvious question. I’m new to Scrivener. Is there any way to modify the Enumerated Outline preset under the Compile Menu so that it also includes the text of each document as well as the title (and the auto-numbering)?
I want to try drafting a contract in Scrivener, and the ultimate formatting is pretty much an enumerated outline, except you need the body text for each outline item as well.
I like the opportunities Scrivener seems to present for moving blocks of text around (i.e., contractual provisions), but If I have to do all of the provision numbering in a different program, I’m not sure that’s going to be an efficient workflow for me.
You have a lot of control over what does and doesn’t get included at Compile time. Go to File > Compile and take a look in the “Formatting” pane (if you don’t see a way to access the Formatting pane, click on the arrow next to the “Format As” button to expand all options:
Under the “Formatting” pane, you will see that you can determine exactly which elements of your documents are included - in the “Enumerated Outline” preset, only titles are included by default:
You can also determine whether or not each level is formatted differently. In the enumerated outline preset, as you can see, each level of folder and text file is formatted slightly differently.
Compare this to the “Original” preset:
Here you can see that all levels are formatted the same (only the topmost level is defined, meaning that lower levels will use the same formatting). You can add new levels to format by clicking on the “add formatting level” button:
For each level, the “Title Settings…” allow you to add auto-numbering before chapter tiles if you want. The “enumerated outline” takes advantage of hierarchical numbering, the tag for which is <$hn> (and which can be inserted via the Edit > Insert > Auto-Number > Hierarchical (1.2.3) menu item):
Basically Scrivener allows you to format and structure your text however you want, so the Compile feature has to be powerful and flexible enough to enable the user to set it up for any possible workflow and binder structure. This means there’s a bit of a learning curve if you want to set up all the formatting in a way that isn’t provided by one of the presets, but you should be able to do what you want by playing with the Formatting pane, “Title Settings” and auto-number in the title prefix.
Hope that helps.
All the best,
Excellent. Not quite sure how I missed it. I’ll experiment more now.
What about run-in headings? Is there any way to do those?
Yes, but not in the compiler, that will always terminate the header with a paragraph break. For inline headings, you can do this without sacrificing flexibility by using the <$title> placeholder tag.
[size=85]Any formatting applied to the placeholder tag will carry over to the compiled copy.[/size]
The magic here is that it uses the binder title of the document it falls within, just like the compiler does with titles turned on, so you can keep using the cards to name your sections without worrying about typed-in headers going out of date. If you want to all-cap the title, use <$TITLE>, instead.
How is numbering handled the <$title> tag? Should I be incorporating a separate numbering tag? Or can you set that as a part of the <$title> tag?
Will <$Title> give you a title where the first letter of each word in the title is capitalized?
Numbering will need be added right in the editor, like “<$hn>: <$title>”, since we are completely bypassing the compiler’s system to get around the newline it adds. You’ll get strange doubling results if you try to add the number to the compiler prefix. There is no title case variant for these tokens. It is presumed you will have typed in the name of the section the way it should be read. The uppercase variant is there for cases where you need that—so you don’t have to mess up the proper case of it. Of course in my example above I didn’t type in the scene name very nicely.
What about indents for various numbering levels? Do they track the levels of the items in the binder. Or do I need to set that up at compile time or in the editor.
For example, how do I accomplish this:
1.1 Entire Agreement. This is the entire agreement of the parties…
1.2 Choice of Law. This agreement is governed by the laws of the state of …
Term. The term of this agreement is 5 years.
You would set up the indents in the Formatting table - my earlier post shows how to add different levels to the formatting list. The whole point of being able to add different levels to the formatting table is so that you can add different formatting (such as indents) to different levels of document in the binder.
So to get the formatting you want, you would set up “Level 1” and a “Level 2+” formatting rows, with Level 2+ indented. It also depends on the type of documents they are - folders or text files - as the formatting rows also allow different types to be formatted differently. So just look at the structure in your binder and set up formatting rows in the “Formatting” pane of the compile sheet to match.
All the best,
Would you set indents in the formatting table even if you are using run-in headers in the fashion described by AmberV in her post above?
I feel like perhaps I’m missing a wrinkle here.
Yes, because if you want the formatting set by level then that is what you do - the run-in headers make no difference and will still work, so there shouldn’t be a wrinkle. Often it’s just a good idea to experiment. Here’s how I achieved what you are after:
Just a hint to expand on the method Keith described: if you start with the Enumerated Outline preset and turn on Synopses for all types and levels (Option-click on any of the Synopsis column checkboxes), you’ll see those have already had their first-line and block-indent markers moved over to where they should be. For each level in the Folder set, simply put your cursor in the Synopsis sample area, press Ctrl-Cmd-C to copy the ruler styles from it, then click in the sample text block Ctrl-Cmd-V to paste. Finally, turn off all the Synopses and Titles (as well as the prefixes). Once you have the Folder set arranged, use the selector table to select each Folder Level # and Cmd-C / Cmd-V to copy and paste the settings to the two other sets.
Thinking about this some more, I’ve added a run-in header option for 2.1: