xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jerem...@apache.org
Subject svn commit: r820972 [8/8] - in /xmlgraphics/site/deploy/fop: ./ 0.94/ 0.95/ dev/ dev/design/ dev/fo/ dev/svg/ fo/ skin/ trunk/
Date Fri, 02 Oct 2009 11:34:14 GMT
Modified: xmlgraphics/site/deploy/fop/trunk/output.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/output.html?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/output.html (original)
+++ xmlgraphics/site/deploy/fop/trunk/output.html Fri Oct  2 11:34:05 2009
@@ -256,6 +256,9 @@
 <a href="#pcl-page-source">Page Source (Tray selection)</a>
 </li>
 <li>
+<a href="#pcl-output-bin">Output Bin</a>
+</li>
+<li>
 <a href="#pcl-duplex-mode">Page Duplex Mode</a>
 </li>
 </ul>
@@ -315,6 +318,9 @@
 <li>
 <a href="#afp-invoke-medium-map">Invoke Medium Map (IMM) Extension</a>
 </li>
+<li>
+<a href="#afp-form-maps">Form Maps/Defs</a>
+</li>
 </ul>
 </li>
 <li>
@@ -353,6 +359,9 @@
 <li>
 <a href="#tiff-configuration">TIFF-specific Configuration</a>
 </li>
+<li>
+<a href="#bitmap-rendering-options">Runtime Rendering Options</a>
+</li>
 </ul>
 </li>
 <li>
@@ -383,10 +392,10 @@
       attention than others.
     </p>
     
-<a name="N10021"></a><a name="general"></a>
+<a name="N10020"></a><a name="general"></a>
 <h2 class="underlined_10">General Information</h2>
 <div class="section">
-<a name="N10027"></a><a name="general-fonts"></a>
+<a name="N10026"></a><a name="general-fonts"></a>
 <h3 class="underlined_5">Fonts</h3>
 <p>
           Most FOP renderers use a FOP-specific system for font registration.
@@ -443,7 +452,7 @@
 </li>
         
 </ol>
-<a name="N1005C"></a><a name="general-direct-output"></a>
+<a name="N1005B"></a><a name="general-direct-output"></a>
 <h3 class="underlined_5">Output to a Printer or Other Device</h3>
 <p>
           The most obvious way to print your document is to use the FOP 
@@ -467,7 +476,7 @@
         </p>
 </div>
     
-<a name="N10080"></a><a name="pdf"></a>
+<a name="N1007F"></a><a name="pdf"></a>
 <h2 class="underlined_10">PDF</h2>
 <div class="section">
 <p>
@@ -482,7 +491,7 @@
         Note that FOP does not currently support "tagged PDF" or PDF/A-1a. 
         Support for <a href="pdfa.html">PDF/A-1b</a> and <a href="pdfx.html">PDF/X</a> has recently been added, however.
       </p>
-<a name="N10094"></a><a name="pdf-fonts"></a>
+<a name="N10093"></a><a name="pdf-fonts"></a>
 <h3 class="underlined_5">Fonts</h3>
 <p>
           PDF has a set of fonts that are always available to all PDF viewers;
@@ -496,7 +505,7 @@
           guaranteed to be available in all PDF viewer applications."</em>
         
 </p>
-<a name="N100A1"></a><a name="pdf-postprocess"></a>
+<a name="N100A0"></a><a name="pdf-postprocess"></a>
 <h3 class="underlined_5">Post-processing</h3>
 <p>
           FOP does not currently support several desirable PDF features: watermarks and signatures. 
@@ -566,7 +575,7 @@
       Check the iText tutorial and documentation for setting access flags, password, 
       encryption strength and other parameters.
     </p>
-<a name="N100C7"></a><a name="pdf-watermark"></a>
+<a name="N100C6"></a><a name="pdf-watermark"></a>
 <h3 class="underlined_5">Watermarks</h3>
 <p>
       In addition to the <a href="#pdf-postprocess">PDF Post-processing</a> options, consider the following workarounds:
@@ -590,7 +599,7 @@
 </ul>
 </div>
 
-<a name="N100DF"></a><a name="ps"></a>
+<a name="N100DE"></a><a name="ps"></a>
 <h2 class="underlined_10">PostScript</h2>
 <div class="section">
 <p>
@@ -603,7 +612,7 @@
     filter (the latter is used for 1:1 embedding of JPEG images), everything 
     else is Level 2.
   </p>
-<a name="N100E8"></a><a name="ps-configuration"></a>
+<a name="N100E7"></a><a name="ps-configuration"></a>
 <h3 class="underlined_5">Configuration</h3>
 <p>
         The PostScript renderer configuration currently allows the following settings:
@@ -646,7 +655,7 @@
         the particular postscript implementation issuing unwanted postscript subsystem
         initgraphics/erasepage calls on each setpagedevice call.
       </p>
-<a name="N10105"></a><a name="ps-limitations"></a>
+<a name="N10104"></a><a name="ps-limitations"></a>
 <h3 class="underlined_5">Limitations</h3>
 <ul>
       
@@ -661,7 +670,7 @@
 </ul>
 </div>
   
-<a name="N1011C"></a><a name="pcl"></a>
+<a name="N1011B"></a><a name="pcl"></a>
 <h2 class="underlined_10">PCL</h2>
 <div class="section">
 <p>
@@ -679,7 +688,7 @@
       painting operations. Certain painting operations are done off-screen and
       rendered to PCL as bitmaps because of limitations in PCL 5.
     </p>
-<a name="N10128"></a><a name="pcl-references"></a>
+<a name="N10127"></a><a name="pcl-references"></a>
 <h3 class="underlined_5">References</h3>
 <ul>
         
@@ -692,7 +701,7 @@
 </li>
       
 </ul>
-<a name="N1013C"></a><a name="pcl-limitations"></a>
+<a name="N1013B"></a><a name="pcl-limitations"></a>
 <h3 class="underlined_5">Limitations</h3>
 <ul>
         
@@ -740,7 +749,7 @@
         </li>
       
 </ul>
-<a name="N1015E"></a><a name="pcl-configuration"></a>
+<a name="N1015D"></a><a name="pcl-configuration"></a>
 <h3 class="underlined_5">Configuration</h3>
 <p>
         The PCL renderer configuration currently allows the following settings:
@@ -776,7 +785,7 @@
         should be enough for most use cases. Note that this setting directly affects
         the size of the output file and the print quality.
       </p>
-<a name="N10178"></a><a name="pcl-extensions"></a>
+<a name="N10177"></a><a name="pcl-extensions"></a>
 <h3 class="underlined_5">Extensions</h3>
 <p>The PCL Renderer supports some PCL specific extensions which can be embedded 
       into the input FO document. To use the extensions the appropriate namespace must 
@@ -785,7 +794,7 @@
       &lt;fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
                xmlns:pcl="http://xmlgraphics.apache.org/fop/extensions/pcl"&gt;
 </pre>
-<a name="N10185"></a><a name="pcl-page-source"></a>
+<a name="N10184"></a><a name="pcl-page-source"></a>
 <h4>Page Source (Tray selection)</h4>
 <p>
           The page-source extension attribute on fo:simple-page-master allows to 
@@ -810,7 +819,28 @@
           "7" is "auto-select".
           Consult the technical reference for your printer for all available values.
         </p>
-<a name="N10196"></a><a name="pcl-duplex-mode"></a>
+<a name="N10195"></a><a name="pcl-output-bin"></a>
+<h4>Output Bin</h4>
+<p>
+          The <span class="codefrag">output-bin</span> extension attribute on fo:simple-page-master allows to 
+          select the output bin into which the printed output should be fed. Example:
+        </p>
+<pre class="code">
+      &lt;fo:layout-master-set&gt;
+        &lt;fo:simple-page-master master-name="simple" pcl:output-bin="2"&gt;
+          ...
+        &lt;/fo:simple-page-master&gt;
+      &lt;/fo:layout-master-set&gt;
+</pre>
+<p>
+          Note: the output bin number is a positive integer and the value depends on
+          the target printer. Not all PCL printers support the same output bins.
+          Usually, 
+          "1" is the upper output bin,
+          "2" is the lower (rear) output bin. 
+          Consult the technical reference for your printer for all available values.
+        </p>
+<a name="N101A9"></a><a name="pcl-duplex-mode"></a>
 <h4>Page Duplex Mode</h4>
 <p>
           The duplex-mode extension attribute on fo:simple-page-master allows to 
