Subject: Re: [xsl] FO: padding within list problem (really FOP) From: "J.Pietschmann" <j3322ptm@xxxxxxxx> Date: Wed, 11 Aug 2004 21:33:30 +0200 |
So it says in the FOP compliance document. Just to clarify, when they say "blocks" they do mean the XSL definition of a block as an area, and not the <fo:block> element?
It means fo:block, fo:block-container (except for positioning bugs) and fo:table-cell (with even more caveats). I don't think it would ever work on fo:table, fo:table-row, fo:list-block and the other list FOs. Note that padding isn't an inheritable property. THere are additional problems in footnotes and table cells, where using padding is likely to mess up link hotspots.
FOP compliance table says that implementation of space-after is only partial - only space-after.optimum supported. Hm.The biggest problem is actually that space-before/after is forced.
Anyway, using space-after doesn't solve the problem of later list items "moving up".
That's strange, I always thought space-before/after is applied even on empty blocks.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] FO: padding within list p, Ralph Holz | Thread | Re: [xsl] FO: padding within list p, Ralph Holz |
Re: [xsl] Can't get output from xml, Josh Canfield | Date | Re: [xsl] XSL Problem, Oleg A. Paraschenko |
Month |