Running FOP


	Prerequisites

Following software must be installed:

a) Java 1.1.x or later (If you want to use the previewer (option -awt), you need Swing or Java 2)

b) All libraries you need are part of the Fop distribution and can be found in the xml-fop/lib directory. Look at the batch/shell script fop.bat/fop.sh to see, how Fop can be invoked easily. These libraries are included:

An XML parser which supports SAX and DOM like Xerces-J. (Xerces is the default xml parser)
An XSLT processor
The SVG library batik.jar is the library from the batik project at xml.apache.org.
The imaging library Jimi from Sun


	Starting FOP as an standalone application

Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-pcl|-txt|-print] <outfile>

[OPTIONS]


	-d debug mode -x dump configuration settings -q quiet mode -c cfg.xml use additional configuration file cfg.xml -l lang the language to use for user information

[INPUT]


	infile xsl:fo input file (the same as the next) -fo infile xsl:fo input file -xml infile xml input file, must be used together with -xsl -xsl stylesheet xslt stylesheet

[OUTPUT]

      outfile           input will be rendered as pdf file into outfile

      -pdf outfile      input will be rendered as pdf file (outfile req'd)

      -awt              input will be displayed on screen

      -mif outfile      input will be rendered as mif file (outfile req'd)

      -pcl outfile      input will be rendered as pcl file (outfile req'd)

      -txt outfile      input will be rendered as text file (outfile req'd)

      -print            input file will be rendered and sent to the printer

                        see options with "-print help"

[Examples]

      Fop foo.fo foo.pdf

      Fop -fo foo.fo -pdf foo.pdf (does the same as the previous line)

      Fop -xsl foo.xsl -xml foo.xml -pdf foo.pdf

      Fop foo.fo -mif foo.mif

      Fop foo.fo -print or Fop -print foo.fo

      Fop foo.fo -awt


	Problems

If you have problems running FOP, please have a look at the FOP FAQ. If you don't find a solution there, you can ask for help on the list fop-dev@xml.apache.org. Maybe it is a bug and maybe somebody is already working on it.