@@ -836,7 +866,7 @@
         </p>
 </div>
   
-<a name="N101A9"></a><a name="afp"></a>
+<a name="N101BC"></a><a name="afp"></a>
 <h2 class="underlined_10">AFP</h2>
 <div class="section">
 <p>
@@ -881,7 +911,7 @@
       FOP creates exactly one Document per Printfile with an optional Resource Group at the
       beginning. FOP does not create document indices.
     </p>
-<a name="N101EF"></a><a name="afp-references"></a>
+<a name="N10202"></a><a name="afp-references"></a>
 <h3 class="underlined_5">References</h3>
 <ul>
         
@@ -898,7 +928,7 @@
 </li>
       
 </ul>
-<a name="N10208"></a><a name="afp-limitations"></a>
+<a name="N1021B"></a><a name="afp-limitations"></a>
 <h3 class="underlined_5">Limitations</h3>
 <p>This list is most likely badly incomplete.</p>
 <ul>
@@ -913,7 +943,7 @@
         </li>
       
 </ul>
-<a name="N1021B"></a><a name="afp-compatibility"></a>
+<a name="N1022E"></a><a name="afp-compatibility"></a>
 <h3 class="underlined_5">Deployment in older environments</h3>
 <p>
         There are still a big number of older (or limited) MO:DCA/IPDS environments in production
@@ -925,9 +955,9 @@
         bits per pixel is configured, FOP has to switch to at least FS11 which may not work
         everywhere.
       </p>
-<a name="N10225"></a><a name="afp-configuration"></a>
+<a name="N10238"></a><a name="afp-configuration"></a>
 <h3 class="underlined_5">Configuration</h3>
-<a name="N1022B"></a><a name="afp-font-config"></a>
+<a name="N1023E"></a><a name="afp-font-config"></a>
 <h4>Fonts</h4>
 <p>The AFP Renderer requires special configuration particularly related to fonts.
       AFP Render configuration is done through the normal FOP configuration file. The MIME type
@@ -1069,13 +1099,18 @@
         &lt;font-triplet name="monospace" style="normal" weight="bold"/&gt;
         &lt;font-triplet name="Courier" style="normal" weight="bold"/&gt;
       &lt;/font&gt;</pre>
-<a name="N10263"></a><a name="afp-renderer-resolution-config"></a>
+<p>
+          By default, all manually configured fonts are embedded, unless they are matched in the
+          <a href="fonts.html#embedding"><span class="codefrag">referenced-fonts</span> section of the configuration file</a>.
+          However, the default fonts shown above will not be embedded.
+        </p>
+<a name="N1027F"></a><a name="afp-renderer-resolution-config"></a>
 <h4>Output Resolution</h4>
 <p>By default the AFP Renderer creates output with a resolution of 240 dpi.
           This can be overridden by the &lt;renderer-resolution/&gt; configuration element. Example:</p>
 <pre class="code">
       &lt;renderer-resolution&gt;240&lt;/renderer-resolution&gt;</pre>
-<a name="N10271"></a><a name="afp-image-config"></a>
+<a name="N1028D"></a><a name="afp-image-config"></a>
 <h4>Images</h4>
 <p>By default the AFP Renderer converts all images to 8 bit grey level.
         This can be overridden by the &lt;images/&gt; configuration element. Example:</p>
@@ -1095,7 +1130,7 @@
       into the datastream using an object container rather than being converted into an IOCA FS45 image.
       Support for native image formats (e.g. JPEG, GIF) is not always available on printer implementations
       so by default this configuration option is set to "false".</p>
-<a name="N10293"></a><a name="afp-shading-config"></a>
+<a name="N102AF"></a><a name="afp-shading-config"></a>
 <h4>Shading</h4>
 <p>
           By default, filled rectangles are painted using their given color using a PTOCA I-axis rule
@@ -1108,7 +1143,7 @@
 <pre class="code">
       &lt;shading&gt;dithered&lt;/shading&gt;
 </pre>
-<a name="N102A1"></a><a name="afp-resource-group-file"></a>
+<a name="N102BD"></a><a name="afp-resource-group-file"></a>
 <h4>Resource Group File</h4>
 <p>By default the AFP Renderer will place all data resource objects such as images within
       the document of the main output datastream.  An external resource group file where document resources
@@ -1120,7 +1155,7 @@
 <div class="label">Note</div>
 <div class="content">Be careful when using this option not to overwrite existing resource files from previous rendering runs.</div>
 </div>
-<a name="N102B2"></a><a name="afp-resource-level-defaults"></a>
+<a name="N102CE"></a><a name="afp-resource-level-defaults"></a>
 <h4>Resource Level Defaults</h4>
 <p>
           By default, bitmap image objects (or page segments derived from them) are put in the
@@ -1139,7 +1174,7 @@
           for the attributes are "inline" and "print-file". In the future,
           additional possibilities may be added.
         </p>
-<a name="N102CB"></a><a name="afp-extensions"></a>
+<a name="N102E7"></a><a name="afp-extensions"></a>
 <h3 class="underlined_5">Extensions</h3>
 <p>The AFP Renderer supports some AFP specific extensions which can be embedded into the input 
       fo document. To use the extensions the appropriate namespace must be declared in the fo:root element like this:</p>
@@ -1147,7 +1182,7 @@
       &lt;fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
                xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp"&gt;
 </pre>
-<a name="N102D8"></a><a name="afp-page-overlay"></a>
+<a name="N102F4"></a><a name="afp-page-overlay"></a>
 <h4>Page Overlay (IPO) Extension</h4>
 <p>The include-page-overlay extension element allows to define on a per simple-page-master basis a page overlay resource. Example:</p>
 <pre class="code">
@@ -1160,7 +1195,7 @@
 </pre>
 <p>The mandatory name attribute must refer to an 8 character (space padded) resource name that
         must be known in the AFP processing environment.</p>
-<a name="N102E9"></a><a name="afp-page-segment"></a>
+<a name="N10305"></a><a name="afp-page-segment"></a>
 <h4>Page Segment (IPS) Extension</h4>
 <p>The include-page-segment extension element allows to define resource substitution for fo:external-graphics elements. 
           Example:</p>
@@ -1182,7 +1217,18 @@
         fo:external-graphic elements and if it is identical (string matching is used) in the generated
         AFP the external graphic is replaced by a reference to the given resource.
         </p>
-<a name="N102FA"></a><a name="afp-tag-logical-element"></a>
+<p>
+          The effect here is that whenever FOP encounters the URI specified in the extension,
+          it will effectively generate code to include the page segment with the given name
+          instead of embedding the image referenced by the URI. The URI is still required as
+          the underlying image serves as a provider for the intrinsic size of the image
+          (At the moment, FOP is unable to extract the intrinsic size of the page segment from
+          an AFP resource file). For the image to appear in an AFP viewer or to be printed, the
+          AFP resource must be available on the target device. FOP does not embed the page
+          segment in the generated file. Please also note that page segments cannot be scaled.
+          They are always rendered in their intrinsic size.
+        </p>
+<a name="N10319"></a><a name="afp-tag-logical-element"></a>
 <h4>Tag Logical Element (TLE) Extension</h4>
 <p>The tag-logical-element extension element allows to injects TLEs into the AFP output stream. Example:</p>
 <pre class="code">
