Problem solved!!! I found a way, by means of DocBook (Dave Cushman referring to Bob Stayton) to change the keep-together property so it works like the old FOP-version.
What I meant by "corrupted" is that, in the resulting pdf, the table was renderered on the whole physical (paper-)page overflowing the page header and footer areas. The table in itself was also "corrupted" in a way. This meaning that the first rows where "truncated" and the end of the table was aligned with the last row at the bottom of the physical page. The table header was furthermore overlayed with the rows rendered at the top of the page. So, it was probably a kind of a "clip" but not readily understandable as such. Thank you for the prompt response. Lars Bjerges Team z/Os Swedbank AB (publ) 105 34 Stockholm Telefon: +46 (0)8 58 59 43 45 Mobil: +46 (0)70 95 27 774 Email:[EMAIL PROTECTED] www.swedbank.se -----Ursprungligt meddelande----- Från: Andreas L Delmelle [mailto:[EMAIL PROTECTED] Skickat: den 21 december 2007 17:59 Till: [email protected] Ämne: Re: Fop 0.94 (Docbook and tables) On Dec 21, 2007, at 10:31, <[EMAIL PROTECTED]> wrote: Hi > I am trying to upgrade from fop 0.20.5 to 0.94 and in conjunction > with DocBook (1.70.1) found out that there is a irritating change in > operations regarding table processing. > > When processing tables they: > > 1 Don´t cross pages (e.g if a table doesn´t fit on the current page it > is rendered on the the next page) and Can you check the resulting FO, and whether it uses the 'keep- together' property on the table? If so, this will somehow have to be removed. No precise idea on how to achieve that, but it should be a matter of adding a customization to the Docbook stylesheet. > > 2 If a table is "too large" to fit a page it will get corrupted (with > an error message: "WARNING: Content of the region-body on page n > overflows the available area in block-progression dimension. > (fo:page-sequence, no context info available)") What do you mean exactly by 'corrupted'? FOP 0.94 interprets keep- values of "always" literally as "without exception", or "if the content does not fit, it will be clipped". Chained 'keep-with-next' and 'keep-with-previous' on the rows will have the same effect: FOP will try to keep the whole table together on a single page. Your best bet is to remove the keep-*="always" properties from being added. HTH! Cheers Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
