xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r840560 [1/16] - in /websites/staging/xmlgraphics/trunk/content: ./ fop/0.95/ fop/1.0/ fop/1.1/ fop/trunk/
Date Mon, 03 Dec 2012 15:47:54 GMT
Author: buildbot
Date: Mon Dec  3 15:47:41 2012
New Revision: 840560

Log:
Staging update by buildbot for xmlgraphics

Modified:
    websites/staging/xmlgraphics/trunk/content/   (props changed)
    websites/staging/xmlgraphics/trunk/content/fop/0.95/anttask.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/compiling.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/configuration.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/embedding.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/extensions.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/fonts.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/graphics.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/hyphenation.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/intermediate.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/metadata.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/output.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/running.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/servlets.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/accessibility.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/anttask.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/compiling.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/configuration.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/embedding.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/events.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/extensions.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/fonts.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/graphics.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/hyphenation.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/intermediate.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/metadata.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/output.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfa.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfencryption.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/running.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/servlets.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/accessibility.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/anttask.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/compiling.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/complexscripts.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/configuration.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/embedding.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/events.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/extensions.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/fonts.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/graphics.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/hyphenation.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/intermediate.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/metadata.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/output.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfa.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfencryption.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/running.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/servlets.html
    websites/staging/xmlgraphics/trunk/content/fop/trunk/configuration.html
    websites/staging/xmlgraphics/trunk/content/fop/trunk/embedding.html
    websites/staging/xmlgraphics/trunk/content/fop/trunk/extensions.html
    websites/staging/xmlgraphics/trunk/content/fop/trunk/output.html
    websites/staging/xmlgraphics/trunk/content/fop/trunk/servlets.html