@@ -1206,7 +1252,7 @@
           Multiple tag-logical-element extension elements within a simple-page-master or
           page-sequence are allowed. The name and value attributes are mandatory.
         </p>
-<a name="N1030B"></a><a name="afp-no-operation"></a>
+<a name="N1032A"></a><a name="afp-no-operation"></a>
 <h4>No Operation (NOP) Extension</h4>
 <p>The no-operation extension provides the ability to carry up to 32K of comments or any other type
         of unarchitected data into the AFP output stream. Example:</p>
@@ -1223,7 +1269,7 @@
         Multiple no-operation extension elements within a simple-page-master are allowed.
         The name attribute is mandatory.
         </p>
-<a name="N1031C"></a><a name="afp-invoke-medium-map"></a>
+<a name="N1033B"></a><a name="afp-invoke-medium-map"></a>
 <h4>Invoke Medium Map (IMM) Extension</h4>
 <p>
           The invoke-medium-map extension allows to generate IMM fields (Invoke Medium Map) in the
@@ -1240,14 +1286,45 @@
 </pre>
 <p>
           The invoke-medium-map element is allowed as child of fo:page-sequence (page group
-          level). It is NOT supported on document level (fo:root), yet. FOP also doesn't support
-          specifying medium maps inside XML (using BMM/EMM). It can only reference an existing
-          medium map by name. The medium map has to be constructed through different means and
-          available on the target platform.
+          level) or fo:simple-page-master. It is NOT supported on document level (fo:root), yet. 
+          FOP also doesn't support specifying medium maps inside XML (using BMM/EMM). It can 
+          only reference an existing medium map by name. The medium map has to be constructed 
+          through different means and available on the target platform.
+        </p>
+<a name="N1034C"></a><a name="afp-form-maps"></a>
+<h4>Form Maps/Defs</h4>
+<p>
+          Apache FOP supports embedding an external form map resource in the
+          generated AFP output. This is done using the <span class="codefrag">afp:include-form-map</span>
+          extension. An example: 
+        </p>
+<pre class="code">
+&lt;fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
+     xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp"&gt;
+  [..]
+  &lt;fo:declarations&gt;
+    &lt;afp:include-form-map name="F1SAMP1" src="file:f1samp1.fde"/&gt;
+  &lt;/fo:declarations&gt;
+</pre>
+<p>
+          The <span class="codefrag">afp:include-form-map</span> is to be placed as a direct child of
+          <span class="codefrag">fo:declarations</span>. The <span class="codefrag">name</span> is an AFP resource name
+          (max. 8 characters) and the <span class="codefrag">src</span> attribute is the URI identifying the
+          external form map resource. When such a form map is embedded, you can use the
+          <span class="codefrag">afp:invoke-medium-map</span> extension (described above) to invoke any medium
+          map included in the form map. 
         </p>
-<a name="N1032E"></a><a name="afp-foreign-attributes"></a>
+<div class="note">
+<div class="label">Note</div>
+<div class="content">
+          Apache FOP doesn't support a way to define a form map or medium map using XML means
+          inside an XSL-FO document. You will have to build the form map with some third-party
+          tool.
+        </div>
+</div>
+<a name="N10373"></a><a name="afp-foreign-attributes"></a>
 <h3 class="underlined_5">Foreign Attributes</h3>
-<a name="N10334"></a><a name="afp-foreign-attributes-resource"></a>
+<a name="N10379"></a><a name="afp-foreign-attributes-resource"></a>
 <h4>Resource</h4>
 <p>The resource foreign attributes provides the ability to name and control where data object resources
         (e.g. images/scalable vector graphics) will reside in the AFP output.
@@ -1284,7 +1361,7 @@
 <p></p>
 </div>
 
-<a name="N1034D"></a><a name="rtf"></a>
+<a name="N10392"></a><a name="rtf"></a>
 <h2 class="underlined_10">RTF</h2>
 <div class="section">
 <p>
@@ -1338,7 +1415,7 @@
 </ul>
 </div>
 
-<a name="N10381"></a><a name="xml"></a>
+<a name="N103C6"></a><a name="xml"></a>
 <h2 class="underlined_10">XML (Area Tree XML)</h2>
 <div class="section">
 <p>
@@ -1352,7 +1429,7 @@
   </p>
 </div>
 
-<a name="N10392"></a><a name="awt"></a>
+<a name="N103D7"></a><a name="awt"></a>
 <h2 class="underlined_10">Java2D/AWT</h2>
 <div class="section">
 <p>
@@ -1367,14 +1444,14 @@
     </p>
 </div>
 
-<a name="N1039F"></a><a name="print"></a>
+<a name="N103E4"></a><a name="print"></a>
 <h2 class="underlined_10">Print</h2>
 <div class="section">
 <p>
     It is possible to directly print the document from the command line.
     This is done with the same code that renders to the Java2D/AWT renderer.
   </p>
-<a name="N103A8"></a><a name="print-issues"></a>
+<a name="N103ED"></a><a name="print-issues"></a>
 <h3 class="underlined_5">Known issues</h3>
 <p>
       If you run into the problem that the printed output is incomplete on Windows:
@@ -1385,7 +1462,7 @@
     </p>
 </div>
 
-<a name="N103B3"></a><a name="bitmap"></a>
+<a name="N103F8"></a><a name="bitmap"></a>
 <h2 class="underlined_10">Bitmap (TIFF/PNG)</h2>
 <div class="section">
 <p>
@@ -1396,25 +1473,76 @@
 <p>
     Currently, two output formats are supported: PNG and TIFF. TIFF produces
     one file with multiple pages, while PNG output produces one file per
-    page. The quality of the bitmap depends on the target resolution setting 
-    on the FOUserAgent.
+    page. Note: FOP can only produce multiple files (with PNG output) if
+    you can set a <span class="codefrag">java.io.File</span> indicating the primary PNG file
+    using the <span class="codefrag">FOUserAgent.setOutputFile(File)</span> method.
   </p>
-<a name="N103BF"></a><a name="bitmap-configuration"></a>
+<p>
+    The quality of the bitmap depends on the target resolution setting 
+    on the FOUserAgent and on further settings described below.
+  </p>
+<a name="N1040D"></a><a name="bitmap-configuration"></a>
 <h3 class="underlined_5">Configuration</h3>
 <p>
         The TIFF and PNG renderer configuration currently allows the following settings:
       </p>
 <pre class="code">&lt;renderer mime="image/png"&gt;
+  &lt;color-mode&gt;rgba&lt;/color-mode&gt;
   &lt;transparent-page-background&gt;true&lt;/transparent-page-background&gt;
+  &lt;background-color&gt;white&lt;/background-color&gt;
+  &lt;anti-aliasing&gt;true&lt;/anti-aliasing&gt;
+  &lt;rendering&gt;quality&lt;/rendering&gt;
   &lt;fonts&gt;&lt;!-- described elsewhere --&gt;&lt;/fonts&gt;
 &lt;/renderer&gt;</pre>
 <p>
-        The default value for the "transparent-page-background" setting is "false" which 
-        paints an opaque, white background for the whole image. If you set this to true,
+        The default value for the <span class="codefrag">"color-mode"</span> setting is <span class="codefrag">"rgba"</span> which
+        is equivalent to a 24bit RGB image with an 8bit alpha channel for transparency.
+        Valid values are:
+      </p>
+<ul>
+        
+<li>
+<span class="codefrag">rgba</span>: RGB with alpha channel (24bit + 8bit = 32bit)</li>
+        
+<li>
+<span class="codefrag">rgb</span>: RGB (24bit)</li>
+        
+<li>
+<span class="codefrag">gray</span>: gray (8bit)</li>
+        
+<li>
+<span class="codefrag">bi-level</span> (or <span class="codefrag">binary</span>): bi-level (1bit)</li>
+      
+</ul>
+<p>
+        Please note that there is currently no dithering or error diffusion available for bi-level
+        bitmap output.
+      </p>
+<p>
+        The default value for the <span class="codefrag">"transparent-page-background"</span> setting is
+        <span class="codefrag">"false"</span> which paints an opaque, white background for the whole image.
+        If you set this to <span class="codefrag">"true"</span>,
         no such background will be painted and you will get a transparent image if
         an alpha channel is available in the output format.
       </p>
