xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r813018 [4/24] - in /websites/staging/xmlgraphics/trunk/content: ./ fop/ fop/0.95/ fop/0.95/images/ fop/1.0/ fop/1.0/images/ fop/dev/ fop/dev/design/ fop/dev/fo/ fop/dev/svg/ fop/fo/ fop/trunk/ fop/trunk/images/
Date Sun, 15 Apr 2012 05:39:54 GMT
Added: websites/staging/xmlgraphics/trunk/content/fop/0.95/output.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/output.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/output.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,618 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP Output Formats</title>
+
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+    <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+    <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+    </style>
+
+    
+
+    
+    
+  </head>
+
+  <body>
+	  <div id="banner">&nbsp;
+	  </div>
+
+	  <div id="navigation">
+	  <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+  <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+  <input type="text" name="q" id="query" /><br />
+  <input type="submit" id="submit" value="Search" />
+</form>
+	  </div>
+	
+	  <div id="bannertext">
+        <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+        <h1>Apache™ FOP Output Formats</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version><authors><person email="keiron@aftexsw.com" name="Keiron Liddle"></person><person email="" name="Art Welch"></person></authors></p>
+<p>Apache™ FOP supports multiple output formats by using a different renderer for each format. The renderers do not all have the same set of capabilities, sometimes because of the output format itself, sometimes because some renderers get more development attention than others.</p>
+<h1 id="general">General Information</h1>
+<h2 id="general-fonts">Fonts</h2>
+<p>Most FOP renderers use a FOP-specific system for font registration. However, the Java2D/AWT and print renderers use the Java AWT package, which gets its font information from the operating system registration. This can result in several differences, including actually using different fonts, and having different font metrics for the same font. The net effect is that the layout of a given FO document can be quite different between renderers that do not use the same font information.</p>
+<p>Theoretically, there's some potential to make the output of the PDF/PS renderers match the output of the Java2D-based renderers. If FOP used the font metrics from its own font subsystem but still used Java2D for text painting in the Java2D-based renderers, this could probably be achieved. However, this approach hasn't been implemented, yet.</p>
+<p>With a work-around, it is possible to match the PDF/PS output in a Java2D-based renderer pretty closely. The clue is to use the <a href="intermediate.html">intermediate format</a> . The trick is to layout the document using FOP's own font subsystem but then render the document using Java2D. Here are the necessary steps (using the command-line):</p>
+<ol>
+<li>
+<p>Produce an IF file: <code>fop -fo myfile.fo -at application/pdf myfile.at.xml</code> <br></br>Specifying "application/pdf" for the "-at" parameter causes FOP to use FOP's own font subsystem (which is used by the PDF renderer). Note that no PDF file is created in this step.</p>
+</li>
+<li>
+<p>Render to a PDF file: <code>fop -atin myfile.at.xml -pdf myfile.pdf</code> </p>
+</li>
+<li>
+<p>Render to a Java2D-based renderer:</p>
+</li>
+<li>
+<p><code>fop -atin myfile.at.xml -print</code> </p>
+</li>
+<li>
+<p><code>fop -atin myfile.at.xml -awt</code> </p>
+</li>
+<li>
+<p><code>fop -atin myfile.at.xml -tiff myfile.tiff</code> </p>
+</li>
+</ol>
+<h2 id="general-direct-output">Output to a Printer or Other Device</h2>
+<p>The most obvious way to print your document is to use the FOP <a href="#print">print renderer</a> , which uses the Java2D API (AWT). However, you can also send output from the Postscript renderer directly to a Postscript device, or output from the PCL renderer directly to a PCL device.</p>
+<p>Here are Windows command-line examples for Postscript and PCL:
+fop ... -ps \computername\printerfop ... -pcl \computername\printer
+Here is some Java code to accomplish the task in UNIX:
+proc = Runtime.getRuntime().exec("lp -d" + print_queue + " -o -dp -");
+out = proc.getOutputStream();
+Set the output MIME type to "application/x-pcl" (MimeConstants.MIME_PCL) and it happily sends the PCL to the UNIX printer queue.</p>
+<h1 id="pdf">PDF</h1>
+<p>PDF is the best supported output format. It is also the most accurate with text and layout. This creates a PDF document that is streamed out as each page is rendered. This means that the internal page index information is stored near the end of the document. The PDF version supported is 1.4. PDF versions are forwards/backwards compatible.</p>
+<p>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>
+<h2 id="pdf-fonts">Fonts</h2>
+<p>PDF has a set of fonts that are always available to all PDF viewers; to quote from the PDF Specification: <em>"PDF prescribes a set of 14 standard fonts that can be used without prior definition. These include four faces each of three Latin text typefaces (Courier, Helvetica, and Times), as well as two symbolic fonts (Symbol and ITC Zapf Dingbats). These fonts, or suitable substitute fonts with the same metrics, are guaranteed to be available in all PDF viewer applications."</em> </p>
+<h2 id="pdf-postprocess">Post-processing</h2>
+<p>FOP does not currently support several desirable PDF features: watermarks and signatures. One workaround is to use Adobe Acrobat (the full version, not the Reader) to process the file manually or with scripting that it supports.</p>
+<p>Another popular post-processing tool is <a href="http://www.lowagie.com/iText">iText</a> , which has tools for adding security features, document properties, watermarks, and many other features to PDF files.
+<warning>Caveat: iText may swallow PDF bookmarks. But <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37589">Jens Stavnstrup tells us</a> that this doesn't happen if you use iText's PDFStamper.</warning>
+Here is some sample code that uses iText to encrypt a FOP-generated PDF. (Note that FOP now supports <a href="pdfencryption.html">PDF encryption</a> . However the principles for using iText for other PDF features are similar.)
+public static void main(String args[]) {
+  try {
+    ByteArrayOutputStream fopout = new ByteArrayOutputStream();
+    FileOutputStream outfile = new FileOutputStream(args[2]);
+    FopFactory fopFactory = FopFactory.newInstance();
+    Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, fopout);</p>
+<div class="codehilite"><pre><span class="n">Transformer</span> <span class="n">transformer</span> <span class="o">=</span> <span class="n">TransformerFactory</span><span class="o">.</span><span class="n">newInstance</span><span class="p">()</span><span class="o">.</span><span class="n">newTransformer</span><span class="p">(</span>
+    <span class="k">new</span> <span class="n">StreamSource</span><span class="p">(</span><span class="k">new</span> <span class="n">File</span><span class="p">(</span><span class="n">args</span><span class="p">[</span><span class="mi">1</span><span class="p">])));</span>
+<span class="n">transformer</span><span class="o">.</span><span class="n">transform</span><span class="p">(</span><span class="k">new</span> <span class="n">StreamSource</span><span class="p">(</span><span class="k">new</span> <span class="n">File</span><span class="p">(</span><span class="n">args</span><span class="p">[</span><span class="mi">0</span><span class="p">])),</span>
+    <span class="k">new</span> <span class="n">SAXResult</span><span class="p">(</span><span class="n">fop</span><span class="o">.</span><span class="n">getDefaultHandler</span><span class="p">()));</span>
+<span class="n">PdfReader</span> <span class="n">reader</span> <span class="o">=</span> <span class="k">new</span> <span class="n">PdfReader</span><span class="p">(</span><span class="n">fopout</span><span class="o">.</span><span class="n">toByteArray</span><span class="p">());</span>
+<span class="nb">int</span> <span class="n">n</span> <span class="o">=</span> <span class="n">reader</span><span class="o">.</span><span class="n">getNumberOfPages</span><span class="p">();</span>
+<span class="n">Document</span> <span class="n">document</span> <span class="o">=</span> <span class="k">new</span> <span class="n">Document</span><span class="p">(</span><span class="n">reader</span><span class="o">.</span><span class="n">getPageSizeWithRotation</span><span class="p">(</span><span class="mi">1</span><span class="p">));</span>
+<span class="n">PdfWriter</span> <span class="n">writer</span> <span class="o">=</span> <span class="n">PdfWriter</span><span class="o">.</span><span class="n">getInstance</span><span class="p">(</span><span class="n">document</span><span class="p">,</span> <span class="n">outfile</span><span class="p">);</span>
+<span class="n">writer</span><span class="o">.</span><span class="n">setEncryption</span><span class="p">(</span><span class="n">PdfWriter</span><span class="o">.</span><span class="n">STRENGTH40BITS</span><span class="p">,</span> <span class="s">&quot;pdf&quot;</span><span class="p">,</span> <span class="n">null</span><span class="p">,</span>
+  <span class="n">PdfWriter</span><span class="o">.</span><span class="n">AllowCopy</span><span class="p">);</span>
+<span class="n">document</span><span class="o">.</span><span class="nb">open</span><span class="p">();</span>
+<span class="n">PdfContentByte</span> <span class="n">cb</span> <span class="o">=</span> <span class="n">writer</span><span class="o">.</span><span class="n">getDirectContent</span><span class="p">();</span>
+<span class="n">PdfImportedPage</span> <span class="n">page</span><span class="p">;</span>
+<span class="nb">int</span> <span class="n">rotation</span><span class="p">;</span>
+<span class="nb">int</span> <span class="n">i</span> <span class="o">=</span> <span class="mi">0</span><span class="p">;</span>
+<span class="k">while</span> <span class="p">(</span><span class="n">i</span> <span class="o">&lt;</span> <span class="n">n</span><span class="p">)</span> <span class="p">{</span>
+  <span class="n">i</span><span class="o">++</span><span class="p">;</span>
+  <span class="n">document</span><span class="o">.</span><span class="n">setPageSize</span><span class="p">(</span><span class="n">reader</span><span class="o">.</span><span class="n">getPageSizeWithRotation</span><span class="p">(</span><span class="n">i</span><span class="p">));</span>
+  <span class="n">document</span><span class="o">.</span><span class="n">newPage</span><span class="p">();</span>
+  <span class="n">page</span> <span class="o">=</span> <span class="n">writer</span><span class="o">.</span><span class="n">getImportedPage</span><span class="p">(</span><span class="n">reader</span><span class="p">,</span> <span class="n">i</span><span class="p">);</span>
+  <span class="n">rotation</span> <span class="o">=</span> <span class="n">reader</span><span class="o">.</span><span class="n">getPageRotation</span><span class="p">(</span><span class="n">i</span><span class="p">);</span>
+  <span class="k">if</span> <span class="p">(</span><span class="n">rotation</span> <span class="o">==</span> <span class="mi">90</span> <span class="o">||</span> <span class="n">rotation</span> <span class="o">==</span> <span class="mi">270</span><span class="p">)</span> <span class="p">{</span>
+    <span class="n">cb</span><span class="o">.</span><span class="n">addTemplate</span><span class="p">(</span><span class="n">page</span><span class="p">,</span> <span class="mi">0</span><span class="p">,</span> <span class="o">-</span><span class="mi">1</span><span class="n">f</span><span class="p">,</span> <span class="mi">1</span><span class="n">f</span><span class="p">,</span> <span class="mi">0</span><span class="p">,</span> <span class="mi">0</span><span class="p">,</span>
+    <span class="n">reader</span><span class="o">.</span><span class="n">getPageSizeWithRotation</span><span class="p">(</span><span class="n">i</span><span class="p">)</span><span class="o">.</span><span class="n">height</span><span class="p">());</span>
+  <span class="p">}</span> <span class="k">else</span> <span class="p">{</span>
+    <span class="n">cb</span><span class="o">.</span><span class="n">addTemplate</span><span class="p">(</span><span class="n">page</span><span class="p">,</span> <span class="mi">1</span><span class="n">f</span><span class="p">,</span> <span class="mi">0</span><span class="p">,</span> <span class="mi">0</span><span class="p">,</span> <span class="mi">1</span><span class="n">f</span><span class="p">,</span> <span class="mi">0</span><span class="p">,</span> <span class="mi">0</span><span class="p">);</span>
+  <span class="p">}</span>
+  <span class="n">System</span><span class="o">.</span><span class="n">out</span><span class="o">.</span><span class="n">println</span><span class="p">(</span><span class="s">&quot;Processed page &quot;</span> <span class="o">+</span> <span class="n">i</span><span class="p">);</span>
+<span class="p">}</span>
+<span class="n">document</span><span class="o">.</span><span class="nb">close</span><span class="p">();</span>
+</pre></div>
+
+
+<p>} catch( Exception e) {
+    e.printStackTrace();
+  }
+}
+Check the iText tutorial and documentation for setting access flags, password, encryption strength and other parameters.</p>
+<h2 id="pdf-watermark">Watermarks</h2>
+<p>In addition to the <a href="#pdf-postprocess">PDF Post-processing</a> options, consider the following workarounds:</p>
+<ul>
+<li>
+<p>Use a background image for the body region.</p>
+</li>
+<li>
+<p>(submitted by Trevor Campbell) Place an image in a region that overlaps the flowing text. For example, make region-before large enough to contain your image. Then include a block (if necessary, use an absolutely positioned block-container) containing the watermark image in the static-content for the region-before. Note that the image will be drawn on top of the normal content.</p>
+</li>
+</ul>
+<h1 id="ps">PostScript</h1>
+<p>The PostScript renderer has been brought up to a similar quality as the PDF renderer, but may still be missing certain features. It provides good support for most text and layout. Images and SVG are not fully supported, yet. Currently, the PostScript renderer generates PostScript Level 3 with most DSC comments. Actually, the only Level 3 features used are the FlateDecode and DCTDecode filter (the latter is used for 1:1 embedding of JPEG images), everything else is Level 2.</p>
+<h2 id="ps-configuration">Configuration</h2>
+<p>The PostScript renderer configuration currently allows the following settings:
+<renderer mime="application/postscript">
+  <auto-rotate-landscape>false</auto-rotate-landscape>
+  <language-level>3</language-level>
+  <optimize-resources>false</optimize-resources>
+  <safe-set-page-device>false</safe-set-page-device>
+  <dsc-compliant>true</dsc-compliant>
+</renderer>
+The default value for the "auto-rotate-landscape" setting is "false". Setting it to "true" will automatically rotate landscape pages and will mark them as landscape.</p>
+<p>The default value for the "language-level" setting is "3". This setting specifies the PostScript language level which should be used by FOP. Set this to "2" only if you don't have a Level 3 capable interpreter.</p>
+<p>The default value for the "optimize-resources" setting is "false". Setting it to "true" will produce the PostScript file in two steps. A temporary file will be written first which will then be processed to add only the fonts which were really used and images are added to the stream only once as PostScript forms. This will reduce file size but can potentially increase the memory needed in the interpreter to process.</p>
+<p>The default value for the "safe-set-page-device" setting is "false". Setting it to "true" will cause the renderer to invoke a postscript macro which guards against the possibility of invalid/unsupported postscript key/values being issued to the implementing postscript page device.</p>
+<p>The default value for the "dsc-compliant" setting is "true". Setting it to "false" will break DSC compliance by minimizing the number of setpagedevice calls in the postscript document output. This feature may be useful when unwanted blank pages are experienced in your postscript output. This problem is caused by the particular postscript implementation issuing unwanted postscript subsystem initgraphics/erasepage calls on each setpagedevice call.</p>
+<h2 id="ps-limitations">Limitations</h2>
+<ul>
+<li>
+<p>Images and SVG may not be displayed correctly. SVG support is far from being complete. No image transparency is available.</p>
+</li>
+<li>
+<p>Only Type 1 fonts are supported.</p>
+</li>
+<li>
+<p>Multibyte characters are not supported.</p>
+</li>
+<li>
+<p>PPD support is still missing.</p>
+</li>
+</ul>
+<h1 id="pcl">PCL</h1>
+<p>This format is for the Hewlett-Packard PCL printers and other printers supporting PCL. It should produce output as close to identical as possible to the printed output of the PDFRenderer within the limitations of the renderer, and output device.</p>
+<p>The output created by the PCLRenderer is generic PCL 5, HP GL/2 and PJL. This should allow any device fully supporting PCL 5 to be able to print the output generated by the PCLRenderer. PJL is used to control the print job and switch to the PCL language. PCL 5 is used for text, raster graphics and rectangular fill graphics. HP GL/2 is used for more complex painting operations. Certain painting operations are done off-screen and rendered to PCL as bitmaps because of limitations in PCL 5.</p>
+<h2 id="pcl-references">References</h2>
+<ul>
+<li>
+<p><a href="http://en.wikipedia.org/wiki/Printer_Control_Language">WikiPedia entry on PCL</a> </p>
+</li>
+<li>
+<p><a href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=bpl04568">Technical reference documents on PCL from Hewlett-Packard</a> </p>
+</li>
+</ul>
+<h2 id="pcl-limitations">Limitations</h2>
+<ul>
+<li>
+<p>Text or graphics outside the left or top of the printable area are not rendered properly. This is a limitation of PCL, not FOP. In general, things that should print to the left of the printable area are shifted to the right so that they start at the left edge of the printable area.</p>
+</li>
+<li>
+<p>The Helvetica and Times fonts are not well supported among PCL printers so Helvetica is mapped to Arial and Times is mapped to Times New. This is done in the PCLRenderer, no changes are required in the FO's. The metrics and appearance for Helvetica/Arial and Times/Times New are nearly identical, so this has not been a problem so far.</p>
+</li>
+<li>
+<p>For the non-symbol fonts, the ISO 8859-1 symbol set is used (PCL set "0N").</p>
+</li>
+<li>
+<p>All fonts available to the Java2D subsystem are usable. The texts are painted as bitmap much like the Windows PCL drivers do.</p>
+</li>
+<li>
+<p>Multibyte characters are not supported.</p>
+</li>
+<li>
+<p>At the moment, only monochrome output is supported. PCL5c color extensions will only be implemented on demand. Color and grayscale images are converted to monochrome bitmaps (1-bit). Dithering only occurs if the JAI image library is available.</p>
+</li>
+<li>
+<p>Images are scaled up to the next resolution level supported by PCL (75, 100, 150, 200, 300, 600 dpi). For color and grayscale images an even higher PCL resolution is selected to give the dithering algorithm a chance to improve the bitmap quality.</p>
+</li>
+<li>
+<p>Currently, there's no support for clipping and image transparency, largely because PCL 5 has certain limitations.</p>
+</li>
+</ul>
+<h2 id="pcl-configuration">Configuration</h2>
+<p>The PCL renderer configuration currently allows the following settings:
+<renderer mime="application/vnd.hp-PCL">
+  <rendering>quality</rendering>
+  <text-rendering>bitmap</text-rendering>
+  <disable-pjl>false</disable-pjl>
+</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>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>
+<p>The default value for the "disable-pjl" setting is "false". This means that the PCL renderer usually generates PJL commands before and after the document in order to switch a printer into PCL language. PJL commands can be disabled if you set this value to "true".</p>
+<p>You can control the output resolution for the PCL using the "target resolution" setting on the FOUserAgent. The actual value will be rounded up to the next supported PCL resolution. Currently, only 300 and 600 dpi are supported which should be enough for most use cases. Note that this setting directly affects the size of the output file and the print quality.</p>
+<h2 id="pcl-extensions">Extensions</h2>
+<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 be declared in the fo:root element like this:</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:pcl</span><span class="o">=</span><span class="s">&quot;http://xmlgraphics.apache.org/fop/extensions/pcl&quot;</span><span class="o">&gt;</span>
+</pre></div>
+
+
+<h3 id="pcl-page-source">Page Source (Tray selection)</h3>
+<p>The page-source extension attribute on fo:simple-page-master allows to select the paper tray the sheet for a particular simple-page-master is to be taken from. Example:</p>
+<div class="codehilite"><pre>  <span class="nt">&lt;fo:layout-master-set&gt;</span>
+    <span class="nt">&lt;fo:simple-page-master</span> <span class="na">master-name=</span><span class="s">&quot;simple&quot;</span> <span class="na">pcl:paper-source=</span><span class="s">&quot;2&quot;</span><span class="nt">&gt;</span>
+      ...
+    <span class="nt">&lt;/fo:simple-page-master&gt;</span>
+  <span class="nt">&lt;/fo:layout-master-set&gt;</span>
+</pre></div>
+
+
+<p>Note: the tray number is a positive integer and the value depends on the target printer. Not all PCL printers support the same paper trays. Usually, "1" is the default tray, "2" is the manual paper feed, "3" is the manual envelope feed, "4" is the "lower" tray and "7" is "auto-select". Consult the technical reference for your printer for all available values.</p>
+<h1 id="afp">AFP</h1>
+<p><warning>The AFP Renderer is a new addition (27-Apr-2006) to the sandbox and as such not yet fully tested or feature complete.</warning>
+The FOP AFP Renderer deals with creating documents conforming to the IBM AFP document architecture also refered to as MO:DCA (Mixed Object Document Content Architecture).</p>
+<h2 id="afp-references">References</h2>
+<ul>
+<li>
+<p><a href="http://en.wikipedia.org/wiki/Advanced_Function_Presentation">AFP (Advanced Function Presentation)</a> </p>
+</li>
+<li>
+<p><a href="http://wiki.apache.org/xmlgraphics-fop/AFPResources">AFP Resources on the FOP WIKI</a> </p>
+</li>
+</ul>
+<h2 id="afp-limitations">Limitations</h2>
+<p>This list is most likely badly incomplete.</p>
+<ul>
+<li>
+<p>Clipping of text and graphics is not supported.</p>
+</li>
+<li>
+<p>Only IBM outline and raster fonts and to a limited extend the original fonts built into FOP are supported. Support for TrueType fonts may be added later.</p>
+</li>
+</ul>
+<h2 id="afp-configuration">Configuration</h2>
+<h3 id="afp-font-config">Fonts</h3>
+<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 for the AFP Renderer is application/x-afp which means the AFP Renderer section in the FOP configuration file looks like:
+<renderer mime="application/x-afp">
+  <!-- AFP Renderer -->
+  ...
+</renderer>
+There are 3 font configuration variants supported:</p>
+<ol>
+<li>
+<p>IBM Raster fonts</p>
+</li>
+<li>
+<p>IBM Outline fonts</p>
+</li>
+<li>
+<p>FOP built-in Base14 fonts</p>
+</li>
+</ol>
+<p>A typical raster font configuration looks like:
+      <!-- This is an example of mapping actual IBM raster fonts / code pages to a FOP font -->
+        <font>
+        <!-- The afp-font element defines the IBM code page, the matching Java encoding and the
+             path to the font -->
+        <afp-font type="raster" codepage="T1V10500" encoding="Cp500" path="fonts/ibm">
+          <!-- For a raster font a separate element for each font size is required providing
+               the font size and the corresponding IBM Character set name -->
+          <afp-raster-font size="7" characterset="C0N20070"/>
+          <afp-raster-font size="8" characterset="C0N20080"/>
+          <afp-raster-font size="10" characterset="C0N20000"/>
+          <afp-raster-font size="11" characterset="C0N200A0"/>
+          <afp-raster-font size="12" characterset="C0N200B0"/>
+          <afp-raster-font size="14" characterset="C0N200D0"/>
+          <afp-raster-font size="16" characterset="C0N200F0"/>
+          <afp-raster-font size="18" characterset="C0N200H0"/>
+          <afp-raster-font size="20" characterset="C0N200J0"/>
+          <afp-raster-font size="24" characterset="C0N200N0"/>
+          <afp-raster-font size="30" characterset="C0N200T0"/>
+          <afp-raster-font size="36" characterset="C0N200Z0"/>
+        </afp-font>
+        <!-- These are the usual FOP font triplets as they apply to this font -->
+        <font-triplet name="serif" style="normal" weight="normal"/>
+        <font-triplet name="Times" style="normal" weight="normal"/>
+        <font-triplet name="Times-Roman" style="normal" weight="normal"/>
+        <font-triplet name="TimesNewRoman" style="normal" weight="normal"/>
+      </font>
+An outline font configuration is simpler as the individual font size entries are not required. However, the characterset definition is now required within the afp-font element.
+      <font>
+          <afp-font type="outline" codepage="T1V10500" encoding="Cp500" characterset="CZH200  "
+             path="fonts/ibm" />
+          <font-triplet name="sans-serif" style="normal" weight="normal"/>
+          <font-triplet name="Helvetica" style="normal" weight="normal"/>
+          <font-triplet name="any" style="normal" weight="normal"/>
+      </font></p>
+<p>Experimentation has shown that the font metrics for the FOP built-in Base14 fonts are actually very similar to some of the IBM outline and raster fonts. In cases were the IBM font files are not available the path attribute in the afp-font element can be replaced by a base14-font attribute giving the name of the matching Base14 font. In this case the AFP Renderer will take the font metrics from the built-in font.
+      <!-- The following are examples of defining outline fonts based on FOP built-in
+           font metrics for the Adobe Base14 fonts -->
+      <!-- sans-serif fonts based on Helvetica -->
+      <font>
+          <afp-font type="outline" codepage="T1V10500" encoding="Cp500" characterset="CZH200  "
+            base14-font="Helvetica" />
+          <font-triplet name="sans-serif" style="normal" weight="normal"/>
+          <font-triplet name="Helvetica" style="normal" weight="normal"/>
+          <font-triplet name="any" style="normal" weight="normal"/>
+      </font>
+      <font>
+          <afp-font type="outline" codepage="T1V10500" encoding="Cp500" characterset="CZH300  "
+            base14-font="HelveticaOblique" />
+          <font-triplet name="sans-serif" style="italic" weight="normal"/>
+          <font-triplet name="Helvetica" style="italic" weight="normal"/>
+          <font-triplet name="any" style="italic" weight="normal"/>
+      </font>
+      <font>
+          <afp-font type="outline" codepage="T1V10500" encoding="Cp500" characterset="CZH400  "
+            base14-font="HelveticaBold" />
+          <font-triplet name="sans-serif" style="normal" weight="bold"/>
+          <font-triplet name="Helvetica" style="normal" weight="bold"/>
+          <font-triplet name="any" style="normal" weight="bold"/>
+      </font>
+      <font>
+          <afp-font type="outline" codepage="T1V10500" encoding="Cp500" characterset="CZH500  "
+            base14-font="HelveticaBoldOblique" />
+          <font-triplet name="sans-serif" style="italic" weight="bold"/>
+          <font-triplet name="Helvetica" style="italic" weight="bold"/>
+          <font-triplet name="any" style="italic" weight="bold"/>
+      </font></p>
+<div class="codehilite"><pre>  <span class="c">&lt;!-- serif fonts based on Times Roman --&gt;</span>
+  <span class="nt">&lt;font&gt;</span>
+      <span class="nt">&lt;afp-font</span> <span class="na">type=</span><span class="s">&quot;outline&quot;</span> <span class="na">codepage=</span><span class="s">&quot;T1V10500&quot;</span> <span class="na">encoding=</span><span class="s">&quot;Cp500&quot;</span> <span class="na">characterset=</span><span class="s">&quot;CZN200  &quot;</span>
+        <span class="na">base14-font=</span><span class="s">&quot;TimesRoman&quot;</span> <span class="nt">/&gt;</span>
+      <span class="nt">&lt;font-triplet</span> <span class="na">name=</span><span class="s">&quot;serif&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;Times&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;Times-Roman&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;!-- The following are examples of defining raster fonts based on FOP built-in</span>
+<span class="c">       font metrics for the Adobe Base14 fonts --&gt;</span>
+  <span class="c">&lt;!-- monospaced fonts based on Courier --&gt;</span>
+  <span class="nt">&lt;font&gt;</span>
+    <span class="nt">&lt;afp-font</span> <span class="na">type=</span><span class="s">&quot;raster&quot;</span> <span class="na">codepage=</span><span class="s">&quot;T1V10500&quot;</span> <span class="na">encoding=</span><span class="s">&quot;Cp500&quot;</span><span class="nt">&gt;</span>
+      <span class="nt">&lt;afp-raster-font</span> <span class="na">size=</span><span class="s">&quot;7&quot;</span> <span class="na">characterset=</span><span class="s">&quot;C0420070&quot;</span> <span class="na">base14-font=</span><span class="s">&quot;Courier&quot;</span><span class="nt">/&gt;</span>
+      <span class="nt">&lt;afp-raster-font</span> <span class="na">size=</span><span class="s">&quot;8&quot;</span> <span class="na">characterset=</span><span class="s">&quot;C0420080&quot;</span> <span class="na">base14-font=</span><span class="s">&quot;Courier&quot;</span><span class="nt">/&gt;</span>
+      <span class="nt">&lt;afp-raster-font</span> <span class="na">size=</span><span class="s">&quot;10&quot;</span> <span class="na">characterset=</span><span class="s">&quot;C0420000&quot;</span> <span class="na">base14-font=</span><span class="s">&quot;Courier&quot;</span><span class="nt">/&gt;</span>
+      <span class="nt">&lt;afp-raster-font</span> <span class="na">size=</span><span class="s">&quot;12&quot;</span> <span class="na">characterset=</span><span class="s">&quot;C04200B0&quot;</span> <span class="na">base14-font=</span><span class="s">&quot;Courier&quot;</span><span class="nt">/&gt;</span>
+      <span class="nt">&lt;afp-raster-font</span> <span class="na">size=</span><span class="s">&quot;14&quot;</span> <span class="na">characterset=</span><span class="s">&quot;C04200D0&quot;</span> <span class="na">base14-font=</span><span class="s">&quot;Courier&quot;</span><span class="nt">/&gt;</span>
+      <span class="nt">&lt;afp-raster-font</span> <span class="na">size=</span><span class="s">&quot;20&quot;</span> <span class="na">characterset=</span><span class="s">&quot;C04200J0&quot;</span> <span class="na">base14-font=</span><span class="s">&quot;Courier&quot;</span><span class="nt">/&gt;</span>
+    <span class="nt">&lt;/afp-font&gt;</span>
+    <span class="nt">&lt;font-triplet</span> <span class="na">name=</span><span class="s">&quot;monospace&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;Courier&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&gt;</span>
+    <span class="nt">&lt;afp-font</span> <span class="na">type=</span><span class="s">&quot;raster&quot;</span> <span class="na">codepage=</span><span class="s">&quot;T1V10500&quot;</span> <span class="na">encoding=</span><span class="s">&quot;Cp500&quot;</span><span class="nt">&gt;</span>
+      <span class="nt">&lt;afp-raster-font</span> <span class="na">size=</span><span class="s">&quot;7&quot;</span> <span class="na">characterset=</span><span class="s">&quot;C0440070&quot;</span> <span class="na">base14-font=</span><span class="s">&quot;CourierBold&quot;</span><span class="nt">/&gt;</span>
+      <span class="nt">&lt;afp-raster-font</span> <span class="na">size=</span><span class="s">&quot;8&quot;</span> <span class="na">characterset=</span><span class="s">&quot;C0440080&quot;</span> <span class="na">base14-font=</span><span class="s">&quot;CourierBold&quot;</span><span class="nt">/&gt;</span>
+      <span class="nt">&lt;afp-raster-font</span> <span class="na">size=</span><span class="s">&quot;10&quot;</span> <span class="na">characterset=</span><span class="s">&quot;C0440000&quot;</span> <span class="na">base14-font=</span><span class="s">&quot;CourierBold&quot;</span><span class="nt">/&gt;</span>
+      <span class="nt">&lt;afp-raster-font</span> <span class="na">size=</span><span class="s">&quot;12&quot;</span> <span class="na">characterset=</span><span class="s">&quot;C04400B0&quot;</span> <span class="na">base14-font=</span><span class="s">&quot;CourierBold&quot;</span><span class="nt">/&gt;</span>
+      <span class="nt">&lt;afp-raster-font</span> <span class="na">size=</span><span class="s">&quot;14&quot;</span> <span class="na">characterset=</span><span class="s">&quot;C04400D0&quot;</span> <span class="na">base14-font=</span><span class="s">&quot;CourierBold&quot;</span><span class="nt">/&gt;</span>
+      <span class="nt">&lt;afp-raster-font</span> <span class="na">size=</span><span class="s">&quot;20&quot;</span> <span class="na">characterset=</span><span class="s">&quot;C04400J0&quot;</span> <span class="na">base14-font=</span><span class="s">&quot;CourierBold&quot;</span><span class="nt">/&gt;</span>
+    <span class="nt">&lt;/afp-font&gt;</span>
+    <span class="nt">&lt;font-triplet</span> <span class="na">name=</span><span class="s">&quot;monospace&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;Courier&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>
+</pre></div>
+
+
+<h3 id="afp-renderer-resolution-config">Output Resolution</h3>
+<p>By default the AFP Renderer creates output with a resolution of 240 dpi. This can be overridden by the <renderer-resolution/> configuration element. Example:</p>
+<div class="codehilite"><pre>  <span class="nt">&lt;renderer-resolution&gt;</span>240<span class="nt">&lt;/renderer-resolution&gt;</span>
+</pre></div>
+
+
+<h3 id="afp-image-config">Images</h3>
+<p>By default the AFP Renderer converts all images to 8 bit grey level. This can be overridden by the <images> configuration element. Example:</p>
+<div class="codehilite"><pre>  <span class="o">&lt;</span><span class="n">images</span> <span class="n">mode</span><span class="o">=</span><span class="s">&quot;color&quot;</span> <span class="o">/&gt;</span>
+</pre></div>
+
+
+<p>This will put images as RGB images into the AFP output stream. The default setting is:</p>
+<div class="codehilite"><pre>  <span class="o">&lt;</span><span class="n">images</span> <span class="n">mode</span><span class="o">=</span><span class="s">&quot;b+w&quot;</span> <span class="n">bits</span><span class="o">-</span><span class="n">per</span><span class="o">-</span><span class="n">pixel</span><span class="o">=</span><span class="s">&quot;8&quot;</span> <span class="o">/&gt;</span>
+</pre></div>
+
+
+<p>Only the values "color" and "b+w" are allowed for the mode attribute. The bits-per-pixel attribute is ignored if mode is "color". For "b+w" mode is must be 1, 4, or 8.</p>
+<h2 id="afp-extensions">Extensions</h2>
+<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>
+<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:afp</span><span class="o">=</span><span class="s">&quot;http://xmlgraphics.apache.org/fop/extensions/afp&quot;</span><span class="o">&gt;</span>
+</pre></div>
+
+
+<h3 id="afp-page-overlay">Page Overlay Extension</h3>
+<p>The include-page-overlay extension element allows to define on a per simple-page-master basis a page overlay resource. Example:</p>
+<div class="codehilite"><pre>  <span class="nt">&lt;fo:layout-master-set&gt;</span>
+    <span class="nt">&lt;fo:simple-page-master</span> <span class="na">master-name=</span><span class="s">&quot;simple&quot;</span><span class="nt">&gt;</span>
+      <span class="nt">&lt;afp:include-page-overlay</span> <span class="na">name=</span><span class="s">&quot;O1SAMP1 &quot;</span> <span class="nt">/&gt;</span>
+      ...
+    <span class="nt">&lt;/fo:simple-page-master&gt;</span>
+  <span class="nt">&lt;/fo:layout-master-set&gt;</span>
+</pre></div>
+
+
+<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>
+<h3 id="afp-page-segment">Page Segment Extension</h3>
+<p>The include-page-segment extension element allows to define resource substitution for fo:external-graphics elements. Example:</p>
+<div class="codehilite"><pre><span class="nt">&lt;fo:root</span> <span class="na">xmlns:fo=</span><span class="s">&quot;http://www.w3.org/1999/XSL/Format&quot;</span>
+ <span class="na">xmlns:afp=</span><span class="s">&quot;http://xmlgraphics.apache.org/fop/extensions/afp&quot;</span><span class="nt">&gt;</span>
+  <span class="nt">&lt;fo:layout-master-set&gt;</span>
+    <span class="nt">&lt;fo:simple-page-master</span> <span class="na">master-name=</span><span class="s">&quot;simple&quot;</span><span class="nt">&gt;</span>
+      <span class="nt">&lt;afp:include-page-segment</span> <span class="na">name=</span><span class="s">&quot;S1ISLOGO&quot;</span> <span class="na">src=</span><span class="s">&quot;../../resources/images/bgimg300dpi.jpg&quot;</span> <span class="nt">/&gt;</span>
+      <span class="nt">&lt;fo:region-body/&gt;</span>
+    <span class="nt">&lt;/fo:simple-page-master&gt;</span>
+  <span class="nt">&lt;/fo:layout-master-set&gt;</span>
+</pre></div>
+
+
+<p>The include-page-segment extension element can only occur within a simple-page-master. Multiple include-page-segment extension elements within a simple-page-master are allowed. The mandatory name attribute must refer to an 8 character (space padded) resource name that must be known in the AFP processing environment. The value of the mandatory src attribute is compared against the value of the src attribute in 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>
+<h3 id="afp-tag-logical-element">Tag Logical Element Extension</h3>
+<p>The tag-logical-element extension element allows to injects TLEs into the AFP output stream. Example:</p>
+<div class="codehilite"><pre><span class="nt">&lt;fo:root</span> <span class="na">xmlns:fo=</span><span class="s">&quot;http://www.w3.org/1999/XSL/Format&quot;</span>
+ <span class="na">xmlns:afp=</span><span class="s">&quot;http://xmlgraphics.apache.org/fop/extensions/afp&quot;</span><span class="nt">&gt;</span>
+  <span class="nt">&lt;fo:layout-master-set&gt;</span>
+    <span class="nt">&lt;fo:simple-page-master</span> <span class="na">master-name=</span><span class="s">&quot;simple&quot;</span><span class="nt">&gt;</span>
+      <span class="nt">&lt;afp:tag-logical-element</span> <span class="na">name=</span><span class="s">&quot;The TLE Name&quot;</span> <span class="na">value=</span><span class="s">&quot;The TLE Value&quot;</span> <span class="nt">/&gt;</span>
+      <span class="nt">&lt;fo:region-body/&gt;</span>
+    <span class="nt">&lt;/fo:simple-page-master&gt;</span>
+  <span class="nt">&lt;/fo:layout-master-set&gt;</span>
+</pre></div>
+
+
+<p>The tag-logical-element extension element can only occur within a simple-page-master. Multiple tag-logical-element extension elements within a simple-page-master are allowed. The name and value attributes are mandatory.</p>
+<h3 id="afp-no-operation">No Operation Extension</h3>
+<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>
+<div class="codehilite"><pre><span class="nt">&lt;fo:root</span> <span class="na">xmlns:fo=</span><span class="s">&quot;http://www.w3.org/1999/XSL/Format&quot;</span>
+ <span class="na">xmlns:afp=</span><span class="s">&quot;http://xmlgraphics.apache.org/fop/extensions/afp&quot;</span><span class="nt">&gt;</span>
+  <span class="nt">&lt;fo:layout-master-set&gt;</span>
+    <span class="nt">&lt;fo:simple-page-master</span> <span class="na">master-name=</span><span class="s">&quot;simple&quot;</span><span class="nt">&gt;</span>
+      <span class="nt">&lt;afp:no-operation</span> <span class="na">name=</span><span class="s">&quot;My NOP&quot;</span><span class="nt">&gt;</span>insert up to 32k of character data here!<span class="nt">&lt;/afp:no-operation&gt;</span>
+    <span class="nt">&lt;/fo:simple-page-master&gt;</span>
+  <span class="nt">&lt;/fo:layout-master-set&gt;</span>
+</pre></div>
+
+
+<p>The no-operation extension element can only occur within a simple-page-master. Multiple no-operation extension elements within a simple-page-master are allowed. The name attribute is mandatory.</p>
+<h1 id="rtf">RTF</h1>
+<p>JFOR, an open source XSL-FO to RTF converter has been integrated into Apache FOP. This will create an RTF (rich text format) document that will attempt to contain as much information from the XSL-FO document as possible. It should be noted that is not possible (due to RTF's limitations) to map all XSL-FO features to RTF. For complex documents, the RTF output will never reach the feature level from PDF, for example. Thus, using RTF output is only recommended for simple documents such as letters.</p>
+<p>The RTF output follows Microsoft's RTF specifications and produces best results on Microsoft Word.
+RTF output is currently unmaintained and lacks many features compared to other output formats. Using other editable formats like Open Document Format, instead of producing XSL-FO then RTF through FOP, might give better results.
+These are some known restrictions compared to other supported output formats (not a complete list):</p>
+<ul>
+<li>
+<p>Not supported/implemented:</p>
+<ul>
+<li>
+<p>break-before/after (supported by the RTF library but not tied into the RTFHandler)</p>
+</li>
+<li>
+<p>fo:page-number-citation-last</p>
+</li>
+<li>
+<p>keeps (supported by the RTF library but not tied into the RTFHandler)</p>
+</li>
+<li>
+<p>region-start/end (RTF limitation)</p>
+</li>
+<li>
+<p>multiple columns</p>
+</li>
+</ul>
+</li>
+<li>
+<p>Only a single page-master is supported</p>
+</li>
+<li>
+<p>Not all variations of fo:leader are supported (RTF limitation)</p>
+</li>
+<li>
+<p>percentages are not supported everywhere</p>
+</li>
+</ul>
+<h1 id="xml">XML (Area Tree XML)</h1>
+<p>This is primarily for testing and verification. The XML created is simply a representation of the internal area tree put into XML. We use that to verify the functionality of FOP's layout engine.</p>
+<p>The other use case of the Area Tree XML is as FOP's "intermediate format". More information on that can be found on the page dedicated to the <a href="intermediate.html">Intermediate Format</a> .</p>
+<h1 id="awt">Java2D/AWT</h1>
+<p>The Java2DRenderer provides the basic functionality for all Java2D-based output formats (AWT viewer, direct print, PNG, TIFF).</p>
+<p>The AWT viewer shows a window with the pages displayed inside a Java graphic. It displays one page at a time. The fonts used for the formatting and viewing depend on the fonts available to your JRE.</p>
+<h1 id="print">Print</h1>
+<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>
+<h2 id="print-issues">Known issues</h2>
+<p>If you run into the problem that the printed output is incomplete on Windows: this often happens to users printing to a PCL printer. There seems to be an incompatibility between Java and certain PCL printer drivers on Windows. Since most network-enabled laser printers support PostScript, try switching to the PostScript printer driver for that printer model.</p>
+<h1 id="bitmap">Bitmap (TIFF/PNG)</h1>
+<p>It is possible to directly create bitmap images from the individual pages generated by the layout engine. This is done with the same code that renders to the Java2D/AWT renderer.</p>
+<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.</p>
+<h2 id="bitmap-configuration">Configuration</h2>
+<p>The TIFF and PNG renderer configuration currently allows the following settings:
+<renderer mime="image/png">
+  <transparent-page-background>true</transparent-page-background>
+  <fonts><!-- described elsewhere --></fonts>
+</renderer>
+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, no such background will be painted and you will get a transparent image if an alpha channel is available in the output format.</p>
+<h2 id="tiff-configuration">TIFF-specific Configuration</h2>
+<p>In addition to the above values the TIFF renderer configuration allows some additional settings:
+<renderer mime="image/tiff">
+  <transparent-page-background>true</transparent-page-background>
+  <compression>CCITT T.6</compression>
+  <fonts><!-- described elsewhere --></fonts>
+</renderer>
+The default value for the "compression" setting is "PackBits" which which is a widely supported RLE compression scheme for TIFF. The set of compression names to be used here matches the set that the Image I/O API uses. Note that not all compression schemes may be available during runtime. This depends on the actual codecs being available. Here is a list of possible values:</p>
+<ul>
+<li>
+<p>NONE (no compression)</p>
+</li>
+<li>
+<p>PackBits (RLE, run-length encoding)</p>
+</li>
+<li>
+<p>JPEG</p>
+</li>
+<li>
+<p>Deflate</p>
+</li>
+<li>
+<p>LZW</p>
+</li>
+<li>
+<p>ZLib</p>
+</li>
+<li>
+<p>CCITT T.4 (Fax Group 3)</p>
+</li>
+<li>
+<p>CCITT T.6 (Fax Group 4)
+If you want to use CCITT compression, please make sure you've got a J2SE 1.4 or later and <a href="http://java.sun.com/products/java-media/jai/current.html">Java Advanced Imaging Image I/O Tools</a> in your classpath. The Sun JRE doesn't come with a TIFF codec built in, so it has to be added separately. The internal TIFF codec from XML Graphics Commons only supports PackBits, Deflate and JPEG compression for writing.</p>
+</li>
+</ul>
+<h1 id="txt">TXT</h1>
+<p>The text renderer produces plain ASCII text output that attempts to match the output of the PDFRenderer as closely as possible. This was originally developed to accommodate an archive system that could only accept plain text files, and is primarily useful for getting a quick-and-dirty view of the document text. The renderer is very limited, so do not be surprised if it gives unsatisfactory results.</p>
+<p>The Text renderer works with a fixed size page buffer. The size of this buffer is controlled with the textCPI and textLPI public variables. The textCPI is the effective horizontal characters per inch to use. The textLPI is the vertical lines per inch to use. From these values and the page width and height the size of the buffer is calculated. The formatting objects to be rendered are then mapped to this grid. Graphic elements (lines, borders, etc) are assigned a lower priority than text, so text will overwrite any graphic element representations.</p>
+<p>Because FOP lays the text onto a grid during layout, there are frequently extra or missing spaces between characters and lines, which is generally unsatisfactory. Users have reported that the optimal settings to avoid such spacing problems are:</p>
+<ul>
+<li>
+<p>font-family="Courier"</p>
+</li>
+<li>
+<p>font-size="7.3pt"</p>
+</li>
+<li>
+<p>line-height="10.5pt"</p>
+</li>
+</ul>
+<h1 id="sandbox">Output Formats in the Sandbox</h1>
+<p>Due to the state of certain renderers we moved some of them to a "sandbox" area until they are ready for more serious use. The renderers and FOEventHandlers in the sandbox 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>
+<h2 id="mif">MIF</h2>
+<p><warning>The MIF handler is in the sandbox and not yet functional in FOP Trunk!!! Please help us ressurrect this feature.</warning>
+This format is the Maker Interchange Format which is used by Adobe Framemaker.</p>
+<h2 id="svg">SVG</h2>
+<p><warning>The SVG renderer is in the sandbox and may not work as expected in FOP Trunk!!! Please help us improve this feature.</warning>
+This format creates an SVG document that has links between the pages. This is primarily for slides and creating svg images of pages. Large documents will create SVG files that are far too large for an SVG viewer to handle. Since FO documents usually have text the SVG document will have a large number of text elements. The font information for the text is obtained from the JVM in the same way as for the AWT viewer. If the SVG is viewed on a system where the fonts are different, such as another platform, then the page may look wrong.</p>
+<h1 id="wishlist">Wish list</h1>
+<p>Apache FOP is easily extensible and allows you to add new output formats to enhance FOP's functionality. There's a number of output formats which are on our wish list. We're looking for volunteers to help us implement them.</p>
+<ul>
+<li><a href="http://en.wikipedia.org/wiki/OpenDocument">ODF (Open Document Format)</a> : The standardized successor to OpenOffice's file format.</li>
+</ul></div></div>
+      <div class="clear"></div>
+
+	  <div id="footer">
+		<a alt="Apache Software Foundation" href="http://www.apache.org">
+		  <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+		</a>
+		<div class="copyright">
+		  <p>
+			Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+			the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+			<br />
+			Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+			trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+			marks mentioned may be trademarks or registered trademarks of their respective owners.
+			<br />
+		  </p>
+		</div> 
+	  </div>
+  </body>
+</html>

Added: websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfa.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfa.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfa.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,136 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP: PDF/A (ISO 19005)</title>
+
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+    <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+    <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+    </style>
+
+    
+
+    
+    
+  </head>
+
+  <body>
+	  <div id="banner">&nbsp;
+	  </div>
+
+	  <div id="navigation">
+	  <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+  <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+  <input type="text" name="q" id="query" /><br />
+  <input type="submit" id="submit" value="Search" />
+</form>
+	  </div>
+	
+	  <div id="bannertext">
+        <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+        <h1>Apache™ FOP: PDF/A (ISO 19005)</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version><authors><person email="jeremias@apache.org" name="Jeremias Märki"></person></authors></p>
+<h1 id="overview">Overview</h1>
+<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 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> . Work on PDF/A-2 is in progress at <a href="http://www.aiim.org/standards.asp?ID=25013">AIIM</a> .</p>
+<p>Design documentation on PDF/A can be found on FOP's Wiki on the <a href="http://wiki.apache.org/xmlgraphics-fop/PDFA1ConformanceNotes">PDFA1ConformanceNotes</a> page.</p>
+<h1 id="status">Implementation Status</h1>
+<p><strong>PDF/A-1b</strong> is implemented to the degree that FOP supports the creation of the elements described in ISO 19005-1.</p>
+<p>Tests have been performed against jHove and Adobe Acrobat 7.0.7 (Preflight function). FOP does not validate completely against Apago's PDF Appraiser. Reasons unknown due to lack of a full license to get a detailed error protocol.</p>
+<p><strong>PDF/A-1a</strong> is not implemented, yet. This is mostly because of the requirement for tagged PDF which is not available in FOP, yet.</p>
+<h1 id="command-line">Usage (command line)</h1>
+<p>To activate PDF/A-1b from the command-line, specify "-pdfprofile PDF/A-1b" as a parameter. If there is a violation of one of the validation rules for PDF/A, an error message is presented and the processing stops.</p>
+<h1 id="embedded">Usage (embedded)</h1>
+<p>When FOP is embedded in another Java application you can set a special option on the renderer options in the user agent to activate the PDF/A-1b profile. Here's an example:</p>
+<p>userAgent.getRendererOptions().put("pdf-a-mode", "PDF/A-1b");
+Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent);
+[..]
+If one of the validation rules of PDF/A is violated, an PDFConformanceException (descendant of RuntimeException) is thrown.</p>
+<h1 id="rules">PDF/A in Action</h1>
+<p>There are a number of things that must be looked after if you activate a PDF/A profile. If you receive a PDFConformanceException, have a look at the following list (not necessarily comprehensive):</p>
+<ul>
+<li>
+<p>Make sure all (!) fonts are embedded. If you use base 14 fonts (like Helvetica) you need to obtain a license for them and embed them like any other font.</p>
+</li>
+<li>
+<p>Don't use PDF encryption. PDF/A doesn't allow it.</p>
+</li>
+<li>
+<p>Don't use CMYK images without an ICC color profile. PDF/A doesn't allow mixing color spaces and FOP currently only properly supports the sRGB color space. Please note that FOP embeds a standard sRGB ICC profile (sRGB IEC61966-2.1) as the primary output intent for the PDF if no other output intent has been specified in the configuration.</p>
+</li>
+<li>
+<p>Don't use non-RGB colors in SVG images. Same issue as with CMYK images.</p>
+</li>
+<li>
+<p>Don't use EPS graphics with fo:external-graphic. Embedding EPS graphics in PDF is deprecated since PDF 1.4 and prohibited by PDF/A.</p>
+</li>
+<li>
+<p>PDF is forced to version 1.4 if PDF/A-1 is activated.</p>
+</li>
+<li>
+<p>No filter must be specified explicitely for metadata objects. Metadata must be embedded in clear text so non-PDF-aware applications can extract the XMP metadata.</p>
+</li>
+</ul>
+<h1 id="profile-compatibility">PDF profile compatibility</h1>
+<p>The PDF profiles "PDF/X-3:2003" and "PDF/A-1b" are compatible and can both be activated at the same time.</p>
+<h1 id="interoperability">Interoperability</h1>
+<p>There has been some confusion about the namespace for the PDF/A indicator in the XMP metadata. At least three variants have been seen in the wild:</p>
+<table>
+<thead>
+<tr>
+<th>http://www.aiim.org/pdfa/ns/id.html</th>
+<th><strong>obsolete</strong> , from an early draft of ISO-19005-1, used by Adobe Acrobat 7.x</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>http://www.aiim.org/pdfa/ns/id/</td>
+<td><strong>correct</strong> , found in the technical corrigendum 1 of ISO 19005-1:2005</td>
+</tr>
+</tbody>
+</table>
+<p>If you get an error validating a PDF/A file in Adobe Acrobat 7.x it doesn't mean that FOP did something wrong. It's Acrobat that is at fault. This is fixed in Adobe Acrobat 8.x which uses the correct namespace as described in the technical corrigendum 1.</p></div></div>
+      <div class="clear"></div>
+
+	  <div id="footer">
+		<a alt="Apache Software Foundation" href="http://www.apache.org">
+		  <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+		</a>
+		<div class="copyright">
+		  <p>
+			Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+			the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+			<br />
+			Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+			trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+			marks mentioned may be trademarks or registered trademarks of their respective owners.
+			<br />
+		  </p>
+		</div> 
+	  </div>
+  </body>
+</html>

