On 20 Jan 2009, at 13:41, Georg Datterl wrote:

Hi Georg

Given this block

<fo:block-container absolute-position="absolute" start- indent="77.16534pt" background-color="cyan"> <fo:block line-height="1em" span="all" orphans="3" background- color="magenta" widows="3"> <fo:inline font-family="arial bold" font-size="18.0pt" line- height="18.0pt" background-color="yellow">PROGEF® Standard Polypropylene</fo:inline>
        </fo:block>
</fo:block-container>

I get a block-container starting at 0pt, containing a block starting at 77pt. Which is good.

Seems to be correct, at first glance, although... How wide is your region-start? IIC, the start-indent should be determined in relation to the page's start-edge (since the block-container is taken out of the normal flow). If it would not be an absolute-positioned block-container, then the inner block would be offset 2 x 77pt from the start-edge of the region- body, due to indent inheritance. (the block inherits the computed value of start-indent from the parent block-container)
see also: http://wiki.apache.org/xmlgraphics-fop/IndentInheritance

But why are both blocks

Small question: /both/ blocks? Where's the second?

ending 77pts left of the right page border? It seems like start- indent is telling the block-container how wide it is.

Indirectly, it should obviously have an impact on how wide the block can grow. Could be that you have stumbled upon a bug here, depending on what the precise result is. If you have a region-start that is roughly 77pt wide, could be that you get the impression that no indent is applied...

Specifying end-indent is even more funny, an end-indent of 77pt makes the block end 77pts inside of the container which seems to end twice 77pts inside of the page...

Same issue, I think. To be certain: can you post the complete document, including the layout-master-set?



Cheers

Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to