How to Compile in v.3

[pseingalt]

I am still struggling with Scrivener 3's compile function. Could someone post a link to a tutorial? Thanks. The attached image has less options than Scrivener 2. Where are they all hiding?

[JimRac]

Have you looked at Keith's update guide? I don't have v3, but my understanding is it speaks to differences between v2 & v3 compile.

https://www.literatureandlatte.com/forum/viewtopic.php?f=2&t=41270

Also, there are a number of video tutorials on compile.

https://www.literatureandlatte.com/learn-and-support/video-tutorials?os=macOS


HTH,
Jim

[KB]

Also see the section on Compile in the updated Scrivener 3 Tutorial. If you create your own Compile format (or duplicate and edit a built-in one) you will see all of the options hat Scrivener 2 had (and more). But you first need to understand how section layouts and section types work. They provide much more flexibility and possibilities, but they are new to 3.0, so you need to understand those (in the same way as you had to learn how to work with Compile levels in 2.0) to start making the most of Compile. The transition guide that JimRac posted goes into great detail for those who are very familiar with Scrivener 2's Compile.

[pseingalt]

You’ll see that “All folders” is set to “Part Heading”. This means that all folders in the project will use the “Part Heading” Section Type by default (that is, any folder whose Section Type is set to “Structure-Based”). This is why the folders we looked at before had their Section Type shown as “Part Heading” in italics.
6. Click the “+” button at the bottom with the two lines next to it. This button adds a structural level. “All folders” will change to “Root folders” and a new folder level will be added: “Level 1 folders and deeper”. Again check to see which documents are highlighted yellow in the binder.
7. The “Draft” and “Research” folders are root folders (they are contained in the root of the binder) and “First Parting” and “Second Parting” are Level 1 folders (one level deep inside root folders). Our chapter folders (“Mudride” etc) are at level two, however, so click on the “+” button again to add a “Level 2 folders and deeper” row.

Completely lost. I learned where "Quick Font Override" has moved to, at least. So, compile will not pick up styles--which are structure based--without going through the additional steps of creating folders and--I'm not sure how to change this globally-- inspector=>metadata settings from structured to?
So structure based is not really structure based? Then what is it?
In other words, if I use styles and set up a document so that (to take a book example):

half title
title
dedication
copyright
Part
chapter
appendix
index

...that Compile will not recognize these styles as structure-based?

[KB]

Huh? Compile does pick up styles. I'm not really sure what you mean. Styles have nothing to do with Section Types or Layouts (except that Section Layouts can *use* styles). Your quote is purely about section layouts. Make sure you check out the tutorial before the transition guide.

[pseingalt]

Use styles for:

Headings (if you are not inserting headings using Compile, that is).

How would you insert lower-level headings in the middle of a document using compile? That is,

{unstyled text}
Here is a heading. [if you don't use styles, this is just plain utf-8 text]
{here is more text}

How can compile identify headings within a block of text where they are not so marked?

[pseingalt]

Huh? Compile does pick up styles. I'm not really sure what you mean. Styles have nothing to do with Section Types or Layouts (except that Section Layouts can *use* styles). Your quote is purely about section layouts. Make sure you check out the tutorial before the transition guide.

"Huh?" is my reaction as well.

Styles have nothing to do with Section Types

So if I use Styles to mark a chapter heading, I am not defining a section type. Instead, I am...
got me.

[pseingalt]

Structure-based: Tells Scrivener that the current document should use the default section type based on its indentation in the binder (we’ll look at this in a moment).

So, "structure-based" has nothing to do with the structure of the document, but instead deals solely with the structure of the binder.

So structure-based really means "outline-based" except that a flat file has no outline.
I need a translator...

[KB]

Why on earth do you need a translator? What is unclear about the binder having a structure? That is *always* how we've talked about the binder. If we called it "outline-based", users would think we were taking about the outliner. And exactly how does your document have a "structure"? The whole point of Scrivener is that you structure it in the binder...

[brookter]

You need to read the Tutorial

Seriously, an hour skim reading that and paying attention to the ‘What’s new section’ and it will become very clear why things are set out the way they are, and why they’re called what they are. It will save you a lot of time.

[pseingalt]

Document structure, generally: https://en.wikipedia.org/wiki/WYSIWYM

In LaTeX (for example):

Code: Select all

\subsection{This is a subsection.}
While this is just UTF-8 text.
\subsubsection{And here is a sub-subsection.}

In Markdown/html:

Code: Select all

## Section
Here is some UTF-8 text.
### Here is a subsection.

These examples refer to elements of the structure of a particular document. I do not see that there is a way of identifying such structrural elements in a Scrivener document unless each element is its own Scrivener document and is placed in an appropriate hierarchical place in the binder. If you use a small number of long Scrivener documents in a project, it is not possible to mark these structural elements, contained in the document though unmarked, during the Compile process.

But as always, I could be wrong as Compile is still a work in progress for me.

[pseingalt]

ps:

I was under the impression that if you defined a selection of UTF-8 text as a chapter, or section or subsection style in Scrivener (as the use of styles is now possible) that such definition would be picked up during Compile. But that is not the case.