xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r840438 [3/6] - in /websites/staging/xmlgraphics/trunk/content: ./ fop/ fop/0.95/ fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/
Date Mon, 03 Dec 2012 04:59:21 GMT
Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/configuration.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/configuration.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/configuration.html Mon Dec  3 04:59:19 2012
@@ -341,11 +341,11 @@ $(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/1.0/">1.0</a></div> -->
-      	<div class="section-content"><h1 id="apachewzxhzdk6-fop-configuration">Apache&trade; FOP: Configuration</h1>
-<h2 id="configuration-file-basics-wzxhzdk7wzxhzdk8">Configuration File Basics <a id="general"></a></h2>
+      	<div class="section-content"><h1 id="apachewzxhzdk10-fop-configuration">Apache&trade; FOP: Configuration</h1>
+<h2 id="configuration-file-basics-wzxhzdk11wzxhzdk12">Configuration File Basics <a id="general"></a></h2>
 <p>The FOP configuration file is an XML file containing a variety of settings that are useful for controlling FOP's behavior, and for helping it find resources that you wish it to use.</p>
 <p>The easiest way to get started using a FOP configuration file is to copy the sample found at <code>{fop-dir}/conf/fop.xconf</code> 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.</p>
-<h3 id="making-configuration-available-to-fop-wzxhzdk9wzxhzdk10">Making Configuration Available to FOP <a id="general-available"></a></h3>
+<h3 id="making-configuration-available-to-fop-wzxhzdk13wzxhzdk14">Making Configuration Available to FOP <a id="general-available"></a></h3>
 <p>After creating your configuration file, you must tell FOP how to find it:</p>
 <ul>
 <li>
@@ -356,7 +356,7 @@ $(document).ready(function () {
 </li>
 </ul>
 <p>See <a href="embedding.html#config-internal">Setting the Configuration Programmatically</a> for instructions on how to do so in an embedded environment.</p>
-<h2 id="summary-of-the-general-configuration-options-wzxhzdk11wzxhzdk12">Summary of the General Configuration Options <a id="general-elements"></a></h2>
+<h2 id="summary-of-the-general-configuration-options-wzxhzdk15wzxhzdk16">Summary of the General Configuration Options <a id="general-elements"></a></h2>
 <table>
 <thead>
 <tr>
@@ -448,56 +448,80 @@ $(document).ready(function () {
 </tbody>
 </table>
 <p>This is an excerpt from the example configuration file coming with FOP:</p>
-<p><fop version="1.0"></p>
-<p><!-- Strict user configuration -->
-  <strict-configuration>true</strict-configuration></p>
-<p><!-- Strict FO validation -->
-  <strict-validation>true</strict-validation></p>
-<p><!-- Base URL for resolving relative URLs -->
-  <base>./</base></p>
-<p><!-- Font Base URL for resolving relative font URLs -->
-  <font-base>./</font-base></p>
-<p><!-- Source resolution in dpi (dots/pixels per inch) for determining the size of pixels in SVG and bitmap images, default: 72dpi -->
-  <source-resolution>72</source-resolution>
-  <!-- Target resolution in dpi (dots/pixels per inch) for specifying the target resolution for generated bitmaps, default: 72dpi -->
-  <target-resolution>72</target-resolution></p>
-<p><!-- default page-height and page-width, in case
-       value is specified as auto -->
-  <default-page-settings height="11in" width="8.26in"/></p>
-<p><!-- etc. etc..... -->
-</fop></p>
-<h1 id="image-loading-customization-wzxhzdk36wzxhzdk37">Image Loading Customization <a id="image-loading"></a></h1>
-<p class=".">Apache FOP uses the image loading framework from <a href="http://xmlgraphics.apache.org/commons/">Apache XML Graphics Commons</a> to load images using various plug-ins. Every image loader plug-in has a hard-coded usage penalty that influences which solution is chosen if there are multiple possibilities to load an image. Sometimes, though, these penalties need to be tweaked and this can be done in the FOP configuration. An example:
-<fop version="1.0"></p>
+<div class="codehilite"><pre><span class="nt">&lt;fop</span> <span class="na">version=</span><span class="s">&quot;1.0&quot;</span><span class="nt">&gt;</span>
+
+  <span class="c">&lt;!-- Strict user configuration --&gt;</span>
+  <span class="nt">&lt;strict-configuration&gt;</span>true<span class="nt">&lt;/strict-configuration&gt;</span>
+
+  <span class="c">&lt;!-- Strict FO validation --&gt;</span>
+  <span class="nt">&lt;strict-validation&gt;</span>true<span class="nt">&lt;/strict-validation&gt;</span>
+
+  <span class="c">&lt;!-- Base URL for resolving relative URLs --&gt;</span>
+  <span class="nt">&lt;base&gt;</span>./<span class="nt">&lt;/base&gt;</span>
+
+  <span class="c">&lt;!-- Font Base URL for resolving relative font URLs --&gt;</span>
+  <span class="nt">&lt;font-base&gt;</span>./<span class="nt">&lt;/font-base&gt;</span>
+
+  <span class="c">&lt;!-- Source resolution in dpi (dots/pixels per inch) for determining the size of pixels in SVG and bitmap images, default: 72dpi --&gt;</span>
+  <span class="nt">&lt;source-resolution&gt;</span>72<span class="nt">&lt;/source-resolution&gt;</span>
+  <span class="c">&lt;!-- Target resolution in dpi (dots/pixels per inch) for specifying the target resolution for generated bitmaps, default: 72dpi --&gt;</span>
+  <span class="nt">&lt;target-resolution&gt;</span>72<span class="nt">&lt;/target-resolution&gt;</span>
+
+  <span class="c">&lt;!-- default page-height and page-width, in case</span>
+<span class="c">       value is specified as auto --&gt;</span>
+  <span class="nt">&lt;default-page-settings</span> <span class="na">height=</span><span class="s">&quot;11in&quot;</span> <span class="na">width=</span><span class="s">&quot;8.26in&quot;</span><span class="nt">/&gt;</span>
+
+  <span class="c">&lt;!-- etc. etc..... --&gt;</span>
+<span class="nt">&lt;/fop&gt;</span>
+</pre></div>
+
+
+<h1 id="image-loading-customization-wzxhzdk17wzxhzdk18">Image Loading Customization <a id="image-loading"></a></h1>
+<p>Apache FOP uses the image loading framework from <a href="http://xmlgraphics.apache.org/commons/">Apache XML Graphics Commons</a> to load images using various plug-ins. Every image loader plug-in has a hard-coded usage penalty that influences which solution is chosen if there are multiple possibilities to load an image. Sometimes, though, these penalties need to be tweaked and this can be done in the FOP configuration. An example:</p>
+<div class="codehilite"><pre><span class="nt">&lt;fop</span> <span class="na">version=</span><span class="s">&quot;1.0&quot;</span><span class="nt">&gt;</span>
+  [..]
+  <span class="nt">&lt;image-loading&gt;</span>
+    <span class="nt">&lt;penalty</span> <span class="na">value=</span><span class="s">&quot;10000&quot;</span>
+      <span class="na">class=</span><span class="s">&quot;org.apache.xmlgraphics.image.loader.impl.ImageLoaderRawCCITTFax&quot;</span><span class="nt">/&gt;</span>
+    <span class="nt">&lt;penalty</span> <span class="na">value=</span><span class="s">&quot;INFINITE&quot;</span>
+      <span class="na">class=</span><span class="s">&quot;org.apache.xmlgraphics.image.loader.impl.ImageLoaderInternalTIFF&quot;</span><span class="nt">/&gt;</span>
+  <span class="nt">&lt;/image-loading&gt;</span>
+  <span class="nt">&lt;renderers....</span>
+<span class="err">&lt;/fop</span><span class="nt">&gt;</span>
+</pre></div>
+
+
+<p>The first penalty element increases the penalty for the raw CCITT loader. This practically forces the decoding of CCITT compressed TIFF images except if there are no TIFF codecs available.</p>
 <p>The second penalty element sets an "infinite" penalty for the TIFF loader using the internal TIFF codec. This practically disables that plug-in as it will never be chosen as a possible solution.</p>
 <p>Negative penalties are possible to promote a plug-in but a negative penalty sum will be treated as zero penalty in most cases. For more details on the image loading framework, please consult the documentation there.</p>
-<h2 id="renderer-configuration-wzxhzdk39wzxhzdk40">Renderer configuration <a id="renderers"></a></h2>
+<h2 id="renderer-configuration-wzxhzdk19wzxhzdk20">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>
-<p><renderers>
-    <renderer mime="application/pdf">
-      <filterList>
-        <!-- provides compression using zlib flate (default is on) -->
-        <value>flate</value>
-      </filterList>
-      <fonts>
-        <font metrics-url="arial.xml" kerning="yes" embed-url="arial.ttf">
-          <font-triplet name="Arial" style="normal" weight="normal"/>
-          <font-triplet name="ArialMT" style="normal" weight="normal"/>
-        </font>
-        <font metrics-url="arialb.xml" kerning="yes" embed-url="arialb.ttf">
-          <font-triplet name="Arial" style="normal" weight="bold"/>
-          <font-triplet name="ArialMT" style="normal" weight="bold"/>
-        </font>
-      </fonts>
-    </renderer></p>
-<div class="codehilite"><pre><span class="o">&lt;</span><span class="n">renderer</span> <span class="n">mime</span><span class="o">=</span><span class="s">&quot;application/postscript&quot;</span><span class="o">&gt;</span>
-<span class="o">&lt;!--</span> <span class="n">etc</span><span class="o">.</span> <span class="n">etc</span><span class="o">.....</span> <span class="o">--&gt;</span>
+<div class="codehilite"><pre>  <span class="nt">&lt;renderers&gt;</span>
+    <span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/pdf&quot;</span><span class="nt">&gt;</span>
+      <span class="nt">&lt;filterList&gt;</span>
+        <span class="c">&lt;!-- provides compression using zlib flate (default is on) --&gt;</span>
+        <span class="nt">&lt;value&gt;</span>flate<span class="nt">&lt;/value&gt;</span>
+      <span class="nt">&lt;/filterList&gt;</span>
+      <span class="nt">&lt;fonts&gt;</span>
+        <span class="nt">&lt;font</span> <span class="na">metrics-url=</span><span class="s">&quot;arial.xml&quot;</span> <span class="na">kerning=</span><span class="s">&quot;yes&quot;</span> <span class="na">embed-url=</span><span class="s">&quot;arial.ttf&quot;</span><span class="nt">&gt;</span>
+          <span class="nt">&lt;font-triplet</span> <span class="na">name=</span><span class="s">&quot;Arial&quot;</span> <span class="na">style=</span><span class="s">&quot;normal&quot;</span> <span class="na">weight=</span><span class="s">&quot;normal&quot;</span><span class="nt">/&gt;</span>
+          <span class="nt">&lt;font-triplet</span> <span class="na">name=</span><span class="s">&quot;ArialMT&quot;</span> <span class="na">style=</span><span class="s">&quot;normal&quot;</span> <span class="na">weight=</span><span class="s">&quot;normal&quot;</span><span class="nt">/&gt;</span>
+        <span class="nt">&lt;/font&gt;</span>
+        <span class="nt">&lt;font</span> <span class="na">metrics-url=</span><span class="s">&quot;arialb.xml&quot;</span> <span class="na">kerning=</span><span class="s">&quot;yes&quot;</span> <span class="na">embed-url=</span><span class="s">&quot;arialb.ttf&quot;</span><span class="nt">&gt;</span>
+          <span class="nt">&lt;font-triplet</span> <span class="na">name=</span><span class="s">&quot;Arial&quot;</span> <span class="na">style=</span><span class="s">&quot;normal&quot;</span> <span class="na">weight=</span><span class="s">&quot;bold&quot;</span><span class="nt">/&gt;</span>
+          <span class="nt">&lt;font-triplet</span> <span class="na">name=</span><span class="s">&quot;ArialMT&quot;</span> <span class="na">style=</span><span class="s">&quot;normal&quot;</span> <span class="na">weight=</span><span class="s">&quot;bold&quot;</span><span class="nt">/&gt;</span>
+        <span class="nt">&lt;/font&gt;</span>
+      <span class="nt">&lt;/fonts&gt;</span>
+    <span class="nt">&lt;/renderer&gt;</span>
+
+    <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="c">&lt;!-- etc. etc..... --&gt;</span>
 </pre></div>
 
 
 <p>The details on the font configuration can be found on the separate <a href="fonts.html">Fonts</a> page. Note especially the section entitled <a href="fonts.html#register">Register Fonts with FOP</a> .</p>
-<h3 id="special-settings-for-the-pdf-renderer-wzxhzdk59wzxhzdk60">Special Settings for the PDF Renderer <a id="pdf-renderer"></a></h3>
+<h3 id="special-settings-for-the-pdf-renderer-wzxhzdk21wzxhzdk22">Special Settings for the PDF Renderer <a id="pdf-renderer"></a></h3>
 <p>The configuration element for the PDF renderer contains two elements. One is for the font configuration (please follow the link above) and one is for the "filter list". The filter list controls how the individual objects in a PDF file are encoded. By default, all objects get "flate" encoded (i.e. simply compressed with the same algorithm that is also used in ZIP files). Most users don't need to change that setting. For debugging purposes, it may be desired not to compress the internal objects at all so the generated PDF commands can be read. In that case, you can simply use the following filter list. The second filter list (type="image") ensures that all images still get compressed but also ASCII-85 encoded so the produced PDF file is still easily readable in a text editor.</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/pdf&quot;</span><span class="nt">&gt;</span>
   <span class="nt">&lt;filterList&gt;</span>
@@ -549,7 +573,7 @@ $(document).ready(function () {
 </pre></div>
 
 
-<h2 id="special-settings-for-the-postscript-renderer-wzxhzdk61wzxhzdk62">Special Settings for the PostScript Renderer <a id="ps-renderer"></a></h2>
+<h2 id="special-settings-for-the-postscript-renderer-wzxhzdk23wzxhzdk24">Special Settings for the PostScript Renderer <a id="ps-renderer"></a></h2>
 <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>
@@ -568,27 +592,34 @@ $(document).ready(function () {
 </pre></div>
 
 
-<h2 id="special-settings-for-the-pcl-renderer-wzxhzdk63wzxhzdk64">Special Settings for the PCL Renderer <a id="pcl-renderer"></a></h2>
+<h2 id="special-settings-for-the-pcl-renderer-wzxhzdk25wzxhzdk26">Special Settings for the PCL Renderer <a id="pcl-renderer"></a></h2>
 <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.
-<renderer mime="application/vnd.hp-PCL">
-  <rendering>quality</rendering>
-  <text-rendering>bitmap</text-rendering>
-</renderer>
-The default value for the "rendering" setting is "speed" which causes borders to be painted as plain rectangles. In this mode, no special borders (dotted, dashed etc.) are available. If you want support for all border modes, set the value to "quality" as indicated above. This will cause the borders to be painted as bitmaps.</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>
+  <span class="nt">&lt;rendering&gt;</span>quality<span class="nt">&lt;/rendering&gt;</span>
+  <span class="nt">&lt;text-rendering&gt;</span>bitmap<span class="nt">&lt;/text-rendering&gt;</span>
+<span class="nt">&lt;/renderer&gt;</span>
+</pre></div>
+
+
+<p>The default value for the "rendering" setting is "speed" which causes borders to be painted as plain rectangles. In this mode, no special borders (dotted, dashed etc.) are available. If you want support for all border modes, set the value to "quality" as indicated above. This will cause the borders to be painted as bitmaps.</p>
 <p>The default value for the "text-rendering" setting is "auto" which paints the base fonts using PCL fonts. Non-base fonts are painted as bitmaps through Java2D. If the mix of painting methods results in unwelcome output, you can set this to "bitmap" which causes all text to be rendered as bitmaps.</p>
-<h3 id="special-settings-for-the-afp-renderer-wzxhzdk71wzxhzdk72">Special Settings for the AFP Renderer <a id="afp-renderer"></a></h3>
-<p>Additionally, there are certain settings that control how the renderer handles various elements.
-<renderer mime="application/x-afp">
-  <images mode="b+w" bits-per-pixel="8" native="true"/>
-  <renderer-resolution>240</renderer-resolution></p>
-<p><!-- a default external resource group file -->
-  <resource-group-file>resources.afp</resource-group-file>
-</renderer>
-The default value for the images "mode" setting is "b+w" (black and white). When the images "mode" setting is "b+w" a "bits-per-pixel" setting can be provided to aid the grayscale conversion process. With this setting all images referenced in your source document are converted to an IOCA FS45 grayscale bitmap image form. When the setting is "color" all images are converted to an IOCA FS45 color bitmap image form. When "native" setting is "true", all images encountered (TIFF, GIF, JPEG and Encapsulated Postscript etc.) will be embedded directly in the datastream in their native form using a MO:DCA Object Container.</p>
+<h3 id="special-settings-for-the-afp-renderer-wzxhzdk27wzxhzdk28">Special Settings for the AFP Renderer <a id="afp-renderer"></a></h3>
+<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/x-afp&quot;</span><span class="nt">&gt;</span>
+  <span class="nt">&lt;images</span> <span class="na">mode=</span><span class="s">&quot;b+w&quot;</span> <span class="na">bits-per-pixel=</span><span class="s">&quot;8&quot;</span> <span class="na">native=</span><span class="s">&quot;true&quot;</span><span class="nt">/&gt;</span>
+  <span class="nt">&lt;renderer-resolution&gt;</span>240<span class="nt">&lt;/renderer-resolution&gt;</span>
+
+  <span class="c">&lt;!-- a default external resource group file --&gt;</span>
+  <span class="nt">&lt;resource-group-file&gt;</span>resources.afp<span class="nt">&lt;/resource-group-file&gt;</span>
+<span class="nt">&lt;/renderer&gt;</span>
+</pre></div>
+
+
+<p>The default value for the images "mode" setting is "b+w" (black and white). When the images "mode" setting is "b+w" a "bits-per-pixel" setting can be provided to aid the grayscale conversion process. With this setting all images referenced in your source document are converted to an IOCA FS45 grayscale bitmap image form. When the setting is "color" all images are converted to an IOCA FS45 color bitmap image form. When "native" setting is "true", all images encountered (TIFF, GIF, JPEG and Encapsulated Postscript etc.) will be embedded directly in the datastream in their native form using a MO:DCA Object Container.</p>
 <p>The default value for the "renderer-resolution" is 240 dpi.</p>
 <p>By default if there is no configuration definition for "resource-group-file", external resources will be placed in a file called resources.afp.</p>
-<h2 id="when-it-does-not-work-wzxhzdk81wzxhzdk82">When it does not work <a id="When+it+does+not+work"></a></h2>
+<h2 id="when-it-does-not-work-wzxhzdk29wzxhzdk30">When it does not work <a id="When+it+does+not+work"></a></h2>
 <p>FOP searches the configuration file for the information it expects, at the position it expects. When that information is not present, FOP will not complain, it will just continue. When there is other information in the file, FOP will not complain, it will just ignore it. That means that when your configuration information is in the file but in a different XML element, or in a different XML path, than FOP expects, it will be silently ignored.</p>
 <p>Check the following possibilities:</p>
 <ul>
@@ -596,15 +627,16 @@ The default value for the images "mode" 
 <p>The format of the configuration file has changed considerably between FOP 0.20.5 and FOP 1.0 and its beta versions. Did you convert your file to the new format?</p>
 </li>
 <li>
-<p>The FOP distribution contains a schema for configuration files, at src/foschema/fop-configuration.xsd. Did you validate your configuration file against it? Add the following schema location to the <code>schema</code> element:<fop
-xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-xsi:noNamespaceSchemaLocation=
-"http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop-configuration.xsd?view=co">
-and run the configuration file through a validating schema parser. Note that the schema cannot detect all errors, and that it is stricter about the order of some elements than FOP itself is.</p>
-</li>
-<li>
-<p>Run FOP in debug mode (command line option <code>-d</code> ). This makes FOP report which configuration information it finds. Check if FOP finds what you expect.</p>
+<p>The FOP distribution contains a schema for configuration files, at src/foschema/fop-configuration.xsd. Did you validate your configuration file against it? Add the following schema location to the <code>schema</code> element:</p>
+<p><fop
+    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    xsi:noNamespaceSchemaLocation=
+    "http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop-configuration.xsd?view=co"></p>
 </li>
+</ul>
+<p>and run the configuration file through a validating schema parser. Note that the schema cannot detect all errors, and that it is stricter about the order of some elements than FOP itself is.</p>
+<ul>
+<li>Run FOP in debug mode (command line option <code>-d</code> ). This makes FOP report which configuration information it finds. Check if FOP finds what you expect.</li>
 </ul></div>
       </div>
       

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/extensions.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/extensions.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/extensions.html Mon Dec  3 04:59:19 2012
@@ -341,24 +341,27 @@ $(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/1.0/">1.0</a></div> -->
-      	<div class="section-content"><h1 id="standard-apachewzxhzdk0-fop-extensions">Standard Apache&trade; FOP Extensions</h1>
+      	<div class="section-content"><h1 id="standard-apachewzxhzdk1-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, Apache&trade; 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> .
 All extensions require the correct use of an appropriate namespace in your input document.</p>
-<h1 id="svg-wzxhzdk2wzxhzdk3">SVG <a id="svg"></a></h1>
+<h1 id="svg-wzxhzdk3wzxhzdk4">SVG <a id="svg"></a></h1>
 <p>Please see the <a href="graphics.html#svg">SVG documentation</a> for more details.</p>
-<h2 id="fo-extensions-wzxhzdk4wzxhzdk5">FO Extensions <a id="fo-extensions"></a></h2>
-<h3 id="namespace-wzxhzdk6wzxhzdk7">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:
-<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
-               xmlns:fox="http://xmlgraphics.apache.org/fop/extensions"></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>
+<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>
 <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>
 <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.
-<fox:destination internal-destination="table-of-contents"/>
-...
-<fo:block id="table-of-contents">Table of Contents</fo:block><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>
+    <fox:destination internal-destination="table-of-contents"/>
+    ...
+    <fo:block id="table-of-contents">Table of Contents</fo:block><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>
 <h2 id="table-continuation-label-wzxhzdk18wzxhzdk19">Table Continuation Label <a id="table-continue-label"></a></h2>
 <p>This extension element hasn't been reimplemented for the redesigned code, yet.</p>
 <h3 id="foxorphan-content-limit-and-foxwidow-content-limit-wzxhzdk20wzxhzdk21">fox:orphan-content-limit and fox:widow-content-limit <a id="widow-orphan-content-limit"></a></h3>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/fonts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/fonts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/fonts.html Mon Dec  3 04:59:19 2012
@@ -341,9 +341,9 @@ $(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/1.0/">1.0</a></div> -->
-      	<div class="section-content"><h1 id="apachewzxhzdk3-fop-fonts">Apache&trade; FOP: Fonts</h1>
+      	<div class="section-content"><h1 id="apachewzxhzdk5-fop-fonts">Apache&trade; FOP: Fonts</h1>
 <p><authors><person email="" name="Jeremias Märki"></person><person email="" name="Tore Engvig"></person><person email="" name="Adrian Cumiskey"></person><person email="" name="Max Berger"></person></authors></p>
-<h2 id="summary-wzxhzdk14wzxhzdk15">Summary <a id="intro"></a></h2>
+<h2 id="summary-wzxhzdk16wzxhzdk17">Summary <a id="intro"></a></h2>
 <p>The following table summarizes the font capabilities of the various Apache&trade; FOP renderers:</p>
 <table>
 <thead>
@@ -421,7 +421,7 @@ $(document).ready(function () {
 </tr>
 </tbody>
 </table>
-<h2 id="base-14-fonts-wzxhzdk17wzxhzdk18">Base-14 Fonts <a id="Base-14+Fonts"></a></h2>
+<h2 id="base-14-fonts-wzxhzdk19wzxhzdk20">Base-14 Fonts <a id="Base-14+Fonts"></a></h2>
 <p>The Adobe PostScript and PDF Specification specify a set of 14 fonts that must be available to every PostScript interpreter and PDF reader: Helvetica (normal, bold, italic, bold italic), Times (normal, bold, italic, bold italic), Courier (normal, bold, italic, bold italic), Symbol and ZapfDingbats.</p>
 <p>The following font family names are hard-coded into FOP for the Base-14 font set:</p>
 <table>
@@ -455,14 +455,14 @@ $(document).ready(function () {
 </tbody>
 </table>
 <p>Please note that recent versions of Adobe Acrobat Reader replace "Helvetica" with "Arial" and "Times" with "Times New Roman" internally. GhostScript replaces "Helvetica" with "Nimbus Sans L" and "Times" with "Nimbus Roman No9 L". Other document viewers may do similar font substitutions. If you need to make sure that there are no such substitutions, you need to specify an explicit font and embed it in the target document.</p>
-<h2 id="missing-fonts-wzxhzdk19wzxhzdk20">Missing Fonts <a id="missing-fonts"></a></h2>
+<h2 id="missing-fonts-wzxhzdk21wzxhzdk22">Missing Fonts <a id="missing-fonts"></a></h2>
 <p>When FOP does not have a specific font at its disposal (because it's not installed in the operating system or set up in FOP's configuration), the font is replaced with "any". "any" is internally mapped to the Base-14 font "Times" (see above).</p>
-<h2 id="missing-glyphs-wzxhzdk21wzxhzdk22">Missing Glyphs <a id="missing-glyphs"></a></h2>
+<h2 id="missing-glyphs-wzxhzdk23wzxhzdk24">Missing Glyphs <a id="missing-glyphs"></a></h2>
 <p>Every font contains a particular set of <a href="http://en.wikipedia.org/wiki/Glyph">glyphs</a> . If no glyph can be found for a given character, FOP will issue a warning and use the glpyh for "#" (if available) instead. Before it does that, it consults a (currently hard-coded) registry of glyph substitution groups (see Glyphs.java in Apache XML Graphics Commons). This registry can supply alternative glyphs in some cases (like using space when a no-break space is requested). But there's no guarantee that the result will be as expected (for example, in the case of hyphens and similar glyphs). A better way is to use a font that has all the necessary glyphs. This glyph substitution is only a last resort.</p>
-<h2 id="java2dawtoperating-system-fonts-wzxhzdk23wzxhzdk24">Java2D/AWT/Operating System Fonts <a id="awt"></a></h2>
+<h2 id="java2dawtoperating-system-fonts-wzxhzdk25wzxhzdk26">Java2D/AWT/Operating System Fonts <a id="awt"></a></h2>
 <p>The Java2D family of renderers (Java2D, AWT, Print, TIFF, PNG), use the Java AWT subsystem for font metric information. Through operating system registration, the AWT subsystem knows what fonts are available on the system, and the font metrics for each one.</p>
 <p>When working with one of these output formats and you're missing a font, just install it in your operating system and they should be available for these renderers. Please note that this is not true for other output formats such as PDF or PostScript.</p>
-<h2 id="custom-fonts-wzxhzdk25wzxhzdk26">Custom Fonts <a id="custom"></a></h2>
+<h2 id="custom-fonts-wzxhzdk27wzxhzdk28">Custom Fonts <a id="custom"></a></h2>
 <p>Support for custom fonts is highly output format dependent (see above table). This section shows how to add Type 1 and TrueType fonts to the PDF, PostScript and Java2D-based renderers. Other renderers (like AFP) support other font formats. Details in this case can be found on the page about <a href="output.html">output formats</a> .</p>
 <p>In earlier FOP versions, it was always necessary to create an XML font metrics file if you wanted to add a custom font. This unconvenient step has been removed and in addition to that, FOP supports auto-registration of fonts, i.e. FOP can find fonts installed in your operating system or can scan user-specified directories for fonts. Font registration via XML font metrics file is still supported and may still be necessary for some very special cases as fallback variant while we stabilize font auto-detection.</p>
 <p>Basic information about fonts can be found at:</p>
@@ -474,27 +474,29 @@ $(document).ready(function () {
 <p><a href="http://partners.adobe.com/asn/developer/technotes/fonts.html">Adobe Font Technote</a> </p>
 </li>
 </ul>
-<h2 id="basic-font-configuration-wzxhzdk27wzxhzdk28">Basic font configuration <a id="basics"></a></h2>
+<h2 id="basic-font-configuration-wzxhzdk29wzxhzdk30">Basic font configuration <a id="basics"></a></h2>
 <p>If you want FOP to use custom fonts, you need to tell it where to find them. This is done in the configuration file and once per renderer (because each output format is a little different). In the basic form, you can either tell FOP to find your operating system fonts or you can specify directories that it will search for support fonts. These fonts will then automatically be registered.</p>
-<p><renderers>
-   <renderer mime="application/pdf">
-      <fonts>
-         <!-- register all the fonts found in a directory -->
-         <directory>C:\MyFonts1</directory></p>
-<div class="codehilite"><pre>     <span class="c">&lt;!-- register all the fonts found in a directory and all of its sub directories (use with care) --&gt;</span>
-     <span class="nt">&lt;directory</span> <span class="na">recursive=</span><span class="s">&quot;true&quot;</span><span class="nt">&gt;</span>C:\MyFonts2<span class="nt">&lt;/directory&gt;</span>
-
-     <span class="c">&lt;!-- automatically detect operating system installed fonts --&gt;</span>
-     <span class="nt">&lt;auto-detect/&gt;</span>  
-  <span class="nt">&lt;/fonts&gt;</span>
+<div class="codehilite"><pre><span class="nt">&lt;renderers&gt;</span>
+   <span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/pdf&quot;</span><span class="nt">&gt;</span>
+      <span class="nt">&lt;fonts&gt;</span>
+         <span class="c">&lt;!-- register all the fonts found in a directory --&gt;</span>
+         <span class="nt">&lt;directory&gt;</span>C:\MyFonts1<span class="nt">&lt;/directory&gt;</span>
+
+         <span class="c">&lt;!-- register all the fonts found in a directory and all of its sub directories (use with care) --&gt;</span>
+         <span class="nt">&lt;directory</span> <span class="na">recursive=</span><span class="s">&quot;true&quot;</span><span class="nt">&gt;</span>C:\MyFonts2<span class="nt">&lt;/directory&gt;</span>
+
+         <span class="c">&lt;!-- automatically detect operating system installed fonts --&gt;</span>
+         <span class="nt">&lt;auto-detect/&gt;</span>  
+      <span class="nt">&lt;/fonts&gt;</span>
+   <span class="nt">&lt;/renderer&gt;</span>
+<span class="nt">&lt;/renderers&gt;</span>
 </pre></div>
 
 
-<p></renderer>
-</renderers>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-wzxhzdk37wzxhzdk38">Advanced font configuration <a id="advanced"></a></h1>
+<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-wzxhzdk31wzxhzdk32">Advanced font configuration <a id="advanced"></a></h1>
 <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-wzxhzdk39wzxhzdk40">Type 1 Font Metrics <a id="type1-metrics"></a></h3>
+<h3 id="type-1-font-metrics-wzxhzdk33wzxhzdk34">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>
 <p>Windows:
 java -cp build\fop.jar;lib\avalon-framework.jar;lib\commons-logging.jar;lib\commons-io.jar
@@ -507,7 +509,7 @@ PFMReader [options]:</p>
 <li><strong>-fn <fontname></strong> By default, FOP uses the fontname from the .pfm file when embedding the font. Use the "-fn" option to override this name with one you have chosen. This may be useful in some cases to ensure that applications using the output document (Acrobat Reader for example) use the embedded font instead of a local font with the same name.
 The classpath in the above example has been simplified for readability. You will have to adjust the classpath to the names of the actual JAR files in the lib directory. xml-apis.jar, xercesImpl.jar, xalan.jar and serializer.jar are not necessary for JDK version 1.4 or later.The tool will construct some values (FontBBox, StemV and ItalicAngle) based on assumptions and calculations which are only an approximation to the real values. FontBBox and Italic Angle can be found in the human-readable part of the PFB file or in the AFM file. The PFMReader tool does not yet interpret PFB or AFM files, so if you want to be correct, you may have to adjust the values in the XML file manually. The constructed values however appear to have no visible influence.</li>
 </ul>
-<h2 id="truetype-font-metrics-wzxhzdk41wzxhzdk42">TrueType Font Metrics <a id="truetype-metrics"></a></h2>
+<h2 id="truetype-font-metrics-wzxhzdk35wzxhzdk36">TrueType Font Metrics <a id="truetype-metrics"></a></h2>
 <p>FOP includes TTFReader, which reads the TTF file and generates an appropriate font metrics file for it. Use it in a similar manner to PFMReader. For example, to create such a metrics file in Windows from the TrueType font at c:\myfonts\cmr10.ttf:
 java -cp build\fop.jar;lib\avalon-framework.jar;lib\commons-logging.jar;lib\commons-io.jar
           org.apache.fop.fonts.apps.TTFReader [options]
@@ -564,35 +566,39 @@ TTFReader [options]:</p>
 java -cp build\fop.jar;lib\avalon-framework.jar;lib\commons-logging.jar;lib\commons-io.jar
           org.apache.fop.fonts.apps.TTFReader -ttcname "MS Mincho"
           msmincho.ttc msminch.xml
-Alternatively, the individual sub-fonts of a TrueType Collections can be selected using the "sub-font" attribute on the "font" element. That means that generating an XML font metrics file for TrueType collections is not necessary anymore. Example:
-<font embed-url="gulim.ttc" sub-font="GulimChe">
-  <font-triplet name="GulimChe" style="normal" weight="normal"/>
-</font></p>
-<h2 id="register-fonts-with-fop-wzxhzdk46wzxhzdk47">Register Fonts with FOP <a id="register"></a></h2>
+Alternatively, the individual sub-fonts of a TrueType Collections can be selected using the "sub-font" attribute on the "font" element. That means that generating an XML font metrics file for TrueType collections is not necessary anymore. Example:</p>
+<div class="codehilite"><pre><span class="nt">&lt;font</span> <span class="na">embed-url=</span><span class="s">&quot;gulim.ttc&quot;</span> <span class="na">sub-font=</span><span class="s">&quot;GulimChe&quot;</span><span class="nt">&gt;</span>
+  <span class="nt">&lt;font-triplet</span> <span class="na">name=</span><span class="s">&quot;GulimChe&quot;</span> <span class="na">style=</span><span class="s">&quot;normal&quot;</span> <span class="na">weight=</span><span class="s">&quot;normal&quot;</span><span class="nt">/&gt;</span>
+<span class="nt">&lt;/font&gt;</span>
+</pre></div>
+
+
+<h2 id="register-fonts-with-fop-wzxhzdk37wzxhzdk38">Register Fonts with FOP <a id="register"></a></h2>
 <p>You must tell FOP how to find and use the font metrics files by registering them in the <a href="configuration.html">FOP Configuration</a> . Add entries for your custom fonts, regardless of font type, to the configuration file in a manner similar to the following:</p>
-<p><renderers>
-   <renderer mime="application/pdf">
-      <fonts>
-         <!-- register a particular font -->
-         <font metrics-url="file:///C:/myfonts/FTL_____.xml" kerning="yes"
-           embed-url="file:///C:/myfonts/FTL_____.pfb"
-           encoding-mode="single-byte">
-            <font-triplet name="FrutigerLight" style="normal" weight="normal"/>
-         </font></p>
-<div class="codehilite"><pre>     <span class="c">&lt;!-- register all the fonts found in a directory --&gt;</span>
-     <span class="nt">&lt;directory&gt;</span>C:\MyFonts1<span class="nt">&lt;/directory&gt;</span>
-
-     <span class="c">&lt;!-- register all the fonts found in a directory and all of its sub directories (use with care) --&gt;</span>
-     <span class="nt">&lt;directory</span> <span class="na">recursive=</span><span class="s">&quot;true&quot;</span><span class="nt">&gt;</span>C:\MyFonts2<span class="nt">&lt;/directory&gt;</span>
-
-     <span class="c">&lt;!-- automatically detect operating system installed fonts --&gt;</span>
-     <span class="nt">&lt;auto-detect/&gt;</span>  
-  <span class="nt">&lt;/fonts&gt;</span>
+<div class="codehilite"><pre><span class="nt">&lt;renderers&gt;</span>
+   <span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/pdf&quot;</span><span class="nt">&gt;</span>
+      <span class="nt">&lt;fonts&gt;</span>
+         <span class="c">&lt;!-- register a particular font --&gt;</span>
+         <span class="nt">&lt;font</span> <span class="na">metrics-url=</span><span class="s">&quot;file:///C:/myfonts/FTL_____.xml&quot;</span> <span class="na">kerning=</span><span class="s">&quot;yes&quot;</span>
+           <span class="na">embed-url=</span><span class="s">&quot;file:///C:/myfonts/FTL_____.pfb&quot;</span>
+           <span class="na">encoding-mode=</span><span class="s">&quot;single-byte&quot;</span><span class="nt">&gt;</span>
+            <span class="nt">&lt;font-triplet</span> <span class="na">name=</span><span class="s">&quot;FrutigerLight&quot;</span> <span class="na">style=</span><span class="s">&quot;normal&quot;</span> <span class="na">weight=</span><span class="s">&quot;normal&quot;</span><span class="nt">/&gt;</span>
+         <span class="nt">&lt;/font&gt;</span>
+
+         <span class="c">&lt;!-- register all the fonts found in a directory --&gt;</span>
+         <span class="nt">&lt;directory&gt;</span>C:\MyFonts1<span class="nt">&lt;/directory&gt;</span>
+
+         <span class="c">&lt;!-- register all the fonts found in a directory and all of its sub directories (use with care) --&gt;</span>
+         <span class="nt">&lt;directory</span> <span class="na">recursive=</span><span class="s">&quot;true&quot;</span><span class="nt">&gt;</span>C:\MyFonts2<span class="nt">&lt;/directory&gt;</span>
+
+         <span class="c">&lt;!-- automatically detect operating system installed fonts --&gt;</span>
+         <span class="nt">&lt;auto-detect/&gt;</span>  
+      <span class="nt">&lt;/fonts&gt;</span>
+   <span class="nt">&lt;/renderer&gt;</span>
+<span class="nt">&lt;/renderers&gt;</span>
 </pre></div>
 
 
-<p></renderer>
-</renderers></p>
 <ul>
 <li>
 <p>URLs are used to access the font metric and font files. Relative URLs are resolved relative to the font-base property (or base) if available. See <a href="configuration.html">FOP: Configuration</a> for more information.</p>
@@ -642,7 +648,7 @@ Alternatively, the individual sub-fonts 
 <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-embed-feature-wzxhzdk57wzxhzdk58">Auto-Detect and auto-embed feature <a id="autodetect"></a></h3>
+<h3 id="auto-detect-and-auto-embed-feature-wzxhzdk39wzxhzdk40">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>
@@ -652,7 +658,7 @@ Manifest-Version: 1.0</p>
 
 
 <p>This feature allows you to create JAR files containing fonts. The JAR files can be added to fop by providem them in the classpath, e.g. copying them into the lib/ directory.</p>
-<h3 id="embedding-wzxhzdk59wzxhzdk60">Embedding <a id="embedding"></a></h3>
+<h3 id="embedding-wzxhzdk41wzxhzdk42">Embedding <a id="embedding"></a></h3>
 <p>By default, all fonts are embedded if an output format supports font embedding. In some cases, however, it is preferred that some fonts are only referenced. When working with referenced fonts it is important to be in control of the target environment where the produced document is consumed, i.e. the necessary fonts have to be installed there.</p>
 <p>There are two different ways how you can specify that a font should be referenced:</p>
 <ol>
@@ -661,8 +667,6 @@ Manifest-Version: 1.0</p>
 </li>
 <li>
 <p>For automatically configured fonts there's a different mechanism to specify which fonts should be referenced rather than embedded. This is done in the "referenced-fonts" element in the configuration. Here's an example:</p>
-</li>
-</ol>
 <p><fop version="1.0">
    <fonts>
       <referenced-fonts>
@@ -670,8 +674,10 @@ Manifest-Version: 1.0</p>
         <match font-family="DejaVu.*"/>
       </referenced-fonts>
    </fonts>
-</fop>
-At the moment, you can only match fonts against their font-family. It is possible to use regular expressions as is shown in the second example above ("DejaVu.*"). The syntax for the regular expressions used here are the one used by the <a href="http://java.sun.com/j2se/1.4/docs/api/java/util/regex/package-summary.html">package</a> . So, in the above snippet "Helvetica" and all variants of the "DejaVu" font family are referenced. If you want to reference all fonts, just specify <code>font-family=".*"</code> .</p>
+</fop></p>
+</li>
+</ol>
+<p>At the moment, you can only match fonts against their font-family. It is possible to use regular expressions as is shown in the second example above ("DejaVu.*"). The syntax for the regular expressions used here are the one used by the <a href="http://java.sun.com/j2se/1.4/docs/api/java/util/regex/package-summary.html">package</a> . So, in the above snippet "Helvetica" and all variants of the "DejaVu" font family are referenced. If you want to reference all fonts, just specify <code>font-family=".*"</code> .</p>
 <p>The <code>referenced-fonts</code> element can be placed either inside the general <code>fonts</code> element (right under the root) or in the <code>fonts</code> element under the renderer configuration. In the first case, matches apply to all renderers. In the second case, matches only apply to the renderer where the element was specified. Both cases can be used at the same time.</p>
 <p>Various notes related to embedded fonts:</p>
 <ul>
@@ -691,7 +697,7 @@ At the moment, you can only match fonts 
 <p>When embedding TrueType fonts (ttf) or TrueType Collections (ttc), a subset of the original font, containing only the glyphs used, is embedded in the output document. That's the default, but if you specify encoding-mode="single-byte" (see above), the complete font is embedded.</p>
 </li>
 </ul>
-<h3 id="substitution-wzxhzdk69wzxhzdk70">Substitution <a id="substitution"></a></h3>
+<h3 id="substitution-wzxhzdk43wzxhzdk44">Substitution <a id="substitution"></a></h3>
 <p>When a <substitutions/> section is defined in the configuration, FOP will re-map any font-family references found in your FO input to a given substitution font.</p>
 <ul>
 <li>
@@ -702,21 +708,24 @@ At the moment, you can only match fonts 
 </li>
 </ul>
 <p>For example you could make all FO font-family references to 'Arial' with weights between 700 and 900 reference the normal 'Arial Black' font.</p>
-<p><fop version="1.0">
-   <fonts>
-      <substitutions>
-         <substitution>
-            <from font-family="Arial" font-weight="700..900"/>
-            <to font-family="Arial Black"/>
-         </substitution>
-         <substitution>
-            <from font-family="FrutigerLight"/>
-            <to font-family="Times" font-weight="bold" font-style="italic"/>
-         </substitution>
-      </substitutions>
-   </fonts>
-</fop></p>
-<h1 id="font-selection-strategies-wzxhzdk86wzxhzdk87">Font Selection Strategies <a id="selection"></a></h1>
+<div class="codehilite"><pre><span class="nt">&lt;fop</span> <span class="na">version=</span><span class="s">&quot;1.0&quot;</span><span class="nt">&gt;</span>
+   <span class="nt">&lt;fonts&gt;</span>
+      <span class="nt">&lt;substitutions&gt;</span>
+         <span class="nt">&lt;substitution&gt;</span>
+            <span class="nt">&lt;from</span> <span class="na">font-family=</span><span class="s">&quot;Arial&quot;</span> <span class="na">font-weight=</span><span class="s">&quot;700..900&quot;</span><span class="nt">/&gt;</span>
+            <span class="nt">&lt;to</span> <span class="na">font-family=</span><span class="s">&quot;Arial Black&quot;</span><span class="nt">/&gt;</span>
+         <span class="nt">&lt;/substitution&gt;</span>
+         <span class="nt">&lt;substitution&gt;</span>
+            <span class="nt">&lt;from</span> <span class="na">font-family=</span><span class="s">&quot;FrutigerLight&quot;</span><span class="nt">/&gt;</span>
+            <span class="nt">&lt;to</span> <span class="na">font-family=</span><span class="s">&quot;Times&quot;</span> <span class="na">font-weight=</span><span class="s">&quot;bold&quot;</span> <span class="na">font-style=</span><span class="s">&quot;italic&quot;</span><span class="nt">/&gt;</span>
+         <span class="nt">&lt;/substitution&gt;</span>
+      <span class="nt">&lt;/substitutions&gt;</span>
+   <span class="nt">&lt;/fonts&gt;</span>
+<span class="nt">&lt;/fop&gt;</span>
+</pre></div>
+
+
+<h1 id="font-selection-strategies-wzxhzdk46wzxhzdk47">Font Selection Strategies <a id="selection"></a></h1>
 <p>There are two font selection strategies: character-by-character or auto. The default is auto.</p>
 <p>Auto selected the first font from the list which is able to display the most characters in a given word. This means (assume font A has characters for abclmn, font B for lnmxyz, fontlist is A,B):</p>
 <ul>
@@ -734,7 +743,7 @@ At the moment, you can only match fonts 
 </li>
 </ul>
 <p>Character-by-Character is NOT yet supported!</p>
-<h2 id="font-list-command-line-tool-wzxhzdk88wzxhzdk89">Font List Command-Line Tool <a id="font-list"></a></h2>
+<h2 id="font-list-command-line-tool-wzxhzdk48wzxhzdk49">Font List Command-Line Tool <a id="font-list"></a></h2>
 <p>FOP contains a small command-line tool that lets you generate a list of all configured fonts. Its class name is: <code>org.apache.fop.tools.fontlist.FontListMain</code> . Run it with the "-?" parameter to get help for the various options.</p></div>
       </div>
       

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/metadata.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/metadata.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/metadata.html Mon Dec  3 04:59:19 2012
@@ -341,15 +341,39 @@ $(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/1.0/">1.0</a></div> -->
-      	<div class="section-content"><h1 id="apachewzxhzdk0-fop-metadata">Apache&trade; FOP: Metadata</h1>
-<h2 id="overview-wzxhzdk1wzxhzdk2">Overview <a id="overview"></a></h2>
+      	<div class="section-content"><h1 id="apachewzxhzdk1-fop-metadata">Apache&trade; FOP: Metadata</h1>
+<h2 id="overview-wzxhzdk2wzxhzdk3">Overview <a id="overview"></a></h2>
 <p>Document metadata is an important tool for categorizing and finding documents. Various formats support different kinds of metadata representation and to different levels. One of the more popular and flexible means of representing document or object metadata is <a href="http://www.adobe.com/products/xmp/">XMP (eXtensible Metadata Platform, specified by Adobe)</a> . PDF 1.4 introduced the use of XMP. The XMP specification lists recommendation for embedding XMP metdata in other document and image formats. Given its flexibility it makes sense to make use this approach in the XSL-FO context. Unfortunately, unlike SVG which also refers to XMP, XSL-FO doesn't recommend a preferred way of specifying document and object metadata. Therefore, there's no portable way to represent metadata in XSL-FO documents. Each implementation does it differently.</p>
-<h2 id="embedding-xmp-in-an-xsl-fo-document-wzxhzdk3wzxhzdk4">Embedding XMP in an XSL-FO document <a id="xmp-in-fo"></a></h2>
+<h2 id="embedding-xmp-in-an-xsl-fo-document-wzxhzdk4wzxhzdk5">Embedding XMP in an XSL-FO document <a id="xmp-in-fo"></a></h2>
 <p>As noted above, there's no officially recommended way to embed metadata in XSL-FO. Apache FOP supports embedding XMP in XSL-FO. Currently, only support for document-level metadata is implemented. Object-level metadata will be implemented when there's interest.</p>
 <p>Document-level metadata can be specified in the <code>fo:declarations</code> element. XMP specification recommends to use <code>x:xmpmeta</code> , <code>rdf:RDF</code> , and <code>rdf:Description</code> elements as shown in example below. Both <code>x:xmpmeta</code> and <code>rdf:RDF</code> elements are recognized as the top-level element introducing an XMP fragment (as per the XMP specification).</p>
-<h3 id="example-wzxhzdk5wzxhzdk6">Example <a id="xmp-example"></a></h3>
-<p class="."></p>
-<h1 id="implementation-in-apache-fop-wzxhzdk7wzxhzdk8">Implementation in Apache FOP <a id="xmp-impl-in-fop"></a></h1>
+<h3 id="example-wzxhzdk6wzxhzdk7">Example <a id="xmp-example"></a></h3>
+<div class="codehilite"><pre><span class="k">[..]</span>
+<span class="err">&lt;/fo:layout-master-set&gt;</span>
+    <span class="err">:declarations&gt;</span>
+  <span class="na">&lt;x:xmpmeta xmlns:x</span><span class="o">=</span><span class="s">&quot;adobe:ns:meta/&quot;&gt;</span>
+<span class="s">    &lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot;&gt;</span>
+<span class="s">      &lt;rdf:Description rdf:about=&quot;&quot;</span>
+<span class="s">          xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot;&gt;</span>
+<span class="s">        &lt;!-- Dublin Core properties go here --&gt;</span>
+<span class="s">        &lt;dc:title&gt;Document title&lt;/dc:title&gt;</span>
+<span class="s">        &lt;dc:creator&gt;Document author&lt;/dc:creator&gt;</span>
+<span class="s">        &lt;dc:description&gt;Document subject&lt;/dc:description&gt;</span>
+<span class="s">      &lt;/rdf:Description&gt;</span>
+<span class="s">      &lt;rdf:Description rdf:about=&quot;&quot;</span>
+<span class="s">          xmlns:xmp=&quot;http://ns.adobe.com/xap/1.0/&quot;&gt;</span>
+<span class="s">        &lt;!-- XMP properties go here --&gt;</span>
+<span class="s">        &lt;xmp:CreatorTool&gt;Tool used to make the PDF&lt;/xmp:CreatorTool&gt;</span>
+<span class="s">      &lt;/rdf:Description&gt;</span>
+<span class="s">    &lt;/rdf:RDF&gt;</span>
+<span class="s">  &lt;/x:xmpmeta&gt;</span>
+<span class="err">&lt;/fo:declarations&gt;</span>
+    <span class="err">:page-sequence</span> <span class="err">...</span>
+</pre></div>
+
+
+<p>[..] <code>fo:declarations</code>  <strong>must</strong> be declared after <code>fo:layout-master-set</code> and before the first <code>page-sequence</code> .</p>
+<h1 id="implementation-in-apache-fop-wzxhzdk8wzxhzdk9">Implementation in Apache FOP <a id="xmp-impl-in-fop"></a></h1>
 <p>Currently, XMP support is only available for PDF output.</p>
 <p>Originally, you could set some metadata information through FOP's FOUserAgent by using its set*() methods (like setTitle(String) or setAuthor(String). These values are directly used to set value in the PDF Info object. Since PDF 1.4, adding metadata as an XMP document to a PDF is possible. That means that there are now two mechanisms in PDF that hold metadata.</p>
 <p>Apache FOP now synchronizes the Info and the Metadata object in PDF, i.e. when you set the title and the author through the FOUserAgent, the two values will end up in the (old) Info object and in the new Metadata object as XMP content. If instead of FOUserAgent, you embed XMP metadata in the XSL-FO document (as shown above), the XMP metadata will be used as-is in the PDF Metadata object and some values from the XMP metadata will be copied to the Info object to maintain backwards-compatibility for PDF readers that don't support XMP metadata.</p>
@@ -442,7 +466,7 @@ $(document).ready(function () {
 </table>
 <p>Please refer to the <a href="http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf">XMP Specification</a> for information on other metadata namespaces.</p>
 <p>Property sets (Namespaces) not listed here are simply passed through to the final document (if supported). That is useful if you want to specify a custom metadata schema.</p>
-<h2 id="links-wzxhzdk9wzxhzdk10">Links <a id="links"></a></h2>
+<h2 id="links-wzxhzdk10wzxhzdk11">Links <a id="links"></a></h2>
 <ul>
 <li>
 <p><a href="http://www.adobe.com/products/xmp/">Adobe's Extensible Metadata Platform (XMP) website</a> </p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/anttask.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/anttask.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/anttask.html Mon Dec  3 04:59:19 2012
@@ -389,44 +389,44 @@ Then create FOP tasks within your Ant bu
 
 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>
+    <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>
+    <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>
 
 The following example transforms and converts a single XML and XSLT file to an AFP document:
 
-<target name="generate-afp-from-transform" description="Generates a single AFP file from an XSLT stylesheet">
-   <fop format="application/x-afp" 
-        xmlfile="c:\working\foDirectory\Document.xml"
-        xsltfile="c:\working\foDirectory\Document.xslt"
-        outfile="c:\working\afpDirectory\Document.afp" />
-</target>
+    <target name="generate-afp-from-transform" description="Generates a single AFP file from an XSLT stylesheet">
+       <fop format="application/x-afp" 
+            xmlfile="c:\working\foDirectory\Document.xml"
+            xsltfile="c:\working\foDirectory\Document.xslt"
+            outfile="c:\working\afpDirectory\Document.afp" />
+    </target>
 
 This example transforms and converts all XML files within an entire directory to PostScript:
 
-<target name="generate-multiple-ps-from-transform" description="Generates multiple PostScript files using an XSLT stylesheet">
-   <fop format="application/postscript" 
-        xsltfile="c:\working\foDirectory\Document.xslt"
-        outdir="${build.dir}" messagelevel="debug">
-        <fileset dir="${test.dir}">
-           <include name="*.xml"/>
-        </fileset>
-   </fop>
-</target></div>
+    <target name="generate-multiple-ps-from-transform" description="Generates multiple PostScript files using an XSLT stylesheet">
+       <fop format="application/postscript" 
+            xsltfile="c:\working\foDirectory\Document.xslt"
+            outdir="${build.dir}" messagelevel="debug">
+            <fileset dir="${test.dir}">
+               <include name="*.xml"/>
+            </fileset>
+       </fop>
+    </target></div>
       </div>
       
       <div class="clear"></div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/complexscripts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/complexscripts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/complexscripts.html Mon Dec  3 04:59:19 2012
@@ -369,9 +369,9 @@ $(document).ready(function () {
 </li>
 <li>
 <p><strong>Optional setting in fop.xconf file:</strong>  <code>&lt;fop version="1.0"&gt;
-  &lt;complex-scripts disabled="true"/&gt;
-  ...
-&lt;/fop&gt;</code> </p>
+      &lt;complex-scripts disabled="true"/&gt;
+      ...
+    &lt;/fop&gt;</code> </p>
 </li>
 </ol>
 <p>When complex scripts features are enabled, additional information related to bidirectional level resolution, the association between characters and glyphs, and glyph position adjustments are added to the internal, parsed representation of the XSL-FO tree and its corresponding formatted area tree. This additional information will somewhat increase the memory requirements for processing documents that use these features.

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/configuration.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/configuration.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/configuration.html Mon Dec  3 04:59:19 2012
@@ -341,11 +341,11 @@ $(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/1.1/">1.1</a></div> -->
-      	<div class="section-content"><h1 id="apachewzxhzdk7-fop-configuration">Apache&trade; FOP: Configuration</h1>
-<h2 id="configuration-file-basics-wzxhzdk8wzxhzdk9">Configuration File Basics <a id="general"></a></h2>
+      	<div class="section-content"><h1 id="apachewzxhzdk11-fop-configuration">Apache&trade; FOP: Configuration</h1>
+<h2 id="configuration-file-basics-wzxhzdk12wzxhzdk13">Configuration File Basics <a id="general"></a></h2>
 <p>The Apache&trade; FOP configuration file is an XML file containing a variety of settings that are useful for controlling FOP's behavior, and for helping it find resources that you wish it to use.</p>
 <p>The easiest way to get started using a FOP configuration file is to copy the sample found at <code>{fop-dir}/conf/fop.xconf</code> 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.</p>
-<h3 id="making-configuration-available-to-fop-wzxhzdk11wzxhzdk12">Making Configuration Available to FOP <a id="general-available"></a></h3>
+<h3 id="making-configuration-available-to-fop-wzxhzdk15wzxhzdk16">Making Configuration Available to FOP <a id="general-available"></a></h3>
 <p>After creating your configuration file, you must tell FOP how to find it:</p>
 <ul>
 <li>
@@ -356,7 +356,7 @@ $(document).ready(function () {
 </li>
 </ul>
 <p>See <a href="embedding.html#config-internal">Setting the Configuration Programmatically</a> for instructions on how to do so in an embedded environment.</p>
-<h2 id="summary-of-the-general-configuration-options-wzxhzdk13wzxhzdk14">Summary of the General Configuration Options <a id="general-elements"></a></h2>
+<h2 id="summary-of-the-general-configuration-options-wzxhzdk17wzxhzdk18">Summary of the General Configuration Options <a id="general-elements"></a></h2>
 <table>
 <thead>
 <tr>
@@ -460,58 +460,83 @@ $(document).ready(function () {
 </tbody>
 </table>
 <p>This is an excerpt from the example configuration file coming with FOP:</p>
-<p><fop version="1.0"></p>
-<p><!-- Strict user configuration -->
-  <strict-configuration>true</strict-configuration></p>
-<p><!-- Strict FO validation -->
-  <strict-validation>true</strict-validation></p>
-<p><!-- Base URL for resolving relative URLs -->
-  <base>./</base></p>
-<p><!-- Font Base URL for resolving relative font URLs -->
-  <font-base>./</font-base></p>
-<p><!-- Source resolution in dpi (dots/pixels per inch) for determining the size of pixels in SVG and bitmap images, default: 72dpi -->
-  <source-resolution>72</source-resolution>
-  <!-- Target resolution in dpi (dots/pixels per inch) for specifying the target resolution for generated bitmaps, default: 72dpi -->
-  <target-resolution>72</target-resolution></p>
-<p><!-- default page-height and page-width, in case
-       value is specified as auto -->
-  <default-page-settings height="11in" width="8.26in"/></p>
-<p><!-- Use file name nl_Bel instead of the default nl_BE -->
-  <hyphenation-pattern lang="nl" country="BE">nl_Bel</hyphenation-pattern></p>
-<p><!-- etc. etc..... -->
-</fop></p>
-<h1 id="image-loading-customization-wzxhzdk41wzxhzdk42">Image Loading Customization <a id="image-loading"></a></h1>
-<p class=".">Apache FOP uses the image loading framework from <a href="http://xmlgraphics.apache.org/commons/">Apache XML Graphics Commons</a> to load images using various plug-ins. Every image loader plug-in has a hard-coded usage penalty that influences which solution is chosen if there are multiple possibilities to load an image. Sometimes, though, these penalties need to be tweaked and this can be done in the FOP configuration. An example:
-<fop version="1.0"></p>
+<div class="codehilite"><pre><span class="nt">&lt;fop</span> <span class="na">version=</span><span class="s">&quot;1.0&quot;</span><span class="nt">&gt;</span>
+
+  <span class="c">&lt;!-- Strict user configuration --&gt;</span>
+  <span class="nt">&lt;strict-configuration&gt;</span>true<span class="nt">&lt;/strict-configuration&gt;</span>
+
+  <span class="c">&lt;!-- Strict FO validation --&gt;</span>
+  <span class="nt">&lt;strict-validation&gt;</span>true<span class="nt">&lt;/strict-validation&gt;</span>
+
+  <span class="c">&lt;!-- Base URL for resolving relative URLs --&gt;</span>
+  <span class="nt">&lt;base&gt;</span>./<span class="nt">&lt;/base&gt;</span>
+
+  <span class="c">&lt;!-- Font Base URL for resolving relative font URLs --&gt;</span>
+  <span class="nt">&lt;font-base&gt;</span>./<span class="nt">&lt;/font-base&gt;</span>
+
+  <span class="c">&lt;!-- Source resolution in dpi (dots/pixels per inch) for determining the size of pixels in SVG and bitmap images, default: 72dpi --&gt;</span>
+  <span class="nt">&lt;source-resolution&gt;</span>72<span class="nt">&lt;/source-resolution&gt;</span>
+  <span class="c">&lt;!-- Target resolution in dpi (dots/pixels per inch) for specifying the target resolution for generated bitmaps, default: 72dpi --&gt;</span>
+  <span class="nt">&lt;target-resolution&gt;</span>72<span class="nt">&lt;/target-resolution&gt;</span>
+
+  <span class="c">&lt;!-- default page-height and page-width, in case</span>
+<span class="c">       value is specified as auto --&gt;</span>
+  <span class="nt">&lt;default-page-settings</span> <span class="na">height=</span><span class="s">&quot;11in&quot;</span> <span class="na">width=</span><span class="s">&quot;8.26in&quot;</span><span class="nt">/&gt;</span>
+
+  <span class="c">&lt;!-- Use file name nl_Bel instead of the default nl_BE --&gt;</span>
+  <span class="nt">&lt;hyphenation-pattern</span> <span class="na">lang=</span><span class="s">&quot;nl&quot;</span> <span class="na">country=</span><span class="s">&quot;BE&quot;</span><span class="nt">&gt;</span>nl_Bel<span class="nt">&lt;/hyphenation-pattern&gt;</span>
+
+  <span class="c">&lt;!-- etc. etc..... --&gt;</span>
+<span class="nt">&lt;/fop&gt;</span>
+</pre></div>
+
+
+<h1 id="image-loading-customization-wzxhzdk19wzxhzdk20">Image Loading Customization <a id="image-loading"></a></h1>
+<p>Apache FOP uses the image loading framework from <a href="http://xmlgraphics.apache.org/commons/">Apache XML Graphics Commons</a> to load images using various plug-ins. Every image loader plug-in has a hard-coded usage penalty that influences which solution is chosen if there are multiple possibilities to load an image. Sometimes, though, these penalties need to be tweaked and this can be done in the FOP configuration. An example:</p>
+<div class="codehilite"><pre><span class="nt">&lt;fop</span> <span class="na">version=</span><span class="s">&quot;1.0&quot;</span><span class="nt">&gt;</span>
+  [..]
+  <span class="nt">&lt;image-loading&gt;</span>
+    <span class="nt">&lt;penalty</span> <span class="na">value=</span><span class="s">&quot;10000&quot;</span>
+      <span class="na">class=</span><span class="s">&quot;org.apache.xmlgraphics.image.loader.impl.ImageLoaderRawCCITTFax&quot;</span><span class="nt">/&gt;</span>
+    <span class="nt">&lt;penalty</span> <span class="na">value=</span><span class="s">&quot;INFINITE&quot;</span>
+      <span class="na">class=</span><span class="s">&quot;org.apache.xmlgraphics.image.loader.impl.ImageLoaderInternalTIFF&quot;</span><span class="nt">/&gt;</span>
+  <span class="nt">&lt;/image-loading&gt;</span>
+  <span class="nt">&lt;renderers....</span>
+<span class="err">&lt;/fop</span><span class="nt">&gt;</span>
+</pre></div>
+
+
+<p>The first penalty element increases the penalty for the raw CCITT loader. This practically forces the decoding of CCITT compressed TIFF images except if there are no TIFF codecs available.</p>
 <p>The second penalty element sets an "infinite" penalty for the TIFF loader using the internal TIFF codec. This practically disables that plug-in as it will never be chosen as a possible solution.</p>
 <p>Negative penalties are possible to promote a plug-in but a negative penalty sum will be treated as zero penalty in most cases. For more details on the image loading framework, please consult the documentation there.</p>
-<h2 id="renderer-configuration-wzxhzdk44wzxhzdk45">Renderer configuration <a id="renderers"></a></h2>
+<h2 id="renderer-configuration-wzxhzdk21wzxhzdk22">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>
-<p><renderers>
-    <renderer mime="application/pdf">
-      <filterList>
-        <!-- provides compression using zlib flate (default is on) -->
-        <value>flate</value>
-      </filterList>
-      <fonts>
-        <font metrics-url="arial.xml" kerning="yes" embed-url="arial.ttf">
-          <font-triplet name="Arial" style="normal" weight="normal"/>
-          <font-triplet name="ArialMT" style="normal" weight="normal"/>
-        </font>
-        <font metrics-url="arialb.xml" kerning="yes" embed-url="arialb.ttf">
-          <font-triplet name="Arial" style="normal" weight="bold"/>
-          <font-triplet name="ArialMT" style="normal" weight="bold"/>
-        </font>
-      </fonts>
-    </renderer></p>
-<div class="codehilite"><pre><span class="o">&lt;</span><span class="n">renderer</span> <span class="n">mime</span><span class="o">=</span><span class="s">&quot;application/postscript&quot;</span><span class="o">&gt;</span>
-<span class="o">&lt;!--</span> <span class="n">etc</span><span class="o">.</span> <span class="n">etc</span><span class="o">.....</span> <span class="o">--&gt;</span>
+<div class="codehilite"><pre>  <span class="nt">&lt;renderers&gt;</span>
+    <span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/pdf&quot;</span><span class="nt">&gt;</span>
+      <span class="nt">&lt;filterList&gt;</span>
+        <span class="c">&lt;!-- provides compression using zlib flate (default is on) --&gt;</span>
+        <span class="nt">&lt;value&gt;</span>flate<span class="nt">&lt;/value&gt;</span>
+      <span class="nt">&lt;/filterList&gt;</span>
+      <span class="nt">&lt;fonts&gt;</span>
+        <span class="nt">&lt;font</span> <span class="na">metrics-url=</span><span class="s">&quot;arial.xml&quot;</span> <span class="na">kerning=</span><span class="s">&quot;yes&quot;</span> <span class="na">embed-url=</span><span class="s">&quot;arial.ttf&quot;</span><span class="nt">&gt;</span>
+          <span class="nt">&lt;font-triplet</span> <span class="na">name=</span><span class="s">&quot;Arial&quot;</span> <span class="na">style=</span><span class="s">&quot;normal&quot;</span> <span class="na">weight=</span><span class="s">&quot;normal&quot;</span><span class="nt">/&gt;</span>
+          <span class="nt">&lt;font-triplet</span> <span class="na">name=</span><span class="s">&quot;ArialMT&quot;</span> <span class="na">style=</span><span class="s">&quot;normal&quot;</span> <span class="na">weight=</span><span class="s">&quot;normal&quot;</span><span class="nt">/&gt;</span>
+        <span class="nt">&lt;/font&gt;</span>
+        <span class="nt">&lt;font</span> <span class="na">metrics-url=</span><span class="s">&quot;arialb.xml&quot;</span> <span class="na">kerning=</span><span class="s">&quot;yes&quot;</span> <span class="na">embed-url=</span><span class="s">&quot;arialb.ttf&quot;</span><span class="nt">&gt;</span>
+          <span class="nt">&lt;font-triplet</span> <span class="na">name=</span><span class="s">&quot;Arial&quot;</span> <span class="na">style=</span><span class="s">&quot;normal&quot;</span> <span class="na">weight=</span><span class="s">&quot;bold&quot;</span><span class="nt">/&gt;</span>
+          <span class="nt">&lt;font-triplet</span> <span class="na">name=</span><span class="s">&quot;ArialMT&quot;</span> <span class="na">style=</span><span class="s">&quot;normal&quot;</span> <span class="na">weight=</span><span class="s">&quot;bold&quot;</span><span class="nt">/&gt;</span>
+        <span class="nt">&lt;/font&gt;</span>
+      <span class="nt">&lt;/fonts&gt;</span>
+    <span class="nt">&lt;/renderer&gt;</span>
+
+    <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="c">&lt;!-- etc. etc..... --&gt;</span>
 </pre></div>
 
 
 <p>The details on the font configuration can be found on the separate <a href="fonts.html">Fonts</a> page. Note especially the section entitled <a href="fonts.html#register">Register Fonts with FOP</a> .</p>
-<h3 id="special-settings-for-the-pdf-renderer-wzxhzdk64wzxhzdk65">Special Settings for the PDF Renderer <a id="pdf-renderer"></a></h3>
+<h3 id="special-settings-for-the-pdf-renderer-wzxhzdk23wzxhzdk24">Special Settings for the PDF Renderer <a id="pdf-renderer"></a></h3>
 <p>The configuration element for the PDF renderer contains two elements. One is for the font configuration (please follow the link above) and one is for the "filter list". The filter list controls how the individual objects in a PDF file are encoded. By default, all objects get "flate" encoded (i.e. simply compressed with the same algorithm that is also used in ZIP files). Most users don't need to change that setting. For debugging purposes, it may be desired not to compress the internal objects at all so the generated PDF commands can be read. In that case, you can simply use the following filter list. The second filter list (type="image") ensures that all images still get compressed but also ASCII-85 encoded so the produced PDF file is still easily readable in a text editor.</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/pdf&quot;</span><span class="nt">&gt;</span>
   <span class="nt">&lt;filterList&gt;</span>
@@ -545,7 +570,7 @@ $(document).ready(function () {
   <span class="err">&lt;disable-srgb-colorspace</span><span class="nt">&gt;</span>true<span class="nt">&lt;/disable-srgb-colorspace&gt;</span>
 
   <span class="nt">&lt;fonts....</span>
-  <span class="err">&lt;/renderer</span><span class="nt">&gt;</span>
+<span class="err">&lt;/renderer</span><span class="nt">&gt;</span>
 </pre></div>
 
 
@@ -575,7 +600,7 @@ $(document).ready(function () {
 </pre></div>
 
 
-<h3 id="special-settings-for-the-postscript-renderer-wzxhzdk67wzxhzdk68">Special Settings for the PostScript Renderer <a id="ps-renderer"></a></h3>
+<h3 id="special-settings-for-the-postscript-renderer-wzxhzdk26wzxhzdk27">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>
@@ -594,29 +619,36 @@ $(document).ready(function () {
 </pre></div>
 
 
-<h2 id="special-settings-for-the-pcl-renderer-wzxhzdk69wzxhzdk70">Special Settings for the PCL Renderer <a id="pcl-renderer"></a></h2>
+<h2 id="special-settings-for-the-pcl-renderer-wzxhzdk28wzxhzdk29">Special Settings for the PCL Renderer <a id="pcl-renderer"></a></h2>
 <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.
-<renderer mime="application/x-pcl">
-  <rendering>quality</rendering>
-  <text-rendering>bitmap</text-rendering>
-</renderer>
-The default value for the "rendering" setting is "speed" which causes borders to be painted as plain rectangles. In this mode, no special borders (dotted, dashed etc.) are available. If you want support for all border modes, set the value to "quality" as indicated above. This will cause the borders to be painted as bitmaps.</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/x-pcl&quot;</span><span class="nt">&gt;</span>
+  <span class="nt">&lt;rendering&gt;</span>quality<span class="nt">&lt;/rendering&gt;</span>
+  <span class="nt">&lt;text-rendering&gt;</span>bitmap<span class="nt">&lt;/text-rendering&gt;</span>
+<span class="nt">&lt;/renderer&gt;</span>
+</pre></div>
+
+
+<p>The default value for the "rendering" setting is "speed" which causes borders to be painted as plain rectangles. In this mode, no special borders (dotted, dashed etc.) are available. If you want support for all border modes, set the value to "quality" as indicated above. This will cause the borders to be painted as bitmaps.</p>
 <p>The default value for the "text-rendering" setting is "auto" which paints the base fonts using PCL fonts. Non-base fonts are painted as bitmaps through Java2D. If the mix of painting methods results in unwelcome output, you can set this to "bitmap" which causes all text to be rendered as bitmaps.</p>
-<h3 id="special-settings-for-the-afp-renderer-wzxhzdk77wzxhzdk78">Special Settings for the AFP Renderer <a id="afp-renderer"></a></h3>
-<p>Additionally, there are certain settings that control how the renderer handles various elements.
-<renderer mime="application/x-afp">
-  <images mode="b+w" bits-per-pixel="8" native="true"/>
-  <renderer-resolution>240</renderer-resolution>
-  <line-width-correction>2.5</line-width-correction></p>
-<p><!-- a default external resource group file -->
-  <resource-group-file>resources.afp</resource-group-file>
-</renderer>
-The default value for the images "mode" setting is "b+w" (black and white). When the images "mode" setting is "b+w" a "bits-per-pixel" setting can be provided to aid the grayscale conversion process. With this setting all images referenced in your source document are converted to an IOCA FS45 grayscale bitmap image form. When the setting is "color" all images are converted to an IOCA FS45 color bitmap image form. When "native" setting is "true", all images encountered (TIFF, GIF, JPEG and Encapsulated Postscript etc.) will be embedded directly in the datastream in their native form using a MO:DCA Object Container.</p>
+<h3 id="special-settings-for-the-afp-renderer-wzxhzdk30wzxhzdk31">Special Settings for the AFP Renderer <a id="afp-renderer"></a></h3>
+<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/x-afp&quot;</span><span class="nt">&gt;</span>
+  <span class="nt">&lt;images</span> <span class="na">mode=</span><span class="s">&quot;b+w&quot;</span> <span class="na">bits-per-pixel=</span><span class="s">&quot;8&quot;</span> <span class="na">native=</span><span class="s">&quot;true&quot;</span><span class="nt">/&gt;</span>
+  <span class="nt">&lt;renderer-resolution&gt;</span>240<span class="nt">&lt;/renderer-resolution&gt;</span>
+  <span class="nt">&lt;line-width-correction&gt;</span>2.5<span class="nt">&lt;/line-width-correction&gt;</span>
+
+  <span class="c">&lt;!-- a default external resource group file --&gt;</span>
+  <span class="nt">&lt;resource-group-file&gt;</span>resources.afp<span class="nt">&lt;/resource-group-file&gt;</span>
+<span class="nt">&lt;/renderer&gt;</span>
+</pre></div>
+
+
+<p>The default value for the images "mode" setting is "b+w" (black and white). When the images "mode" setting is "b+w" a "bits-per-pixel" setting can be provided to aid the grayscale conversion process. With this setting all images referenced in your source document are converted to an IOCA FS45 grayscale bitmap image form. When the setting is "color" all images are converted to an IOCA FS45 color bitmap image form. When "native" setting is "true", all images encountered (TIFF, GIF, JPEG and Encapsulated Postscript etc.) will be embedded directly in the datastream in their native form using a MO:DCA Object Container.</p>
 <p>The default value for the "renderer-resolution" is 240 dpi.</p>
 <p>The default line width is device dependent and may need to be fine tuned so that the output matches the expected result. The default correction value is 2.5.</p>
 <p>By default if there is no configuration definition for "resource-group-file", external resources will be placed in a file called resources.afp.</p>
-<h2 id="when-it-does-not-work-wzxhzdk89wzxhzdk90">When it does not work <a id="When+it+does+not+work"></a></h2>
+<h2 id="when-it-does-not-work-wzxhzdk32wzxhzdk33">When it does not work <a id="When+it+does+not+work"></a></h2>
 <p>FOP searches the configuration file for the information it expects, at the position it expects. When that information is not present, FOP will not complain, it will just continue. When there is other information in the file, FOP will not complain, it will just ignore it. That means that when your configuration information is in the file but in a different XML element, or in a different XML path, than FOP expects, it will be silently ignored.</p>
 <p>Check the following possibilities:</p>
 <ul>
@@ -624,15 +656,16 @@ The default value for the images "mode" 
 <p>The format of the configuration file has changed considerably between FOP 0.20.5 and FOP 1.0 and its beta versions. Did you convert your file to the new format?</p>
 </li>
 <li>
-<p>The FOP distribution contains a schema for configuration files, at src/foschema/fop-configuration.xsd. Did you validate your configuration file against it? Add the following schema location to the <code>schema</code> element:<fop
-xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-xsi:noNamespaceSchemaLocation=
-"http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop-configuration.xsd?view=co">
-and run the configuration file through a validating schema parser. Note that the schema cannot detect all errors, and that it is stricter about the order of some elements than FOP itself is.</p>
-</li>
-<li>
-<p>Run FOP in debug mode (command line option <code>-d</code> ). This makes FOP report which configuration information it finds. Check if FOP finds what you expect.</p>
+<p>The FOP distribution contains a schema for configuration files, at src/foschema/fop-configuration.xsd. Did you validate your configuration file against it? Add the following schema location to the <code>schema</code> element:</p>
+<p><fop
+    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    xsi:noNamespaceSchemaLocation=
+    "http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop-configuration.xsd?view=co"></p>
 </li>
+</ul>
+<p>and run the configuration file through a validating schema parser. Note that the schema cannot detect all errors, and that it is stricter about the order of some elements than FOP itself is.</p>
+<ul>
+<li>Run FOP in debug mode (command line option <code>-d</code> ). This makes FOP report which configuration information it finds. Check if FOP finds what you expect.</li>
 </ul></div>
       </div>
       



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


Mime
View raw message