DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=26163>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=26163

margin-left in nested fo:block not used in PDF output

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|Other                       |Medium



------- Additional Comments From [EMAIL PROTECTED]  2004-06-18 13:20 -------
I am seeing a bug that is probably related to this one. It suggests to me that
inheritance is not operating properly for list-blocks, at least for spacing and
possibly in general.

The scenario I am seeing is as follows:

Given

<fo:list-item-body start-indent="body-start()">
<fo:block>
...
</fo:block>
</fo:list-item-body>

The fo:block will indent as expected -- that is, it will appear at the
indentation position that is expected of the list-item-body.

If, however, a start-indent is specified for the fo:block:

<fo:list-item-body start-indent="body-start()">
<fo:block start-indent="0.25in">
...
</fo:block>
</fo:list-item-body>

then the fo-block is indented **relative to the indentation of the containing
<fo:list-block>

I have not tried it, but it would be interesting to see what the effect would be
of specifying <fo:block indent="0">.

I haven't looked at the code, but my suspicion is that either (a) the
start-indent inheritance processing within FOP has a bug of some sort, or (b)
the XSL-FO specification got the inheritance specification wrong. At the moment,
I'm leaning toward FOP as the culprit.

BTW, this problem is not in any way docbook specific. It's purely a fop issue.

Reply via email to