Hi Vincent, That seems to solve two problems in one, just one last(?) thing: Why is the marker defined in each row?
Regards, Georg Datterl ------ Kontakt ------ Georg Datterl Geneon media solutions gmbh Gutenstetter Straße 8a 90449 Nürnberg HRB Nürnberg: 17193 Geschäftsführer: Yong-Harry Steiert Tel.: 0911/36 78 88 - 26 Fax: 0911/36 78 88 - 20 www.geneon.de Weitere Mitglieder der Willmy MediaGroup: IRS Integrated Realization Services GmbH: www.irs-nbg.de Willmy PrintMedia GmbH: www.willmy.de Willmy Consult & Content GmbH: www.willmycc.de -----Ursprüngliche Nachricht----- Von: Vincent Hennebert [mailto:[email protected]] Gesendet: Mittwoch, 21. Januar 2009 13:09 An: [email protected] Betreff: Re: multicolumn with headline Hi Georg, Georg Datterl wrote: > Hi Andreas, > >> I think Vincent is right: not doable with XSL-FO. >> Breaking the flow's column-layout can only be achieved by span="all" >> and that property only has effect for direct children of the flow. >> If you specify it on a deeper block, the processor should ignore it >> (according to the Rec) > > So the only maybe possible solution is a dynamic height page header. When > specifying the header extend, I'd need to reference the block in the header > and include its size... Have a look at the attached FO file. Actually you would specify a 'normal' height for the region-before, and set the overflow property to 'visible'. When the marker for the table is retrieved, then it would overflow the region-before and appear in the body. The second part of the trick is to enclose the table into a block with padding-before.conditionality set to 'retain'. That way, when the table is broken over columns it will be 'shifted' from the top of the region-body, leaving room for the marker. Provided that you don't specify any background on the region-body you should get the desired result. You normally can safely ignore the overflow warnings FOP will issue. > Regards, > > Georg Datterl HTH, Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