Added: websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,214 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP: PDF encryption.</title>
+
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+    <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+    <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+    </style>
+
+    
+
+    
+    
+  </head>
+
+  <body>
+	  <div id="banner">&nbsp;
+	  </div>
+
+	  <div id="navigation">
+	  <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+  <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+  <input type="text" name="q" id="query" /><br />
+  <input type="submit" id="submit" value="Search" />
+</form>
+	  </div>
+	
+	  <div id="bannertext">
+        <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+        <h1>Apache™ FOP: PDF encryption.</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version><authors><person email="pietsch@apache.org" name="J.Pietschmann"></person><person email="jeremias@apache.org" name="Jeremias Märki"></person></authors></p>
+<h1 id="Overview">Overview</h1>
+<p>Apache™ FOP supports encryption of PDF output, thanks to Patrick C. Lankswert. This feature is commonly used to prevent unauthorized viewing, printing, editing, copying text from the document and doing annotations. It is also possible to ask the user for a password in order to view the contents. Note that there already exist third party applications which can decrypt an encrypted PDF without effort and allow the aforementioned operations, therefore the degree of protection is limited.</p>
+<p>For further information about features and restrictions regarding PDF encryption, look at the documentation coming with Adobe Acrobat or the technical documentation on the Adobe web site.</p>
+<h1 id="usage-command-line-usage28commandline29">Usage (command line) # {#Usage+%28command+line%29}</h1>
+<p>Encryption is enabled by supplying any of the encryption related options.</p>
+<p>An owner password is set with the <code>-o</code> option. This password is actually used as encryption key. Many tools for PDF processing ask for this password to disregard any restriction imposed on the PDF document.</p>
+<p>If no owner password has been supplied but FOP was asked to apply some restrictions, a random password is used. In this case it is obviously impossiible to disregard restrictions in PDF processing tools.</p>
+<p>A user password, supplied with the <code>-u</code> option, will cause the PDF display software to ask the reader for this password in order to view the contents of the document. If no user password was supplied, viewing the content is not restricted.</p>
+<p>Further restrictions can be imposed by using the <code>-noprint</code> , <code>-nocopy</code> , <code>-noedit</code> and <code>-noannotations</code> options, which disable printing, copying text, editing in Adobe Acrobat and making annotations, respectively.</p>
+<h1 id="usage-embedded-usage28embedded29">Usage (embedded) # {#Usage+%28embedded%29}</h1>
+<p>When FOP is embedded in another Java application you need to set an options map on the renderer. These are the supported options:</p>
+<table>
+<thead>
+<tr>
+<th>Option</th>
+<th>Description</th>
+<th>Values</th>
+<th>Default</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>ownerPassword</td>
+<td>The owner password</td>
+<td>String</td>
+<td></td>
+</tr>
+<tr>
+<td>userPassword</td>
+<td>The user password</td>
+<td>String</td>
+<td></td>
+</tr>
+<tr>
+<td>allowPrint</td>
+<td>Allows/disallows printing of the PDF</td>
+<td>"TRUE" or "FALSE"</td>
+<td>"TRUE"</td>
+</tr>
+<tr>
+<td>allowCopyContent</td>
+<td>Allows/disallows copy/paste of content</td>
+<td>"TRUE" or "FALSE"</td>
+<td>"TRUE"</td>
+</tr>
+<tr>
+<td>allowEditContent</td>
+<td>Allows/disallows editing of content</td>
+<td>"TRUE" or "FALSE"</td>
+<td>"TRUE"</td>
+</tr>
+<tr>
+<td>allowEditAnnotations</td>
+<td>Allows/disallows editing of annotations</td>
+<td>"TRUE" or "FALSE"</td>
+<td>"TRUE"</td>
+</tr>
+<tr>
+<td>Encryption is enabled as soon as one of these options is set.</td>
+<td></td>
+<td></td>
+<td></td>
+</tr>
+<tr>
+<td>An example to enable PDF encryption in Java code:</td>
+<td></td>
+<td></td>
+<td></td>
+</tr>
+</tbody>
+</table>
+<p>import org.apache.fop.pdf.PDFEncryptionParams;</p>
+<p>[..]</p>
+<p>FOUserAgent userAgent = fopFactory.newFOUserAgent();
+useragent.getRendererOptions().put("encryption-params", new PDFEncryptionParams(
+    null, "password", false, false, true, true));
+Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent);
+[..]
+The parameters for the constructor of PDFEncryptionParams are:</p>
+<ol>
+<li>
+<p>userPassword: String, may be null</p>
+</li>
+<li>
+<p>ownerPassword: String, may be null</p>
+</li>
+<li>
+<p>allowPrint: true if printing is allowed</p>
+</li>
+<li>
+<p>allowCopyContent: true if copying content is allowed</p>
+</li>
+<li>
+<p>allowEditContent: true if editing content is allowed</p>
+</li>
+<li>
+<p>allowEditAnnotations: true if editing annotations is allowed</p>
+</li>
+</ol>
+<p>Alternatively, you can set each value separately in the Map provided by FOUserAgent.getRendererOptions() by using the following keys:</p>
+<ol>
+<li>
+<p>user-password: String</p>
+</li>
+<li>
+<p>owner-password: String</p>
+</li>
+<li>
+<p>noprint: Boolean or "true"/"false"</p>
+</li>
+<li>
+<p>nocopy: Boolean or "true"/"false"</p>
+</li>
+<li>
+<p>noedit: Boolean or "true"/"false"</p>
+</li>
+<li>
+<p>noannotations: Boolean or "true"/"false"</p>
+</li>
+</ol>
+<h1 id="Environment">Environment</h1>
+<p>In order to use PDF encryption, FOP has to be compiled with cryptography support. Currently, only <a href="http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html">JCE</a> is supported. JCE is part of JDK 1.4. For earlier JDKs, it can be installed separately. The build process automatically detects JCE presence and installs PDF encryption support if possible, otherwise a stub is compiled in.</p>
+<p>Cryptography support must also be present at run time. In particular, a provider for the RC4 cipher is needed. Unfortunately, the sample JCE provider in Sun's JDK 1.4 does <strong>not</strong> provide RC4. If you get a message saying
+"Cannot find any provider supporting RC4"
+then you don't have the needed infrastructure.</p>
+<p>There are several commercial and a few Open Source packages which provide RC4. A pure Java implementation is produced by <a href="http://www.bouncycastle.org/">The Legion of the Bouncy Castle</a> . <a href="http://www.mozilla.org/projects/security/pki/jss/">Mozilla JSS</a> is an interface to a native implementation.</p>
+<h1 id="install_crypto">Installing a crypto provider</h1>
+<p>The pure Java implementation from <a href="http://www.bouncycastle.org/">Bouncy Castle</a> is easy to install.</p>
+<ol>
+<li>
+<p>Unpack the distribution. Add the jar file to your classpath. A convenient way to use the jar on Linux is to simply drop it into the FOP lib directory, it will be automatically picked up by <code>fop.sh</code> .</p>
+</li>
+<li>
+<p>Open the <code>java.security</code> file and add<br></br> <code>security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider</code> ,<br></br>preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on <a href="http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html#InstallProvider">Sun's web site</a> .</p>
+</li>
+</ol>
+<p>If you have any experience with Mozilla JSS or any other cryptography provider, please post it to the fop-user list.</p></div></div>
+      <div class="clear"></div>
+
+	  <div id="footer">
+		<a alt="Apache Software Foundation" href="http://www.apache.org">
+		  <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+		</a>
+		<div class="copyright">
+		  <p>
+			Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+			the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+			<br />
+			Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+			trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+			marks mentioned may be trademarks or registered trademarks of their respective owners.
+			<br />
+		  </p>
+		</div> 
+	  </div>
+  </body>
+</html>

