But would be cool if I could just say everything that isn’t specifically overridden gets this default override.
There is a file type that works, that way: ePub. There is a CSS pane, and in there you can set a global paragraph default. Then individual Section Layouts can choose to override the global default if they need to, or even pass-thru editor formatting (useful for stuff like dedication pages).
As to why the rest doesn’t—well, I would say you can achieve that if you want, without a dedicated feature for it. Consider:
- Go into the Styles compile format pane. Create a “Body” or “Normal” paragraph style and set up its formatting. This is your global fallback default.
- In each Section Layout that prints body text, enable formatting override and then apply this style.
That’s more of a WYSIWYG output approach of course, to be clear. For LaTeX we really only need styles for syntax as the preamble and such handles the formatting for us. But if I ever had to dabble in using Scrivener’s WYSIWYG side of things, that’s the hard line approach I’d take: I wouldn’t use any of the formatting tools in Section Layouts. They would exist purely to show were styles are assigned.
I was just coming back to say that this worked. Now I have to re-check the other method.
Okay, yes, you probably will need to roll back some style usage for that to work as expected. You can go the style route, it’s just more busy-work in my opinion, as you then need to add paragraph padding to the Styles pane overrides. It’s a lot easier to just use styles for when you need special purpose text, and that’s the assumption the compiler is built on. And, as explored above, not using paragraph styles in the editor doesn’t mean you can’t end up with them in the output. Sorry, that was a lot of negatives in one sentence.
Doesn’t everyone use a regex when they don’t really need one. My issue with doing a simple replace is that it replaced the special characters in the LaTeX code in the front matter and back matter.
Exactly what I was worried about. I don’t think I could use a global escape replacement in any of my projects, as that would make handling actual syntax a bit of a bother.
Maybe the raw markup style would help here.
Unfortunately it won’t, that doesn’t stop Replacements from running, it only stops Scrivener’s own attempts to escape special characters, if applicable.
Hmm, well one approach would be something I do with Markdown. I have a "Raw LaTeX’ character style that handles a similar issue, but in your case you could just leave the style alone entirely for the .tex format. What you’d want to do special is add that style to the .docx output, and use the checkbox that deletes the styled text. This is a great technique for multi-format outputs where you may, here and there, want to speak more directly to a particular format without syntax ending up in other outputs. In this case you’d only be using it to mark the slash though—not a lot, but just enough.