[lmi] help with orphan-control in xsl-fo

[Wendy Boutin]

We have a production concern where some output is unreadable.
Rows are printed on a page that has orphan control; two lines
are superimposed on each other in certain cases. Often times,
the final row of data is the most important line and that's
the one that's unreadable.

Normally there are 35 rows that will print six blocks on one
page and a block of five on the next. If three rows are left
over instead then they fit on the same page; however, they
collide with the text in the footer and cause the next page
to only contain headers and footers. I will send a few pdf
examples in private email to show the precise problem.

The problem was detected using 'nasd.xsl'. Greg and I zoomed
in on this subroutine:
 <xsl:template name="generate-table-values">
and found these comments:
 <!--
 Ensure that a group of 5 rows is never split across multiple pages.
 Add a dummy cell, that spans 5 rows. Since FOP avoids breaking cells,
 this cell remains on one page, so will the group of 5 rows.
 -->
in 'fo_common.xsl', but we just don't know enough about xsl
to see how to fix the problem the right way.

In general, the reports do not produce a consistent maximum
number of rows within each *.xsl; sometimes it's thirty rows,
sometimes it's thirty five, and other times it's somewhere
in between with a defect at certain durations. It seems best
to set each page to a fixed number of rows, like thirty. Is
there a technique we just don't know about that could help
us do this fairly easily. If not, is there a way you could
help us fix the problem?