I’ve been getting progressively more confident with changing compile settings, but I have a question about the checkbox in the Footnotes/Comments settings that says Group footnotes: (at <$–ENDNOTES–> marker). This option doesn’t seem to do anything, as when exporting to PDF or printing, endnotes will always appear at the end of the document even if you check this box and put the token in the project somewhere. I thought maybe this option was only useful for RTF, where you can exports footnotes as regular text (which I thought could be positioned directly by Scrivener in a particular place), but when compiling to RTF the option isn’t there.
Am I missing something about the use of this token?
You have to actually have that placeholder tag typed into the document at some point, in the draft, for it to work. There is at least one template (MLA) which demonstrates this setup in the default example structure. It isn’t available in RTF. As far as I know, RTF doesn’t have the capacity to place true endnotes in a specific location. The would have to be “faked” as formatted text rather than cross-linked endnotes for this to work.
Thanks for the reply. I have been including the tag, but in the compiled document it just prints the tag as entered, then puts the endnotes at the end of the document. I looked at the MLA paper template, but that actually uses the ‘Group footnotes: before last page break’ option. Still, if that option does work it could be almost as useful, I guess.
Huh. Although it hadn’t worked in my project before, it worked when I dragged the endnotes page out of the APA template and used that instead of the page I’d written. I must have made some dumb mistake.