Bug details

Footnotes flows on the following page even if there is still space on the page where is the reference number

Indesign CC 14.0.1
MAC OS High Sierra 10.13.6

unfortunately it happens very often that the text of the footnotes flows on the following page even if there is still space (several lines) on the page where is the footnote’s reference number.
for this bug, the result of many jobs is very bad

3 votes
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)

We’ll send you updates on this idea

Vladan shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

3 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Anonymous commented  ·   ·  Flag as inappropriate

    Lo que sucede es que si el texto se mueve, en versiones anteriores se movían las notas en automático, en la última versión no sucede y eso genera que nunca se obtiene una formación correcta o definitiva porque no hay control de las notas y su continuación en las siguientes páginas.

  • Vladan commented  ·   ·  Flag as inappropriate

    Hi Ravi,
    thank you for your answer.
    In this case unchecking the option "Span Footnotes Across Columns" could helps me overcome this issue but this is not the solution. The bug remains.
    If I have a file with different layout pages with one columns and two or more columns and, for example, for editorial decision I may not uncheck this option, the bug is always there.

  • Vladan commented  ·   ·  Flag as inappropriate

    Hi Ravi,
    thank you for your answer but I absolytley don't want to uncheck the option "allow split footnotes" across the pages.
    The option "Allow Split Footnotes" is necessary for the all documents with many and large footnotes.
    However, in previous versions of InDesign it has never occurred this type of bug.
    In this cases as a workaround I enlarge the text box just a little and then I setting it as it was before.
    Also this fact that after this operation the footnotes are fixed confirms that it is a bug

Feedback and Knowledge Base