I use the position=absolute attribute. With that there are attributes for left, top, width, and height. I set them all but they may be optional. If you just leave out height does it spill to the next page? If not, that could get complicated trying to wrap text to a new page.
My case is the ideal absolute positioning. I have the whole page in one region and position everything. Everything I print is one custom fixed width font. I write programs which generate the xml input so I know exactly what needs to print on each page and how big it needs to be. -----Original Message----- From: Andreas Delmelle [mailto:[email protected]] Sent: Monday, March 14, 2011 3:00 PM To: [email protected] Subject: Flow data in 2 different regions? On 14 Mar 2011, at 19:48, Zac Nichol wrote: Hi Zac, >> I want to flow data into 2 different regions (region-body and >> region-before). is this possible? when i do it, FOP complains that >> "For fo:page-sequence, only one fo:flow may be declared." It seems >> weird to me that you can have many fo:static-content objects within a >> single page-sequence, but you can't have many fo:flow objects. >> >> How can I flow data into 2 different regions in a single .fo file? Currently, with FOP, this is not possible. There is no support at all for XSL 1.1 fo:flow-maps, and fo:flow can only be mapped to the fo:region-body. Basically, that leaves only fo:static-content as a candidate to be mapped to fo:region-before. The only alternative might be what Eric just suggested: use a combination of fo:block-containers, but then absolute-positioned block-containers will not flow to the next page, so the content would have to be very well prepared to pull that off... It depends on the requirements whether this is feasible. Regards, Andreas --- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
