configuration files are xml files, so keep them at least well-formed ;-)
</p>
<p>The file userconfig.xml is not read automatically, but the user must specify its use on
- the command line. See <jump href="running.html">Running Fop</jump> for details.
+ the command line. See <jump href="running.html">Running Fop</jump>
+ or <jump href="embedding.html">Embedding Fop</jump> for details.
</p>
</s2>
<s2 title="setting up hyphenation">
driver.run();
]]></source>
+ <p>To setup the user config file you can do the following
+ </p>
+ <source><![CDATA[
+ userConfigFile = new File(userConfig);
+ options = new Options(userConfigFile);
+]]></source>
<p>Once the Driver is set up, the render method
is called. Depending on whether DOM or SAX is being used, the
like XT or Xalan) or can be passed in memory as a DOM Document or (in
the case of XT) SAX events.
</p>
- <p>The latest version of Fop is 0.18 and it supports the xsl:fo candidate release.
+ <p>The latest version of Fop is 0.20.1 and it supports the xsl:fo candidate release.
You can <jump href="download.html">download</jump>
Fop including a precompiled version, the source code and many example files to
get you started. Pointers to introductions into xsl:fo can be found in the
values properly (including ones that change depending on the element) and
all possible values.
</p>
+ <p>
+To see if a property is implemented then look in the src/codegen/foproperties.xml file.
+ </p>
+ <p>
+To see if a particular element uses this property then look in the element code. This is generally found in the package org.apache.fop.fo.flow.*.
+ </p>
</s3>
<s3 title="Property Resolution">
<p>
</s3>
<s3 title="stream encoding">
<p>
-support for different encoding on different types of streams
+Support for different encoding on different types of streams
in pdf document.
+For example images.
</p>
</s3>
<s3 title="svg features">