Propchange: websites/staging/xmlgraphics/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec  3 15:47:41 2012
@@ -1 +1 @@
-1416525
+1416565

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/anttask.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/anttask.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/anttask.html Mon Dec  3 15:47:41 2012
@@ -341,68 +341,134 @@ $(document).ready(function () {
         <div id="items">
         </div>
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></div> -->
-      	<div class="section-content"><h1 id="apachewzxhzdk1-fop-ant-task">Apache&trade; FOP: Ant task</h1>
+      	<div class="section-content"><h1 id="apachewzxhzdk3-fop-ant-task">Apache&trade; FOP: Ant task</h1>
 <p>Apache&trade; FOP provides an Ant task for automating the document build process.</p>
-<h2 id="description-wzxhzdk3wzxhzdk4">Description <a id="basics"></a></h2>
+<h2 id="description-wzxhzdk5wzxhzdk6">Description <a id="basics"></a></h2>
 <p>The FOP Ant task will convert XSL-FO documents to PDF, PS, PCL etc. output (see <a href="output.html">Output formats</a> for available formats).</p>
 <p>To call FOP tasks within Ant, first add a FOP task definition to your Ant build file. One method of defining the task is as follows:</p>
-<property name="fop.home" value="....path to your FOP HOME directory..."/>
+<div class="codehilite"><pre><span class="nt">&lt;property</span> <span class="na">name=</span><span class="s">&quot;fop.home&quot;</span> <span class="na">value=</span><span class="s">&quot;....path to your FOP HOME directory...&quot;/</span><span class="nt">&gt;</span>
 
-<taskdef name="fop" 
-         classname="org.apache.fop.tools.anttasks.Fop">
-  <classpath>
-    <fileset dir="${fop.home}/lib">
-      <include name="*.jar"/>
-    </fileset>
-    <fileset dir="${fop.home}/build">
-      <include name="fop.jar"/>
-      <include name="fop-hyph.jar" />
-    </fileset>
-  </classpath>
-</taskdef>
-
-Then create FOP tasks within your Ant build file, using the FOP task parameters listed below.
-
-## Parameters for FOP Ant task <a id="parameters"></a>
-
-<caption>Parameters specified as attributes</caption>| Attribute | Description | Required |
-|-----------|-------------|----------|
-| fofile | XSL-FO file to be rendered | Yes, if no fileset nested element is used |
-| outfile | Output filename | Yes, when fofile is used. (This attribute is not valid for filesets.) |
-| format | Possible output formats:<br></br> `application/X-fop-awt-preview` <br></br> `application/X-fop-print` <br></br> `application/X-fop-areatree` <br></br> `application/pdf` <br></br> `application/postscript` <br></br> `application/mif` <br></br> `application/rtf` , `text/richtext` , `text/rtf` <br></br> `application/x-pcl` , `application/vnd.hp-PCL` <br></br> `application/x-afp` , `application/vnd.ibm.modcap` <br></br> `text/plain` <br></br> `image/svg+xml` <br></br> `image/gif` <br></br> `image/png` <br></br> `image/tiff` <br></br> | No, defaults to `application/pdf`  |
-| outdir | Output directory | Required if a fileset is used to specify the files to render; optional for fofile. (Can alternatively specify the full path in the fofile value.) |
-| force | Recreate target files, even if they are newer than their corresponding source files. Note: This attribute is available in post-0.20.5 versions (0.20.x nightly build and 1.0dev) only; target files are always generated (i.e., force=true) in 0.20.5 release. | No, default is `false`  |
-| basedir | Base directory to resolve relative references (e.g., graphics files) within the FO document. | No, for single FO File entry, default is to use the location of that FO file. |
-| relativebase | For fileset usage only. A value of `true` specifies using the location of each .fo file as the base directory for resolving relative file references located within that .fo file. A value of `false` specifies using the value of basedir for all files within the fileset, or just the current working directory if basedir is not specified. | No, default is `false` . |
-| userconfig | User configuration file (same as the FOP "-c" command line option). | No |
-| messagelevel | Logging level<br></br>Possible values: `error` , `warn` , `info` , `verbose` , `debug` . **Currently doesn't work in FOP Trunk!!!**  | No, defaults to `verbose`  |
-| logFiles | Controls whether the names of the files that are processed are logged ( `true` ) or not ( `false` ). **Currently doesn't work in FOP Trunk!!!**  | No, default is `true`  |
-
-<caption>Parameters specified as nested elements</caption>| Attribute | Description | Required |
-|-----------|-------------|----------|
-| fileset |  [FileSets](http://ant.apache.org/manual/CoreTypes/fileset.html) are used to specify multiple XSL-FO files to be rendered. | Yes, if no fofile attribute is supplied |
-
-## Examples <a id="examples"></a>
-
-The following example converts a single XSL-FO file to a PDF document:
-
-    <target name="generate-pdf" description="Generates a single PDF file">
-       <fop format="application/pdf" 
-            fofile="c:\working\foDirectory\foDocument.fo"
-            outfile="c:\working\pdfDirectory\pdfDocument.pdf" />
-    </target>
-
-This example converts all XSL-FO files within an entire directory to PostScript:
-
-    <target name="generate-multiple-ps" 
-            description="Generates multiple PostScript files">
-       <fop format="application/postscript" 
-            outdir="${build.dir}" messagelevel="debug">
-            <fileset dir="${fo.examples.dir}">
-               <include name="*.fo"/>
-            </fileset>
-       </fop>
-    </target></div>
+<span class="nt">&lt;taskdef</span> <span class="na">name=</span><span class="s">&quot;fop&quot;</span> 
+         <span class="na">classname=</span><span class="s">&quot;org.apache.fop.tools.anttasks.Fop&quot;</span><span class="nt">&gt;</span>
+  <span class="nt">&lt;classpath&gt;</span>
+    <span class="nt">&lt;fileset</span> <span class="na">dir=</span><span class="s">&quot;</span><span class="cp">${</span><span class="n">fop</span><span class="o">.</span><span class="n">home</span><span class="cp">}</span><span class="s">/lib&quot;</span><span class="nt">&gt;</span>
+      <span class="nt">&lt;include</span> <span class="na">name=</span><span class="s">&quot;*.jar&quot;/</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;/fileset&gt;</span>
+    <span class="nt">&lt;fileset</span> <span class="na">dir=</span><span class="s">&quot;</span><span class="cp">${</span><span class="n">fop</span><span class="o">.</span><span class="n">home</span><span class="cp">}</span><span class="s">/build&quot;</span><span class="nt">&gt;</span>
+      <span class="nt">&lt;include</span> <span class="na">name=</span><span class="s">&quot;fop.jar&quot;/</span><span class="nt">&gt;</span>
+      <span class="nt">&lt;include</span> <span class="na">name=</span><span class="s">&quot;fop-hyph.jar&quot;</span> <span class="nt">/&gt;</span>
+    <span class="nt">&lt;/fileset&gt;</span>
+  <span class="nt">&lt;/classpath&gt;</span>
+<span class="nt">&lt;/taskdef&gt;</span>
+</pre></div>
+
+
+<p>Then create FOP tasks within your Ant build file, using the FOP task parameters listed below.</p>
+<h2 id="parameters-for-fop-ant-task-wzxhzdk7wzxhzdk8">Parameters for FOP Ant task <a id="parameters"></a></h2>
+<p><caption>Parameters specified as attributes</caption></p>
+<table>
+<thead>
+<tr>
+<th>Attribute</th>
+<th>Description</th>
+<th>Required</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>fofile</td>
+<td>XSL-FO file to be rendered</td>
+<td>Yes, if no fileset nested element is used</td>
+</tr>
+<tr>
+<td>outfile</td>
+<td>Output filename</td>
+<td>Yes, when fofile is used. (This attribute is not valid for filesets.)</td>
+</tr>
+<tr>
+<td>format</td>
+<td>Possible output formats:<br></br> <code>application/X-fop-awt-preview</code> <br></br> <code>application/X-fop-print</code> <br></br> <code>application/X-fop-areatree</code> <br></br> <code>application/pdf</code> <br></br> <code>application/postscript</code> <br></br> <code>application/mif</code> <br></br> <code>application/rtf</code> , <code>text/richtext</code> , <code>text/rtf</code> <br></br> <code>application/x-pcl</code> , <code>application/vnd.hp-PCL</code> <br></br> <code>application/x-afp</code> , <code>application/vnd.ibm.modcap</code> <br></br> <code>text/plain</code> <br></br> <code>image/svg+xml</code> <br></br> <code>image/gif</code> <br></br> <code>image/png</code> <br></br> <code>image/tiff</code> <br></br></td>
+<td>No, defaults to <code>application/pdf</code></td>
+</tr>
+<tr>
+<td>outdir</td>
+<td>Output directory</td>
+<td>Required if a fileset is used to specify the files to render; optional for fofile. (Can alternatively specify the full path in the fofile value.)</td>
+</tr>
+<tr>
+<td>force</td>
+<td>Recreate target files, even if they are newer than their corresponding source files. Note: This attribute is available in post-0.20.5 versions (0.20.x nightly build and 1.0dev) only; target files are always generated (i.e., force=true) in 0.20.5 release.</td>
+<td>No, default is <code>false</code></td>
+</tr>
+<tr>
+<td>basedir</td>
+<td>Base directory to resolve relative references (e.g., graphics files) within the FO document.</td>
+<td>No, for single FO File entry, default is to use the location of that FO file.</td>
+</tr>
+<tr>
+<td>relativebase</td>
+<td>For fileset usage only. A value of <code>true</code> specifies using the location of each .fo file as the base directory for resolving relative file references located within that .fo file. A value of <code>false</code> specifies using the value of basedir for all files within the fileset, or just the current working directory if basedir is not specified.</td>
+<td>No, default is <code>false</code> .</td>
+</tr>
+<tr>
+<td>userconfig</td>
+<td>User configuration file (same as the FOP "-c" command line option).</td>
+<td>No</td>
+</tr>
+<tr>
+<td>messagelevel</td>
+<td>Logging level<br></br>Possible values: <code>error</code> , <code>warn</code> , <code>info</code> , <code>verbose</code> , <code>debug</code> . <strong>Currently doesn't work in FOP Trunk!!!</strong></td>
+<td>No, defaults to <code>verbose</code></td>
+</tr>
+<tr>
+<td>logFiles</td>
+<td>Controls whether the names of the files that are processed are logged ( <code>true</code> ) or not ( <code>false</code> ). <strong>Currently doesn't work in FOP Trunk!!!</strong></td>
+<td>No, default is <code>true</code></td>
+</tr>
+</tbody>
+</table>
+<p><br/></p>
+<table>
+<thead>
+<tr>
+<th><caption>Parameters specified as nested elements</caption></th>
+<th>Attribute</th>
+<th>Description</th>
+<th>Required</th>
+<th></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td></td>
+<td>fileset</td>
+<td><a href="http://ant.apache.org/manual/CoreTypes/fileset.html">FileSets</a> are used to specify multiple XSL-FO files to be rendered.</td>
+<td>Yes, if no fofile attribute is supplied</td>
+<td></td>
+</tr>
+</tbody>
+</table>
+<h2 id="examples-wzxhzdk12wzxhzdk13">Examples <a id="examples"></a></h2>
+<p>The following example converts a single XSL-FO file to a PDF document:</p>
+<div class="codehilite"><pre><span class="nt">&lt;target</span> <span class="na">name=</span><span class="s">&quot;generate-pdf&quot;</span> <span class="na">description=</span><span class="s">&quot;Generates a single PDF file&quot;</span><span class="nt">&gt;</span>
+   <span class="nt">&lt;fop</span> <span class="na">format=</span><span class="s">&quot;application/pdf&quot;</span> 
+        <span class="na">fofile=</span><span class="s">&quot;c:\working\foDirectory\foDocument.fo&quot;</span>
+        <span class="na">outfile=</span><span class="s">&quot;c:\working\pdfDirectory\pdfDocument.pdf&quot;</span> <span class="nt">/&gt;</span>
+<span class="nt">&lt;/target&gt;</span>
+</pre></div>
+
+
+<p>This example converts all XSL-FO files within an entire directory to PostScript:</p>
+<div class="codehilite"><pre><span class="nt">&lt;target</span> <span class="na">name=</span><span class="s">&quot;generate-multiple-ps&quot;</span> 
+        <span class="na">description=</span><span class="s">&quot;Generates multiple PostScript files&quot;</span><span class="nt">&gt;</span>
+   <span class="nt">&lt;fop</span> <span class="na">format=</span><span class="s">&quot;application/postscript&quot;</span> 
+        <span class="na">outdir=</span><span class="s">&quot;</span><span class="cp">${</span><span class="n">build</span><span class="o">.</span><span class="n">dir</span><span class="cp">}</span><span class="s">&quot;</span> <span class="na">messagelevel=</span><span class="s">&quot;debug&quot;</span><span class="nt">&gt;</span>
+        <span class="nt">&lt;fileset</span> <span class="na">dir=</span><span class="s">&quot;</span><span class="cp">${</span><span class="n">fo</span><span class="o">.</span><span class="n">examples</span><span class="o">.</span><span class="n">dir</span><span class="cp">}</span><span class="s">&quot;</span><span class="nt">&gt;</span>
+           <span class="nt">&lt;include</span> <span class="na">name=</span><span class="s">&quot;*.fo&quot;/</span><span class="nt">&gt;</span>
+        <span class="nt">&lt;/fileset&gt;</span>
+   <span class="nt">&lt;/fop&gt;</span>
+<span class="nt">&lt;/target&gt;</span>
+</pre></div></div>
       </div>
       
       <div class="clear"></div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/compiling.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/compiling.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/compiling.html Mon Dec  3 15:47:41 2012
@@ -379,7 +379,7 @@ OR
 ant all
 To clean the build directory first:
 ant clean allIf you want to shorten the build time you can just call the "package" target which doesn't perform any automated tests during the build.</p>
-<h1 id="troubleshooting-wzxhzdk16wzxhzdk17">Troubleshooting <a id="problems"></a></h1>
+<h2 id="troubleshooting-wzxhzdk16wzxhzdk17">Troubleshooting <a id="problems"></a></h2>
 <p>If you have problems building FOP, please try the following:</p>
 <ul>
 <li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/configuration.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/configuration.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/configuration.html Mon Dec  3 15:47:41 2012
@@ -470,7 +470,7 @@ $(document).ready(function () {
 </pre></div>
 
 
-<h1 id="renderer-configuration-wzxhzdk14wzxhzdk15">Renderer configuration <a id="renderers"></a></h1>
+<h2 id="renderer-configuration-wzxhzdk14wzxhzdk15">Renderer configuration <a id="renderers"></a></h2>
 <p>Each Renderer has its own configuration section which is identified by the MIME type the Renderer is written for, ex. "application/pdf" for the PDF Renderer.</p>
 <p>The configuration for the PDF Renderer could look like this:</p>
 <div class="codehilite"><pre>  <span class="nt">&lt;renderers&gt;</span>
@@ -535,7 +535,7 @@ $(document).ready(function () {
 </pre></div>
 
 
-<h2 id="special-settings-for-the-postscript-renderer-wzxhzdk18wzxhzdk19">Special Settings for the PostScript Renderer <a id="ps-renderer"></a></h2>
+<h3 id="special-settings-for-the-postscript-renderer-wzxhzdk18wzxhzdk19">Special Settings for the PostScript Renderer <a id="ps-renderer"></a></h3>
 <p>Besides the normal font configuration (the same "fonts" element as for the PDF renderer) the PostScript renderer has an additional setting to force landscape pages to be rotated to fit on a page inserted into the printer in portrait mode. Set the value to "true" to activate this feature. The default is "false". Example:</p>
 <div class="codehilite"><pre>    <span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/postscript&quot;</span><span class="nt">&gt;</span>
       <span class="nt">&lt;auto-rotate-landscape&gt;</span>true<span class="nt">&lt;/auto-rotate-landscape&gt;</span>
@@ -554,7 +554,7 @@ $(document).ready(function () {
 </pre></div>
 
 
-<h2 id="special-settings-for-the-pcl-renderer-wzxhzdk20wzxhzdk21">Special Settings for the PCL Renderer <a id="pcl-renderer"></a></h2>
+<h3 id="special-settings-for-the-pcl-renderer-wzxhzdk20wzxhzdk21">Special Settings for the PCL Renderer <a id="pcl-renderer"></a></h3>
 <p>Non-standard fonts for the PCL renderer are made available through the Java2D subsystem which means that you don't have to do any custom font configuration in this case but you have to use the font names offered by Java.</p>
 <p>Additionally, there are certain settings that control how the renderer handles various elements.</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/vnd.hp-PCL&quot;</span><span class="nt">&gt;</span>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/embedding.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/embedding.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/embedding.html Mon Dec  3 15:47:41 2012
@@ -341,43 +341,55 @@ $(document).ready(function () {
         <div id="items">
         </div>
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></div> -->
-      	<div class="section-content"><h1 id="apachewzxhzdk0-fop-embedding">Apache&trade; FOP: Embedding</h1>
+      	<div class="section-content"><h1 id="apachewzxhzdk21-fop-embedding">Apache&trade; FOP: Embedding</h1>
 <p><subtitle>How to Embed Apache&trade; FOP in a Java application</subtitle></p>
-<h2 id="overview-wzxhzdk4wzxhzdk5">Overview <a id="overview"></a></h2>
+<h2 id="overview-wzxhzdk25wzxhzdk26">Overview <a id="overview"></a></h2>
 <p>Review <a href="running.html">Running Apache&trade; FOP</a> for important information that applies to embedded applications as well as command-line use, such as options and performance.</p>
 <p>To embed Apache&trade; FOP in your application, first create a new org.apache.fop.apps.FopFactory instance. This object can be used to launch multiple rendering runs. For each run, create a new org.apache.fop.apps.Fop instance through one of the factory methods of FopFactory. In the method call you specify which output format (i.e. Renderer) to use and, if the selected renderer requires an OutputStream, which OutputStream to use for the results of the rendering. You can customize FOP's behaviour in a rendering run by supplying your own FOUserAgent instance. The FOUserAgent can, for example, be used to set your own Renderer instance (details below). Finally, you retrieve a SAX DefaultHandler instance from the Fop object and use that as the SAXResult of your transformation.
 We recently changed FOP's outer API to what we consider the final API. This might require some changes in your application. The main reasons for these changes were performance improvements due to better reuse of reusable objects and reduced use of static variables for added flexibility in complex environments.</p>
-<h1 id="basic-usage-pattern-wzxhzdk8wzxhzdk9">Basic Usage Pattern <a id="basics"></a></h1>
+<h2 id="basic-usage-pattern-wzxhzdk29wzxhzdk30">Basic Usage Pattern <a id="basics"></a></h2>
 <p>Apache FOP relies heavily on JAXP. It uses SAX events exclusively to receive the XSL-FO input document. It is therefore a good idea that you know a few things about JAXP (which is a good skill anyway). Let's look at the basic usage pattern for FOP...</p>
 <p>Here is the basic pattern to render an XSL-FO file to PDF:</p>
-<p>import org.apache.fop.apps.FopFactory;
-import org.apache.fop.apps.Fop;
-import org.apache.fop.apps.MimeConstants;</p>
-<p>/<em>..</em>/</p>
-<p>// Step 1: Construct a FopFactory
-// (reuse if you plan to render multiple documents!)
-FopFactory fopFactory = FopFactory.newInstance();</p>
-<p>// Step 2: Set up output stream.
-// Note: Using BufferedOutputStream for performance reasons (helpful with FileOutputStreams).
-OutputStream out = new BufferedOutputStream(new FileOutputStream(new File("C:/Temp/myfile.pdf")));</p>
-<p>try {
-  // Step 3: Construct fop with desired output format
-  Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, out);</p>
-<p>// Step 4: Setup JAXP using identity transformer
-  TransformerFactory factory = TransformerFactory.newInstance();
-  Transformer transformer = factory.newTransformer(); // identity transformer</p>
-<p>// Step 5: Setup input and output for XSLT transformation 
-  // Setup input stream
-  Source src = new StreamSource(new File("C:/Temp/myfile.fo"));</p>
-<p>// Resulting SAX events (the generated FO) must be piped through to FOP
-  Result res = new SAXResult(fop.getDefaultHandler());</p>
-<p>// Step 6: Start XSLT transformation and FOP processing
-  transformer.transform(src, res);</p>
-<p>} finally {
-  //Clean-up
-  out.close();
-}
-Let's discuss these 5 steps in detail:</p>
+<div class="codehilite"><pre><span class="nb">import</span> <span class="n">org</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">fop</span><span class="o">.</span><span class="n">apps</span><span class="o">.</span><span class="n">FopFactory</span><span class="p">;</span>
+<span class="nb">import</span> <span class="n">org</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">fop</span><span class="o">.</span><span class="n">apps</span><span class="o">.</span><span class="n">Fop</span><span class="p">;</span>
+<span class="nb">import</span> <span class="n">org</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">fop</span><span class="o">.</span><span class="n">apps</span><span class="o">.</span><span class="n">MimeConstants</span><span class="p">;</span>
+
+<span class="sr">/*..*/</span>
+
+<span class="sr">//</span> <span class="n">Step</span> <span class="mi">1</span><span class="p">:</span> <span class="n">Construct</span> <span class="n">a</span> <span class="n">FopFactory</span>
+<span class="sr">//</span> <span class="p">(</span><span class="n">reuse</span> <span class="k">if</span> <span class="n">you</span> <span class="n">plan</span> <span class="n">to</span> <span class="n">render</span> <span class="n">multiple</span> <span class="n">documents</span><span class="o">!</span><span class="p">)</span>
+<span class="n">FopFactory</span> <span class="n">fopFactory</span> <span class="o">=</span> <span class="n">FopFactory</span><span class="o">.</span><span class="n">newInstance</span><span class="p">();</span>
+
+<span class="sr">//</span> <span class="n">Step</span> <span class="mi">2</span><span class="p">:</span> <span class="n">Set</span> <span class="n">up</span> <span class="n">output</span> <span class="n">stream</span><span class="o">.</span>
+<span class="sr">//</span> <span class="n">Note:</span> <span class="n">Using</span> <span class="n">BufferedOutputStream</span> <span class="k">for</span> <span class="n">performance</span> <span class="n">reasons</span> <span class="p">(</span><span class="n">helpful</span> <span class="n">with</span> <span class="n">FileOutputStreams</span><span class="p">)</span><span class="o">.</span>
+<span class="n">OutputStream</span> <span class="n">out</span> <span class="o">=</span> <span class="k">new</span> <span class="n">BufferedOutputStream</span><span class="p">(</span><span class="k">new</span> <span class="n">FileOutputStream</span><span class="p">(</span><span class="k">new</span> <span class="n">File</span><span class="p">(</span><span class="s">&quot;C:/Temp/myfile.pdf&quot;</span><span class="p">)));</span>
+
+<span class="n">try</span> <span class="p">{</span>
+  <span class="sr">//</span> <span class="n">Step</span> <span class="mi">3</span><span class="p">:</span> <span class="n">Construct</span> <span class="n">fop</span> <span class="n">with</span> <span class="n">desired</span> <span class="n">output</span> <span class="nb">format</span>
+  <span class="n">Fop</span> <span class="n">fop</span> <span class="o">=</span> <span class="n">fopFactory</span><span class="o">.</span><span class="n">newFop</span><span class="p">(</span><span class="n">MimeConstants</span><span class="o">.</span><span class="n">MIME_PDF</span><span class="p">,</span> <span class="n">out</span><span class="p">);</span>
+
+  <span class="sr">//</span> <span class="n">Step</span> <span class="mi">4</span><span class="p">:</span> <span class="n">Setup</span> <span class="n">JAXP</span> <span class="n">using</span> <span class="n">identity</span> <span class="n">transformer</span>
+  <span class="n">TransformerFactory</span> <span class="n">factory</span> <span class="o">=</span> <span class="n">TransformerFactory</span><span class="o">.</span><span class="n">newInstance</span><span class="p">();</span>
+  <span class="n">Transformer</span> <span class="n">transformer</span> <span class="o">=</span> <span class="n">factory</span><span class="o">.</span><span class="n">newTransformer</span><span class="p">();</span> <span class="sr">//</span> <span class="n">identity</span> <span class="n">transformer</span>
+
+  <span class="sr">//</span> <span class="n">Step</span> <span class="mi">5</span><span class="p">:</span> <span class="n">Setup</span> <span class="n">input</span> <span class="ow">and</span> <span class="n">output</span> <span class="k">for</span> <span class="n">XSLT</span> <span class="n">transformation</span>
+  <span class="sr">//</span> <span class="n">Setup</span> <span class="n">input</span> <span class="n">stream</span>
+  <span class="n">Source</span> <span class="n">src</span> <span class="o">=</span> <span class="k">new</span> <span class="n">StreamSource</span><span class="p">(</span><span class="k">new</span> <span class="n">File</span><span class="p">(</span><span class="s">&quot;C:/Temp/myfile.fo&quot;</span><span class="p">));</span>
+
+  <span class="sr">//</span> <span class="n">Resulting</span> <span class="n">SAX</span> <span class="n">events</span> <span class="p">(</span><span class="n">the</span> <span class="n">generated</span> <span class="n">FO</span><span class="p">)</span> <span class="n">must</span> <span class="n">be</span> <span class="n">piped</span> <span class="n">through</span> <span class="n">to</span> <span class="n">FOP</span>
+  <span class="n">Result</span> <span class="n">res</span> <span class="o">=</span> <span class="k">new</span> <span class="n">SAXResult</span><span class="p">(</span><span class="n">fop</span><span class="o">.</span><span class="n">getDefaultHandler</span><span class="p">());</span>
+
+  <span class="sr">//</span> <span class="n">Step</span> <span class="mi">6</span><span class="p">:</span> <span class="n">Start</span> <span class="n">XSLT</span> <span class="n">transformation</span> <span class="ow">and</span> <span class="n">FOP</span> <span class="n">processing</span>
+  <span class="n">transformer</span><span class="o">.</span><span class="n">transform</span><span class="p">(</span><span class="n">src</span><span class="p">,</span> <span class="n">res</span><span class="p">);</span>
+
+<span class="p">}</span> <span class="n">finally</span> <span class="p">{</span>
+  <span class="sr">//</span><span class="n">Clean</span><span class="o">-</span><span class="n">up</span>
+  <span class="n">out</span><span class="o">.</span><span class="nb">close</span><span class="p">();</span>
+<span class="p">}</span>
+</pre></div>
+
+
+<p>Let's discuss these 5 steps in detail:</p>
 <ul>
 <li>
 <p><strong>Step 1:</strong> You create a new FopFactory instance. The FopFactory instance holds references to configuration information and cached data. It's important to reuse this instance if you plan to render multiple documents during a JVM's lifetime.</p>
@@ -400,157 +412,200 @@ Let's discuss these 5 steps in detail:</
 </ul>
 <p>If you're not totally familiar with JAXP Transformers, please have a look at the <a href="#examples">Embedding examples</a> below. The section contains examples for all sorts of use cases. If you look at all of them in turn you should be able to see the patterns in use and the flexibility this approach offers without adding too much complexity.</p>
 <p>This may look complicated at first, but it's really just the combination of an XSL transformation and a FOP run. It's also easy to comment out the FOP part for debugging purposes, for example when you're tracking down a bug in your stylesheet. You can easily write the XSL-FO output from the XSL transformation to a file to check if that part generates the expected output. An example for that can be found in the <a href="#examples">Embedding examples</a> (See "ExampleXML2FO").</p>
-<h3 id="logging-wzxhzdk10wzxhzdk11">Logging <a id="basic-logging"></a></h3>
+<h3 id="logging-wzxhzdk31wzxhzdk32">Logging <a id="basic-logging"></a></h3>
 <p>Logging is now a little different than it was in FOP 0.20.5. We've switched from Avalon Logging to <a href="http://commons.apache.org/logging/">Jakarta Commons Logging</a> . While with Avalon Logging the loggers were directly given to FOP, FOP now retrieves its logger(s) through a statically available LogFactory. This is similar to the general pattern that you use when you work with Apache Log4J directly, for example. We call this "static logging" (Commons Logging, Log4J) as opposed to "instance logging" (Avalon Logging). This has a consequence: You can't give FOP a logger for each processing run anymore. The log output of multiple, simultaneously running FOP instances is sent to the same logger.
 We know this may be an issue in multi-threaded server environments if you'd like to know what's going on in every single FOP processing run. We're planning to add an additional feedback facility to FOP which can be used to obtain all sorts of specific feedback (validation messages, layout problems etc.). "Static logging" is mainly interesting for a developer working on FOP and for advanced users who are debugging FOP. We don't consider the logging output to be useful to normal FOP users. Please have some patience until we can add this feature or jump in and help us build it. We've set up a <a href="http://wiki.apache.org/xmlgraphics-fop/ProcessingFeedback">Wiki page</a> which documents what we're going to build.
 By default, <a href="http://commons.apache.org/logging/">Jakarta Commons Logging</a> uses JDK logging (available in JDKs 1.4 or higher) as its backend. You can configure Commons Logging to use an alternative backend, for example Log4J. Please consult the <a href="http://commons.apache.org/logging/">documentation for Jakarta Commons Logging</a> on how to configure alternative backends.</p>
-<h3 id="processing-xsl-fo-wzxhzdk12wzxhzdk13">Processing XSL-FO <a id="render"></a></h3>
+<h3 id="processing-xsl-fo-wzxhzdk33wzxhzdk34">Processing XSL-FO <a id="render"></a></h3>
 <p>Once the Fop instance is set up, call <code>getDefaultHandler()</code> to obtain a SAX DefaultHandler instance to which you can send the SAX events making up the XSL-FO document you'd like to render. FOP processing starts as soon as the DefaultHandler's <code>startDocument()</code> method is called. Processing stops again when the DefaultHandler's <code>endDocument()</code> method is called. Please refer to the basic usage pattern shown above to render a simple XSL-FO document.</p>
-<h3 id="processing-xsl-fo-generated-from-xmlxslt-wzxhzdk14wzxhzdk15">Processing XSL-FO generated from XML+XSLT <a id="render-with-xslt"></a></h3>
+<h3 id="processing-xsl-fo-generated-from-xmlxslt-wzxhzdk35wzxhzdk36">Processing XSL-FO generated from XML+XSLT <a id="render-with-xslt"></a></h3>
 <p>If you want to process XSL-FO generated from XML using XSLT we recommend again using standard JAXP to do the XSLT part and piping the generated SAX events directly through to FOP. The only thing you'd change to do that on the basic usage pattern above is to set up the Transformer differently:</p>
 <p>//without XSLT:
   //Transformer transformer = factory.newTransformer(); // identity transformer</p>
 <p>//with XSLT:
   Source xslt = new StreamSource(new File("mystylesheet.xsl"));
   Transformer transformer = factory.newTransformer(xslt);</p>
-<h1 id="input-sources-wzxhzdk16wzxhzdk17">Input Sources <a id="input"></a></h1>
+<h2 id="input-sources-wzxhzdk37wzxhzdk38">Input Sources <a id="input"></a></h2>
 <p>The input XSL-FO document is always received by FOP as a SAX stream (see the <a href="../dev/design/parsing.html">Parsing Design Document</a> for the rationale).</p>
 <p>However, you may not always have your input document available as a SAX stream. But with JAXP it's easy to convert different input sources to a SAX stream so you can pipe it into FOP. That sounds more difficult than it is. You simply have to set up the right Source instance as input for the JAXP transformation. A few examples:</p>
 <ul>
 <li>
-<p><strong>URL:</strong>  <code>Source src = new StreamSource("http://localhost:8080/testfile.xml");</code> </p>
+<p><strong>URL:</strong>  <code>Source src = new StreamSource("http://localhost:8080/testfile.xml");</code></p>
 </li>
 <li>
-<p><strong>File:</strong>  <code>Source src = new StreamSource(new File("C:/Temp/myinputfile.xml"));</code> </p>
+<p><strong>File:</strong>  <code>Source src = new StreamSource(new File("C:/Temp/myinputfile.xml"));</code></p>
 </li>
 <li>
-<p><strong>String:</strong>  <code>Source src = new StreamSource(new StringReader(myString)); // myString is a String</code> </p>
+<p><strong>String:</strong>  <code>Source src = new StreamSource(new StringReader(myString)); // myString is a String</code></p>
 </li>
 <li>
-<p><strong>InputStream:</strong>  <code>Source src = new StreamSource(new MyInputStream(something));</code> </p>
+<p><strong>InputStream:</strong>  <code>Source src = new StreamSource(new MyInputStream(something));</code></p>
 </li>
 <li>
-<p><strong>Byte Array:</strong>  <code>Source src = new StreamSource(new ByteArrayInputStream(myBuffer)); // myBuffer is a byte[] here</code> </p>
+<p><strong>Byte Array:</strong>  <code>Source src = new StreamSource(new ByteArrayInputStream(myBuffer)); // myBuffer is a byte[] here</code></p>
 </li>
 <li>
-<p><strong>DOM:</strong>  <code>Source src = new DOMSource(myDocument); // myDocument is a Document or a Node</code> </p>
+<p><strong>DOM:</strong>  <code>Source src = new DOMSource(myDocument); // myDocument is a Document or a Node</code></p>
 </li>
 <li>
 <p><strong>Java Objects:</strong> Please have a look at the <a href="#examples">Embedding examples</a> which contain an example for this.</p>
 </li>
 </ul>
 <p>There are a variety of upstream data manipulations possible. For example, you may have a DOM and an XSL stylesheet; or you may want to set variables in the stylesheet. Interface documentation and some cookbook solutions to these situations are provided in <a href="http://xml.apache.org/xalan-j/usagepatterns.html">Xalan Basic Usage Patterns</a> .</p>
-<h2 id="configuring-apache-fop-programmatically-wzxhzdk18wzxhzdk19">Configuring Apache FOP Programmatically <a id="config-internal"></a></h2>
+<h2 id="configuring-apache-fop-programmatically-wzxhzdk39wzxhzdk40">Configuring Apache FOP Programmatically <a id="config-internal"></a></h2>
 <p>Apache FOP provides two levels on which you can customize FOP's behaviour: the FopFactory and the user agent.</p>
-<h3 id="customizing-the-fopfactory-wzxhzdk20wzxhzdk21">Customizing the FopFactory <a id="fop-factory"></a></h3>
+<h3 id="customizing-the-fopfactory-wzxhzdk41wzxhzdk42">Customizing the FopFactory <a id="fop-factory"></a></h3>
 <p>The FopFactory holds configuration data and references to objects which are reusable over multiple rendering runs. It's important to instantiate it only once (except in special environments) and reuse it every time to create new FOUserAgent and Fop instances.</p>
 <p>You can set all sorts of things on the FopFactory:</p>
-<ul>
-<li>
-<p>The <strong>font base URL</strong> to use when resolving relative URLs for fonts. Example:
-fopFactory.setFontBaseURL("file:///C:/Temp/fonts");</p>
-</li>
-<li>
-<p>The <strong>hyphenation base URL</strong> to use when resolving relative URLs for hyphenation patterns. Example:
-fopFactory.setHyphenBaseURL("file:///C:/Temp/hyph");</p>
-</li>
-<li>
-<p>Disable <strong>strict validation</strong> . When disabled FOP is less strict about the rules established by the XSL-FO specification. Example:
-fopFactory.setStrictValidation(false);</p>
-</li>
-<li>
-<p>Enable an <strong>alternative set of rules for text indents</strong> that tries to mimic the behaviour of many commercial FO implementations, that chose to break the specification in this respect. The default of this option is 'false', which causes Apache FOP to behave exactly as described in the specification. To enable the alternative behaviour, call:
-fopFactory.setBreakIndentInheritanceOnReferenceAreaBoundary(true);</p>
-</li>
-<li>
-<p>Set the <strong>source resolution</strong> for the document. This is used internally to determine the pixel size for SVG images and bitmap images without resolution information. Default: 72 dpi. Example:
-fopFactory.setSourceResolution(96); // =96dpi (dots/pixels per Inch)</p>
-</li>
-<li>
-<p>Manually add an <strong>ElementMapping instance</strong> . If you want to supply a special FOP extension you can give the instance to the FOUserAgent. Normally, the FOP extensions can be automatically detected (see the documentation on extension for more info). Example:
-fopFactory.addElementMapping(myElementMapping); // myElementMapping is a org.apache.fop.fo.ElementMapping</p>
-</li>
-<li>
-<p>Set a <strong>URIResolver</strong> for custom URI resolution. By supplying a JAXP URIResolver you can add custom URI resolution functionality to FOP. For example, you can use <a href="http://xml.apache.org/commons/components/resolver/">Apache XML Commons Resolver</a> to make use of XCatalogs. Example:
-fopFactory.setURIResolver(myResolver); // myResolver is a javax.xml.transform.URIResolverBoth the FopFactory and the FOUserAgent have a method to set a URIResolver. The URIResolver on the FopFactory is primarily used to resolve URIs on factory-level (hyphenation patterns, for example) and it is always used if no other URIResolver (for example on the FOUserAgent) resolved the URI first.</p>
-</li>
-</ul>
-<h3 id="customizing-the-user-agent-wzxhzdk22wzxhzdk23">Customizing the User Agent <a id="user-agent"></a></h3>
+<p>-
+The <strong>font base URL</strong> to use when resolving relative URLs for fonts. Example:</p>
+<div class="codehilite"><pre><span class="sb">`fopFactory.setFontBaseURL(&quot;file:///C:/Temp/fonts&quot;);`</span>
+</pre></div>
+
+
+<p>-
+The <strong>hyphenation base URL</strong> to use when resolving relative URLs for hyphenation patterns. Example:</p>
+<div class="codehilite"><pre><span class="sb">`fopFactory.setHyphenBaseURL(&quot;file:///C:/Temp/hyph&quot;);`</span>
+</pre></div>
+
+
+<p>-
+Disable <strong>strict validation</strong> . When disabled FOP is less strict about the rules established by the XSL-FO specification. Example:</p>
+<div class="codehilite"><pre><span class="sb">`fopFactory.setStrictValidation(false);`</span>
+</pre></div>
+
+
+<p>-
+Enable an <strong>alternative set of rules for text indents</strong> that tries to mimic the behaviour of many commercial FO implementations, that chose to break the specification in this respect. The default of this option is 'false', which causes Apache FOP to behave exactly as described in the specification. To enable the alternative behaviour, call:</p>
+<div class="codehilite"><pre><span class="sb">`fopFactory.setBreakIndentInheritanceOnReferenceAreaBoundary(true);`</span>
+</pre></div>
+
+
+<p>-
+Set the <strong>source resolution</strong> for the document. This is used internally to determine the pixel size for SVG images and bitmap images without resolution information. Default: 72 dpi. Example:</p>
+<div class="codehilite"><pre><span class="sb">`fopFactory.setSourceResolution(96); // =96dpi (dots/pixels per Inch)`</span>
+</pre></div>
+
+
+<p>-
+Manually add an <strong>ElementMapping instance</strong> . If you want to supply a special FOP extension you can give the instance to the FOUserAgent. Normally, the FOP extensions can be automatically detected (see the documentation on extension for more info). Example:</p>
+<div class="codehilite"><pre><span class="sb">`fopFactory.addElementMapping(myElementMapping); // myElementMapping is a org.apache.fop.fo.ElementMapping`</span>
+</pre></div>
+
+
+<p>-
+Set a <strong>URIResolver</strong> for custom URI resolution. By supplying a JAXP URIResolver you can add custom URI resolution functionality to FOP. For example, you can use <a href="http://xml.apache.org/commons/components/resolver/">Apache XML Commons Resolver</a> to make use of XCatalogs. Example:</p>
+<div class="codehilite"><pre><span class="sb">`fopFactory.setURIResolver(myResolver); // myResolver is a javax.xml.transform.URIResolver`</span>
+</pre></div>
+
+
+<p>Both the FopFactory and the FOUserAgent have a method to set a URIResolver. The URIResolver on the FopFactory is primarily used to resolve URIs on factory-level (hyphenation patterns, for example) and it is always used if no other URIResolver (for example on the FOUserAgent) resolved the URI first.</p>
+<h3 id="customizing-the-user-agent-wzxhzdk43wzxhzdk44">Customizing the User Agent <a id="user-agent"></a></h3>
 <p>The user agent is the entity that allows you to interact with a single rendering run, i.e. the processing of a single document. If you wish to customize the user agent's behaviour, the first step is to create your own instance of FOUserAgent using the appropriate factory method on FopFactory and pass that to the factory method that will create a new Fop instance:</p>
-<p>FopFactory fopFactory = FopFactory.newInstance(); // Reuse the FopFactory if possible!
-  // do the following for each new rendering run
-  FOUserAgent userAgent = fopFactory.newFOUserAgent();
-  // customize userAgent
-  Fop fop = fopFactory.newFop(MimeConstants.MIME_POSTSCRIPT, userAgent, out);
-You can do all sorts of things on the user agent:</p>
-<ul>
-<li>
-<p>The <strong>base URL</strong> to use when resolving relative URLs. Example:
-userAgent.setBaseURL("file:///C:/Temp/");</p>
-</li>
-<li>
-<p>Set the <strong>producer</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. The default producer is "Apache FOP". Example:
-userAgent.setProducer("MyKillerApplication");</p>
-</li>
-<li>
-<p>Set the <strong>creating user</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. Example:
-userAgent.setCreator("John Doe");</p>
-</li>
-<li>
-<p>Set the <strong>author</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. Example:
-userAgent.setAuthor("John Doe");</p>
-</li>
-<li>
-<p>Override the <strong>creation date and time</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. Example:
-userAgent.setCreationDate(new Date());</p>
-</li>
-<li>
-<p>Set the <strong>title</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. Example:
-userAgent.setTitle("Invoice No 138716847");</p>
-</li>
-<li>
-<p>Set the <strong>keywords</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. Example:
-userAgent.setKeywords("XML XSL-FO");</p>
-</li>
-<li>
-<p>Set the <strong>target resolution</strong> for the document. This is used to specify the output resolution for bitmap images generated by bitmap renderers (such as the TIFF renderer) and by bitmaps generated by Apache Batik for filter effects and such. Default: 72 dpi. Example:
-userAgent.setTargetResolution(300); // =300dpi (dots/pixels per Inch)</p>
-</li>
-<li>
-<p>Set <strong>your own Renderer instance</strong> . If you want to supply your own renderer or configure a Renderer in a special way you can give the instance to the FOUserAgent. Normally, the Renderer instance is created by FOP. Example:
-userAgent.setRendererOverride(myRenderer); // myRenderer is an org.apache.fop.render.Renderer</p>
-</li>
-<li>
-<p>Set <strong>your own FOEventHandler instance</strong> . If you want to supply your own FOEventHandler or configure an FOEventHandler subclass in a special way you can give the instance to the FOUserAgent. Normally, the FOEventHandler instance is created by FOP. Example:
-userAgent.setFOEventHandlerOverride(myFOEventHandler); // myFOEventHandler is an org.apache.fop.fo.FOEventHandler</p>
-</li>
-<li>
-<p>Set a <strong>URIResolver</strong> for custom URI resolution. By supplying a JAXP URIResolver you can add custom URI resolution functionality to FOP. For example, you can use <a href="http://xml.apache.org/commons/components/resolver/">Apache XML Commons Resolver</a> to make use of XCatalogs. Example:
-userAgent.setURIResolver(myResolver); // myResolver is a javax.xml.transform.URIResolverBoth the FopFactory and the FOUserAgent have a method to set a URIResolver. The URIResolver on the FOUserAgent is used for resolving URIs which are document-related. If it's not set or cannot resolve a URI, the URIResolver from the FopFactory is used.
-You should not reuse an FOUserAgent instance between FOP rendering runs although you can. Especially in multi-threaded environment, this is a bad idea.</p>
-</li>
-</ul>
-<h1 id="using-a-configuration-file-wzxhzdk24wzxhzdk25">Using a Configuration File <a id="config-external"></a></h1>
+<div class="codehilite"><pre><span class="n">FopFactory</span> <span class="n">fopFactory</span> <span class="o">=</span> <span class="n">FopFactory</span><span class="o">.</span><span class="n">newInstance</span><span class="p">();</span> <span class="sr">//</span> <span class="n">Reuse</span> <span class="n">the</span> <span class="n">FopFactory</span> <span class="k">if</span> <span class="n">possible</span><span class="o">!</span>
+<span class="sr">//</span> <span class="k">do</span> <span class="n">the</span> <span class="n">following</span> <span class="k">for</span> <span class="nb">each</span> <span class="k">new</span> <span class="n">rendering</span> <span class="n">run</span>
+<span class="n">FOUserAgent</span> <span class="n">userAgent</span> <span class="o">=</span> <span class="n">fopFactory</span><span class="o">.</span><span class="n">newFOUserAgent</span><span class="p">();</span>
+<span class="sr">//</span> <span class="n">customize</span> <span class="n">userAgent</span>
+<span class="n">Fop</span> <span class="n">fop</span> <span class="o">=</span> <span class="n">fopFactory</span><span class="o">.</span><span class="n">newFop</span><span class="p">(</span><span class="n">MimeConstants</span><span class="o">.</span><span class="n">MIME_POSTSCRIPT</span><span class="p">,</span> <span class="n">userAgent</span><span class="p">,</span> <span class="n">out</span><span class="p">);</span>
+</pre></div>
+
+
+<p>You can do all sorts of things on the user agent:</p>
+<p>-
+The <strong>base URL</strong> to use when resolving relative URLs. Example:</p>
+<div class="codehilite"><pre><span class="sb">`userAgent.setBaseURL(&quot;file:///C:/Temp/&quot;);`</span>
+</pre></div>
+
+
+<p>-
+Set the <strong>producer</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. The default producer is "Apache FOP". Example:</p>
+<div class="codehilite"><pre><span class="sb">`userAgent.setProducer(&quot;MyKillerApplication&quot;);`</span>
+</pre></div>
+
+
+<p>-
+Set the <strong>creating user</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. Example:</p>
+<div class="codehilite"><pre><span class="sb">`userAgent.setCreator(&quot;John Doe&quot;);`</span>
+</pre></div>
+
+
+<p>-
+Set the <strong>author</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. Example:</p>
+<div class="codehilite"><pre><span class="sb">`userAgent.setAuthor(&quot;John Doe&quot;);`</span>
+</pre></div>
+
+
+<p>-
+Override the <strong>creation date and time</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. Example:</p>
+<div class="codehilite"><pre><span class="sb">`userAgent.setCreationDate(new Date());`</span>
+</pre></div>
+
+
+<p>-
+Set the <strong>title</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. Example:</p>
+<div class="codehilite"><pre><span class="sb">`userAgent.setTitle(&quot;Invoice No 138716847&quot;);`</span>
+</pre></div>
+
+
+<p>-
+Set the <strong>keywords</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. Example:</p>
+<div class="codehilite"><pre><span class="sb">`userAgent.setKeywords(&quot;XML XSL-FO&quot;);`</span>
+</pre></div>
+
+
+<p>-
+Set the <strong>target resolution</strong> for the document. This is used to specify the output resolution for bitmap images generated by bitmap renderers (such as the TIFF renderer) and by bitmaps generated by Apache Batik for filter effects and such. Default: 72 dpi. Example:</p>
+<div class="codehilite"><pre><span class="sb">`userAgent.setTargetResolution(300); // =300dpi (dots/pixels per Inch)`</span>
+</pre></div>
+
+
+<p>-
+Set <strong>your own Renderer instance</strong> . If you want to supply your own renderer or configure a Renderer in a special way you can give the instance to the FOUserAgent. Normally, the Renderer instance is created by FOP. Example:</p>
+<div class="codehilite"><pre><span class="sb">`userAgent.setRendererOverride(myRenderer); // myRenderer is an org.apache.fop.render.Renderer`</span>
+</pre></div>
+
+
+<p>-
+Set <strong>your own FOEventHandler instance</strong> . If you want to supply your own FOEventHandler or configure an FOEventHandler subclass in a special way you can give the instance to the FOUserAgent. Normally, the FOEventHandler instance is created by FOP. Example:</p>
+<div class="codehilite"><pre><span class="sb">`userAgent.setFOEventHandlerOverride(myFOEventHandler); // myFOEventHandler is an org.apache.fop.fo.FOEventHandler`</span>
+</pre></div>
+
+
+<p>-
+Set a <strong>URIResolver</strong> for custom URI resolution. By supplying a JAXP URIResolver you can add custom URI resolution functionality to FOP. For example, you can use <a href="http://xml.apache.org/commons/components/resolver/">Apache XML Commons Resolver</a> to make use of XCatalogs. Example:</p>
+<div class="codehilite"><pre><span class="sb">`userAgent.setURIResolver(myResolver); // myResolver is a javax.xml.transform.URIResolver`</span>
+</pre></div>
+
+
+<p>Both the FopFactory and the FOUserAgent have a method to set a URIResolver. The URIResolver on the FOUserAgent is used for resolving URIs which are document-related. If it's not set or cannot resolve a URI, the URIResolver from the FopFactory is used. You should not reuse an FOUserAgent instance between FOP rendering runs although you can. Especially in multi-threaded environment, this is a bad idea.</p>
+<h2 id="using-a-configuration-file-wzxhzdk45wzxhzdk46">Using a Configuration File <a id="config-external"></a></h2>
 <p>Instead of setting the parameters manually in code as shown above you can also set many values from an XML configuration file:</p>
-<p>import org.apache.avalon.framework.configuration.Configuration;
-import org.apache.avalon.framework.configuration.DefaultConfigurationBuilder;</p>
-<p>/<em>..</em>/</p>
-<p>DefaultConfigurationBuilder cfgBuilder = new DefaultConfigurationBuilder();
-Configuration cfg = cfgBuilder.buildFromFile(new File("C:/Temp/mycfg.xml"));
-fopFactory.setUserConfig(cfg);</p>
-<p>/<em> ..or.. </em>/</p>
-<p>fopFactory.setUserConfig(new File("C:/Temp/mycfg.xml"));
-The layout of the configuration file is described on the <a href="configuration.html">Configuration page</a> .</p>
-<h2 id="hints-wzxhzdk26wzxhzdk27">Hints <a id="hints"></a></h2>
-<h3 id="object-reuse-wzxhzdk28wzxhzdk29">Object reuse <a id="object-reuse"></a></h3>
+<div class="codehilite"><pre><span class="nb">import</span> <span class="n">org</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">avalon</span><span class="o">.</span><span class="n">framework</span><span class="o">.</span><span class="n">configuration</span><span class="o">.</span><span class="n">Configuration</span><span class="p">;</span>
+<span class="nb">import</span> <span class="n">org</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">avalon</span><span class="o">.</span><span class="n">framework</span><span class="o">.</span><span class="n">configuration</span><span class="o">.</span><span class="n">DefaultConfigurationBuilder</span><span class="p">;</span>
+
+<span class="sr">/*..*/</span>
+
+<span class="n">DefaultConfigurationBuilder</span> <span class="n">cfgBuilder</span> <span class="o">=</span> <span class="k">new</span> <span class="n">DefaultConfigurationBuilder</span><span class="p">();</span>
+<span class="n">Configuration</span> <span class="n">cfg</span> <span class="o">=</span> <span class="n">cfgBuilder</span><span class="o">.</span><span class="n">buildFromFile</span><span class="p">(</span><span class="k">new</span> <span class="n">File</span><span class="p">(</span><span class="s">&quot;C:/Temp/mycfg.xml&quot;</span><span class="p">));</span>
+<span class="n">fopFactory</span><span class="o">.</span><span class="n">setUserConfig</span><span class="p">(</span><span class="n">cfg</span><span class="p">);</span>
+
+<span class="sr">/* ..or.. */</span>
+
+<span class="n">fopFactory</span><span class="o">.</span><span class="n">setUserConfig</span><span class="p">(</span><span class="k">new</span> <span class="n">File</span><span class="p">(</span><span class="s">&quot;C:/Temp/mycfg.xml&quot;</span><span class="p">));</span>
+</pre></div>
+
+
+<p>The layout of the configuration file is described on the <a href="configuration.html">Configuration page</a> .</p>
+<h2 id="hints-wzxhzdk47wzxhzdk48">Hints <a id="hints"></a></h2>
+<h3 id="object-reuse-wzxhzdk49wzxhzdk50">Object reuse <a id="object-reuse"></a></h3>
 <p>Fop instances shouldn't (and can't) be reused. Please recreate Fop and FOUserAgent instances for each rendering run using the FopFactory. This is a cheap operation as all reusable information is held in the FopFactory. That's why it's so important to reuse the FopFactory instance.</p>
-<h3 id="awt-issues-wzxhzdk30wzxhzdk31">AWT issues <a id="awt"></a></h3>
+<h3 id="awt-issues-wzxhzdk51wzxhzdk52">AWT issues <a id="awt"></a></h3>
 <p>If your XSL-FO files contain SVG then Apache Batik will be used. When Batik is initialised it uses certain classes in <code>java.awt</code> that intialise the Java AWT classes. This means that a daemon thread is created by the JVM and on Unix it will need to connect to a DISPLAY.</p>
 <p>The thread means that the Java application may not automatically quit when finished, you will need to call <code>System.exit()</code> . These issues should be fixed in the JDK 1.4.</p>
 <p>If you run into trouble running FOP on a head-less server, please see the <a href="graphics.html#batik">notes on Batik</a> .</p>
-<h3 id="getting-information-on-the-rendering-process-wzxhzdk32wzxhzdk33">Getting information on the rendering process <a id="render-info"></a></h3>
+<h3 id="getting-information-on-the-rendering-process-wzxhzdk53wzxhzdk54">Getting information on the rendering process <a id="render-info"></a></h3>
 <p>To get the number of pages that were rendered by FOP you can call <code>Fop.getResults()</code> . This returns a <code>FormattingResults</code> object where you can look up the number of pages produced. It also gives you the page-sequences that were produced along with their id attribute and their numbers of pages. This is particularly useful if you render multiple documents (each enclosed by a page-sequence) and have to know the number of pages of each document.</p>
-<h2 id="improving-performance-wzxhzdk34wzxhzdk35">Improving performance <a id="performance"></a></h2>
+<h2 id="improving-performance-wzxhzdk55wzxhzdk56">Improving performance <a id="performance"></a></h2>
 <p>There are several options to consider:</p>
 <ul>
 <li>
@@ -569,35 +624,35 @@ The layout of the configuration file is 
 <p>Fine-tune your stylesheet to make the XSLT process more efficient and to create XSL-FO that can be processed by FOP more efficiently. Less is more: Try to make use of property inheritance where possible.</p>
 </li>
 </ul>
-<h2 id="multithreading-fop-wzxhzdk36wzxhzdk37">Multithreading FOP <a id="multithreading"></a></h2>
+<h2 id="multithreading-fop-wzxhzdk57wzxhzdk58">Multithreading FOP <a id="multithreading"></a></h2>
 <p>Apache FOP may currently not be completely thread safe. The code has not been fully tested for multi-threading issues, yet. If you encounter any suspicious behaviour, please notify us.</p>
 <p>There is also a known issue with fonts being jumbled between threads when using the Java2D/AWT renderer (which is used by the -awt and -print output options). In general, you cannot safely run multiple threads through the AWT renderer.</p>
-<h2 id="examples-wzxhzdk38wzxhzdk39">Examples <a id="examples"></a></h2>
+<h2 id="examples-wzxhzdk59wzxhzdk60">Examples <a id="examples"></a></h2>
 <p>The directory "{fop-dir}/examples/embedding" contains several working examples.</p>
-<h3 id="examplefo2pdfjava-wzxhzdk40wzxhzdk41">ExampleFO2PDF.java <a id="ExampleFO2PDF"></a></h3>
+<h3 id="examplefo2pdfjava-wzxhzdk61wzxhzdk62">ExampleFO2PDF.java <a id="ExampleFO2PDF"></a></h3>
 <p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleFO2PDF.java?view=markup">example</a> demonstrates the basic usage pattern to transform an XSL-FO file to PDF using FOP.</p>
 <p><img alt="Example XSL-FO to PDF" src="images/EmbeddingExampleFO2PDF.png" /></p>
-<h2 id="examplexml2fojava-wzxhzdk42wzxhzdk43">ExampleXML2FO.java <a id="ExampleXML2FO"></a></h2>
+<h3 id="examplexml2fojava-wzxhzdk63wzxhzdk64">ExampleXML2FO.java <a id="ExampleXML2FO"></a></h3>
 <p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleXML2FO.java?view=markup">example</a> has nothing to do with FOP. It is there to show you how an XML file can be converted to XSL-FO using XSLT. The JAXP API is used to do the transformation. Make sure you've got a JAXP-compliant XSLT processor in your classpath (ex. <a href="http://xml.apache.org/xalan-j">Xalan</a> ).</p>
 <p><img alt="Example XML to XSL-FO" src="images/EmbeddingExampleXML2FO.png" /></p>
-<h2 id="examplexml2pdfjava-wzxhzdk44wzxhzdk45">ExampleXML2PDF.java <a id="ExampleXML2PDF"></a></h2>
+<h3 id="examplexml2pdfjava-wzxhzdk65wzxhzdk66">ExampleXML2PDF.java <a id="ExampleXML2PDF"></a></h3>
 <p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleXML2PDF.java?view=markup">example</a> demonstrates how you can convert an arbitrary XML file to PDF using XSLT and XSL-FO/FOP. It is a combination of the first two examples above. The example uses JAXP to transform the XML file to XSL-FO and FOP to transform the XSL-FO to PDF.</p>
 <p><img alt="Example XML to PDF (via XSL-FO)" src="images/EmbeddingExampleXML2PDF.png" /></p>
 <p>The output (XSL-FO) from the XSL transformation is piped through to FOP using SAX events. This is the most efficient way to do this because the intermediate result doesn't have to be saved somewhere. Often, novice users save the intermediate result in a file, a byte array or a DOM tree. We strongly discourage you to do this if it isn't absolutely necessary. The performance is significantly higher with SAX.</p>
-<h3 id="exampleobj2xmljava-wzxhzdk46wzxhzdk47">ExampleObj2XML.java <a id="ExampleObj2XML"></a></h3>
+<h3 id="exampleobj2xmljava-wzxhzdk67wzxhzdk68">ExampleObj2XML.java <a id="ExampleObj2XML"></a></h3>
 <p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleObj2XML.java?view=markup">example</a> is a preparatory example for the next one. It's an example that shows how an arbitrary Java object can be converted to XML. It's an often needed task to do this. Often people create a DOM tree from a Java object and use that. This is pretty straightforward. The example here, however, shows how to do this using SAX, which will probably be faster and not even more complicated once you know how this works.</p>
 <p><img alt="Example Java object to XML" src="images/EmbeddingExampleObj2XML.png" /></p>
 <p>For this example we've created two classes: ProjectTeam and ProjectMember (found in xml-fop/examples/embedding/java/embedding/model). They represent the same data structure found in xml-fop/examples/embedding/xml/xml/projectteam.xml. We want to serialize to XML a project team with several members which exist as Java objects. Therefore we created the two classes: ProjectTeamInputSource and ProjectTeamXMLReader (in the same place as ProjectTeam above).</p>
 <p>The XMLReader implementation (regard it as a special kind of XML parser) is responsible for creating SAX events from the Java object. The InputSource class is only used to hold the ProjectTeam object to be used.</p>
 <p>Have a look at the source of ExampleObj2XML.java to find out how this is used. For more detailed information see other resources on JAXP (ex. <a href="http://java.sun.com/xml/jaxp/dist/1.1/docs/tutorial/xslt/3_generate.html">An older JAXP tutorial</a> ).</p>
-<h3 id="exampleobj2pdfjava-wzxhzdk48wzxhzdk49">ExampleObj2PDF.java <a id="ExampleObj2PDF"></a></h3>
+<h3 id="exampleobj2pdfjava-wzxhzdk69wzxhzdk70">ExampleObj2PDF.java <a id="ExampleObj2PDF"></a></h3>
 <p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleObj2PDF.java?view=markup">example</a> combines the previous and the third to demonstrate how you can transform a Java object to a PDF directly in one smooth run by generating SAX events from the Java object that get fed to an XSL transformation. The result of the transformation is then converted to PDF using FOP as before.</p>
 <p><img alt="Example Java object to PDF (via XML and XSL-FO)" src="images/EmbeddingExampleObj2PDF.png" /></p>
-<h2 id="exampledom2pdfjava-wzxhzdk50wzxhzdk51">ExampleDOM2PDF.java <a id="ExampleDOM2PDF"></a></h2>
+<h3 id="exampledom2pdfjava-wzxhzdk71wzxhzdk72">ExampleDOM2PDF.java <a id="ExampleDOM2PDF"></a></h3>
 <p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleDOM2PDF.java?view=markup">example</a> has FOP use a DOMSource instead of a StreamSource in order to use a DOM tree as input for an XSL transformation.</p>
-<h3 id="examplesvg2pdfjava-pdf-transcoder-example-wzxhzdk52wzxhzdk53">ExampleSVG2PDF.java (PDF Transcoder example) <a id="ExampleSVG2PDF"></a></h3>
+<h3 id="examplesvg2pdfjava-pdf-transcoder-example-wzxhzdk73wzxhzdk74">ExampleSVG2PDF.java (PDF Transcoder example) <a id="ExampleSVG2PDF"></a></h3>
 <p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleSVG2PDF.java?view=markup">example</a> shows the usage of the PDF Transcoder, a sub-application within FOP. It is used to generate a PDF document from an SVG file.</p>
-<h3 id="final-notes-wzxhzdk54wzxhzdk55">Final notes <a id="example-notes"></a></h3>
+<h3 id="final-notes-wzxhzdk75wzxhzdk76">Final notes <a id="example-notes"></a></h3>
 <p>These examples should give you an idea of what's possible. It should be easy to adjust these examples to your needs. Also, if you have other examples that you think should be added here, please let us know via either the fop-users or fop-dev mailing lists. Finally, for more help please send your questions to the fop-users mailing list.</p></div>
       </div>
       

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/extensions.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/extensions.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/extensions.html Mon Dec  3 15:47:41 2012
@@ -341,40 +341,44 @@ $(document).ready(function () {
         <div id="items">
         </div>
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></div> -->
-      	<div class="section-content"><h1 id="standard-apachewzxhzdk2-fop-extensions">Standard Apache&trade; FOP Extensions</h1>
+      	<div class="section-content"><h1 id="standard-apachewzxhzdk3-fop-extensions">Standard Apache&trade; FOP Extensions</h1>
 <p>By "extension", we mean any data that can be placed in the input XML document that is not addressed by the XSL-FO standard. By having a mechanism for supporting extensions, FOP is able to add features that are not covered in the specification.</p>
-<p>The extensions documented here are included with FOP, and are automatically available to you. If you wish to add an extension of your own to FOP, please see the <a href="../dev/extensions.html">Developers' Extension Page</a> .
+<p>The extensions documented here are included with FOP, and are automatically available to you. If you wish to add an extension of your own to FOP, please see the <a href="../dev/extensions.html">Developers' Extension Page</a>.
 All extensions require the correct use of an appropriate namespace in your input document.</p>
-<h1 id="svg-wzxhzdk3wzxhzdk4">SVG <a id="svg"></a></h1>
+<h2 id="svg-wzxhzdk4wzxhzdk5">SVG <a id="svg"></a></h2>
 <p>Please see the <a href="graphics.html#svg">SVG documentation</a> for more details.</p>
-<h2 id="fo-extensions-wzxhzdk5wzxhzdk6">FO Extensions <a id="fo-extensions"></a></h2>
-<h3 id="namespace-wzxhzdk7wzxhzdk8">Namespace <a id="fox-namespace"></a></h3>
+<h2 id="fo-extensions-wzxhzdk6wzxhzdk7">FO Extensions <a id="fo-extensions"></a></h2>
+<h3 id="namespace-wzxhzdk8wzxhzdk9">Namespace <a id="fox-namespace"></a></h3>
 <p>By convention, FO extensions in FOP use the "fox" namespace prefix. To use any of the FO extensions, add a namespace entry for <code>http://xmlgraphics.apache.org/fop/extensions</code> to the root element:</p>
 <div class="codehilite"><pre><span class="o">&lt;</span><span class="n">fo:root</span> <span class="n">xmlns:fo</span><span class="o">=</span><span class="s">&quot;http://www.w3.org/1999/XSL/Format&quot;</span>
            <span class="n">xmlns:fox</span><span class="o">=</span><span class="s">&quot;http://xmlgraphics.apache.org/fop/extensions&quot;</span><span class="o">&gt;</span>
 </pre></div>
 
 
-<h2 id="pdf-bookmarks-wzxhzdk9wzxhzdk10">PDF Bookmarks <a id="bookmarks"></a></h2>
+<h3 id="pdf-bookmarks-wzxhzdk10wzxhzdk11">PDF Bookmarks <a id="bookmarks"></a></h3>
 <p>In previous versions of Apache FOP there was a <code>fox:outline</code> element which was used to create outlines in PDF files. The redesigned code makes use of the new <a href="http://www.w3.org/TR/xsl11/#fo_bookmark-tree">bookmark feature defined in the latest XSL 1.1 working draft</a> .</p>
-<h3 id="anchors-or-named-destinations-wzxhzdk11wzxhzdk12">Anchors or Named Destinations <a id="named-destinations"></a></h3>
+<h3 id="anchors-or-named-destinations-wzxhzdk12wzxhzdk13">Anchors or Named Destinations <a id="named-destinations"></a></h3>
 <p>Use the fox:destination element to define "named destinations" inside a PDF document. These are useful as fragment identifiers, e.g. "http://server/document.pdf#anchor-name". fox:destination elements can be placed almost anywhere in the fo document, including a child of root, a block-level element, or an inline-level element. For the destination to actually work, it must correspond to an "id" attribute on some fo element within the document. In other words, the "id" attribute actually creates the "view" within the PDF document. The fox:destination simply gives that view an independent name.</p>
 <div class="codehilite"><pre><span class="nt">&lt;fox:destination</span> <span class="na">internal-destination=</span><span class="s">&quot;table-of-contents&quot;</span><span class="nt">/&gt;</span>
 ...
-<span class="nt">&lt;fo:block</span> <span class="na">id=</span><span class="s">&quot;table-of-contents&quot;</span><span class="nt">&gt;</span>Table of Contents<span class="nt">&lt;/fo:block&gt;&lt;warning&gt;</span>It is possible that in some future release of FOP, *all* elements with &quot;id&quot; attributes will generate named-destinations, which will eliminate the need for fox:destination.<span class="nt">&lt;/warning&gt;</span>
+<span class="nt">&lt;fo:block</span> <span class="na">id=</span><span class="s">&quot;table-of-contents&quot;</span><span class="nt">&gt;</span>Table of Contents<span class="nt">&lt;/fo:block&gt;</span>
 </pre></div>
 
 
-<h2 id="table-continuation-label-wzxhzdk13wzxhzdk14">Table Continuation Label <a id="table-continue-label"></a></h2>
+<p><warning>It is possible that in some future release of FOP, <em>all</em> elements with "id" attributes will generate named-destinations, which will eliminate the need for fox:destination.</warning></p>
+<h3 id="table-continuation-label-wzxhzdk16wzxhzdk17">Table Continuation Label <a id="table-continue-label"></a></h3>
 <p>This extension element hasn't been reimplemented for the redesigned code, yet.</p>
-<h3 id="foxorphan-content-limit-and-foxwidow-content-limit-wzxhzdk15wzxhzdk16">fox:orphan-content-limit and fox:widow-content-limit <a id="widow-orphan-content-limit"></a></h3>
-<p>The two proprietary extension properties, fox:orphan-content-limit and fox:widow-content-limit, are used to improve the layout of list-blocks and tables. If you have a table with many entries, you don't want a single row to be left over on a page. You will want to make sure that at least two or three lines are kept together. The properties take an absolute length which specifies the area at the beginning (fox:widow-content-limit) or at the end (fox:orphan-content-limit) of a table or list-block. The properties are inherited and only have an effect on fo:table and fo:list-block. An example: fox:widow-content-limit="3 * 1.2em" would make sure the you'll have at least three lines (assuming line-height="1.2") together on a table or list-block.</p>
-<h3 id="foxexternal-document-wzxhzdk17wzxhzdk18">fox:external-document <a id="external-document"></a></h3>
-<p>This feature is incomplete. Support for multi-page documents will be added shortly. At the moment, only single-page images will work. And this will not work with RTF output.
-This is a proprietary extension element which allows to add whole images as pages to an FO document. For example, if you have a scanned document or a fax as multi-page TIFF file, you can append or insert this document using the <code>fox:external-document</code> element. Each page of the external document will create one full page in the target format.</p>
+<h3 id="foxorphan-content-limit-and-foxwidow-content-limit-wzxhzdk18wzxhzdk19">fox:orphan-content-limit and fox:widow-content-limit <a id="widow-orphan-content-limit"></a></h3>
+<p>The two proprietary extension properties, <code>fox:orphan-content-limit</code> and <code>fox:widow-content-limit</code>, are used to improve the layout of list-blocks and tables. If you have a table with many entries, you don't want a single row to be left over on a page. You will want to make sure that at least two or three lines are kept together. The properties take an absolute length which specifies the area at the beginning (<code>fox:widow-content-limit</code>) or at the end (<code>fox:orphan-content-limit</code>) of a table or list-block. The properties are inherited and only have an effect on <code>fo:table</code> and <code>fo:list-block</code>. An example: <code>fox:widow-content-limit="3 * 1.2em"</code> would make sure the you'll have at least three lines (assuming <code>line-height="1.2"</code>) together on a table or list-block.</p>
+<h3 id="foxexternal-document-wzxhzdk20wzxhzdk21">fox:external-document <a id="external-document"></a></h3>
+<p>This feature is incomplete. Support for multi-page documents will be added shortly. At the moment, only single-page images will work. And this will not work with RTF output.</p>
+<p>This is a proprietary extension element which allows to add whole images as pages to an FO document. For example, if you have a scanned document or a fax as multi-page TIFF file, you can append or insert this document using the <code>fox:external-document</code> element. Each page of the external document will create one full page in the target format.</p>
 <p>The <code>fox:external-document</code> element is structurally a peer to <code>fo:page-sequence</code> , so wherever you can put an <code>fo:page-sequence</code> you could also place a <code>fox:external-document</code> . Therefore, the specified contents for <code>fo:root</code> change to:</p>
-<p><code>(layout-master-set, declarations?, bookmark-tree?, (page-sequence|page-sequence-wrapper|fox:external-document|fox:destination)+)</code> </p>
-<h4 id="specification-wzxhzdk19wzxhzdk20">Specification ## <a id="Specification"></a></h4>
+<div class="codehilite"><pre>        <span class="p">(</span><span class="n">layout</span><span class="o">-</span><span class="n">master</span><span class="o">-</span><span class="n">set</span><span class="p">,</span> <span class="n">declarations</span><span class="p">?,</span> <span class="n">bookmark</span><span class="o">-</span><span class="n">tree</span><span class="p">?,</span> <span class="p">(</span><span class="n">page</span><span class="o">-</span><span class="n">sequence</span><span class="o">|</span><span class="n">page</span><span class="o">-</span><span class="n">sequence</span><span class="o">-</span><span class="n">wrapper</span><span class="o">|</span><span class="n">fox:external</span><span class="o">-</span><span class="n">document</span><span class="o">|</span><span class="n">fox:destination</span><span class="p">)</span><span class="o">+</span><span class="p">)</span>
+</pre></div>
+
+
+<h4 id="specificationwzxhzdk22wzxhzdk23">Specification<a id="Specification"></a></h4>
 <p>The <code>fox:external-document</code> extension formatting object is used to specify how to create a (sub-)sequence of pages within a document. The content of these pages comes from the individual subimages/pages of an image or paged document (for example: multi-page TIFF in the form of faxes or scanned documents, or PDF files). The formatting object creates the necessary areas to display one image per page.</p>
 <p>In terms of page numbers, the behaviour is the same as for <code>fo:page-sequence</code> . The placement of the image inside the page is similar to that of <code>fo:external-graphic</code> or <code>fo:instream-foreign-object</code> , i.e. the viewport (and therefore the page size) is defined by either the intrinsic size of the image or by the size properties that apply to this formatting object.</p>
 <p>Content: EMPTY</p>
@@ -437,13 +441,13 @@ This is a proprietary extension element 
 </ul>
 <p>Datatype "page-set": Value: auto | <integer-range>, Default: "auto" which means all pages/subimages of the document. <integer-range> allows values such as "7" or "1-3"
  <code>fox:external-document</code> is not suitable for concatenating FO documents. For this, XInclude is recommended.</p>
-<h2 id="free-form-transformation-for-foblock-container-wzxhzdk23wzxhzdk24">Free-form Transformation for fo:block-container <a id="transform"></a></h2>
+<h3 id="free-form-transformation-for-foblock-container-wzxhzdk26wzxhzdk27">Free-form Transformation for fo:block-container <a id="transform"></a></h3>
 <p>For <code>fo:block-container</code> elements whose <code>absolute-position</code> set to "absolute" or "fixed" you can use the extension attribute <code>fox:transform</code> to apply a free-form transformation to the whole block-container. The content of the <code>fox:transform</code> attribute is the same as for <a href="http://www.w3.org/TR/SVG/coords.html#TransformAttribute">SVG's transform attribute</a> . The transformation specified here is performed in addition to other implicit transformations of the block-container (resulting from top, left and other properties) and after them.</p>
 <p>Examples: <code>fox:transform="rotate(45)"</code> would rotate the block-container by 45 degrees clock-wise around its upper-left corner. <code>fox:transform="translate(10000,0)"</code> would move the block-container to the right by 10 points (=10000 millipoints, FOP uses millipoints internally!).
 This extension attribute doesn't work for all output formats! It's currently only supported for PDF, PS and Java2D-based renderers.</p>
-<h2 id="color-functions-wzxhzdk25wzxhzdk26">Color functions <a id="color-functions"></a></h2>
+<h3 id="color-functions-wzxhzdk28wzxhzdk29">Color functions <a id="color-functions"></a></h3>
 <p>XSL-FO supports specifying color using the rgb(), rgb-icc() and system-color() functions. Apache FOP provides additional color functions for special use cases. Please note that using these functions compromises the interoperability of an FO document.</p>
-<h4 id="cmyk-wzxhzdk27wzxhzdk28">cmyk() ## <a id="color-function-cmyk"></a></h4>
+<h4 id="cmykwzxhzdk30wzxhzdk31">cmyk()<a id="color-function-cmyk"></a></h4>
 <p><code>color cmyk(numeric, numeric, numeric, numeric)</code> </p>
 <p>This function will construct a color in device-specific CMYK color space. The numbers must be between 0.0 and 1.0. For output formats that don't support device-specific color space the CMYK value is converted to an sRGB value.</p></div>
       </div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/fonts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/fonts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/fonts.html Mon Dec  3 15:47:41 2012
@@ -458,7 +458,7 @@ $(document).ready(function () {
 
 
 <p>Review the documentation for <a href="configuration.html">FOP Configuration</a> for instructions on making the FOP configuration available to FOP when it runs. Otherwise, FOP has no way of finding your custom font information. It is currently not possible to easily configure fonts from Java code.</p>
-<h1 id="advanced-font-configuration-wzxhzdk26wzxhzdk27">Advanced font configuration <a id="advanced"></a></h1>
+<h2 id="advanced-font-configuration-wzxhzdk26wzxhzdk27">Advanced font configuration <a id="advanced"></a></h2>
 <p>The instructions found above should be sufficient for most users. Below are some additional instructions in case the basic font configuration doesn't lead to the desired results.</p>
 <h3 id="type-1-font-metrics-wzxhzdk28wzxhzdk29">Type 1 Font Metrics <a id="type1-metrics"></a></h3>
 <p>FOP includes PFMReader, which reads the PFM file that normally comes with a Type 1 font, and generates an appropriate font metrics file for it. To use it, run the class org.apache.fop.fonts.apps.PFMReader:</p>
@@ -587,7 +587,7 @@ java -cp build\fop.jar;lib\avalon-framew
 <p>If relative URLs are specified, they are evaluated relative to the value of the "font-base" setting. If there is no "font-base" setting, the fonts are evaluated relative to the base directory.</p>
 </li>
 </ul>
-<h3 id="auto-detect-and-auto-embedd-feature-wzxhzdk34wzxhzdk35">Auto-Detect and auto-embedd feature <a id="autodetect"></a></h3>
+<h3 id="auto-detect-and-auto-embed-feature-wzxhzdk34wzxhzdk35">Auto-Detect and auto-embed feature <a id="autodetect"></a></h3>
 <p>When the "auto-detect" flag is set in the configuration, FOP will automatically search for fonts in the default paths for your operating system.</p>
 <p>FOP will also auto-detect fonts which are available in the classpath, if they are described as "application/x-font" in the MANIFEST.MF file. For example, if your .jar file contains font/myfont.ttf:
 Manifest-Version: 1.0</p>



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org


Mime
View raw message