Articles in this series:
- Part 1: Prepping Your Brain (Changing Your Scrivener Habits)
- Part 2: Prepping Your Existing Scrivener Project
- Part 3: Setting Up Sync
- →Part 3.5: This article.←
- Part 4: Dealing With Scrivener Metadata
- Part 5: Aeon Timeline—Scrivener—Ulysses Workflow
UPDATE 2020-10-28: “Convert Multimarkdown to Rich Text” Bug alert:
In Mac Scrivener 3.1.5 and earlier, conversion to rich text can fail if there is no paragraph break at the end of a text file. If you have files in which some or all MMD is not being converted in compile though other files convert normally, see if adding a paragraph break at the end of the file fixes it.
Literature and Latte have acknowledged this bug, and it will be fixed in version 3.1.6 and subsequent versions.
Addendum (Part 3.5): Finding Compile
It struck me that in all this time, I haven’t discussed actually compiling with the “Convert Multimarkdown to Rich Text” option on—where to find it, what to do with it, etc. Okay, then, when you first use File→Compile in Scrivener, here’s how you turn on that option:
- Choose any “Compile for:” target except a target that says “Multimarkdown,” Those are part of a different workflow that compiles to an intermediate format. You’re going to compile directly to your intended final output format.
- In the right-hand sidebar, click on the gear icon to bring up the Compile Options panel.
- Turn the “Convert Multimarkdown to Rich Text in Notes and Text” option ON.
- Choose a compile format from the left hand column.
That’s it! Scrivener will now take your Multimarkdown and convert it to rich text before compiling to your chosen target.
- Remove Annotations: Turn this on to make sure your inline annotation “tags” don’t show up in your compiled output.
- “Convert Markdown to rich text in titles and synopses”: This is a bit misleading. It only really converts *italics* and **bold.** But if you use these in your titles (and in your synopses if you’re including them in your compile) you can convert them on compile with this.
I’m not going to cover more detail of how to compile. You can find compile help in Scrivener’s Interactive Tutorial (Help→Interactive Tutorial…) and a complete reference in the Scrivener Manual (Chapter 23, “Compiling the Draft” and Chapter 24 “The Compile Format Designer”). But I will say that if you’re new to Scrivener’s compiler, give yourself plenty of time to learn it! Compile is almost a whole second application. On the Scrivener forums, I often see posts from desperate writers who left learning the compiler until two hours before a hard deadline. Such posts usually end in tears.
Don’t be that writer. Take time to learn to compile.