-<a name="N103D0"></a><a name="tiff-configuration"></a>
+<p>
+        The default value for the <span class="codefrag">"background-color"</span> setting is <span class="codefrag">"white"</span>.
+        The color specifies in which color the page background is painted. It will only be
+        painted if <span class="codefrag">"transparent-page-background"</span> is not set to <span class="codefrag">"true"</span>.
+        All XSL-FO colors (including color functions) can be used.
+      </p>
+<p>
+        The default value for the <span class="codefrag">"anti-aliasing"</span> setting is <span class="codefrag">"true"</span>.
+        You can set this value to <span class="codefrag">"false"</span> to disable anti-aliasing and
+        thus improve rendering speeds a bit at the loss of some image quality.
+      </p>
+<p>
+        The default value for the <span class="codefrag">"rendering"</span> setting is <span class="codefrag">"true"</span>.
+        You can set this value to <span class="codefrag">"false"</span> to improve rendering speeds a bit
+        at the loss of some image quality. If this setting has an actual effect depends
+        on the JVM's Java2D backend.
+      </p>
+<a name="N10474"></a><a name="tiff-configuration"></a>
 <h3 class="underlined_5">TIFF-specific Configuration</h3>
 <p>
         In addition to the above values the TIFF renderer configuration allows some additional
@@ -1434,27 +1562,44 @@
       </p>
 <ul>
         
-<li>NONE (no compression)</li>
+<li>
+<span class="codefrag">NONE</span> (no compression)</li>
         
-<li>PackBits (RLE, run-length encoding)</li>
+<li>
+<span class="codefrag">PackBits</span> (RLE, run-length encoding)</li>
         
-<li>JPEG</li>
+<li>
+<span class="codefrag">JPEG</span>
+</li>
         
-<li>Deflate</li>
+<li>
+<span class="codefrag">Deflate</span>
+</li>
         
-<li>LZW</li>
+<li>
+<span class="codefrag">LZW</span>
+</li>
         
-<li>ZLib</li>
+<li>
+<span class="codefrag">ZLib</span>
+</li>
         
-<li>CCITT T.4 (Fax Group 3)</li>
+<li>
+<span class="codefrag">CCITT T.4</span> (Fax Group 3)</li>
         
-<li>CCITT T.6 (Fax Group 4)</li>
+<li>
+<span class="codefrag">CCITT T.6</span> (Fax Group 4)</li>
       
 </ul>
+<p>
+        This setting may override any setting made using the <span class="codefrag">"color-mode"</span>. For example, if
+        <span class="codefrag">"CCITT T.6"</span> is selected, the color mode is automatically forced to <span class="codefrag">"bi-level"</span> because
+        this compression format only supports bi-level images.
+      </p>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-        If you want to use CCITT compression, please make sure you've got a J2SE 1.4 or later and
+        If you want to use CCITT compression, please make sure you've got
         <a class="external" href="http://java.sun.com/products/java-media/jai/current.html">
           Java Advanced Imaging Image I/O Tools
         </a>
@@ -1463,9 +1608,19 @@
         Deflate and JPEG compression for writing.
       </div>
 </div>
+<a name="N104BF"></a><a name="bitmap-rendering-options"></a>
+<h3 class="underlined_5">Runtime Rendering Options</h3>
+<p>
+        The IF-based bitmap output implementations support a rendering option with the key
+        "target-bitmap-size" (value: java.awt.Dimension) that allows to force the pages to
+        be proportionally fit into a bitmap of a given size. This can be used to produce
+        thumbnails or little preview images of the individual pages. An example:
+      </p>
+<pre class="code">userAgent.getRenderingOptions().put(
+    "target-bitmap-size", new Dimension(320, 200));</pre>
 </div>
 
-<a name="N10404"></a><a name="txt"></a>
+<a name="N104CE"></a><a name="txt"></a>
 <h2 class="underlined_10">TXT</h2>
 <div class="section">
 <p>
@@ -1503,7 +1658,7 @@
 </ul>
 </div>
 
-<a name="N10420"></a><a name="sandbox"></a>
+<a name="N104EA"></a><a name="sandbox"></a>
 <h2 class="underlined_10">Output Formats in the Sandbox</h2>
 <div class="section">
 <p>
@@ -1512,7 +1667,7 @@
     can be found under src/sandbox and are compiled into build/fop-sandbox.jar during the
     main build. The output formats in the sandbox are marked as such below.
   </p>
-<a name="N10429"></a><a name="mif"></a>
+<a name="N104F3"></a><a name="mif"></a>
 <h3 class="underlined_5">MIF</h3>
 <div class="warning">
 <div class="label">Warning</div>
@@ -1522,7 +1677,7 @@
       This format is the Maker Interchange Format which is used by
       Adobe Framemaker.
     </p>
-<a name="N10436"></a><a name="svg"></a>
+<a name="N10500"></a><a name="svg"></a>
 <h3 class="underlined_5">SVG</h3>
 <div class="warning">
 <div class="label">Warning</div>
@@ -1541,7 +1696,7 @@
      </p>
 </div>
 
-<a name="N10444"></a><a name="wishlist"></a>
+<a name="N1050E"></a><a name="wishlist"></a>
 <h2 class="underlined_10">Wish list</h2>
 <div class="section">
 <p>
@@ -1564,7 +1719,7 @@
 <font size="-2">by&nbsp;Keiron Liddle,&nbsp;Art Welch</font>
 </p>
 <span class="version">
-          version 769445</span>
+          version 820939</span>
 </div>
 <!--+
     |end content

Modified: xmlgraphics/site/deploy/fop/trunk/output.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/output.pdf?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/output.pdf (original) and xmlgraphics/site/deploy/fop/trunk/output.pdf Fri Oct  2 11:34:05 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/output.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/output.xml?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/output.xml (original)
+++ xmlgraphics/site/deploy/fop/trunk/output.xml Fri Oct  2 11:34:05 2009
@@ -14,10 +14,10 @@
   See the License for the specific language governing permissions and
   limitations under the License.
 --><!-- $Id$ --><!-- Output Formats: Renderers --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "document-v13.dtd">
-<document xmlns:xi="http://www.w3.org/2001/XInclude">
+<document>
   <header>
     <title>Apache FOP Output Formats</title>
-    <version>$Revision: 769445 $</version>
+    <version>$Revision: 820939 $</version>
     <authors>
       <person name="Keiron Liddle" email="keiron@aftexsw.com"/>
       <person name="Art Welch" email=""/>
@@ -417,6 +417,28 @@
           Consult the technical reference for your printer for all available values.
         </p>
       </section>
+      <section id="pcl-output-bin">
+        <title>Output Bin</title>
+        <p>
+          The <code>output-bin</code> extension attribute on fo:simple-page-master allows to 
+          select the output bin into which the printed output should be fed. Example:
+        </p>
+      <source xml:space="preserve"><![CDATA[
+      <fo:layout-master-set>
+        <fo:simple-page-master master-name="simple" pcl:output-bin="2">
+          ...
+        </fo:simple-page-master>
+      </fo:layout-master-set>
+]]></source>
+        <p>
+          Note: the output bin number is a positive integer and the value depends on
+          the target printer. Not all PCL printers support the same output bins.
+          Usually, 
+          "1" is the upper output bin,
+          "2" is the lower (rear) output bin. 
+          Consult the technical reference for your printer for all available values.
+        </p>
+      </section>
       <section id="pcl-duplex-mode">
         <title>Page Duplex Mode</title>
         <p>
