The following formatting objects and properties of the XSL-FO 1.0 W3C Recommandation are implemented. Please have also a look at the section on limitations.

This section follows the table "B Formatting Object Summary" in the xsl:fo specification. At the end of each sub-section you find listed what is not implemented.

  • root
  • page-sequence
  • page-sequence-master
  • single-page-master-reference
  • repeatable-page-master-reference
  • repeatable-page-master-alternatives
  • conditional-page-master-reference
  • layout-master-set
  • simple-page-master
  • region-body
  • region-before
  • region-after
  • region-start
  • region-end
  • flow
  • static-content

Not implemented: declarations, color-profile, title

  • block
  • block-container (limited)
  • character
  • external-graphic
  • inline
  • instream-foreign-object
  • leader
  • page-number
  • page-number-citation, see limitations

Not implemented: bidi-override, initial-property-set, inline-container

  • table
  • table-body
  • table-cell
  • table-column
  • table-footer
  • table-header
  • table-row

Not implemented: table-and-caption, table-caption

  • list-block
  • list-item
  • list-item-body
  • list-item-label
  • basic-link (internal and external)

Not implemented: multi-switch, multi-case, multi-toggle, multi-properties, multi-property-set

  • footnote
  • footnote-body

Not implemented: float

  • wrapper
  • marker, retrieve marker

Property values can be computed. Compound properties are also understood by Fop.

All other properties are not implemented.

FOP uses Batik directly for its SVG support. Therefore FOP supports the same elements and properties as are supported by Batik. As FOP is designed for rendering to a static medium then only static SVG is rendered.

Due to some limitations in PDF some SVG images, particularly ones with effects or transparency, may not come out correctly. The images should still be rendered correctly for the AWT and Print renderers.