Added: websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfx.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfx.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfx.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,117 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP: PDF/X (ISO 15930)</title>
+
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+    <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+    <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+    </style>
+
+    
+
+    
+    
+  </head>
+
+  <body>
+	  <div id="banner">&nbsp;
+	  </div>
+
+	  <div id="navigation">
+	  <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+  <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+  <input type="text" name="q" id="query" /><br />
+  <input type="submit" id="submit" value="Search" />
+</form>
+	  </div>
+	
+	  <div id="bannertext">
+        <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+        <h1>Apache™ FOP: PDF/X (ISO 15930)</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version><authors><person email="jeremias@apache.org" name="Jeremias Märki"></person></authors></p>
+<h1 id="overview">Overview</h1>
+<p><warning>Support for PDF/X is available beginning with version 0.93. This feature is new and may not be 100% complete, yet. Feedback is welcome.</warning>
+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 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> . More info on PDF/X can be found on the <a href="http://www.pdfx.info/">PDF/X info site</a> .</p>
+<h1 id="status">Implementation Status</h1>
+<p><strong>PDF/X-3:2003</strong> is implemented to the degree that FOP supports the creation of the elements described in ISO 15930-6.</p>
+<p>An important restriction of the current implementation is that all normal RGB colors specified in XSL-FO and SVG are left unchanged in the sRGB color space (XSL-FO and SVG both use sRGB as their default color space). There's no conversion to a CMYK color space. Although sRGB is a calibrated color space, its color space has a different size than a CMYK color space which makes the conversion a lossy conversion and can lead to unwanted results. Although the use of the calibrated sRGB has been promoted for years, print shops usually prefer to convert an sRGB PDF to CMYK prior to production. Until there's full CMYK support in FOP you will have to work closely with your print service provider to make sure you get the intended result.</p>
+<p>Tests have been performed against Adobe Acrobat 7.0.7 (Preflight function). Note that there are bugs in Adobe Acrobat which cause false alarms if both PDF/A-1b and PDF/X-3:2003 are activated at the same time.</p>
+<h1 id="command-line">Usage (command line)</h1>
+<p>To activate PDF/X-3:2003 from the command-line, specify "-pdfprofile PDF/X-3:2003" as a parameter. If there is a violation of one of the validation rules for PDF/X, an error message is presented and the processing stops.</p>
+<h1 id="embedded">Usage (embedded)</h1>
+<p>When FOP is embedded in another Java application you can set a special option on the renderer options in the user agent to activate the PDF/A-1b profile. Here's an example:</p>
+<p>FOUserAgent userAgent = fopFactory.newFOUserAgent();
+userAgent.getRendererOptions().put("pdf-x-mode", "PDF/X-3:2003");
+Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent);
+[..]
+If one of the validation rules of PDF/X is violated, an PDFConformanceException (descendant of RuntimeException) is thrown.</p>
+<h1 id="rules">PDF/X in Action</h1>
+<p>There are a number of things that must be looked after if you activate a PDF/X profile. If you receive a PDFConformanceException, have a look at the following list (not necessarily comprehensive):</p>
+<ul>
+<li>
+<p>Make sure all (!) fonts are embedded. If you use base 14 fonts (like Helvetica) you need to obtain a license for them and embed them like any other font.</p>
+</li>
+<li>
+<p>Don't use PDF encryption. PDF/X doesn't allow it.</p>
+</li>
+<li>
+<p>Don't use CMYK images without an ICC color profile. PDF/X doesn't allow mixing color spaces and FOP currently only properly supports the sRGB color space. However, you will need to specify an <a href="configuration.html#pdf-renderer">output device profile</a> (usually a CMYK profile) in the configuration. sRGB won't work here since it's a display device profile, not an output device profile.</p>
+</li>
+<li>
+<p>Don't use non-RGB colors in SVG images. Same issue as with CMYK images.</p>
+</li>
+<li>
+<p>Don't use EPS graphics with fo:external-graphic. Embedding EPS graphics in PDF is deprecated since PDF 1.4 and prohibited by PDF/X-3:2003.</p>
+</li>
+<li>
+<p>PDF is forced to version 1.4 if PDF/X-3:2003 is activated.</p>
+</li>
+</ul>
+<h1 id="profile-compatibility">PDF profile compatibility</h1>
+<p>The PDF profiles "PDF/X-3:2003" and "PDF/A-1b" are compatible and can both be activated at the same time.</p></div></div>
+      <div class="clear"></div>
+
+	  <div id="footer">
+		<a alt="Apache Software Foundation" href="http://www.apache.org">
+		  <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+		</a>
+		<div class="copyright">
+		  <p>
+			Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+			the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+			<br />
+			Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+			trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+			marks mentioned may be trademarks or registered trademarks of their respective owners.
+			<br />
+		  </p>
+		</div> 
+	  </div>
+  </body>
+</html>