@@ -646,6 +668,11 @@
         <font-triplet name="monospace" style="normal" weight="bold"/>
         <font-triplet name="Courier" style="normal" weight="bold"/>
       </font>]]></source>
+        <p>
+          By default, all manually configured fonts are embedded, unless they are matched in the
+          <link href="fonts.html#embedding"><code>referenced-fonts</code> section of the configuration file</link>.
+          However, the default fonts shown above will not be embedded.
+        </p>
       </section>
       <section id="afp-renderer-resolution-config">
         <title>Output Resolution</title>
@@ -764,6 +791,17 @@
         fo:external-graphic elements and if it is identical (string matching is used) in the generated
         AFP the external graphic is replaced by a reference to the given resource.
         </p>
+        <p>
+          The effect here is that whenever FOP encounters the URI specified in the extension,
+          it will effectively generate code to include the page segment with the given name
+          instead of embedding the image referenced by the URI. The URI is still required as
+          the underlying image serves as a provider for the intrinsic size of the image
+          (At the moment, FOP is unable to extract the intrinsic size of the page segment from
+          an AFP resource file). For the image to appear in an AFP viewer or to be printed, the
+          AFP resource must be available on the target device. FOP does not embed the page
+          segment in the generated file. Please also note that page segments cannot be scaled.
+          They are always rendered in their intrinsic size.
+        </p>
       </section>
       <section id="afp-tag-logical-element">
         <title>Tag Logical Element (TLE) Extension</title>
@@ -825,12 +863,41 @@
 ]]></source>
         <p>
           The invoke-medium-map element is allowed as child of fo:page-sequence (page group
-          level). It is NOT supported on document level (fo:root), yet. FOP also doesn't support
-          specifying medium maps inside XML (using BMM/EMM). It can only reference an existing
-          medium map by name. The medium map has to be constructed through different means and
-          available on the target platform.
+          level) or fo:simple-page-master. It is NOT supported on document level (fo:root), yet. 
+          FOP also doesn't support specifying medium maps inside XML (using BMM/EMM). It can 
+          only reference an existing medium map by name. The medium map has to be constructed 
+          through different means and available on the target platform.
         </p>
       </section>
+      <section id="afp-form-maps">
+        <title>Form Maps/Defs</title>
+        <p>
+          Apache FOP supports embedding an external form map resource in the
+          generated AFP output. This is done using the <code>afp:include-form-map</code>
+          extension. An example: 
+        </p>
+      <source xml:space="preserve"><![CDATA[
+<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
+     xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp">
+  [..]
+  <fo:declarations>
+    <afp:include-form-map name="F1SAMP1" src="file:f1samp1.fde"/>
+  </fo:declarations>
+]]></source>
+        <p>
+          The <code>afp:include-form-map</code> is to be placed as a direct child of
+          <code>fo:declarations</code>. The <code>name</code> is an AFP resource name
+          (max. 8 characters) and the <code>src</code> attribute is the URI identifying the
+          external form map resource. When such a form map is embedded, you can use the
+          <code>afp:invoke-medium-map</code> extension (described above) to invoke any medium
+          map included in the form map. 
+        </p>
+        <note>
+          Apache FOP doesn't support a way to define a form map or medium map using XML means
+          inside an XSL-FO document. You will have to build the form map with some third-party
+          tool.
+        </note>
+      </section>
     </section>
     <section id="afp-foreign-attributes">
       <title>Foreign Attributes</title>
@@ -961,8 +1028,13 @@
   <p>
     Currently, two output formats are supported: PNG and TIFF. TIFF produces
     one file with multiple pages, while PNG output produces one file per
-    page. The quality of the bitmap depends on the target resolution setting 
-    on the FOUserAgent.
+    page. Note: FOP can only produce multiple files (with PNG output) if
+    you can set a <code>java.io.File</code> indicating the primary PNG file
+    using the <code>FOUserAgent.setOutputFile(File)</code> method.
+  </p>
+  <p>
+    The quality of the bitmap depends on the target resolution setting 
+    on the FOUserAgent and on further settings described below.
   </p>
     <section id="bitmap-configuration">
       <title>Configuration</title>
@@ -970,15 +1042,52 @@
         The TIFF and PNG renderer configuration currently allows the following settings:
       </p>
 <source xml:space="preserve"><![CDATA[<renderer mime="image/png">
+  <color-mode>rgba</color-mode>
   <transparent-page-background>true</transparent-page-background>
+  <background-color>white</background-color>
+  <anti-aliasing>true</anti-aliasing>
+  <rendering>quality</rendering>
   <fonts><!-- described elsewhere --></fonts>
 </renderer>]]></source>
       <p>
-        The default value for the "transparent-page-background" setting is "false" which 
-        paints an opaque, white background for the whole image. If you set this to true,
+        The default value for the <code>"color-mode"</code> setting is <code>"rgba"</code> which
+        is equivalent to a 24bit RGB image with an 8bit alpha channel for transparency.
+        Valid values are:
+      </p>
+      <ul>
+        <li><code>rgba</code>: RGB with alpha channel (24bit + 8bit = 32bit)</li>
+        <li><code>rgb</code>: RGB (24bit)</li>
+        <li><code>gray</code>: gray (8bit)</li>
+        <li><code>bi-level</code> (or <code>binary</code>): bi-level (1bit)</li>
+      </ul>
+      <p>
+        Please note that there is currently no dithering or error diffusion available for bi-level
+        bitmap output.
+      </p>
+      <p>
+        The default value for the <code>"transparent-page-background"</code> setting is
+        <code>"false"</code> which paints an opaque, white background for the whole image.
+        If you set this to <code>"true"</code>,
         no such background will be painted and you will get a transparent image if
         an alpha channel is available in the output format.
       </p>
+      <p>
+        The default value for the <code>"background-color"</code> setting is <code>"white"</code>.
+        The color specifies in which color the page background is painted. It will only be
+        painted if <code>"transparent-page-background"</code> is not set to <code>"true"</code>.
+        All XSL-FO colors (including color functions) can be used.
+      </p>
+      <p>
+        The default value for the <code>"anti-aliasing"</code> setting is <code>"true"</code>.
+        You can set this value to <code>"false"</code> to disable anti-aliasing and
+        thus improve rendering speeds a bit at the loss of some image quality.
+      </p>
+      <p>
+        The default value for the <code>"rendering"</code> setting is <code>"true"</code>.
+        You can set this value to <code>"false"</code> to improve rendering speeds a bit
+        at the loss of some image quality. If this setting has an actual effect depends
+        on the JVM's Java2D backend.
+      </p>
     </section>
     <section id="tiff-configuration">
       <title>TIFF-specific Configuration</title>
@@ -999,17 +1108,22 @@
         actual codecs being available. Here is a list of possible values:
       </p>
       <ul>
-        <li>NONE (no compression)</li>
-        <li>PackBits (RLE, run-length encoding)</li>
-        <li>JPEG</li>
-        <li>Deflate</li>
-        <li>LZW</li>
-        <li>ZLib</li>
-        <li>CCITT T.4 (Fax Group 3)</li>
-        <li>CCITT T.6 (Fax Group 4)</li>
+        <li><code>NONE</code> (no compression)</li>
+        <li><code>PackBits</code> (RLE, run-length encoding)</li>
+        <li><code>JPEG</code></li>
+        <li><code>Deflate</code></li>
+        <li><code>LZW</code></li>
+        <li><code>ZLib</code></li>
+        <li><code>CCITT T.4</code> (Fax Group 3)</li>
+        <li><code>CCITT T.6</code> (Fax Group 4)</li>
       </ul>
+      <p>
+        This setting may override any setting made using the <code>"color-mode"</code>. For example, if
+        <code>"CCITT T.6"</code> is selected, the color mode is automatically forced to <code>"bi-level"</code> because
+        this compression format only supports bi-level images.
+      </p>
       <note>
