build.xml is the replacement of makefile. Look there for detailed information on the build
process and different targets. </p>
<p>A help screen is shown by calling "build usage".</p>
- <p>If you only want to use Fop, you don't need to build it. A fop.jar comes with the distribution.</p>
+ <p>If you only want to use FOP, you don't need to build it. A fop.jar comes with the distribution.</p>
<section>
<title>Setting up your classpath</title>
- <note>You don't have to setup your classpath; all libraries needed to compile Fop are coming with
+ <note>You don't have to setup your classpath; all libraries needed to compile FOP are coming with
the distribution and are referenced by the build script, so you only need to care about them,
- if you build Fop in any other way. See build.bat/build.sh for details. </note>
+ if you build FOP in any other way. See build.bat/build.sh for details. </note>
</section>
<section>
<title>Setting of JAVA_HOME</title>
</section>
<section>
<title>Problems</title>
- <p>If you have problems compiling Fop, please try this first: </p>
+ <p>If you have problems compiling FOP, please try this first: </p>
<ul>
<li>delete the build directory completely and try a new build from scratch</li>
<li>check, whether you have an older version of xerces.jar, xalan.jar, batik.jar somewhere in
on AnonCVS in the <link href="http://xml.apache.org/cvs.html">xml.apache.org documentation</link> for details.
Sometimes people have difficulties to access the cvs server; in this case you can download
a snapshot from the cvs files <link href="http://xml.apache.org/from-cvs/xml-fop/">here</link>.
- In both cases you have to build Fop yourself - see <link href="compiling.html">Compiling Fop</link> for details.
+ In both cases you have to build FOP yourself - see <link href="compiling.html">Compiling FOP</link> for details.
</p>
<note>
Important: Currently, releases of FOP are coming out of the
examples/fo/basic for a more complete example.
</p>
</section>
+ <section>
+ <title>Continued-label (for table-header/-footer</title>
+ <p>
+Please see examples/fo/basic/contlabel.fo
+ </p>
+ </section>
</section>
<section>
<title>Adding Your Own</title>
The PDF files on this site are created using current CVS.
</note>
<figure width="480" height="260" src="images/document.jpg" alt="Render Diagram" />
- <p>The latest version of Fop is 0.20.4 and it supports the
+ <p>The latest version of FOP is 0.20.5 and it supports the
<link href="http://www.w3.org/TR/2001/REC-xsl-20011015/">XSL-FO Version 1.0
W3C Recommendation</link>.
You can <link href="download.html">download</link>
- Fop including a precompiled version, the source code and many example files to
+ FOP including a precompiled version, the source code and many example files to
get you started. Pointers to introductions into xsl:fo can be found in the
<link href="resources.html">resources</link> section. Please be aware, that
- Fop is at the moment not a full implementation of the basic conformance level
+ FOP is at the moment not a full implementation of the basic conformance level
of the xsl:fo standard. You can find a list of supported flow objects and properties
in the section <link href="implemented.html">Features</link> and in section
<link href="limitations.html">Limitations</link> in what way this support is
<title>News</title>
</header>
<body>
+ <section>
+ <title>23 December 2002 - Official FOP Wiki</title>
+ <p>
+ See <link href="http://nagoya.apache.org/wiki/apachewiki.cgi?FOPProjectPages"
+ >FOP project pages</link> at the ApacheWiki.
+ </p>
+ </section>
+ <section>
+ <title>10 December 2002 - FOP 0.20.5 Release Candidate available</title>
+ <p>
+ See the full text of the <link
+ href="http://marc.theaimsgroup.com/?l=fop-user&m=103954279712704&w=2"
+ >announcement</link>.
+ </p>
+ </section>
+ <section>
+ <title>23 November 2002 - EXLSFO project has been created</title>
+ <p>
+ The EXSLFO project is a community effort to define functional extensions
+ to thet XSL Formatting Objects specification. See the
+ <link href="http://exslfo.sourceforge.net">EXSLFO website</link> for details.
+ </p>
+ </section>
<section>
<title>22 November 2002 - New Committer</title>
<p>Welcome Victor Mote!</p>
<document>
<header>
<title>Release Notes</title>
- <subtitle>Fop 0.20.4</subtitle>
- <authors>
- <person name="Christian Geisert" email=""/>
- </authors>
</header>
<body>
+<section>
+ <title>FOP 0.20.5</title>
+ <p>This is the last planed release in the 0.20.x series (aka maintenance branch).</p>
+ <p>Important changes since the last release (0.20.4):</p>
+ <ul>
+ <li>Documentation is done with <link href="http://xml.apache.org/forrest/">
+ Forrest</link>. You need to install Forrest if you want build the docs
+ yourself. (See
+ <link href="http://xml.apache.org/forrest/your-project.html">Using Forrest</link>)
+ </li>
+ <li>The following JARs have been updated:
+ Xerces to version 2.2.1, Xalan to version 2.4.1 and Batik to version 1.5beta4.
+ </li>
+ <li>Fop has been compiled with Jimi support this time but you still have to download
+ <link href="http://java.sun.com/products/jimi/">Jimi</link>, extract the archive,
+ copy JimiProClasses.zip to FOP's lib dir and rename it to jimi-1.0.jar.
+ </li>
+ <li>Fop has been compiled with
+ <link href="http://java.sun.com/products/java-media/jai/JAI">JAI</link>
+ support. For using JAI you just need to install it.
+ </li>
+ <li>Links in PDF won't generate multiple link rectangles anymore. If this causes
+ a problem you can set the system property "links.merge" to "no".
+ </li>
+ </ul>
+
+</section>
<section>
<title>FOP 0.20.4</title>
<p>Important changes since 0.20.3:</p>
<title>Starting FOP as a standalone application</title>
<p>Review the batch file fop.bat or the shell script fop.sh to see how FOP is invoked.</p>
<p>The standard scripts for starting FOP require that the environment variable JAVA_HOME be set to a path pointing to the appropriate Java installation on your system. Macintosh OSX includes a Java environment as part of its distribution. We are told by Mac OSX users that the path to use in this case is <code>/Library/Java/Home</code>. <strong>Caveat: </strong>We suspect that, as Apple releases new Java environments and as FOP upgrades the minimum Java requirements, the two will inevitably not match on some systems. Please see <jump href="http://developer.apple.com/java/faq">Java on Mac OSX FAQ</jump> for information as it becomes available.</p>
- <p><code>Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-pcl|-txt|-svg|-at|-print] <outfile></code></p>
+ <p><code>fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-pcl|-ps|-txt|-svg|-at|-print] <outfile></code></p>
<p>[OPTIONS]</p>
<source>
-d debug mode<br/>
-awt input will be displayed on screen<br/>
-mif outfile input will be rendered as mif file (outfile req'd)<br/>
-pcl outfile input will be rendered as pcl file (outfile req'd)<br/>
- -txt outfile input will be rendered as text file (outfile req'd)<br/> -svg outfile input will be rendered as an svg slides file (outfile req'd)
+ -ps outfile input will be rendered as PostScript file (outfile req'd)<br/>
+ -txt outfile input will be rendered as text file (outfile req'd)<br/>
+ -svg outfile input will be rendered as an svg slides file (outfile req'd)
-at outfile representation of area tree as XML (outfile req'd)
-print input file will be rendered and sent to the printer<br/> see options with "-print help"<br/></source>
<p>[Examples]</p>
<source>
- Fop foo.fo foo.pdf<br/>
- Fop -fo foo.fo -pdf foo.pdf (does the same as the previous line)<br/>
- Fop -xsl foo.xsl -xml foo.xml -pdf foo.pdf<br/>
- Fop foo.fo -mif foo.mif<br/>
- Fop foo.fo -print or Fop -print foo.fo<br/>
- Fop foo.fo -awt<br/></source>
+ fop foo.fo foo.pdf<br/>
+ fop -fo foo.fo -pdf foo.pdf (does the same as the previous line)<br/>
+ fop -xsl foo.xsl -xml foo.xml -pdf foo.pdf<br/>
+ fop foo.fo -mif foo.mif<br/>
+ fop foo.fo -print or Fop -print foo.fo<br/>
+ fop foo.fo -awt<br/></source>
</section>
<section>
<document>
<header>
- <title>SVG</title>
- <subtitle>Embedding SVG in FOP</subtitle>
+ <title>Testing FOP</title>
</header>
<body>
-<section>
- <title>Testing FOP</title>
<section>
<title>Running and Using Tests</title>
<p>
testing is how the SVG image is embedded inside the flow of the fo document.
</p>
</section>
-</section>
</body>
</document>
projects / xmlgraphics-fop.git / commitdiff