Sushanth, without a clean XSL-FO snippet, we only can provide you 'hypothetic' solutions. a possible solution should be using the 2 Fop extensions fox:orphan-content-limit and fox:widow-content-limit. Read [1] for further details.
[1] http://xmlgraphics.apache.org/fop/0.95/extensions.html#widow-orphan-content-limit -- Pascal Le 07/07/2010 11:58, Georg Datterl a écrit : > Hi Sushanth. > > First question: Are you definitely sure there are no body lines on the first > page? You don't have empty lines (for spacing or because of missing data) at > the beginning of your table? If so, please drop us a code example, because > then I guess it would be a bug. > > If you have empty lines, put a keep-with-next.within-page="always" on them. > > Regards, > > Georg Datterl > > -----Ursprüngliche Nachricht----- > Von: Sushanth [mailto:[email protected]] > > First of all, I'm extremely sorry for the long text that follows this :) > > I looked all around the internet for a solution to this problem and still > haven't found a straightforward solution. I am generating a PDF using FOP > 0.95, where I have a bunch of pages, each of which can have multiple tables. > There are times I encounter this problem where the fo:table-header content > of one of the tables ends up as the last element on a page with no > table-body under it. The table-body starts on the next page, of course > preceded by table-header on the next page also which is fine, but is there > any way I can prevent a table-header from ending up as the last element on a > page if there is not enough space for the table-body to be displayed on the > same page? > > The options I have tried so far include using > keep-together.within-page="always". This doesn't help because some tables > can even span multiple pages, in which case a page-break is not introduced. > I have read that FOP-Trunk provides integer support for keep-together, but I > wasn't able to build the FOP-Trunk jar. Is there any place where I can > directly download the latest FOP-Trunk jar? > > The other option I have tried is brute-force, trying to keep count of the > number of rows printed on a page and introducing a manual page break, but > this is an ugly patch and I want to avoid using it and it will not work in > all scenarios. > > Is there a simple solution to this problem using FOP 0.95? I'm sure somebody > would have anticipated this problem while developing FOP and must have some > solution in place for this :) Please let me know. I can't live with this > problem anymore. > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