-        If you want to use CCITT compression, please make sure you've got a J2SE 1.4 or later and
+        If you want to use CCITT compression, please make sure you've got
         <link href="http://java.sun.com/products/java-media/jai/current.html">
           Java Advanced Imaging Image I/O Tools
         </link>
@@ -1018,6 +1132,17 @@
         Deflate and JPEG compression for writing.
       </note>
     </section>
+    <section id="bitmap-rendering-options">
+      <title>Runtime Rendering Options</title>
+      <p>
+        The IF-based bitmap output implementations support a rendering option with the key
+        "target-bitmap-size" (value: java.awt.Dimension) that allows to force the pages to
+        be proportionally fit into a bitmap of a given size. This can be used to produce
+        thumbnails or little preview images of the individual pages. An example:
+      </p>
+      <source xml:space="preserve"><![CDATA[userAgent.getRenderingOptions().put(
+    "target-bitmap-size", new Dimension(320, 200));]]></source>
+    </section>
 </section>
 <section id="txt">
   <title>TXT</title>
@@ -1098,4 +1223,4 @@
 </section>
 
   </body>
-</document>
\ No newline at end of file
+</document>

Modified: xmlgraphics/site/deploy/fop/trunk/pdfa.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfa.html?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/pdfa.html (original)
+++ xmlgraphics/site/deploy/fop/trunk/pdfa.html Fri Oct  2 11:34:05 2009
@@ -226,14 +226,14 @@
 </div>
 </div>
     
-<a name="N10019"></a><a name="overview"></a>
+<a name="N10018"></a><a name="overview"></a>
 <h2 class="underlined_10">Overview</h2>
 <div class="section">
 <p>
         PDF/A is a standard which turns PDF into an "electronic document file 
         format for long-term preservation". PDF/A-1 is the first part of the 
         standard and is documented in 
-        <a class="external" href="http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=38920&amp;ICS1=37&amp;ICS2=100&amp;ICS3=99">ISO 19005-1:2005(E)</a>. 
+        <a class="external" href="http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=38920&ICS1=37&ICS2=100&ICS3=99">ISO 19005-1:2005(E)</a>. 
         Work on PDF/A-2 is in progress at 
         <a class="external" href="http://www.aiim.org/standards.asp?ID=25013">AIIM</a>.
       </p>
@@ -243,7 +243,7 @@
       </p>
 </div>
     
-<a name="N10032"></a><a name="status"></a>
+<a name="N10031"></a><a name="status"></a>
 <h2 class="underlined_10">Implementation Status</h2>
 <div class="section">
 <p>
@@ -263,7 +263,7 @@
       </p>
 </div>
     
-<a name="N10048"></a><a name="command-line"></a>
+<a name="N10047"></a><a name="command-line"></a>
 <h2 class="underlined_10">Usage (command line)</h2>
 <div class="section">
 <p>
@@ -273,7 +273,7 @@
       </p>
 </div>
     
-<a name="N10052"></a><a name="embedded"></a>
+<a name="N10051"></a><a name="embedded"></a>
 <h2 class="underlined_10">Usage (embedded)</h2>
 <div class="section">
 <p>
@@ -291,7 +291,7 @@
       </p>
 </div>
     
-<a name="N10063"></a><a name="rules"></a>
+<a name="N10062"></a><a name="rules"></a>
 <h2 class="underlined_10">PDF/A in Action</h2>
 <div class="section">
 <p>
@@ -339,7 +339,7 @@
 </ul>
 </div>
     
-<a name="N10085"></a><a name="profile-compatibility"></a>
+<a name="N10084"></a><a name="profile-compatibility"></a>
 <h2 class="underlined_10">PDF profile compatibility</h2>
 <div class="section">
 <p>
@@ -348,7 +348,7 @@
       </p>
 </div>
     
-<a name="N1008F"></a><a name="interoperability"></a>
+<a name="N1008E"></a><a name="interoperability"></a>
 <h2 class="underlined_10">Interoperability</h2>
 <div class="section">
 <p>

Modified: xmlgraphics/site/deploy/fop/trunk/pdfa.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfa.pdf?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/pdfa.pdf (original) and xmlgraphics/site/deploy/fop/trunk/pdfa.pdf Fri Oct  2 11:34:05 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/pdfa.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfa.xml?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/pdfa.xml (original)
+++ xmlgraphics/site/deploy/fop/trunk/pdfa.xml Fri Oct  2 11:34:05 2009
@@ -14,7 +14,7 @@
   See the License for the specific language governing permissions and
   limitations under the License.
 --><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "document-v13.dtd">
-<document xmlns:xi="http://www.w3.org/2001/XInclude">
+<document>
   <header>
     <title>PDF/A (ISO 19005)</title>
     <version>$Revision: 688653 $</version>
@@ -150,4 +150,4 @@
       </p>
     </section>
   </body>
-</document>
\ No newline at end of file
+</document>

Modified: xmlgraphics/site/deploy/fop/trunk/pdfencryption.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfencryption.html?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/pdfencryption.html (original)
+++ xmlgraphics/site/deploy/fop/trunk/pdfencryption.html Fri Oct  2 11:34:05 2009
@@ -220,7 +220,7 @@
 </div>
 </div>
     
-<a name="N1001D"></a><a name="Overview"></a>
+<a name="N1001C"></a><a name="Overview"></a>
 <h2 class="underlined_10">Overview</h2>
 <div class="section">
 <p>
@@ -240,7 +240,7 @@
       </p>
 </div>
     
-<a name="N1002A"></a><a name="Usage+%28command+line%29"></a>
+<a name="N10029"></a><a name="Usage+%28command+line%29"></a>
 <h2 class="underlined_10">Usage (command line)</h2>
 <div class="section">
 <p>
@@ -272,7 +272,7 @@
       </p>
 </div>
     
-<a name="N10052"></a><a name="Usage+%28embedded%29"></a>
+<a name="N10051"></a><a name="Usage+%28embedded%29"></a>
 <h2 class="underlined_10">Usage (embedded)</h2>
 <div class="section">
 <p>
@@ -403,7 +403,7 @@
 </ol>
 </div>
     
-<a name="N10138"></a><a name="Environment"></a>
+<a name="N10137"></a><a name="Environment"></a>
 <h2 class="underlined_10">Environment</h2>
 <div class="section">
 <p>
@@ -432,7 +432,7 @@
       </p>
 </div>
     
-<a name="N1015E"></a><a name="install_crypto"></a>
+<a name="N1015D"></a><a name="install_crypto"></a>
 <h2 class="underlined_10">Installing a crypto provider</h2>
 <div class="section">
 <p>

Modified: xmlgraphics/site/deploy/fop/trunk/pdfencryption.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfencryption.pdf?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/pdfencryption.pdf (original) and xmlgraphics/site/deploy/fop/trunk/pdfencryption.pdf Fri Oct  2 11:34:05 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/pdfencryption.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfencryption.xml?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/pdfencryption.xml (original)
+++ xmlgraphics/site/deploy/fop/trunk/pdfencryption.xml Fri Oct  2 11:34:05 2009
@@ -14,7 +14,7 @@
   See the License for the specific language governing permissions and
   limitations under the License.
 --><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "document-v13.dtd">
-<document xmlns:xi="http://www.w3.org/2001/XInclude">
+<document>
   <header>
     <title>PDF encryption.</title>
     <version>$Revision: 638396 $</version>
@@ -218,4 +218,4 @@
       </p>
     </section>
   </body>
-</document>
\ No newline at end of file
+</document>

Modified: xmlgraphics/site/deploy/fop/trunk/pdfx.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfx.html?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/pdfx.html (original)
+++ xmlgraphics/site/deploy/fop/trunk/pdfx.html Fri Oct  2 11:34:05 2009
@@ -223,7 +223,7 @@
 </div>
 </div>
     
-<a name="N10019"></a><a name="overview"></a>
+<a name="N10018"></a><a name="overview"></a>
 <h2 class="underlined_10">Overview</h2>
 <div class="section">
 <div class="warning">
