Togan Muftuoglu wrote:
> The question is as follows. I have a document as follows
The original XML file is not relevant.
> The ending PDF when I use XEP is correct meaning
>
> 1. First Term bla ba
>
> 2. Second Term bla bla
>
> However the PDF created via FOP 0.20.5rc3 (CVS build of yesterday) is as
> follows
>
> 1.
> First Term bla bla
>
> 2.
> Second Term bla bla
>
>
> So there is something wrong with how FOP understands the nested lists
> compared to XEP . Hope this time the communication is established :-)
Yes, now I understand. I duplicated the behavior that you mention. Here is
the relevant XSL-FO code (after pretty-printing):
<fo:list-item-label end-indent="label-end()">
<fo:block>1.</fo:block>
</fo:list-item-label>
<fo:list-item-body start-indent="body-start()">
<fo:block space-before.optimum="1em"
space-before.minimum="0.8em" space-before.maximum="1.2em"
space-after.optimum="1em" space-after.minimum="0.8em"
space-after.maximum="1.2em" id="N1000D">
<fo:block space-before.optimum="1em"
space-before.minimum="0.8em" space-before.maximum="1.2em"
keep-with-next.within-column="always" keep-together.within-column="always"
id="N1000F">
<fo:inline font-weight="bold">First Term</fo:inline>
</fo:block>
<fo:block margin-left="0.25in">
<fo:block>This is the first para of <fo:inline
font-weight="bold">first
term</fo:inline> which is the first list item of the <fo:inline
font-weight="bold">ordered list</fo:inline>
</fo:block>
</fo:block>
</fo:block>
</fo:list-item-body>
So I guess what you are really complaining about is that even though you
told FOP to place a minimum of 1.6 ems more space above the list-item-body
than you did above the list-item-label, you don't really want it to?
I just looked in the standard & could not readily find where conformance in
this situation is defined. If you think that FOP's behavior here is
nonconformant (and it very well might be), please enter a Bug report &
document the section(s) of the standard that apply:
http://xml.apache.org/fop/bugs.html
Even if everyone agrees that FOP should do this differently, I would be
surprised to see this addressed until the redesign work is done. In the
meantime, I see two workarounds: 1) you have already identified RenderX as
satisfying your needs, and 2) you could just remove the offending
space-before.minimum attributes.
Victor Mote
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
