bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #63176] [me] After column-count changes, -me might place running te


From: Dave
Subject: [bug #63176] [me] After column-count changes, -me might place running text on page below footnote
Date: Thu, 13 Oct 2022 18:03:49 -0400 (EDT)

Follow-up Comment #1, bug #63176 (project groff):

[comment #0 original submission:]
> I feel certain I've already posted an example that exhibits this problem,

Ha, yes, back in the original submission of bug #58736, which is what I was
testing when I (accidentally re)created this test case.

The concerns as articulated over the subsequent 39 comments of 58736 were
addressed by adding warnings in various situations beyond -me's ability to
handle (because -me cannot guess what layout the user might want with some
multicolumn/footnote combinations).  Warning of such situations is valid.

This is not one of those situations: the footnote is generated in
single-column mode, and then later (should be) output in single-column mode on
the same page.  There is no ambiguity here about what ought to be done.

The first problem seems to be that the .1c macro is unnecessarily springing
the end-of-page trap: plenty of room is left on the page for the next line of
running text.  (Omit the "| cat -s" from the sample command to see this more
clearly.)  Were the layout as expected, the footnote, generated in one-column
mode, would have later been output also in one-column mode, requiring no
warning, so the warning is presumably a side effect of the layout problem. 
(And, incidentally, its wording seems backwards: the footnote is associated
with one-column text, but the layout in which it is output is two columns.)

The second problem (the one reported in the Summary of this bug) is that after
the footnote is output, more running text is placed on the page below it. 
This might technically be a separate bug, but it seems like it can only happen
after the first bug is triggered, so squashing that one might be sufficient to
resolve this.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63176>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]