I have set the section formatting (with title text in a grey) and assigned the section, but title text color changes not appearing in compiled PDF. It worked for a while but now just black. Shows correct color in the section editor, but not in compiled PDF.
I am experiencing so many crazy inconsistencies when compiling.
OK, found this “Remove Text Color” option and turned it off. But this means that if I want colored titles in compile, I have to make sure that I have removed all color I’ve used to annotate my manuscript text in the editor. Is there another way? Seems if the compile options offer text color, that should override all editor styles… no?
Remove Annotations is already ticked–see 5 options up.
Sorry, but I am confused as to what your comment has to do with my problem. There are lots of other reasons and ways to apply color to text other than “annotations”. Let’s say I want to make changes to text (color) here and there in my text during the editing process, but also want to be able to apply color to to titles etc during the compile output process, but I don’t want the colors I have applied in the editor to show up in my compiled output? Surely there must be a way to suppress editor text colors while allowing colored text in compiled text?
The way you’ve described it, it’s as though you want a total absence of colour in what you compile. Unless Scrivener on Mac is vastly different to Windows that is easily achieved in the menu you’re floating in, in your picture.
This makes no sense. Either you want to suppress colors or you don’t.
The general options are all manuscript-wide settings. So removing the text color here affects the entire manuscript. You might do that, for instance, if you wanted to send the file to a printer and didn’t want them to charge you for color printing, or if you didn’t want the person receiving the file to see the colors you applied for your own use.
If you want for some, but not all, Editor colors to appear, probably Styles are the easiest way to do that.
In my case, I don’t want ANY colors from the editor to show up in a particular compiled output… but I do expect to be able to have colors set in the compile set up to included in the compiled output. Editor and Compile settings should be independent. No? All of the other text style settings in compile are independent of editor settings. When I tell compile to use a section that uses 20pt Helvetica Bold for a title, I don’t have to allow or suppress font or size settings in the editor. Why should text color be any different?
In the editor, a person uses colors in the editor to annotate their text, to help the WRITER organize and understand their writing as they write. On the compile side, a person uses colors for typographic output, uses colors to help the READER. On the compile side, each target compile targets a different READER. Making changes to settings in any one compile should not require the writer to change their document in the editor, to remove information essential for the writing process, or to remove information needed for other compiles.
I want to make layout color decisions when Compiling, not when editing. Seems the only option to allow my Compile section typography settings to have the titles or the text to be grey (or any other color) is to set another attribute when compiling to allow all editor set colors to come through in the Compiled output. So yes I want to set my compile to have grey titles, but no, of course I don’t want the colors I have used in the editor to leak out into my compiled output. This seems to be the whole point of Scrivener’s use model, to separate the activity of writing from the compiled output. But in this case, seems decisions made during Compile backwards effect decisions made during editing. This should not be the case. Scrivener was created to allow many different Compiled outputs from the same Editor project. If one of those Compiled outputs demands that I should have to remove important information from my Project such that that information is no longer available in the editor or to other Compiles, well that really goes against Scrivener’s advertised use model and one of Scrivener’s key advantages as a book writing environment.
Again, I wan’t any color information added in the writing of my project to be independent from any color settings I choose in any one particular compile. Deciding to change the color of a title in a section of a particular compile format should not force me to allow all editor colors into the compiled output.
Is there a way to set up a compile such that it will honor section title and or text color settings, AND suppress editor color attributes in the compiled output?
One way mentioned earlier would be to make the colours applied in the project editor to be part of a style; those styles could then be overwritten by the compile format to remove their colour. That might be an option to consider when starting a new project.
Assuming in this case that the editor colours are just part of the direct formatting, you could overwrite that by applying black as a colour to the text in the compile format. This depends on you ticking the “override text and notes formatting” for the sections that need it. Then, with the cursor in the sample main text (in the section layouts), right-click the text colour block on the format bar and select black, vs. the “no color” option, which is the usual default.
That will let you set a colour for the titles in compile and leave off the option to remove text colours from the compiled document but still overwrite all direct-formatting editor text colours with black (or some other colour you choose to set for the particular section).
Text colour coming from styles will still be preserved in the output this way, because styles will take precedence over the section layout formatting that’s setting the general colour to black. If you want these removed too, add the style to the compile format and change the style’s colour there (to black or no colour).
