Since I switched to Scrivener 3, the footnotes numbers do no longer appear in the inspector, despite having selected in the menu View ▸ Text Editing ▸ Show Compiled Footnote Numbers in Inspector.
Remember that the footnote numbers will only appear after you have compiled at least once.
All the best,
Keith
Sorry, I should have mentioned it: even after compiling the text, no number appears, contrary to what used to be the case in Scrivener 2. It isn’t a huge problem, but I don’t understand why it is so when, normally, these numbers should be apparent after each compile.
Very strange - I cannot reproduce this, as the footnote numbers are appearing fine for me. Do you see the same problem in all projects or only in one?
All the best,
Keith
Actually no, you’re right: in previous projects (written with S3), the numbers are there.
Interesting. Would it be possible to zip up and send us the project to see what is going on (to Mac.support AT literatureandlatte.com)? Please reply here after you have sent it if so, so that I know to look for it.
Thanks and all the best,
Keith
I just sent you the link.
Thanks for the project. I’ve found the problem, and there is indeed a bug here. To keep memory use down to a minimum, Scrivener only temporarily opens in memory all of the text documents being compiled, and then closes them again if they have not been used during the session. However, in this case, this memory conservation code is causing the text documents to be closed internally before the updated footnote numbering has been saved, causing the numbers never to get saved. Note that numbers will get correctly updated in the document you have opened in the editor.
I have fixed the bug for 3.0.4, but in the meantime you should be able to work around it by opening your entire manuscript in scrivenings just before compiling. This will force all of the text documents to stay open in memory.
Thanks and all the best,
Keith
Many thanks, Keith, for the tip.
As I said earlier, it is not a real problem as long as in the final document (the output), it is properly numbered, which is the case.
O.
Hello, this issue is occurring on my system as well on version 3.2.3.
As odalage said, it’s not a huge problem but I would like it to display correctly.
Thanks and best
Raphael