https://issues.apache.org/bugzilla/show_bug.cgi?id=44920

           Summary: nested, multi-page tables and keep-with-previous
           Product: Fop
           Version: all
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: fop-dev@xmlgraphics.apache.org
        ReportedBy: [EMAIL PROTECTED]


Created an attachment (id=21900)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=21900)
see bug description

Running FOP 0.95beta from the command line on the attached XSL-FO and producing
a PDF output, I get no warnings/errors and the expected text on the first page
up until "LOOK HERE". Then follows an empty second page and the end of the
document, even though there is some text left in the XSL-FO. I expected the
text to be printed on the 2nd page.

Removing the attribute keep-with-previous.within-column='always' from the table
row below "LOOK HERE" makes the text on the 2nd page appear again.

FOP 0.94 behaves differently and does not hide any text, but breaks the table
apart a bit early imho (there seems to be plenty of place left at the bottom of
page 1).

The support for keep-with-previous should be partial, as per the compliance
page
(http://xmlgraphics.apache.org/fop/compliance.html#fo-property-keep-with-previous).
The comments there read:
    * [0.20.5] works only in table rows
    * [0.94] works on all implemented FOs, except list- and table-related and
      inline-level FOs.
    * [0.95] works on all implemented FOs, except list- and inline-level FOs.
    * [0.94 and later] <integer> values are not supported.
I would expect my document not to work in 0.94 but to work in 0.95, as the
usage of keep-with-previous is table-related. Nevertheless, not showing parts
of the table is a bit unexpected.  Just ignoring the keep-with-previous
attribute would have been fine. :)


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to