--- Comment #1 from Andreas L. Delmelle <[EMAIL PROTECTED]>  2008-08-29 
10:47:36 PST ---
(In reply to comment #0)
> Created an attachment (id=22493)
 --> ( [details]
> test source and example pdfs
> the margins of blocks are displayed different, whether the block has a border
> or not. Additionaly it isnĀ“t displayed as expected compared to xep 4.11. Just
> see attached example.

Very unexpected result indeed, but also entirely wrong? There is definitely
something 'off', but I'm wondering whether FOP gets it half right, and XEP is
actually more at fault for not collapsing the space-before and space-after with
the margins of the nested blocks.

As for the difference between the cases with and without additional borders,
I'm still looking for the reference, but I seem to remember that borders act as
a fence for space-resolution, so I guess there should at least be /some/
difference between the two. XEP seems to miss the ball there (and, of course,
FOP's dashed borders are much nicer ;-))

A workaround, if you want to guarantee that all spaces are preserved under all
conditions, would be to  abandon the "margin" shorthand, and use the more
verbose native XSL-FO properties, like so:

<block space-after.optimum="5mm" 
        space-after.precedence="force" ...>
  <block space-before.optimum="2mm"
            space-before.precedence="force" ...>

You can still use the margin shorthand to set space-start and space-end, but if
you want control over precedence and conditionality, you also have to set the
length component through the native property.

Precedence explains why the margin-bottom of the first nested block seems to
disappear. It is collapsed, because the 5mm space-after wins ( 5 > 2 ).
Conditionality may explain why the margin-top for that very same block is
dropped (?)

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to