Yes. I did that. But how could I know that specifically defining a style in the Editor would not be carried over to the Compile process? Why would anyone reach that conclusion after spending time to define the style and apply it to text in the editor? Shouldn’t there be a pop-up or some kind of warning saying, “if you want to use a defined style during Compile, you must also define it there.”
Either a defined style is an override or it isn’t. This is supposed to be binary.
I’m happy to look at the manual, but at this stage, it is its own set of problems, e.g., the “Scrivener Preview Feature”, mentioned but hidden. Yes, you might serendipitously hover over a strange icon and find it (shades of Stewart Brand from the Whole Earth Software magazine, "just play around with the software, hit keys at random (this is pre-Windows GUI days, so no clicking).
If I have to learn that a defined style overrides text settings, fine, the onus is on me. But where a defined style is not always a defined style, is only sometimes a defined style, the fault lies elsewhere. This is why planes go down, btw.
If you want to change a defined Style via the Compile command, you have to change it in the Compile settings. But if you simply want to pass the Editor formatting (for the Style) straight through, that should work fine. (With the exception of the global override that we’ve already discussed.)
Of course it does. It overrides No Style after clicking the Override checkbox in a layout, and it overrides a style if you add it to the styles pane in Compile and modify the style.
Papyrus is usually a font, not a style. Did you define a style by that name?
Apparently, you did not. Hence, as expected, overriding editor formatting in the layout overrode the font (not a style).
You couldn’t know that, because it isn’t true. (Unless you modify the style in Compile, where you’d know if you did it.) I think you’re insisting on the idea that fonts (Papyrus in this case) are styles, after being told that they are not. Ditto for indents. An indentation setting can be included in a style, but it isn’t a style.
The same is true in Word; fonts are not styles. Indents are not styles. A style is a named paragraph or character format with multiple formatting settings – font family, size, left and right indentation, before/after spacing, alignment, tab stops, etc. Each of those is a formatting element, but none of them are styles.
A key feature of a style, in either program, is that changing the style changes formatting for all text to which the style has been applied. Papyrus is a fixed entity – a font, defined by a font file outside the Word or Scrivener app – and cannot be changed (unless you uninstall it and install another font with the same name). Styles can be changed. In Scrivener, they define Editor formatting and they override the simplest sort of Compile formatting (the override that applies to No style text). They can also be redefined in Compile, which doesn’t happen in Word, which is WYSIWYG and has no Compile step.
No. The style was defined based on how it displayed in the editor. The sole reason to use the Papyrus font at 24 points is because it is difficult to see the difference between 11 point and 10 point Bembo. As an example I could have used any font; or Greek or Cyrillic.
The problem was that unless the defined style is also defined in the Compile settings, it has no effect. It doesn’t override anything. I showed this several times:
Except that defining a style in the Editor does not override text settings unless the style has also been defined in Compile. Merely setting up the style in the editor does not override when Compiling unless the style has also been defined in Compile.
This was the source of my confusion, since I believed that setting up a style in the Editor would cause all text so styled to display as styled and that is not the case unless the style is also set up in Compile.
I understand the difference between a “style” and a font.
I ran Compile at least ten times yesterday with a block quote style. Compile failed (that is, the defined style failed to override the text settings) each time until I also defined the block quote in Compile. Then and only then did it work.
How would anyone think that a defined style in the editor is not a style in Compile? And there is even a third place where styles could be defined, but I don’t want to complicate this even more.
