Trying to get a doc to compile in TNR font via the Compile instructions window. It looks right in that window’s preview. But then, when I open the result rtf doc in a word processor, everything is in Courier.
I hadn’t noticed this problem before so I wonder if it is new, ie a bug?
To be specific: In the Compile window, I have clicked on “Override text and notes” and then clicked on one “level” after the other. With each, I’ve gone down to the window below, clicked on the “A” button to bring up font selection, and selected TNR. As a result, in that Compile window preview, I see only TNR for all text.
I option-click to get Save and Save the settings.
Then I close the Compile window.
Then I open it, click “Load…” and load the settings I just saved. Then I click compile.
What I get is a doc in Courier.
I guess maybe I’m doing something wrong but I don’t see what it could be. As far as I can understand from the manual and instructions, I should be compiling a doc in TNR. But it’s not “taking.”
Bug? Or me? Anyone have a diagnosis?
When you Option-click to get “Save”, that just saves the settings into the current project rather than compile them - it has no effect on the settings in the Save/Load compile settings pane. For that you would need to click on the “Save…” button on the bottom-left. So what you have done is change your settings, save them into the project, and the loaded your old settings (saved externally to the project) over the changes you made, thus wiping them.
All the best,
The other mystery of mysteries is why I can never get double space. I override text formatting in the compile window, most certainly do NOT check “preserve line spacing” in options, and go down the levels saying that EVERYTHING must be line spaced 2.0.
Yet inevitably the result is single spaced and I have to convert to dble space in Word or Mellel or text edit. Not a big deal, but I wish I understood what the problem is.
If you’re exporting to .docx, then this is a known bug in Apple’s .docx exporter. Export to RTF or .doc instead.
All the best,
Great, Keith. Once again – thanks.