@@ -237,13 +237,13 @@
         PDF/X is a standard which faciliates prepress digital data exchange using PDF.
         Currently, only PDF/X-3:2003 is implemented out of the many different flavours of PDF/X
         profiles. PDF/X-3:2003 is documented in 
-        <a class="external" href="http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=39940&amp;ICS1=37&amp;ICS2=100&amp;ICS3=99">ISO 15930-6:2003(E)</a>. 
+        <a class="external" href="http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=39940&ICS1=37&ICS2=100&ICS3=99">ISO 15930-6:2003(E)</a>. 
         More info on PDF/X can be found on the  
         <a class="external" href="http://www.pdfx.info/">PDF/X info site</a>.
       </p>
 </div>
     
-<a name="N1002E"></a><a name="status"></a>
+<a name="N1002D"></a><a name="status"></a>
 <h2 class="underlined_10">Implementation Status</h2>
 <div class="section">
 <p>
@@ -271,7 +271,7 @@
       </p>
 </div>
     
-<a name="N10041"></a><a name="command-line"></a>
+<a name="N10040"></a><a name="command-line"></a>
 <h2 class="underlined_10">Usage (command line)</h2>
 <div class="section">
 <p>
@@ -281,7 +281,7 @@
       </p>
 </div>
     
-<a name="N1004B"></a><a name="embedded"></a>
+<a name="N1004A"></a><a name="embedded"></a>
 <h2 class="underlined_10">Usage (embedded)</h2>
 <div class="section">
 <p>
@@ -300,7 +300,7 @@
       </p>
 </div>
     
-<a name="N1005C"></a><a name="rules"></a>
+<a name="N1005B"></a><a name="rules"></a>
 <h2 class="underlined_10">PDF/X in Action</h2>
 <div class="section">
 <p>
@@ -344,7 +344,7 @@
 </ul>
 </div>
     
-<a name="N1007F"></a><a name="profile-compatibility"></a>
+<a name="N1007E"></a><a name="profile-compatibility"></a>
 <h2 class="underlined_10">PDF profile compatibility</h2>
 <div class="section">
 <p>

Modified: xmlgraphics/site/deploy/fop/trunk/pdfx.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfx.pdf?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/pdfx.pdf (original) and xmlgraphics/site/deploy/fop/trunk/pdfx.pdf Fri Oct  2 11:34:05 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/pdfx.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfx.xml?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/pdfx.xml (original)
+++ xmlgraphics/site/deploy/fop/trunk/pdfx.xml Fri Oct  2 11:34:05 2009
@@ -13,7 +13,7 @@
   See the License for the specific language governing permissions and
   limitations under the License.
 --><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "document-v13.dtd">
-<document xmlns:xi="http://www.w3.org/2001/XInclude">
+<document>
   <header>
     <title>PDF/X (ISO 15930)</title>
     <version>$Revision: 627324 $</version>
@@ -130,4 +130,4 @@
       </p>
     </section>
   </body>
-</document>
\ No newline at end of file
+</document>

Modified: xmlgraphics/site/deploy/fop/trunk/running.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/running.html?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/running.html (original)
+++ xmlgraphics/site/deploy/fop/trunk/running.html Fri Oct  2 11:34:05 2009
@@ -245,7 +245,7 @@
 </div>
 </div>
     
-<a name="N10012"></a><a name="require"></a>
+<a name="N10011"></a><a name="require"></a>
 <h2 class="underlined_10">System Requirements</h2>
 <div class="section">
 <p>The following software must be installed:</p>
@@ -315,10 +315,10 @@
 </ul>
 </div>
     
-<a name="N10076"></a><a name="install"></a>
+<a name="N10075"></a><a name="install"></a>
 <h2 class="underlined_10">Installation</h2>
 <div class="section">
-<a name="N1007C"></a><a name="install-instruct"></a>
+<a name="N1007B"></a><a name="install-instruct"></a>
 <h3 class="underlined_5">Instructions</h3>
 <p>
           Basic FOP installation consists of first unzipping the <span class="codefrag">.gz</span> file that is the 
@@ -327,7 +327,7 @@
           documentation or Zip application software documentation for instructions specific to your 
           site.
         </p>
-<a name="N1008C"></a><a name="install-problems"></a>
+<a name="N1008B"></a><a name="install-problems"></a>
 <h3 class="underlined_5">Problems</h3>
 <p>
           Some Mac OSX users have experienced filename truncation problems using Stuffit to unzip 
@@ -337,10 +337,10 @@
         </p>
 </div>
     
-<a name="N1009A"></a><a name="standalone-start"></a>
+<a name="N10099"></a><a name="standalone-start"></a>
 <h2 class="underlined_10">Starting FOP as a Standalone Application</h2>
 <div class="section">
-<a name="N100A0"></a><a name="fop-script"></a>
+<a name="N1009F"></a><a name="fop-script"></a>
 <h3 class="underlined_5">Using the fop script or batch file</h3>
 <p>
         The usual and recommended practice for starting FOP from the command line is to run the 
@@ -432,7 +432,7 @@
         <strong>and</strong> if compatible encryption support is available at run time. 
         Currently, only the JCE is supported. Check the <a href="pdfencryption.html">Details</a>.
       </p>
-<a name="N100C2"></a><a name="your-own-script"></a>
+<a name="N100C1"></a><a name="your-own-script"></a>
 <h3 class="underlined_5">Writing your own script</h3>
 <p>FOP's entry point for your own scripts is the class
 <span class="codefrag">org.apache.fop.cli.Main</span>. The general pattern for the
@@ -443,7 +443,7 @@
         the standard scripts to make sure that 
         you get your environment properly configured. 
         </p>
-<a name="N100D2"></a><a name="jar-option"></a>
+<a name="N100D1"></a><a name="jar-option"></a>
 <h3 class="underlined_5">Running with java's -jar option</h3>
 <p>
         As an alternative to the start scripts you can run <span class="codefrag">java
@@ -461,7 +461,7 @@
 <p>In both cases the arguments consist of the options and
         infile and outfile specifications as shown above for the
         standard scripts.</p>
-<a name="N10101"></a><a name="dynamical-classpath"></a>
+<a name="N10100"></a><a name="dynamical-classpath"></a>
 <h3 class="underlined_5">FOP's dynamical classpath construction</h3>
 <p>If FOP is started without a proper classpath, it tries to
           add its dependencies dynamically. If the system property
@@ -485,7 +485,7 @@
           <span class="codefrag">org.apache.fop.cli.Main</span>.</p>
 </div>
     
-<a name="N10133"></a><a name="check-input"></a>
+<a name="N10132"></a><a name="check-input"></a>
 <h2 class="underlined_10">Using Xalan to Check XSL-FO Input</h2>
 <div class="section">
 <p>
@@ -539,7 +539,7 @@
       </p>
 </div>
     
-<a name="N10161"></a><a name="memory"></a>
+<a name="N10160"></a><a name="memory"></a>
 <h2 class="underlined_10">Memory Usage</h2>
 <div class="section">
 <p>
@@ -600,7 +600,7 @@
 </ul>
 </div>
     
-<a name="N10188"></a><a name="problems"></a>
+<a name="N10187"></a><a name="problems"></a>
 <h2 class="underlined_10">Problems</h2>
 <div class="section">
 <p>If you have problems running FOP, please see the <a href="../gethelp.html">"How to get Help" page</a>.</p>

Modified: xmlgraphics/site/deploy/fop/trunk/running.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/running.pdf?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/running.pdf (original) and xmlgraphics/site/deploy/fop/trunk/running.pdf Fri Oct  2 11:34:05 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/running.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/running.xml?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/running.xml (original)
+++ xmlgraphics/site/deploy/fop/trunk/running.xml Fri Oct  2 11:34:05 2009
@@ -14,7 +14,7 @@
   See the License for the specific language governing permissions and
   limitations under the License.
 --><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "document-v13.dtd">
