douglasr
2008-03-16 08:13:56 UTC
I often experience the problem of spurious extra headings being
generated by longtable.
For example, the following:
% --------------------------------------
Some text of variable length before the longtable ...
\begin{longtable}{ll}
Heading
\endfirsthead
Heading (continued)
\endhead
a & b\\
c & d\\
e & f
\end{longtable}
More text after the longtable ...
% --------------------------------------
can sometimes produce:
Some text of variable length before the longtable ...
Heading
a b
c d
e f
<at top of the following page>
Heading (continued)
More text after the longtable ...
i.e., a spurious heading can appear at the top of a page with no
subsequent rows of the longtable (all the rows having been already
properly generated on the previous page).
The problem likely only occurs with particular height of the page
content before the longtable. A small change of vertical spacing can
either trigger or suppress a spurious extra heading.
Since my longtables are usually generated programatically from a
database, it is troublesome to check for and suppress such spurious
headings.
Any ideas for a solution would be much appreciated.
Best Regards,
Douglas
generated by longtable.
For example, the following:
% --------------------------------------
Some text of variable length before the longtable ...
\begin{longtable}{ll}
Heading
\endfirsthead
Heading (continued)
\endhead
a & b\\
c & d\\
e & f
\end{longtable}
More text after the longtable ...
% --------------------------------------
can sometimes produce:
Some text of variable length before the longtable ...
Heading
a b
c d
e f
<at top of the following page>
Heading (continued)
More text after the longtable ...
i.e., a spurious heading can appear at the top of a page with no
subsequent rows of the longtable (all the rows having been already
properly generated on the previous page).
The problem likely only occurs with particular height of the page
content before the longtable. A small change of vertical spacing can
either trigger or suppress a spurious extra heading.
Since my longtables are usually generated programatically from a
database, it is troublesome to check for and suppress such spurious
headings.
Any ideas for a solution would be much appreciated.
Best Regards,
Douglas