From 78f92bdee60faf0480ea6a2751c3501b9a43c9ff Mon Sep 17 00:00:00 2001 From: fotis Date: Thu, 14 Dec 2000 18:11:45 +0000 Subject: documentation: spreading the word about configuration git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@193873 13f79535-47bb-0310-9956-ffa450edef68 --- docs/xml-docs/fop/configuration.xml | 14 ++++++++++++-- docs/xml-docs/fop/embedding.xml | 2 +- docs/xml-docs/fop/running.xml | 15 +++++++++++++-- 3 files changed, 26 insertions(+), 5 deletions(-) (limited to 'docs/xml-docs') diff --git a/docs/xml-docs/fop/configuration.xml b/docs/xml-docs/fop/configuration.xml index c5b896f51..6404485bb 100644 --- a/docs/xml-docs/fop/configuration.xml +++ b/docs/xml-docs/fop/configuration.xml @@ -1,9 +1,19 @@ - +

In the directory xml-fop/conf you will find two configuration files. One of them, + config.xml, is only intended for Fop developers, who want to add new default values + to some Fop feature. Don't change this file. For user configuration there is a file called + userconfig.xml. It contains templates for all settings a user can change. Most of them are + commented out. Uncomment the entry you want to set and change the value according to + your wishes. Please regard any comments which specify the value range. And, well, the + configuration files are xml files, so keep them at least well-formed ;-) +

+

The file userconfig.xml is not read automatically, but the user must specify its use on + the command line. See Running Fop for details. +

Fop comes already with some hyphenation pattern. If you need a hyphenation pattern @@ -28,7 +38,7 @@ be picked up and added to the fop.jar.

b) Put the file into a directory of your choice and specify this directory - in the userconfig.xml in the entry . + in the userconfig.xml in the entry <hyphenation-dir>.

diff --git a/docs/xml-docs/fop/embedding.xml b/docs/xml-docs/fop/embedding.xml index dbed2a95b..90c319f49 100644 --- a/docs/xml-docs/fop/embedding.xml +++ b/docs/xml-docs/fop/embedding.xml @@ -22,7 +22,7 @@ buildFOTree(Parser, InputSource) respectively.

A third possibility may be used to build the FO Tree, namely - calling getDocumentHandler() and firing the SAX events yourself. + calling getContentHandler() and firing the SAX events yourself.

Once the FO Tree is built, the format() and render() methods may be called in that order. diff --git a/docs/xml-docs/fop/running.xml b/docs/xml-docs/fop/running.xml index 4eea85359..b78212e6d 100644 --- a/docs/xml-docs/fop/running.xml +++ b/docs/xml-docs/fop/running.xml @@ -24,7 +24,7 @@

-

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

+

There are three 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) Batch processing xml files (includes production of the fo-files):

@@ -32,7 +32,7 @@

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.

+ each method in detail.

One is to first use an XSLT engine to produce the formatting object tree as an XML document and then running the class org.apache.fop.apps.CommandLine with the @@ -76,6 +76,17 @@

The viewer uses the swing classes.

+ +

Fop supports at the moment following commandline switches:

+ +

This switch informs you in case of an error of the method stack

+
+ +

The switch '-c' immediately followed by a file name, p.e. Userconfig.xml, tells Fop to use this + user configuration file. +

+
+

Ensure that you have a recent MRJ, and that you have downloaded and -- cgit v1.2.3