From a692c9b1e3837bc8f2da5eabe023bffebdccfc97 Mon Sep 17 00:00:00 2001 From: fotis Date: Mon, 7 Aug 2000 22:34:08 +0000 Subject: updates docs for coming release 0.14 git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@193610 13f79535-47bb-0310-9956-ffa450edef68 --- docs/html-docs/running.html | 40 +++++++++++++++++++++++++--------------- 1 file changed, 25 insertions(+), 15 deletions(-) (limited to 'docs/html-docs/running.html') diff --git a/docs/html-docs/running.html b/docs/html-docs/running.html index a5213a955..f2e3b20d7 100644 --- a/docs/html-docs/running.html +++ b/docs/html-docs/running.html @@ -24,20 +24,23 @@

a) Java 1.1.x or later (If you want to use AWTCommandLine, you need Swing)

b) An XML parser which supports SAX and DOM like Xerces-J. - (Xerces is the default xml parser)

-

c) If you have to produce the flow objects files, which are the input for FOP, - you need a transformation utility to create this files from your xml files. - Normally this is an XSLT stylesheet processor like - XT - or XALAN. + (Xerces is the default xml parser) +

+

c) Fop supports SVG (see Features for further information) and + needs the w3c.jar library. This library comes with Fop (xml-fop/lib) and must + be included in your classpath +

+

d) Optional: Fop supports the jimi library for image processing, if it is in your classpath + when you build Fop.


Starting FOP as an standalone application
 

There are two ways to run FOP from the command line.

a) Batch processing formatting objects (fo) files:

java org.apache.fop.apps.CommandLine fo-file pdf-file

- -

b) Previewing the fo-file:

+

b) Batch processing xml files (includes production of the fo-files):

+

java org.apache.fop.apps.XalanCommandLine xml-file xsl-file pdf-file

+

c) Previewing the fo-file:

java org.apache.fop.apps.AWTCommandLine fo-file

Each method uses next to the fop classes other packages. The following describes each method in detail.

@@ -61,8 +64,20 @@

org.apache.fop.apps.CommandLine fo-file pdf-file

Note: The xerces jar file must be included, because xp has no dom support.


- -
Method Two
  +-
Method Two
  +

Rather than performing transformation with an XSLT before invoking FOP, it is + possible, if you use Xalan as your XSLT engine, to just call FOP and have it call + Xalan for you. To do this, run the class org.apache.fop.apps.XalanCommandLine with the + source XML file name, XSL file name and PDF file name as arguments. You will + need to include Xalan in your classpath and so you might invoke +

+

java -cp fop.jar;xalan.jar;xerces.jar;w3c.jar

+

org.apache.fop.apps.XalanCommandLine xml-file xsl-file pdf-file

+

Again, if your SAX Parser is other than Xerces, you will need to set the property + org.xml.sax.parser to the SAX Parser class to use. +

+

+
Method Three
 

If you already produced the FO file, you can preview the results of your transformation without using any pdf viewer by invoking FOP with the viewer application. You will need to include FOP and your XML Parser in your classpath @@ -70,11 +85,6 @@

java -cp fop.jar;xerces.jar;w3c.jar

org.apache.fop.apps.AWTCommandLine fo-file

The viewer uses the swing classes.

-

Note: If you are using java 2 or later (i.e. jdk 1.2. or later) you can put all - needed jar files into the subdirectory jdk1.2.x\jre\lib\ext (windows example). Then - FOP can be started without classpath: -

-

java org.apache.fop.apps.CommandLine fo-file pdf-file



Running FOP on MacOS
  -- cgit v1.2.3