From 03b1fae3c7cf3b50ee066f4fdd103f2de560dba4 Mon Sep 17 00:00:00 2001 From: William Victor Mote Date: Wed, 9 Jul 2003 16:06:14 +0000 Subject: [PATCH] reformulate introductory section for clarity git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196664 13f79535-47bb-0310-9956-ffa450edef68 --- .../content/xdocs/configuration.xml | 27 +++++++++---------- 1 file changed, 13 insertions(+), 14 deletions(-) diff --git a/src/documentation/content/xdocs/configuration.xml b/src/documentation/content/xdocs/configuration.xml index c7160ab4d..38bc9b49c 100644 --- a/src/documentation/content/xdocs/configuration.xml +++ b/src/documentation/content/xdocs/configuration.xml @@ -4,24 +4,23 @@
- Configuration + FOP: Configuration
- How to configure FOP -

In the directory {fop-dir}/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 - or Embedding FOP for details. -

+ Configuration File Basics +

The FOP configuration file is an XML file contains a variety of settings that are useful for controlling FOP's behavior, and for helping it find resources that you wish it to use.

+

The easiest way to get started using a FOP configuration file is to copy the sample found at {fop-dir}/conf/userconfig.xml to a location of your choice, and then to edit it according to your needs. +It contains templates for the various configuration options, most of which are commented out. Remove the comments and change the settings for entries that you wish to use. +Be sure to follow any instructions, including comments which specify the value range. +Also, since the configuration file is XML, be sure to keep it well-formed.

+ Do not change {fop-dir}/conf/config.xml or use it as the basis for your configuration file. It has an entirely different purpose. +

After creating your configuration file, you must tell FOP how to find it:

+
    +
  • If running FOP from the command-line, see the "-c" command-line option in Running FOP.
  • +
  • If running FOP as an embedded application, see FOP: Embedding, Using a Configuration File.
  • +
Setting up hyphenation -- 2.39.5