Compiling RTF w/ page-based footnotes+chapter based endnotes

I am having trouble figuring out to make this work. I am trying to compile a Scrivener project to a format for further editing in Nisus Writer Pro, which supports:

  1. page based footnotes, at the end of each page;
  2. chapter based endnotes, at the end of each chapter;

I intend to use both: 1) for more expedite footnotes, which derive from the main text flow, but will complement it; 2) for more lengthy footnotes, at the end of each chapter.

Problem is: I can’t seem to compile to a format that supports both: I can:

  1. compile to RTF and get page based footnotes, + endnotes at the end of the document (no endnotes for each chapter);

  2. compile to RTFD and get chapter based endnotes (before each page break) but in this case I can’t get page based footnotes.

I am using inline footnotes which I expect to be compiled into page based footnotes; and inspector footnotes which I expect to be compiled into chapter based endnotes.

Can anyone help on this? Thanks!

One question: does Nisus Writer Pro even support this capability? I briefly went through the documentation on endnotes and clicked around a bit, but I couldn’t find anything about controlling where endnotes appear. I know in Word it is easy enough to take a Scrivener generated RTF and change endnotes to end-of-section with a couple of clicks. If NWP does support it and I just completely missed it, it might be equally easy to do so.

To explain a bit of what you’re seeing with compile options: with RTFD there is no true footnote or endnote support at all. What you’re seeing there is a rendering of how endnotes work, using normal (static) text. The markers aren’t linked—if you add a new one in the middle of the document all of the numbers would be messed up and the new one wouldn’t be added to the stream of endnotes where it should be, but rather tacked on at the very end as #1. So that specific technique may not be the best for what you want anyway. This is why we have more effective control here with formats that don’t support true notation, because we can print text wherever we want just as easily as printing a separator between files.

Well, theory aside, we are going to attempt supporting end-of-section notes in the future. It’s just a matter of using the right codes from what I understand.

Thanks for the reply. I also posted on Nisus forum and found something that can be useful for Scrivener users who want this particular formatting in NWP. Not straightforward but simple enough:

– compile in Scrivener as RTF, checking “Export inspector footnotes as endnotes” (that’s my particular taste, inline footnotes will be exported as regular end-of-page footnotes);

– open the exported RTF in NWP; page-based footnotes should appear as well as one block with all endnotes in the very end of the document;

  • in my compile options I have Scrivener adding a page break between chapters; replace it in NWP with a section break (you can toggle invisibles on + regex find and replace to kind of automate this);

– go to Style Sheet View in NWP, search for the “Endnote” options and you will see a placement options – select “end of section” instead of “end of document”;

– NWP currently has a bug in which the endnotes will seem to disappear; they don’t, but you need to save the file, close Nisus, and open it again.

In the end you get what I wanted – page-based footnotes and several blocks of endnotes, one at the end of each section! I find this reading friendly … you will distinguish notes that complement the flow of the main text, but can be set aside from it, from notes that are bigger and more complex, which may be useful for deeper knowledge on the topic, but are overwhelming if placed in the main text (or in the regular footnotes as well).

Sounds good! That’s exactly what I was looking for but failing to find. Thanks for posting the tips here.

You’re welcome :slight_smile:
Now I must find a comprehensive way of adding pictures and tables in Scrivener, while making use of the several TOC’s NWP allows.