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=37906>. 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=37906 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 2005-12-14 14:47 ------- This effect is due to indent inheritance, as I call it. I've documented the whole topic on our Wiki: http://wiki.apache.org/xmlgraphics-fop/IndentInheritance In contrast to many commercial implementations we've chosen to closely follow the specification which, unfortunately, may have certain side-effects. The specialist group at the W3C is aware of the issue. There are two solutions here: 1. Spec-conformant solution: margins are mapped to the start-indent and end-indent properties. The latter two properties are inherited. If you cross a reference area boundary you will the see the effect you describe unless you reset start-indent and end-indent to 0. For a table, this can conventiently be done on the table-body, so it fans out to all child elements. For more detail, please see the Wiki page indicated above. 2. Non-spec-conformant solution: I've recently added an option to FOP that lets you activate an alternative set of rules concerning indent inheritance. These rules try to mimic the behaviour implemented by some commercial FO implementations. With these rules enabled you don't get the strange side-effect as long as you work with margins only because the margins are not automatically propagated to the start-indent and end-indent properties. Documentation on how to turn this on will be available shortly. I've already written it, but it's not yet published. The fix for that is found in FOP Trunk (available via SVN only). Please note that enabling this feature makes FOP behave differently from what the specification says it should do. I've recently asked the W3C SG about their updated opinion on the matter: http://lists.w3.org/Archives/Public/xsl-editors/2005OctDec/0026.html -- 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.