-<document xmlns:xi="http://www.w3.org/2001/XInclude">
+<document>
   <header>
     <title>Running Apache FOP</title>
     <version>$Revision: 638396 $</version>
@@ -343,4 +343,4 @@
       <p>If you have problems running FOP, please see the <link href="../gethelp.html">"How to get Help" page</link>.</p>
     </section>
   </body>
-</document>
\ No newline at end of file
+</document>

Modified: xmlgraphics/site/deploy/fop/trunk/servlets.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/servlets.html?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/servlets.html (original)
+++ xmlgraphics/site/deploy/fop/trunk/servlets.html Fri Oct  2 11:34:05 2009
@@ -249,7 +249,7 @@
 </div>
 </div>
     
-<a name="N10015"></a><a name="overview"></a>
+<a name="N10014"></a><a name="overview"></a>
 <h2 class="underlined_10">Overview</h2>
 <div class="section">
 <p>
@@ -257,7 +257,7 @@
       </p>
 </div>
     
-<a name="N1001F"></a><a name="example-servlets"></a>
+<a name="N1001E"></a><a name="example-servlets"></a>
 <h2 class="underlined_10">Example Servlets in the FOP distribution</h2>
 <div class="section">
 <p>
@@ -288,7 +288,7 @@
 </div>
 </div>
     
-<a name="N1003D"></a><a name="servlet"></a>
+<a name="N1003C"></a><a name="servlet"></a>
 <h2 class="underlined_10">Create your own Servlet</h2>
 <div class="section">
 <div class="note">
@@ -297,7 +297,7 @@
         This section assumes you are familiar with <a href="embedding.html">embedding FOP</a>.
       </div>
 </div>
-<a name="N1004A"></a><a name="minimal-servlet"></a>
+<a name="N10049"></a><a name="minimal-servlet"></a>
 <h3 class="underlined_5">A minimal Servlet</h3>
 <p>
           Here is a minimal code snippet to demonstrate the basics:
@@ -326,7 +326,7 @@
           See below for details.
         </div>
 </div>
-<a name="N1005B"></a><a name="xslt"></a>
+<a name="N1005A"></a><a name="xslt"></a>
 <h3 class="underlined_5">Adding XSL tranformation (XSLT)</h3>
 <p>
           A common requirement is to transform an XML source to
@@ -390,12 +390,12 @@
           Because you have an explicit <span class="codefrag">Transformer</span> object, you can also use it to 
           explicitely set parameters for the transformation run.
         </p>
-<a name="N1007B"></a><a name="cfg"></a>
+<a name="N1007A"></a><a name="cfg"></a>
 <h3 class="underlined_5">Custom configuration</h3>
 <p>
           You can easily set up your own FOUserAgent as demonstrated on the <a href="embedding.html">Embedding page</a>.
         </p>
-<a name="N10089"></a><a name="performance"></a>
+<a name="N10088"></a><a name="performance"></a>
 <h3 class="underlined_5">Improving performance</h3>
 <p>
           There are several options to consider:
@@ -422,7 +422,7 @@
           <a href="embedding.html#performance">performance hints from the Embedding page</a>
           apply here, too.
         </p>
-<a name="N100AA"></a><a name="uriresolver"></a>
+<a name="N100A9"></a><a name="uriresolver"></a>
 <h3 class="underlined_5">Accessing resources in your web application</h3>
 <p>
           Often, you will want to use resources (stylesheets, images etc.) which are bundled with
@@ -492,7 +492,7 @@
 transformer.setURIResolver(this.uriResolver);</pre>
 </div>
     
-<a name="N100D8"></a><a name="ie"></a>
+<a name="N100D7"></a><a name="ie"></a>
 <h2 class="underlined_10">Notes on Microsoft Internet Explorer</h2>
 <div class="section">
 <p>
@@ -539,7 +539,7 @@
 </ul>
 </div>
     
-<a name="N10109"></a><a name="servlet-engine"></a>
+<a name="N10108"></a><a name="servlet-engine"></a>
 <h2 class="underlined_10">Servlet Engines</h2>
 <div class="section">
 <p>
@@ -547,13 +547,13 @@
         with existing XML/XSLT libraries. Servlet containers also often use their own classloaders 
         for loading webapps, which can cause bugs and security problems.
       </p>
-<a name="N10112"></a><a name="tomcat"></a>
+<a name="N10111"></a><a name="tomcat"></a>
 <h3 class="underlined_5">Tomcat</h3>
 <p>
           Check Tomcat's documentation for detailed instructions about installing FOP and Cocoon.
           There are known bugs that must be addressed, particularly for Tomcat 4.0.3.
         </p>
-<a name="N1011C"></a><a name="websphere"></a>
+<a name="N1011B"></a><a name="websphere"></a>
 <h3 class="underlined_5">WebSphere 3.5</h3>
 <p>
           Put a copy of a working parser in some directory where WebSphere can access it.
@@ -569,7 +569,7 @@
         </p>
 </div>
     
-<a name="N10127"></a><a name="complex-usecases"></a>
+<a name="N10126"></a><a name="complex-usecases"></a>
 <h2 class="underlined_10">Handling complex use cases</h2>
 <div class="section">
 <p>

Modified: xmlgraphics/site/deploy/fop/trunk/servlets.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/servlets.pdf?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/servlets.pdf (original) and xmlgraphics/site/deploy/fop/trunk/servlets.pdf Fri Oct  2 11:34:05 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/servlets.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/servlets.xml?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/servlets.xml (original)
+++ xmlgraphics/site/deploy/fop/trunk/servlets.xml Fri Oct  2 11:34:05 2009
@@ -14,7 +14,7 @@
   See the License for the specific language governing permissions and
   limitations under the License.
 --><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "document-v13.dtd">
-<document xmlns:xi="http://www.w3.org/2001/XInclude">
+<document>
   <header>
     <title>Servlets</title>
     <subtitle>How to use Apache FOP in a Servlet</subtitle>
@@ -319,4 +319,4 @@
       </p>
     </section>
   </body>
-</document>
\ No newline at end of file
+</document>

Modified: xmlgraphics/site/deploy/fop/trunk/upgrading.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/upgrading.html?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/upgrading.html (original)
+++ xmlgraphics/site/deploy/fop/trunk/upgrading.html Fri Oct  2 11:34:05 2009
@@ -211,7 +211,7 @@
 </div>
 </div>
     
-<a name="N10012"></a><a name="important"></a>
+<a name="N10011"></a><a name="important"></a>
 <h2 class="underlined_10">Important!</h2>
 <div class="section">
 <p>
@@ -292,7 +292,7 @@
 </ul>
 </div>
     
-<a name="N10055"></a><a name="issues"></a>
+<a name="N10054"></a><a name="issues"></a>
 <h2 class="underlined_10">What you need to know when you upgrade!</h2>
 <div class="section">
 <p>

Modified: xmlgraphics/site/deploy/fop/trunk/upgrading.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/upgrading.pdf?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/upgrading.pdf (original) and xmlgraphics/site/deploy/fop/trunk/upgrading.pdf Fri Oct  2 11:34:05 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/upgrading.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/upgrading.xml?rev=820972&r1=820971&r2=820972&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/upgrading.xml (original)
+++ xmlgraphics/site/deploy/fop/trunk/upgrading.xml Fri Oct  2 11:34:05 2009
@@ -14,7 +14,7 @@
   See the License for the specific language governing permissions and
   limitations under the License.
 --><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "document-v13.dtd">
-<document xmlns:xi="http://www.w3.org/2001/XInclude">
+<document>
   <header>
     <title>Upgrading from an Earlier Version of Apache FOP</title>
     <version>$Revision: 733034 $</version>
@@ -122,4 +122,4 @@
       </ul>
     </section>
   </body>
-</document>
\ No newline at end of file
+</document>



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


Mime
View raw message