Thanks for your idea. Calculating the height of the left column is no problem,
I can get the height of blocks A-D. Block E is tricky. The table height can be
calculated, but the text part may contain lists or flow text. I guess I will
have to count line breaks, calculate linelengths and guess how many breaks
hyphenation will generate. Not very reliable, I'm afraid, but it sounds doable.
------ Kontakt ------
Geneon media solutions gmbh
Gutenstetter Straße 8a
HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert
Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20
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
Von: Vincent Hennebert [mailto:vhenneb...@gmail.com]
Gesendet: Mittwoch, 4. Februar 2009 11:04
Betreff: Re: table cell duplication
Georg Datterl a écrit :
> Hi Jeremias,
> Yes, I include a picture of my table (created with iText, except for the red
> stuff). The left colum contains numbers (Block A), photos (Block B),
> drawings (Block C) and finally another number (Block D). The right column
> contains headlines, text, tables, various stuff. As you can see on the second
> page, last table, Block A aligns with Block E, Block D is on the bottom line
> of the table, not necessarily aligned to anything in Block E.
Please have a look at the FO file attached. That's the most accurate approach I
could find. That requires a bit of pre-processing, and knowing the heights of
the images, but since your content seems to be even you might be happy with it.
Plus it's implementable straight away, without any modification to FOP.
I can think of two FO constructs to make content repeat on pages:
markers or table headers/footers. Markers are not really an option here (even
supposing that table markers are implemented), since the repeated content
should be mixed with the table body, and have an influence on its height.
Remains table header. The idea is to put the drawing in a header and fill the
body with blank content such that the height of the table matches the height of
content E. In the sample FO I used blocks containing non-breaking spaces. The
whole challenge is to determine how many such blocks should be put. In your
case you seem to always have the same content: 2 title lines, a few list items,
then tables with a certain amount of entries. If the title content and list
items are short enough to never be broken over lines, then you can easily
estimate the height of content E, substract the heights of A, B and C, which
gives you the amount of blank blocks to put.
However, I can't think of any way to extend the borders to the final horizontal
Block D is relatively easy to achieve: just put a block with negative margin
after the whole table.
> The text "PE universeel fittingen" is in the header area and can be ignored.
> Maybe my table structure is not that smart, but it seemed the easiest way to
> keep block D on the bottom. More or less... If you know a way to elongate the
> table columns down to the table baseline regardless of empty rows, that would
> be most welcome, too.
> Georg Datterl