# This is an example configuration file for refdbxml, the XML transformation
# tool of RefDB
# RefDB is a reference database and bibliography tool, see
# http://refdb.sourceforge.net for further information

# Syntax rules of this file:
# 1. Each line contains a pair of variable name and variable value, 
#    separated by whitespace.
# 2. The hash (#) denotes the start of a comment, the rest of the line
#    will be ignored
# 3. The line ending must be Unix-style (LF) regardless of the operating
#    system


# Note: Each of these options can be overridden at execution time by
# invoking refdbxml with command line options.
# To see the available options, type 'refdbxml -h' or refer to the manual.


## XSLT processor.
# An xslt processor is used to transform your DocBook xml document to
# (x)html or fo.
# Currently available choices are:
#   xalan
#   xt
#   xsltproc (default)
#   saxon
#   saxon-xerces
# Note: 'saxon-xerces' refers to the saxon xslt processor using the
# xerces xml parser from Apache.
# Note: 'saxon', both with and without 'xerces', will use the Apache resolver.
# Note: _You_ must ensure that the xslt processor is installed and
# correctly configured.  RefDB does not check for processors other than the
# default xsltproc.
#xslt_processor	xsltproc

## XSLT classpath
# You only need to set this variable if your XSLT processor is java-based.
# If it's not java-based (eg. xsltproc), don't set this variable.
# Some XSLT processors _are_ java-based (including xalan, xt and saxon)
# and need to access certain directories and java class files.
# This is done by specifying a classpath.
# Refer to the application's documentation for further information
# about the necessary classpath.
# One approach is to choose a directory and put in it symlinks to
# the required jars, so the classpath may be something like:
#   /usr/share/java
# Do not use backslashes to concatenate lines.
#xslt_classpath	<classpath_root>

## FO processor
# When producing printed output the xslt processor produces a "formatted
# objects" file (.fo).  An FO processor then transforms this to printed
# output.
# Currently available choices are:
#   fop (default)        -> pdf output
#   passivetex           -> pdf output
#   xep                  -> pdf output
#   jfor                 -> rtf output
# Note: _You_ must ensure that the fo processor is installed and
# correctly configured.  RefDB does not check.
#fo_processor	fop

## FO classpath
# You only need to set this variable if your FO processor is java-based.
# If it's not java-based (eg. passivetex), don't set this variable.
# Some FO processors _are_ java-based (including fop, xep and jfor)
# and need to access certain directories and java class files.
# This is done by specifying a classpath.
# Refer to the application's documentation for further information
# about the necessary classpath.
# One approach is to choose a directory and put in it symlinks to
# the required jars, so the classpath may be something like:
#   /usr/share/java
# Do not use backslashes to concatenate lines.
#fo_classpath	<classpath_root>

## FOP configuration file (optional). This option is useful to add font
## support to FOP
#fop_config_file	/path/to/your/config/file

## FOP command. Usually a shell script provided by FOP
#fop_command fop

## Include following variables to cover all command line options
## Not needed with refdbnd/make system

## stylesheet
# refdbxml currently sets no stylesheet default, relying on command line
# option.  I'll do the same.
#stylesheet		

## output format
# The format of the output file.
# Current options are:
#   html (default)
#   pdf
#   rtf
# refdbxml currently sets outformat to html as default. I'll do the same.
#outformat	html
