More than half of the codebase has been rewritten over the last three years. With version 0.93 the code has reached <strong>production level</strong>.
</li>
<li>
- The API of FOP has changed considerably and is not backwards-compatible with versions 0.20.5 and 0.91beta.
+ The API of FOP has changed considerably and is not
+ backwards-compatible with versions 0.20.5 and
+ 0.91beta. Version 0.92 introduced the <strong>new stable
+ API</strong>.
+ </li>
+ <li>
+ Since version 0.92 some deprecated methods which were part
+ of the old API have been removed. If you upgrade from 0.91
+ beta, you will need to adjust your Java code. Similarly if
+ you upgrade from 0.92 and use deprecated methods.
</li>
<li>
If you are using a configuration file for version 0.20.5, you have to rebuild it in the new format. The format
an example configuration file. A XML Schema file can be found under
src/foschema/fop-configuration.xsd.
</li>
- <li>
- There have been changes to the end-user API since 0.91 beta. As of version 0.92,
- <strong>the API is now considered stable</strong>. Some methods have been deprecated and will be removed with
- the next release. If you upgrade from 0.91 beta, you will need to adjust your Java code.
+ <li>
+ If you are using font metrics files for version 0.20.5 or
+ 0.92 or earlier, you have to regenerate them in the new
+ format. The new format is characterized by a version
+ attribute on the top-level font-metrics element, whose value
+ is 2.0. The absence of a version attribute will be
+ interpreted as version 1.0, and such metrics files will no
+ longer be parsed.
</li>
<li>
<p>
<li>
Extensions and Renderers written for version 0.20.5 will not work with the new code! The new FOP
extension for <a href="http://barcode4j.krysalis.org">Barcode4J</a> will be available in
- January 2006.
+ January 2007.
</li>
<li>
The PCL Renderer and the MIF Handler have not been resurrected, yet! They are currently non-functional
<body>
<section>
<title>FOP 0.93</title>
- <p>This is the first stable release after the big redesign effort. Its API is that first introduced in release 0.92 beta. The preceding API has been removed. This release again contains many bug fixes and new features. See the changes file for details.
- </p>
+ <p>This is the first stable release after the big redesign
+ effort.</p>
+ <ul>
+ <li>The API was first introduced in release 0.92 beta. The
+ preceding API has been removed.
+ </li>
+ <li>
+ This release again contains many bug fixes and new features. See
+ the <a href="changes.html">changes file</a> for details.
+ </li>
+ <li>
+ See the <a href="compliance.html">compliance page</a> for an
+ overview of the compliance of this release with the XSL 1.0 and
+ 1.1 recommendations.
+ </li>
+ </ul>
<p>Caveats:</p>
<ul>
<li>
Please consult the <a href="stable/upgrading.html">"Upgrading"</a> page for details.
</li>
</ul>
+ <p>Known Issues:</p>
+ <ul>
+ <li>
+ PCL, MIF and SVG output support have not been restored, yet.
+ </li>
+ <li>
+ Java2D/AWT support has been improved, but some problems remain,
+ for example with block-containers.
+ </li>
+ <li>
+ Auto table layout is not implemented, yet.
+ </li>
+ <li>
+ The collapsing border model on tables is not implemented, yet. Please
+ use border-collapse="separate" for now.
+ </li>
+ <li>
+ Footnotes may overlap with text of the region-body in multi-column
+ documents.
+ </li>
+ <li>
+ Space resolution does not work between footnote regions.
+ </li>
+ <li>
+ There's a problem involving nested block-containers and
+ reference-orientation 180/-180 (<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=36391">Bugzilla #36391</a>)
+ </li>
+ <li>
+ block-containers with no height currently don't create a fence for
+ spaces as they should (they behave like a normal block).
+ </li>
+ <li>
+ Preserved linefeeds in fo:character are not handled correctly.
+ </li>
+ <li>
+ An empty block currently produces a fence for stacking constraints
+ which it shouldn't.
+ </li>
+ <li>
+ There are several small problems around white space handling.
+ </li>
+ <li>
+ Images currently don't shrink so they fit on a page when they are
+ too big and shrinking is allowed to happen.
+ </li>
+ <li>
+ inline-container may not work as expected.
+ </li>
+ <li>
+ letter-spacing and word-spacing properties may not work as expected.
+ </li>
+ <li>
+ leaders with leader-pattern="use-content" may not work as expected.
+ </li>
+ <li>
+ keep-with-previous doesn't work inside tables and lists, yet.
+ </li>
+ <li>
+ If two consecutive pages don't have the same available width, the
+ content currently isn't properly fit into the available space on
+ the new page.
+ </li>
+ <li>
+ background-images on page-number-citations are not placed correctly.
+ </li>
+ <li>
+ Not all FO elements can be referenced by their "id", most notably:
+ table-body, table-header, table-footer and table-row.
+ </li>
+ <li>
+ The backgrounds of table-body, table-header, table-footer and
+ table-column are not painted, yet.
+ </li>
+ <li>
+ Border and padding conditionality are not supported on table-cells, yet.
+ </li>
+ <li>
+ Column balancing in multi-column documents may not work as expected
+ (<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=36356">Bugzilla #36356</a>)
+ </li>
+ <li>
+ Omitting fo:table-column or having fo:table-column without a column-width
+ and attempting to create columns implicitly from the first
+ table row is not implemented, yet (<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=35656">Bugzilla #35656</a>).
+ </li>
+ <li>
+ Internal basic-links don't point to the exact location on a page, yet, as they
+ did in 0.20.5. Currently you land in the upper left corner of the page.
+ </li>
+ </ul>
</section>
<section>
projects / xmlgraphics-fop.git / commitdiff