Created attachment 169650 [details] FootNoteOrphans There is an old bug report marked RESOLVED, https://bugs.documentfoundation.org/show_bug.cgi?id=35285, but the discussioon there seems to be somehow intransparent, and I also can't find a solution there. So I'll try again, using a simple example file: The problem ist the failing orphan control in footnotes: It often happens that only one line of the footnote is wrapped to the next page, although the orphan setting (2 lines) is activated for the footnote and therefore two last lines should be wrapped. It should be the case that the problem basically only occurs with a footnote, inserted in the very last line. (Thanks to mikeleb, https://de.openoffice.info/viewtopic.php?f=1&t=75294, for the demo file.)
1. Open the attached file 2. CTRL+A 3. CTRL+C 4. CTRL+N 5. CTRL+SHIFT+V -> RTF -> Now it's fine. Still kind of mystery why. Increasing the font spacing to 1.15 for the footnote and it's back again
Created attachment 169665 [details] Example file 1. Open the attached file 2. Go to footnote 2 3. Increase Orphan Control to 4 -> Now it does work.. ? Help say: Orphan control Specifies the minimum number of lines in a paragraph before a page break. Select this check box, and then enter a number in the Lines box. If the number of lines at the end of the page is less than the amount specified in the Lines box, the paragraph is shifted to the next page. Also in 3.0.0. So this does match the description. Need for lines on page 1.. not present, break to next page. However expected is, if 1 line on next page, break differently Also not covered by Widow control Widow control Specifies the minimum number of lines in a paragraph in the first page after the break. Select this check box, and then enter a number in the Lines box. If the number of lines at the top of the page is less than the amount specified in the Lines box, the position of the break is adjusted.
SORRY FOR THE CONFUSION, the correct term is WIDOW, not orphan. @ Moderator: Could you please remove this report or move it to the new report Bug 140334 already created
*** This bug has been marked as a duplicate of bug 140334 ***