> From: Jay Chiu [mailto:[EMAIL PROTECTED] > > The tables may span multiple pages. The free form data may be in > any place of any page, depending on the data in database. Thus I > put all absolute positioned block-containers inside a relative > positioned block-container to make the absolute position > relative to the outside block-container. >
Don't know if you have taken a look at the example i sent afterwards, but seems the latter part is working. It's only the position of the outer, relative positioned block-container which needs to take into account the eventual portion of the table already on the page... > Thus it is impossible to tweak xslt. Is there any other aproach > to implement the report I listed in previous message? > Can't think of any right away. XSL-FO is very (printed-)page-layout-oriented (as is PDF in its roots), so I guess these co�rdinates need to become fix at some point (at the very least, in theory, it should be possible to derive these from the generated fo - whether intermediate or not...) > >I'm not sure what to make of the width of the block-container > being set to "100%" > Previous it is inside a table-cell and use "100%". I did not > change it. I guess it should work. > As you could derive from the regions overlapping the page-margin, it didn't. I think the appropriate interpretation of the '100%' would be 'the width of the containing block-container'... but that inside block-container already has an offset from the containing one. Again, default XSL-FO behaviour, neatly according to spec http://www.w3.org/TR/xsl/slice7.html#width In any case - and I think I have mentioned it before somewhere in this list, but in case you missed it - don't rely too much upon the renderer to guess what effect you are trying to achieve. Take care, especially where it comes to relative attribute values. Cheerz, Andreas Delmelle --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
