Hello! Upon compiling, I keep getting the following message.
“Page number processing could cause problems with footnote placement.
Replacing <$p> or <$p-r> placeholders with page numbers caused the page count to change during Compile, which could break footnote placement. Please see under “Warnings” in the section on “Compiling and Saving Settings” in the user manual for more details.”
Page number processing could cause problems with footnote placement
In extremely rare cases when printing or compiling a PDF, the expansion of the
page numbering placeholders (such as <$p> or <$p-r>) to actual numbers can
cause the page layout to change. As this happens after the placement of footnotes
has been calculated it can result in some footnotes appearing on the wrong page,
displaced from the marker in the text that identifies them.
This problem can most often be avoided by only ever using right-aligned tab
stops to present page numbers in a list where they would be separated from a
heading to their left, by a tab, such as in a typical table of contents.
In other words, if the actual page number takes up more space than the placeholder, it can change the page layout in a way that pushes footnotes to the following page.
The best solution is to compile to a format other than PDF, and finalize the layout in a true page layout tool. Our PDF engine is great for draft-level output, but is not intended to be a true publishing solution.
Thank you for your rapid answer. I have put the page numbering place holders in the center footer. I still get the warning message but the footnotes seem to be placed in the same page as the indicator itself. Do you think I can disregard the warning ?
What Scrivener is saying is that it can’t guarantee the placement of the footnotes. So what are the personal or professional consequences to you if a footnote is misplaced?
The book will mainly be in epub format. I will probably also offer it in paperback form, like my first book. The editor printed copies using a PDF that I sent him. Everything was fine.
The strange thing is that I did not have this kind of warning for the first one, even if I used the same settings. We shall see.
Thank you very much for your help and quick response.