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=42049>.
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=42049





------- Additional Comments From [EMAIL PROTECTED]  2007-09-05 12:09 -------
(In reply to comment #10)
> It's not clear what version of fop (any of you) are referring to. I tried to
> generate the examples
> (http://people.apache.org/~jeremias/fop/indent-inheritance2.fo) found on the
> Wiki mentioned above and got different results for the versions I tried. The
> versions I tried were 0.20.5 and 0.94.
> 
> I'm not sure which one is correct, but I assume fop 0.20.5 got it right (0.94
> seems to give nested blocks where start-indent has been reset a negative 
> indent
> relative its containing block - or did I miss something :-).

Yes, you seem to have missed the point on the Wiki :-) 
Indent-inheritance precisely means that a descendant block of another block 
with start-indent > 0 will 
inherit the indent from its ancestor. Since this ancestor is already 
'displaced', the nested block will in 
fact appear to have *twice* the indent of the ancestor. Jeremias verified this 
with the XSL-FO editors, 
and they agreed that that unexpected behavior is in fact correct. To achieve 
the effect that seems to be 
generally expected, an author would always need to reset the indent on the 
block in question. Its 
descendants then inherit the zero indent etc.

So, the real problem seems to be limited to the RTF renderer here, which 
currently behaves non-
compliant.

There is a configuration option you can use to make FOP behave as expected, but 
I would only really 
use it if it's too much trouble to reset the start-indents.

Hope it makes sense now.

Cheers

Andreas

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to