That the word “Section” does not mean section in the 400 year-old hierarchy of:
Volume=>Book=>Part=>Chapter=>Section=>Paragraph
is astounding, Perhaps colors or names of animals or cities could have been used–except that cities are somewhat hierarchical as they are political subdivisions. Maybe animals names of mountain ranges would have been a better option if meaning is thrown out with the bathwater.
Maybe pissing off the fellow user who’s most likely to get you through this mess isn’t the smartest move at this point.
Yikes! Not trying to piss anyone off. I can’t do Zoom calls. I honestly didn’t know that a “section” is not a Section. His help has been great and I’m still working through it. I just wonder why Mr. Keith didn’t make this clearer.
I know this can be a bit overwhelming at first. Scrivener covers a lot of different use cases, e.g. what you think of as the section is a “scene” for others. In reality it’s (one kind of) a section.
“Section” in this context is a generic term indicating a sub-division of your manuscript. Some manuscripts have five or more outline levels, some have only one, hence the need for a generic term. If your manuscript has more than one outline level, you can assign different Section Types (Part, Chapter, Scene, etc.), and correspondingly different Section Layouts as needed.
Keith is not responsible for the ambiguities of the English language. However, there’s an extremely detailed discussion in the manual, which you are welcome to read. The key, uh, sections would be:
7.6, about assigning Section Types;
23.3 about assigning Section Layouts; and
24.2 about changing the specifications for a Section Layout.
If you have used Markdown to indicate headings, you should probably also review Section 24.14, which explains how the Compile command handles Markdown.
Edit: Oh, and those hash marks are coming from the Separators pane in the Compile Format Editor. See Section 24.4.
well said. !!!
Meaning is not thrown out with the bathwater, just the opposite.
Here’s a video. Turn it up if necessary.
Really? In what other program can I have a source project where each document/snippet has its own combination of font and other formatting, but create output files that are normalized to a single font/formatting combo?
You could do it with ctrl (cmd) +a, then make the font change.
I realize that bringing in different formats is not optimal. In my defense I was bringing over quotes from laws, and you have to examine the text of laws to make sure that changing the formatting doesn’t alter the meaning. This is especially the case when dealing with nested lists. On more than one occasion, I have even discovered errors in the printed law.
So what like to do is come up with a draft, edit the draft in Scrivener and then Compile. This is the first time I’m using Scrivener to Compile to an end product; in the past I’ve usually Compiled to LaTeX for pdf creation or Markdown or Vellum for epubs. That choice is because LaTeX doesn’t handle graphics easily (yes, I know about tikz but will it automatically scale images?) whereas Scrivener handles them out of the box. Similarly, Vellum can’t handle tables at all (they recommend you take a screenshot of a table and include it in the text as a graphic, so you’re back to graphics problems). Over the years Scrivener has done a great job when the goal was a first draft, but obviously I need assistance when using the program to create a final product.
You should be able to specify the image size as part of the LaTeX \includegraphics command.
Normally I don’t suggest LaTeX as an “easier” option, but if you’re used to it already figuring out how to make it do images is probably going to be easier than completely changing how you think about the Compile format.
The problem is that LaTeX does not automatically scale a graphic as Scrivener does. You have to fuss around with it each time you change the paper size. I’m looking for a write once, publish many solution or as close as I can get to it. Here’s what I’m talking about, with a graphic added to an existing LaTeX document:
But here’s a control “[width=\textwidth]” to limit the size. This should work for different paper sizes but I haven’t tested it.
All he had said at that point was
I’ve followed your guidance and put together a new template, The body text appears OK, but footnotes are a problem: if you use this control:
The body text, size and typeface are fixed, but you can’t change the size of the footnotes. I’m trying to figure out if this changes automatically and opened a separate thread on the footnote issue: Where is the Compile Footnote Formatting Control - #14 by pseingalt
With the previous control checked, you can still change sizes (24 pt is obviously an unwanted size) but not typeface.
I’ve run Compile 5 or 6 times. I think the only way to fix the font sizes, typeface and uniformity issues is to treat Scrivener like a word processor and fix the text in the editor. I’m running 3.2.3, so it’s probably not a deprecated version issue.
I don’t see where you can place different headers on versos vs. recto pages. The verso page should have the name of the project (book title), the recto page should have the section title, but I don’t see a control that will make this work properly.
These setting yield:
Where the verso page has no header at all and the facing recto page has two headers. I’ll go out on a limb and say that where “facing pages” is checked there should be two lines for radio boxes, one for the verso page, another for the recto page, but what do I know.
You need to click on Options (in the same screenshot) and enable different headers for verso and recto.
When Use Facing Pages is off, Main Pages supplies the headers/footers for every page. When you enable Use Facing Pages, the settings under the newly listed Facing Pages item handles the headings on verso pages. So, you want to put one of your headers in the Main Pages area and the other in the Facing Pages area.
Thank you. The existing menu interface is not intuitive.
It’s not a menu, it’s a dialog (with various panes and tabs), but never mind. This is why searching in the Help box doesn’t find any of this – because the Help box searches menus only, not Preferences, Compile dialogs, or any other dialogs. Sad but true, maybe because it’s an Apple feature, not a Scrivener feature.
If a big fat Options tab sits right next to the Header and Footer Text tab, it’s intuitive (in my opinion) to look at it and see what it does.
I didn’t know that “Help” only searches menus. That’s a valuable insight, thank you.
It’s too bad the Scrivener manual doesn’t have an index.
Creating a useful index is a highly specialized task. I don’t know if it’s practical for something like the Scrivener manual.
