You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-commits@xmlgraphics.apache.org by Apache Wiki <wi...@apache.org> on 2005/12/14 14:53:14 UTC

[Xmlgraphics-fop Wiki] Update of "IndentInheritance" by JeremiasMaerki

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Xmlgraphics-fop Wiki" for change notification.

The following page has been changed by JeremiasMaerki:
http://wiki.apache.org/xmlgraphics-fop/IndentInheritance

The comment on the change is:
Added a conclusion on the matter

------------------------------------------------------------------------------
   * 5.3.2 Margin, Space and Indent Properties (http://www.w3.org/TR/xsl/slice5.html#section-N5987-Margin,-Space,-and-Indent-Properties)
   * 5.1.2 Computed Values (http://www.w3.org/TR/xsl/slice5.html#section-N5717-Computed-Values)
   * "Disposition of Comments on XSL Candidate Recommendation" (see '''comment 20''', July 2001, http://www.w3.org/2001/08/28-XSL-PR-DOC.html)
+  * Updated opinion of the W3C SG (see http://lists.w3.org/Archives/Public/xsl-editors/2005OctDec/0026.html)
  
  == Main difference between start-indent and margin-left ==
  
@@ -334, +335 @@

  
  To avoid the strange effects, you can reset start-indent and end-indent to "0pt" on fo:table-body, fo:table-header and fo:table-footer. These two properties don't apply to these FOs but can still be specified as they are inherited.
  
- == What now? ==
+ == Results ==
  
- We need to verify that this interpretation is 100% correct. Once this is done, we have to find out if we also want to break inheritance or if we stick to a strict interpretation of the specification. It's mostly a question of interoperability. If you run the first example FO through various FO implementations you just as many different results.
+ Apache FOP should, by default, stick to the rules defined by the XSL-FO specification. The W3C SG has recently [http://lists.w3.org/Archives/Public/xsl-editors/2005OctDec/0026.html confirmed] that our interpretation is correct. However, an option was recently added that allows to enable an alternative rule set that lets FOP mimic the behaviour chosen by many commercial XSL-FO implementations. Please note that enabling this feature lets FOP behave differently from what the spec dictates.
  
  == Discussions on the fop-dev mailing list ==
  

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-commits-help@xmlgraphics.apache.org