diff options
Diffstat (limited to 'src/documentation/content/xdocs/trunk/upgrading.xml')
| -rw-r--r-- | src/documentation/content/xdocs/trunk/upgrading.xml | 38 |
1 files changed, 24 insertions, 14 deletions
diff --git a/src/documentation/content/xdocs/trunk/upgrading.xml b/src/documentation/content/xdocs/trunk/upgrading.xml index 4772fcb4c..b8aa58200 100644 --- a/src/documentation/content/xdocs/trunk/upgrading.xml +++ b/src/documentation/content/xdocs/trunk/upgrading.xml @@ -31,24 +31,34 @@ </p> <ul> <li> - More than half of the codebase has been rewritten over the last three years. The code is - relatively new and possibly not as stable as version 0.20.5 in every regard. But the code - is <strong>quickly approaching production level</strong>, especially when you're happy - with only PDF and PostScript output. + 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 version 0.20.5. + 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> - If you are using a configuration file, you have to rebuild it in the new format. The format + 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 of the configuration files has changed since version 0.20.5. See conf/fop.xconf for 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 between 0.91 beta and 0.92 beta. With version 0.92, - the API is now considered stable. 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> @@ -67,7 +77,7 @@ <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 @@ -106,13 +116,13 @@ or <code>instream-foreign-object</code> objects. If images or SVGs are sized differently in your outputs with the new FOP version check <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37136">Bug 37136</a> - as it contains some hints on what to. The file + as it contains some hints on what to do. The file <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/fo/basic/images.fo?view=markup"> <code>"examples/fo/basic/images.fo"</code></a> has - a number of good examples that shows the new, more correct behaviour. + a number of good examples that show the new, more correct behaviour. </li> <li> - The <code>fox:outline</code> extension not implemented in this version anymore. + The <code>fox:outline</code> extension is not implemented in this version anymore. It has been superseded by the new bookmark elements from XSL-FO 1.1. </li> <li> |