Hi Georg, Georg Datterl wrote: > Hi Vincent, > > Upon a closer look, it doesn't quite solve the main, initial problem: If the > headline takes more than one line, it spills into the table. If I could be > sure it's always only one line, I could as well let the header extend for > 12pt+14.4pt, write "Headline..." into the header and let the body start > below. But if the headline is "Headline for an example with regard to > headlines in pages for tables", how much would padding-before.length be?
Then you have to do it in two steps: one to see in how many lines the headline will be broken, one to adjust the padding accordingly. Or implement some pre-processing step that would estimate the space required by the headline, and the number of lines it will give. Note that there is a limitation if the table does not end on a third column, as on my FO example. The headline will still span the three columns. I’m not sure there is any way to fix that. About the number of occurences of the marker: you just have to make sure that at least one marker will be present on every page. Putting a marker on every row naively ensures that; it depends on the actual content of the cell, but in my example putting a marker every 30 rows would have been enough. > 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: Georg Datterl [mailto:[email protected]] > Gesendet: Mittwoch, 21. Januar 2009 13:16 > An: [email protected] > Betreff: AW: multicolumn with headline > > 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]
