- From: Giannetti, Fabio <Fabio_Giannetti@hplb.hpl.hp.com>
- Date: Wed, 10 Oct 2001 15:34:17 +0100
- To: "'www-xsl-fo@w3c.org'" <www-xsl-fo@w3c.org>
Hi Dariusch, why don't you try to generate a sequence with a different first page and put the address in the header. I try to better explain the idea ... with some ASCII art ... |---------------| | (header) | | | |address | |---------------| |text | | (body) | | | In this way you don't have to specify any space before because the rendering is inside separate areas, a static one (the header) and a flow one (the body). The second page (that can be repeated) will not contain the address |---------------| | (header) | | | |---------------| |flowed text | | (body) | | | Hope this will help .... Fabio > -----Original Message----- > From: Dariusch Bagheri [mailto:Dariusch.Bagheri@gwi-ag.com] > Sent: 10 October 2001 12:38 > To: 'www-xsl-fo@w3c.org' > Subject: AW: stacking > > > Hi Fabio, > > your solution works on the first page but the text will have a > space-before="4.1cm" on every new page! Multiply the lines in > the block and > you will see. > > I experimented with different attributes but couldn't get it right. I > finally came across the possibility of putting the > block-container into the > block and leaving the rest to the rendering process, which, > as i thought, > would apply the stacking strategies mentioned in "4.2.5 Stacking > Constraints" (XSL Ver. 1, 28.8.2001). But fop quits the > process with errors > and i am not sure, wether this is a bug or my > misinterpretation of the xsl > specs. > > regards > dariusch >
Received on Wednesday, 10 October 2001 10:36:02 UTC