Added: websites/staging/xmlgraphics/trunk/content/fop/0.95/releaseNotes_0.95.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/releaseNotes_0.95.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/releaseNotes_0.95.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,121 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Release Notes for Apache FOP 0.95</title>
+
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+    <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+    <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+    </style>
+
+    
+
+    
+    
+  </head>
+
+  <body>
+	  <div id="banner">&nbsp;
+	  </div>
+
+	  <div id="navigation">
+	  <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+  <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+  <input type="text" name="q" id="query" /><br />
+  <input type="submit" id="submit" value="Search" />
+</form>
+	  </div>
+	
+	  <div id="bannertext">
+        <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+        <h1>Release Notes for Apache FOP 0.95</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><notes><section id="Notes">
+Besides the important changes listed below, the most important areas with improvements in this release are:</p>
+<ul>
+<li>
+<p>Many bugfixes in tables, plus some new features (full support for keeps and breaks, border conditionality, background on columns and header/footer/body)</p>
+</li>
+<li>
+<p>Improvements and bugfixes for font handling and font auto-detection/-registration.</p>
+</li>
+<li>
+<p>Performance improvements and memory optimizations for the property handling in the FO tree.</p>
+</li>
+</ul>
+<p>Please note that with this release, we've dropped support for Java 1.3. FOP will, from now on, <strong>require at least Java 1.4</strong> .</p>
+<p>There have been a few changes in tables that make FOP both more strict and more compliant to the Recommendation:</p>
+<ul>
+<li>
+<p>XSL-FO 1.1 explicitly states that a row-spanning fo:table-cell element is not allowed to span further than its enclosing fo:table-header/footer/body element (see bottom of <a href="http://www.w3.org/TR/xsl11/#fo_table">section 6.7.3</a> ). From now on FOP will give a validation error if a document contains such an erroneous cell.</p>
+</li>
+<li>
+<p>If an fo:table element contains explicit fo:table-column children, then those elements set the total number of columns in the table. This means that a validation error will now occur if a row contains more cells than available columns. This change allows to improve performance, since the rendering of the table may start as soon as the table-column elements have been parsed.</p>
+</li>
+</ul>
+<p>If more flexibility is needed, then the fo:table-column elements may be just omitted. The final number of columns will then be set by the row that has the most cells.</p>
+<p>The image libraries Jimi and JAI are no longer needed (and used) for image loading. Instead we rely completely on the Image I/O API that has been introduced with Java 1.4. If you still need support for bitmap image formats that do not work out-of-the-box, we recommend adding <a href="http://jai-imageio.dev.java.net/">JAI Image I/O Tools</a> (an Image I/O compatible image codec package) to the classpath. JAI is still required for building the FOP distribution but it is optional for normal builds and at run-time.
+This final 0.95 release also includes all of the <a href="changes_0.95beta.html">changes made for Apache FOP 0.95beta</a> .</section></notes></p>
+<h1 id="version_0.95">Major Changes in Version 0.95</h1>
+<p>This is not a complete list of changes, just some of the more important ones. A full list of changes in this release <a href="changes_0.95.html">is available</a> .</p>
+<h2 id="changes-to-the-code-base-changestothecodebase">Changes to the Code Base ## {#Changes+to+the+Code+Base}</h2>
+<ul>
+<li><icon alt="fix" src="../images/fix.jpg"></icon>Fixed potential multi-threading problem concerning the use of DecimalFormat. Committed by JM. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=44887">44887</a> .</li>
+</ul>
+<h2 id="changes-to-the-layout-engine-changestothelayoutengine">Changes to the Layout Engine ## {#Changes+to+the+Layout+Engine}</h2>
+<ul>
+<li><icon alt="fix" src="../images/fix.jpg"></icon>Various bugfixes for table layout. Committed by VH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=44621">44621</a> .</li>
+</ul>
+<h2 id="changes-to-renderers-output-formats-changestorenderers28outputformats29">Changes to Renderers (Output Formats) ## {#Changes+to+Renderers+%28Output+Formats%29}</h2>
+<ul>
+<li>
+<p><icon alt="fix" src="../images/fix.jpg"></icon>Fixed positioning of absolutely positioned block-containers in multi-column documents. Committed by JM.</p>
+</li>
+<li>
+<p><icon alt="fix" src="../images/fix.jpg"></icon>Fixed rendering of fixed block-containers in AFP output. Committed by JM.</p>
+</li>
+</ul></div></div>
+      <div class="clear"></div>
+
+	  <div id="footer">
+		<a alt="Apache Software Foundation" href="http://www.apache.org">
+		  <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+		</a>
+		<div class="copyright">
+		  <p>
+			Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+			the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+			<br />
+			Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+			trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+			marks mentioned may be trademarks or registered trademarks of their respective owners.
+			<br />
+		  </p>
+		</div> 
+	  </div>
+  </body>
+</html>



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


Mime
View raw message