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>)
</known-issue>
- <known-issue>
- 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>).
- </known-issue>
<known-issue>
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.
<repository>
<SVNRepository>
<location rdf:resource="http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/"/>
- <browse rdf:resource="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/"/>
+ <browse rdf:resource="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/"/>
</SVNRepository>
</repository>
</Project>
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<document>
<header>
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<document>
<header>
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<document>
<header>
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<!-- Embedding FOP -->
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<document>
<header>
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<document>
<header>
<title>FOP: Fonts</title>
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<document>
<header>
<title>FOP: Graphics Formats</title>
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<document>
<header>
<title>FOP: Hyphenation</title>
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<!-- Output Formats: Renderers -->
<document>
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<document>
<header>
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<document>
<header>
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<document>
<header>
<title>Servlets</title>
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<document>
<header>
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<document>
<header>
<answer>
<p>
When it's ready and the committers have enough time to go through
- the time-consuming process of creating a release. We'll try to do
- a new release every 3 or 4 months, but that's no promise. If you
+ the time-consuming process of creating a release. We
+ released version 0.93 on 2 January 2007, and intend to
+ release version 1.0 later in 2007. If you
want to speed up the process, consider to
<link href="dev/index.html#involved">contribute</link> to FOP.</p>
</answer>
<faq id="redesign">
<question>Why did you redesign FOP?</question>
<answer>
- <p>The core redesign of FOP was necessary in order to be able to adress following issues:</p>
+ <p>The code redesign of FOP was necessary in order to be able to adress following issues:</p>
<ul>
<li>Keeps and Breaks</li>
<li>XSL-FO Compliance in general</li>
<p>
If you run FOP embedded in your servlet, web application or
other Java application, check the classpath of the
- application. Check the also the information pertaining <link
- href="0.20.5/servlets.html#servlet-engine">servlet engines</link>
+ application. Check the also the information pertaining to <link
+ href="0.93/servlets.html#servlet-engine">servlet engines</link>
for further hints.
</p>
<p>
<question>I get an OutOfMemoryException.</question>
<answer>
<p>
- See <link href="0.20.5/running.html#memory">FOP Memory</link>.
+ See <link href="0.93/running.html#memory">FOP Memory</link>.
</p>
</answer>
</faq>
<p>
If you use XSLT, problems in your style sheet and in your
source XML also can produce a NullPointerException. <link
- href="0.20.5/running.html#check-input">Run the transformation
+ href="0.93/running.html#check-input">Run the transformation
separately</link> to check for this, usually you'll get a
detailed error message from the XSLT processor.
</p>
<faq id="not-implemented">
<question>FOP returns the message "[ERROR] <em>object|property - 'x'</em> is not implemented yet." When will it be implemented?</question>
<answer>
- <p>See the article "<link href="gethelp.html#compliance">Review FOP's Standards Compliance</link>".</p>
+ <p>See FOP's Standards <link href="compliance.html">Compliance</link> page.</p>
</answer>
</faq>
<faq id="fop-hangs">
</p>
<p>
Try also setting the <link
- href="0.20.5/configuration.html#summary-key-value">fontBaseDir
+ href="0.93/configuration.html#general-elements">font-base
configuration</link>.
</p>
</answer>
<part id="part-output">
<title>Problems with FOP output</title>
<faq id="leader-expansion">
- <question>Leaders don't work anymore in 0.20.5. Instead of
+ <question>Leaders don't work anymore in 0.93. Instead of
filling the line, only three dots or a short ruler is
output.</question>
<answer>
</p>
<p>
The <link
- href="http://www.w3.org/TR/xsl/slice7.html#force-page-count">force-page-count
+ href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#force-page-count">force-page-count
property</link> controls how a FO processor pads page sequences in
order to get certain page counts or last page numbers. The default is
"<code>auto</code>". With this setting, if the next page sequence
<p>Other possibilities:</p>
<ul>
<li>The image format is not supported or not supported completely.
- See <link href="0.20.5/graphics.html">FOP Graphics Formats</link> for a
+ See <link href="0.93/graphics.html">FOP Graphics Formats</link> for a
list of supported formats and related issues.</li>
<li>The graphic may be too large to fit into the intended space.</li>
<li>There may be something (static content) that is obscuring the
<faq id="png-fails">
<question>My graphical images do not work properly.</question>
<answer>
- <p>See <link href="0.20.5/graphics.html">FOP Graphics Formats</link> for a
+ <p>See <link href="0.93/graphics.html">FOP Graphics Formats</link> for a
list of supported graphics formats and related issues.</p>
</answer>
</faq>
<faq id="graphic-resolution">
<question>Why is my graphic rendered at a different resolution than it was created?</question>
<answer>
- <p>See <link href="0.20.5/graphics.html#resolution">Graphics Resolution</link>.</p>
+ <p>See <link href="0.93/graphics.html#resolution">Graphics Resolution</link>.</p>
</answer>
</faq>
<faq id="keep-with">
<faq id="hyphenation-fails">
<question>Hyphenation does not work.</question>
<answer>
- <p>Make sure you have set the language and/or country attributes for an appropriate XSL-FO element (fo:page-sequence, fo:block or fo:character):</p>
+ <p>Make sure you have set the language and optionally the country attributes for an appropriate XSL-FO element (fo:page-sequence, fo:block or fo:character):</p>
<source><![CDATA[<fo:page-sequence language="fi">]]></source>
- <p>See <link href="0.20.5/hyphenation.html#support">Hyphenation Support</link> for details and instructions on using hyphenation with FOP.</p>
+ <p>See <link href="0.93/hyphenation.html#support">Hyphenation Support</link> for details and instructions on using hyphenation with FOP.</p>
<p>Explicitly enable hyphenation for an appropriate XSL-FO element (fo:block, fo:character):</p>
<source><![CDATA[<fo:block hyphenate="true">]]></source>
</answer>
<question>How do I use FOP in a servlet?</question>
<answer>
<p>
- See <link href="0.20.5/servlets.html">Using FOP in a Servlet</link>.
+ See <link href="0.93/servlets.html">Using FOP in a Servlet</link>.
</p>
</answer>
</faq>
transformation?</question>
<answer>
<p>
- See <link href="0.20.5/servlets.html#xslt">Using FOP in a Servlet with XSLT Transformation</link>.
+ See <link href="0.93/servlets.html#xslt">Using FOP in a Servlet with XSLT Transformation</link>.
</p>
</answer>
</faq>
<question>How do I pass parameters to the XSLT transformation?</question>
<answer>
<p>
- See <link href="0.20.5/servlets.html#xslt">Using FOP in a Servlet with XSLT Transformation</link>.
+ See <link href="0.93/servlets.html#xslt">Using FOP in a Servlet with XSLT Transformation</link>.
</p>
</answer>
</faq>
<question>How do I set the baseDir property in a servlet environment?</question>
<answer>
<p>
- See <link href="0.20.5/embedding.html#config-internal">Setting the Configuration Programmatically</link>.
+ See <link href="0.93/embedding.html#config-internal">Setting the Configuration Programmatically</link>.
</p>
</answer>
</faq>
<question>How do I use a user configuration file from a servlet?</question>
<answer>
<p>
- See <link href="0.20.5/embedding.html#config-external">Using a Configuration File in an Embedded App</link>.
+ See <link href="0.93/embedding.html#config-external">Using a Configuration File in an Embedded App</link>.
</p>
</answer>
</faq>
get FOP working for various servlet engines?</question>
<answer>
<p>
- See <link href="0.20.5/servlets.html#servlet-engine">Servlet Engines</link>.
+ See <link href="0.93/servlets.html#servlet-engine">Servlet Engines</link>.
</p>
</answer>
</faq>
<question>Can FOP be used in multithreaded environments?</question>
<answer>
<p>
- See <link href="0.20.5/embedding.html#multithreading">Multithreading FOP</link>.
+ See <link href="0.93/embedding.html#multithreading">Multithreading FOP</link>.
</p>
</answer>
</faq>
<question>The rendering of SVG text in my PDF is of poor quality.
Can I control this?</question>
<answer>
- <p>See <link href="0.20.5/graphics.html#svg-pdf-text">Placing SVG Text into PDF</link>.</p>
+ <p>See <link href="0.93/graphics.html#svg-pdf-text">Placing SVG Text into PDF</link>.</p>
</answer>
</faq>
<faq id="svg-headless">
<question>How do I use FOP with SVG on headless servers?</question>
<answer>
- <p>See <link href="0.20.5/graphics.html#batik">FOP: Graphics (Batik)</link>.</p>
+ <p>See <link href="0.93/graphics.html#batik">FOP: Graphics (Batik)</link>.</p>
</answer>
</faq>
<faq id="svghangs">
<faq id="svg-scaling">
<question>Why is my SVG rendered at a size different from that specified in my fo:external-graphic element?</question>
<answer>
- <p>See <link href="0.20.5/graphics.html#svg-scaling">SVG Scaling</link>.</p>
+ <p>See <link href="0.93/graphics.html#svg-scaling">SVG Scaling</link>.</p>
</answer>
</faq>
<faq id="svg-attribute-required">
<question>How do I embed fonts in PDF?</question>
<answer>
<p>
- See the <link href="0.20.5/fonts.html">Fonts</link> page for information
+ See the <link href="0.93/fonts.html">Fonts</link> page for information
about embedding fonts.
</p>
</answer>
set. For a variety of reasons, even those are not completely
guaranteed to work, for example you can't use the fi
ligature from the standard serif font. Check the <link
- href="0.20.5/output.html#pdf-fonts">overview</link> for the default
+ href="0.93/output.html#pdf-fonts">overview</link> for the default
PDF fonts.
</p>
<p>
the desired character. Furthermore the font must be
available on the machine where the PDF is viewed or it must
have been embedded in the PDF file. See <link
- href="0.20.5/fonts.html">embedding fonts</link>.
+ href="0.93/fonts.html">embedding fonts</link>.
</p>
<p>
For most symbols, it is better to select the symbol font
<faq id="pdf-postprocess">
<question>What tools are available for post-processing my PDF document?</question>
<answer>
- <p>See <link href="0.20.5/output.html#pdf-postprocess">PDF Post-processing</link>.</p>
+ <p>See <link href="0.93/output.html#pdf-postprocess">PDF Post-processing</link>.</p>
</answer>
</faq>
<faq id="pdf-security">
to my PDF document?</question>
<answer>
<p>
- See <link href="0.20.5/pdfencryption.html">PDF Encryption</link>.
- See also <link href="0.20.5/output.html#pdf-postprocess">PDF Post-processing</link>.
+ See <link href="0.93/pdfencryption.html">PDF Encryption</link>.
+ See also <link href="0.93/output.html#pdf-postprocess">PDF Post-processing</link>.
</p>
</answer>
</faq>
<question>How do I add document properties (title, author, etc.) to my
PDF document?</question>
<answer>
- <p>See <link href="0.20.5/output.html#pdf-postprocess">PDF Post-processing</link>.</p>
+ <p>See <link href="0.93/output.html#pdf-postprocess">PDF Post-processing</link>.</p>
</answer>
</faq>
<faq id="pdf-watermark">
<question>How do I add watermarks to my PDF document?</question>
<answer>
- <p>See <link href="0.20.5/output.html#pdf-watermark">PDF Watermarks</link>.</p>
+ <p>See <link href="0.93/output.html#pdf-watermark">PDF Watermarks</link>.</p>
</answer>
</faq>
<faq id="pdf-print-contortion">
<answer>
<p>
This is a problem of Internet Explorer requesting the content several
- times. Please see the <link href="0.20.5/servlets.html#ie">notes on Internet Explorer</link>
+ times. Please see the <link href="0.93/servlets.html#ie">notes on Internet Explorer</link>
for more information.
</p>
</answer>
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<document>
<header>
<title>XSL-FO Input</title>
<link href="http://www.renderx.com">RenderX</link> has provided an <link href="http://www.renderx.com/Tests/validator/fo.dtd.html">Unofficial DTD for FO Documents</link>, which may be helpful in validating general FO issues.
</p>
<p>
- FOP also maintains an <link href="http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-fop/src/foschema/fop.xsd?rev=HEAD&content-type=text/plain">Unofficial FOP Schema</link> in the FOP CVS Repository.
+ FOP also maintains an <link href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop.xsd?view=co">Unofficial FOP Schema</link> in the FOP CVS Repository.
This document can be used either to validate against the FO standard, or against the actual FOP implementation.
See the notes near the beginning of the document for instructions on how to use it.
</p>
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<document>
<header>
-->
<!-- $Id$ -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
<document>
<header>
<version>$Revision$</version>
</header>
<body>
+ <section>
+ <title>2 January 2007 - Apache FOP 0.93 released</title>
+ <p>
+ The Apache FOP team is proud to present to you the first
+ production grade release of the new FOP codebase. This release
+ has the new API first introduced in release 0.92 beta. It
+ contains again many bug fixes and new features.
+ </p>
+ </section>
<section>
<title>16 October 2006 - New Committer</title>
<p>Welcome Vincent Hennebert!</p>
<resources label="Resources" href="dev/" tab="development">
<faq label="FAQs" href="faq.html"/>
<tools label="Tools" href="tools.html"/>
- <viewcvs label="ViewCVS" href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop"/>
+ <viewcvs label="ViewVC" href="http://svn.apache.org/viewvc/xmlgraphics/fop"/>
</resources>
<subpackages label="SubPackages" href="dev/" tab="development">
<body>
<section>
<title>Status</title>
- <p>[last updated December 19, 2005]</p>
+ <p>[last updated 2 January 2007]</p>
<figure width="585" height="175" src="images/track.png" alt="Planning and branches of FOP development"/>
<p>
- This is the development status of Apache FOP. Development on the maintenance branch where
- FOP 0.20.5 came from has been halted as the focus was transferred entirely to the redesign effort.
+ This is the development status of Apache FOP. Development on
+ the maintenance branch where FOP 0.20.5 came from has been
+ halted. The code base has been largely redesigned. The new
+ code base has reached release 0.93.
</p>
</section>
<section>
<title>Development Status</title>
- <p>
- Development for FOP Trunk (aka Redesign) is addressing the design issues for layout and
- performance. The new design is focusing on making it possible to be conformant
- to the spec and be able to handle large documents.
- </p>
- <p>
- The first preview release (0.90alpha1) had similar functionality
- to previous FOP releases (although not in every point), some new features
- (like keeps on all implemented FOs), a rough API and a suitable design for
- developers to work on more functionality. It turned out that the new code
- is more stable and useful than we thought. In the meantime many of the
- problems reported since the initial release have already been resolved.
- </p>
- <p>
- We now have a good overall design and have been able to add several new features
- besides recreating most of the features from 0.20.5. We are doing ongoing work
- to make it easier for newbies to jump in and help. Furthermore, an extensive
- test suite helps us maintain and improve the quality of the package.
- </p>
- <p>
- Of course, we also welcome any help on the layout managers. So if you
- want to push your brain to the limit, come and join us! But don't worry:
- there are also various other locations where you can find an easier start
- into the code. And we're glad to help you get jumpstarted. Just ask!
- </p>
+ <p>The FOP code base has been largely rewritten, to address
+ design issues for layout and performance. The new design makes
+ it better possible to be conformant to the spec and be able to
+ handle large documents.</p>
+ <p>The redesign of the code base has largely been completed. The
+ new code reached production quality with release 0.93. In the
+ course of 2007 we plan to release version 1.0.</p>
<p>
If you're looking for a long-term road-map we have to disappoint you. This is Open
Source and we're mostly voluteers working in their free time. What we have
<section>
<title>Maintenance Status</title>
<p>
- The latest maintenance release is FOP 0.20.5, released on July 18th, 2003.
- See <a href="relnotes.html">release notes</a> for more details.
- The maintenance branch has been frozen in 2004 so the team can concentrate
- on the redesign efforts.
+ The latest release of the maintenance branch is FOP 0.20.5,
+ released on July 18th, 2003. See <a
+ href="relnotes.html">release notes</a> for more details. The
+ maintenance branch has been frozen in 2004 so the team can
+ concentrate on the new code base.
</p>
</section>
<!--section id="stats">
-->
<!-- $Id$ -->
<!DOCTYPE tabs PUBLIC "-//APACHE//DTD Cocoon Documentation Tab V1.0//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/tab-cocoon-v10.dtd">
+ "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/tab-cocoon-v10.dtd?view=co">
<tabs software="FOP" title="FOP" copyright="@year@ The Apache Software Foundation" xmlns:xlink="http://www.w3.org/1999/xlink">
<tab label="Home" dir=""/>
<section id="intro">
<title>Introduction</title>
<p>
- <strong>FOP Trunk</strong> is the name for the current development code as found in the
- <a href="ext:svn-repo/trunk">Subversion repository</a>. This section of the FOP provides
- the documentation for this version.
+ <strong>FOP Trunk</strong> is the name for the current
+ development code as found in the <a
+ href="ext:svn-repo/trunk">Subversion repository</a>. This
+ section of the FOP web site provides the documentation for
+ this version.
</p>
<p>
The Apache FOP team is proud to present to you the largely rewritten codebase which is
finally in a state where you can start to use it. It has taken over three years to get this
- far and over two years without a new release from the FOP project. We would like to encourage
- you to download the code and to play with it. We're still in the process of adding new major
- features and stabilizing the code. We welcome any feedback you might have and even more, any
+ far and over two years without a new release from the FOP project. We're still in the process of adding new
+ features. We welcome any feedback you might have and even more, any
other form of help to get the project forward.
</p>
</section>
</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>
<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
</release>
<release version="0.93" date="2 January 2007">
<notes>
- <p>This is the first stable release after the big redesign
- effort.</p>
+ <p>This is the first production grade release of the new FOP
+ codebase.</p>
<ul>
- <li>The API was first introduced in release 0.92 beta. The
- preceding API has been removed.
+ <li>It contains the new API first introduced in release 0.92
+ beta. The preceding API has been removed.
</li>
<li>
See the <a href="../compliance.html">compliance page</a> for an
projects / xmlgraphics-fop.git / commitdiff