xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r840642 [4/6] - in /websites/staging/xmlgraphics/trunk/content: ./ fop/ fop/0.95/ fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/ fop/trunk/
Date Tue, 04 Dec 2012 05:02:25 GMT
Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/fonts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/fonts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/fonts.html Tue Dec  4 05:02:22 2012
@@ -341,9 +341,9 @@ $(document).ready(function () {
         <div id="items">
         </div>
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/1.1/">1.1</a></div> -->
-      	<div class="section-content"><h1 id="apachewzxhzdk4-fop-fonts">Apache&trade; FOP: Fonts</h1>
+      	<div class="section-content"><h1 id="apachewzxhzdk5-fop-fonts">Apache&trade; FOP: Fonts</h1>
 <p><authors><person email="" name="Jeremias Märki"></person><person email="" name="Tore Engvig"></person><person email="" name="Adrian Cumiskey"></person><person email="" name="Max Berger"></person></authors></p>
-<h2 id="summary-wzxhzdk15wzxhzdk16">Summary <a id="intro"></a></h2>
+<h2 id="summary-wzxhzdk16wzxhzdk17">Summary <a id="intro"></a></h2>
 <p>The following table summarizes the font capabilities of the various Apache&trade; FOP renderers:</p>
 <table>
 <thead>
@@ -421,7 +421,7 @@ $(document).ready(function () {
 </tr>
 </tbody>
 </table>
-<h2 id="base-14-fonts-wzxhzdk18wzxhzdk19">Base-14 Fonts <a id="Base-14+Fonts"></a></h2>
+<h2 id="base-14-fonts-wzxhzdk19wzxhzdk20">Base-14 Fonts <a id="Base-14+Fonts"></a></h2>
 <p>The Adobe PostScript and PDF Specification specify a set of 14 fonts that must be available to every PostScript interpreter and PDF reader: Helvetica (normal, bold, italic, bold italic), Times (normal, bold, italic, bold italic), Courier (normal, bold, italic, bold italic), Symbol and ZapfDingbats.</p>
 <p>The following font family names are hard-coded into FOP for the Base-14 font set:</p>
 <table>
@@ -455,14 +455,14 @@ $(document).ready(function () {
 </tbody>
 </table>
 <p>Please note that recent versions of Adobe Acrobat Reader replace "Helvetica" with "Arial" and "Times" with "Times New Roman" internally. GhostScript replaces "Helvetica" with "Nimbus Sans L" and "Times" with "Nimbus Roman No9 L". Other document viewers may do similar font substitutions. If you need to make sure that there are no such substitutions, you need to specify an explicit font and embed it in the target document.</p>
-<h2 id="missing-fonts-wzxhzdk20wzxhzdk21">Missing Fonts <a id="missing-fonts"></a></h2>
+<h2 id="missing-fonts-wzxhzdk21wzxhzdk22">Missing Fonts <a id="missing-fonts"></a></h2>
 <p>When FOP does not have a specific font at its disposal (because it's not installed in the operating system or set up in FOP's configuration), the font is replaced with "any". "any" is internally mapped to the Base-14 font "Times" (see above).</p>
-<h2 id="missing-glyphs-wzxhzdk22wzxhzdk23">Missing Glyphs <a id="missing-glyphs"></a></h2>
+<h2 id="missing-glyphs-wzxhzdk23wzxhzdk24">Missing Glyphs <a id="missing-glyphs"></a></h2>
 <p>Every font contains a particular set of <a href="http://en.wikipedia.org/wiki/Glyph">glyphs</a> . If no glyph can be found for a given character, FOP will issue a warning and use the glpyh for "#" (if available) instead. Before it does that, it consults a (currently hard-coded) registry of glyph substitution groups (see Glyphs.java in Apache XML Graphics Commons). This registry can supply alternative glyphs in some cases (like using space when a no-break space is requested). But there's no guarantee that the result will be as expected (for example, in the case of hyphens and similar glyphs). A better way is to use a font that has all the necessary glyphs. This glyph substitution is only a last resort.</p>
-<h2 id="java2dawtoperating-system-fonts-wzxhzdk24wzxhzdk25">Java2D/AWT/Operating System Fonts <a id="awt"></a></h2>
+<h2 id="java2dawtoperating-system-fonts-wzxhzdk25wzxhzdk26">Java2D/AWT/Operating System Fonts <a id="awt"></a></h2>
 <p>The Java2D family of renderers (Java2D, AWT, Print, TIFF, PNG), use the Java AWT subsystem for font metric information. Through operating system registration, the AWT subsystem knows what fonts are available on the system, and the font metrics for each one.</p>
 <p>When working with one of these output formats and you're missing a font, just install it in your operating system and they should be available for these renderers. Please note that this is not true for other output formats such as PDF or PostScript.</p>
-<h2 id="custom-fonts-wzxhzdk26wzxhzdk27">Custom Fonts <a id="custom"></a></h2>
+<h2 id="custom-fonts-wzxhzdk27wzxhzdk28">Custom Fonts <a id="custom"></a></h2>
 <p>Support for custom fonts is highly output format dependent (see above table). This section shows how to add Type 1 and TrueType fonts to the PDF, PostScript and Java2D-based renderers. Other renderers (like AFP) support other font formats. Details in this case can be found on the page about <a href="output.html">output formats</a> .</p>
 <p>In earlier FOP versions, it was always necessary to create an XML font metrics file if you wanted to add a custom font. This unconvenient step has been removed and in addition to that, FOP supports auto-registration of fonts, i.e. FOP can find fonts installed in your operating system or can scan user-specified directories for fonts. Font registration via XML font metrics file is still supported and may still be necessary for some very special cases as fallback variant while we stabilize font auto-detection.</p>
 <p>Basic information about fonts can be found at:</p>
@@ -474,7 +474,7 @@ $(document).ready(function () {
 <p><a href="http://partners.adobe.com/asn/developer/technotes/fonts.html">Adobe Font Technote</a> </p>
 </li>
 </ul>
-<h2 id="bulk-font-configuration-wzxhzdk28wzxhzdk29">Bulk Font Configuration <a id="bulk"></a></h2>
+<h2 id="bulk-font-configuration-wzxhzdk29wzxhzdk30">Bulk Font Configuration <a id="bulk"></a></h2>
 <p>If you want FOP to use custom fonts, you need to tell it where to find them. This is done in the configuration file and once per renderer (because each output format is a little different). For convenience, FOP allows bulk registering of fonts; you can either tell FOP to find your operating system fonts or you can specify directories that it will search for support fonts. These fonts will then automatically be registered.</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderers&gt;</span>
   <span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/pdf&quot;</span><span class="nt">&gt;</span>
@@ -494,7 +494,7 @@ $(document).ready(function () {
 
 
 <p>Review the documentation for <a href="configuration.html">FOP Configuration</a> for instructions on making the FOP configuration available to FOP when it runs. Otherwise, FOP has no way of finding your custom font information. It is currently not possible to easily configure fonts from Java code.</p>
-<h3 id="register-fonts-with-fop-wzxhzdk30wzxhzdk31">Register Fonts with FOP <a id="register"></a></h3>
+<h3 id="register-fonts-with-fop-wzxhzdk31wzxhzdk32">Register Fonts with FOP <a id="register"></a></h3>
 <p>You must tell FOP how to find and use the font files by registering them in the <a href="configuration.html">FOP Configuration</a> . Add entries for your custom fonts, regardless of font type, to the configuration file in a manner similar to the following:</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderers&gt;</span>
    <span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/pdf&quot;</span><span class="nt">&gt;</span>
@@ -560,18 +560,21 @@ $(document).ready(function () {
 <p>If relative URLs are specified, they are evaluated relative to the value of the "font-base" setting. If there is no "font-base" setting, the fonts are evaluated relative to the base directory.</p>
 </li>
 </ul>
-<h3 id="truetype-collections-wzxhzdk32wzxhzdk33">TrueType Collections <a id="truetype-collections-metrics"></a></h3>
+<h3 id="truetype-collections-wzxhzdk33wzxhzdk34">TrueType Collections <a id="truetype-collections-metrics"></a></h3>
 <p>TrueType collections (.ttc files) contain more than one font. To create metrics files for these fonts, you must specify which font in the collection should be generated, by using the "-ttcname" option with the TTFReader.</p>
 <p>To get a list of the fonts in a collection, just start the TTFReader as if it were a normal TrueType file (without the -ttcname option). It will display all of the font names and exit with an Exception.</p>
 <p>Here is an example of generating a metrics file for a .ttc file:
 java -cp build\fop.jar;lib\avalon-framework.jar;lib\commons-logging.jar;lib\commons-io.jar
           org.apache.fop.fonts.apps.TTFReader -ttcname "MS Mincho"
           msmincho.ttc msminch.xml
-Alternatively, the individual sub-fonts of a TrueType Collections can be selected using the "sub-font" attribute on the "font" element. That means that generating an XML font metrics file for TrueType collections is not necessary anymore. Example:
-<font embed-url="gulim.ttc" sub-font="GulimChe">
-  <font-triplet name="GulimChe" style="normal" weight="normal"/>
-</font></p>
-<h3 id="auto-detect-and-auto-embed-feature-wzxhzdk37wzxhzdk38">Auto-Detect and auto-embed feature <a id="autodetect"></a></h3>
+Alternatively, the individual sub-fonts of a TrueType Collections can be selected using the "sub-font" attribute on the "font" element. That means that generating an XML font metrics file for TrueType collections is not necessary anymore. Example:</p>
+<div class="codehilite"><pre><span class="nt">&lt;font</span> <span class="na">embed-url=</span><span class="s">&quot;gulim.ttc&quot;</span> <span class="na">sub-font=</span><span class="s">&quot;GulimChe&quot;</span><span class="nt">&gt;</span>
+  <span class="nt">&lt;font-triplet</span> <span class="na">name=</span><span class="s">&quot;GulimChe&quot;</span> <span class="na">style=</span><span class="s">&quot;normal&quot;</span> <span class="na">weight=</span><span class="s">&quot;normal&quot;</span><span class="nt">/&gt;</span>
+<span class="nt">&lt;/font&gt;</span>
+</pre></div>
+
+
+<h3 id="auto-detect-and-auto-embed-feature-wzxhzdk35wzxhzdk36">Auto-Detect and auto-embed feature <a id="autodetect"></a></h3>
 <p>When the "auto-detect" flag is set in the configuration, FOP will automatically search for fonts in the default paths for your operating system.</p>
 <p>FOP will also auto-detect fonts which are available in the classpath, if they are described as "application/x-font" in the MANIFEST.MF file. For example, if your .jar file contains font/myfont.ttf:
 Manifest-Version: 1.0</p>
@@ -581,10 +584,10 @@ Manifest-Version: 1.0</p>
 
 
 <p>This feature allows you to create JAR files containing fonts. The JAR files can be added to fop by providem them in the classpath, e.g. copying them into the lib/ directory.</p>
-<h4 id="the-font-cache-wzxhzdk39wzxhzdk40">The font cache <a id="font-cache"></a></h4>
+<h4 id="the-font-cache-wzxhzdk37wzxhzdk38">The font cache <a id="font-cache"></a></h4>
 <p>Apache FOP maintains a cache file that is used to speed up auto-detection. This file is usually found in the ".fop" directory under the user's home directory. It's called "fop-fonts.cache". When the user's home directory is not writable, the font cache file is put in the directory for temporary files.</p>
 <p>If there was a problem loading a particular font, it is flagged in the cache file so it is not loaded anymore. So, if a font is actually around but is still not found by Apache FOP, it's worth a try to delete the font cache file which forces Apache FOP to reparse all fonts.</p>
-<h3 id="type-1-font-metrics-wzxhzdk41wzxhzdk42">Type 1 Font Metrics <a id="type1-metrics"></a></h3>
+<h3 id="type-1-font-metrics-wzxhzdk39wzxhzdk40">Type 1 Font Metrics <a id="type1-metrics"></a></h3>
 <p>Note that metrics files are optional and no longer required</p>
 <p>FOP includes PFMReader, which reads the PFM file that normally comes with a Type 1 font, and generates an appropriate font metrics file for it. To use it, run the class org.apache.fop.fonts.apps.PFMReader:</p>
 <p>Windows:
@@ -598,7 +601,7 @@ PFMReader [options]:</p>
 <li><strong>-fn <fontname></strong> By default, FOP uses the fontname from the .pfm file when embedding the font. Use the "-fn" option to override this name with one you have chosen. This may be useful in some cases to ensure that applications using the output document (Acrobat Reader for example) use the embedded font instead of a local font with the same name.
 The classpath in the above example has been simplified for readability. You will have to adjust the classpath to the names of the actual JAR files in the lib directory. xml-apis.jar, xercesImpl.jar, xalan.jar and serializer.jar are not necessary for JDK version 1.4 or later.The tool will construct some values (FontBBox, StemV and ItalicAngle) based on assumptions and calculations which are only an approximation to the real values. FontBBox and Italic Angle can be found in the human-readable part of the PFB file or in the AFM file. The PFMReader tool does not yet interpret PFB or AFM files, so if you want to be correct, you may have to adjust the values in the XML file manually. The constructed values however appear to have no visible influence.</li>
 </ul>
-<h3 id="truetype-font-metrics-wzxhzdk43wzxhzdk44">TrueType Font Metrics <a id="truetype-metrics"></a></h3>
+<h3 id="truetype-font-metrics-wzxhzdk41wzxhzdk42">TrueType Font Metrics <a id="truetype-metrics"></a></h3>
 <p>Note that metrics files are optional and no longer required</p>
 <p>FOP includes TTFReader, which reads the TTF file and generates an appropriate font metrics file for it. Use it in a similar manner to PFMReader. For example, to create such a metrics file in Windows from the TrueType font at c:\myfonts\cmr10.ttf:
 java -cp build\fop.jar;lib\avalon-framework-4.2.0.jar;lib\commons-logging-1.0.4.jar;lib\commons-io-1.3.1.jar;lib\commons-logging-1.0.4.jar;lib\xmlgraphics-commons-1.5.jar
@@ -641,7 +644,7 @@ TTFReader [options]:</p>
 </tbody>
 </table>
 <p><warning>You may experience failures with certain TrueType fonts, especially if they don't contain the so-called Unicode "cmap" table. TTFReader can currently not deal with font like this.</warning></p>
-<h3 id="embedding-wzxhzdk47wzxhzdk48">Embedding <a id="embedding"></a></h3>
+<h3 id="embedding-wzxhzdk45wzxhzdk46">Embedding <a id="embedding"></a></h3>
 <p>By default, all fonts are embedded if an output format supports font embedding. In some cases, however, it is preferred that some fonts are only referenced. When working with referenced fonts it is important to be in control of the target environment where the produced document is consumed, i.e. the necessary fonts have to be installed there.</p>
 <p>There are two different ways how you can specify that a font should be referenced:</p>
 <ol>
@@ -680,7 +683,7 @@ TTFReader [options]:</p>
 <p>When embedding TrueType fonts (ttf) or TrueType Collections (ttc), a subset of the original font, containing only the glyphs used, is embedded in the output document. That's the default, but if you specify encoding-mode="single-byte" (see above), the complete font is embedded.</p>
 </li>
 </ul>
-<h3 id="substitution-wzxhzdk49wzxhzdk50">Substitution <a id="substitution"></a></h3>
+<h3 id="substitution-wzxhzdk47wzxhzdk48">Substitution <a id="substitution"></a></h3>
 <p>When a <code>&lt;substitutions/&gt;</code> section is defined in the configuration, FOP will re-map any font-family references found in your FO input to a given substitution font.</p>
 <ul>
 <li>
@@ -708,7 +711,7 @@ TTFReader [options]:</p>
 </pre></div>
 
 
-<h2 id="font-selection-strategies-wzxhzdk51wzxhzdk52">Font Selection Strategies <a id="selection"></a></h2>
+<h2 id="font-selection-strategies-wzxhzdk49wzxhzdk50">Font Selection Strategies <a id="selection"></a></h2>
 <p>There are two font selection strategies: character-by-character or auto. The default is auto.</p>
 <p>Auto selected the first font from the list which is able to display the most characters in a given word. This means (assume font A has characters for abclmn, font B for lnmxyz, fontlist is A,B):</p>
 <ul>
@@ -726,7 +729,7 @@ TTFReader [options]:</p>
 </li>
 </ul>
 <p>Character-by-Character is NOT yet supported!</p>
-<h2 id="font-list-command-line-tool-wzxhzdk53wzxhzdk54">Font List Command-Line Tool <a id="font-list"></a></h2>
+<h2 id="font-list-command-line-tool-wzxhzdk51wzxhzdk52">Font List Command-Line Tool <a id="font-list"></a></h2>
 <p>FOP contains a small command-line tool that lets you generate a list of all configured fonts. Its class name is: <code>org.apache.fop.tools.fontlist.FontListMain</code> . Run it with the "-?" parameter to get help for the various options.</p></div>
       </div>
       

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/output.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/output.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/output.html Tue Dec  4 05:02:22 2012
@@ -341,11 +341,11 @@ $(document).ready(function () {
         <div id="items">
         </div>
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/1.1/">1.1</a></div> -->
-      	<div class="section-content"><h1 id="apachewzxhzdk40-fop-output-formats">Apache&trade; FOP Output Formats</h1>
+      	<div class="section-content"><h1 id="apachewzxhzdk41-fop-output-formats">Apache&trade; FOP Output Formats</h1>
 <p><authors><person email="keiron@aftexsw.com" name="Keiron Liddle"></person><person email="" name="Art Welch"></person></authors></p>
 <p>Apache&trade; 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>
-<h2 id="general-information-wzxhzdk48wzxhzdk49">General Information <a id="general"></a></h2>
-<h3 id="fonts-wzxhzdk50wzxhzdk51">Fonts <a id="general-fonts"></a></h3>
+<h2 id="general-information-wzxhzdk49wzxhzdk50">General Information <a id="general"></a></h2>
+<h3 id="fonts-wzxhzdk51wzxhzdk52">Fonts <a id="general-fonts"></a></h3>
 <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>
@@ -369,7 +369,7 @@ $(document).ready(function () {
 <p><code>fop -atin myfile.at.xml -tiff myfile.tiff</code> </p>
 </li>
 </ol>
-<h3 id="output-to-a-printer-or-other-device-wzxhzdk52wzxhzdk53">Output to a Printer or Other Device <a id="general-direct-output"></a></h3>
+<h3 id="output-to-a-printer-or-other-device-wzxhzdk53wzxhzdk54">Output to a Printer or Other Device <a id="general-direct-output"></a></h3>
 <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
@@ -377,12 +377,12 @@ Here is some Java code to accomplish the
 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>
-<h2 id="pdf-wzxhzdk54wzxhzdk55">PDF <a id="pdf"></a></h2>
+<h2 id="pdf-wzxhzdk55wzxhzdk56">PDF <a id="pdf"></a></h2>
 <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 PDF/A-1a. Support for <a href="accessibility.html">Tagged PDF</a> , <a href="pdfa.html">PDF/A-1b</a> and <a href="pdfx.html">PDF/X</a> has recently been added, however.</p>
-<h3 id="fonts-wzxhzdk56wzxhzdk57">Fonts <a id="pdf-fonts"></a></h3>
+<h3 id="fonts-wzxhzdk57wzxhzdk58">Fonts <a id="pdf-fonts"></a></h3>
 <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>
-<h3 id="post-processing-wzxhzdk58wzxhzdk59">Post-processing <a id="pdf-postprocess"></a></h3>
+<h3 id="post-processing-wzxhzdk59wzxhzdk60">Post-processing <a id="pdf-postprocess"></a></h3>
 <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>
@@ -432,7 +432,7 @@ Here is some sample code that uses iText
 
 
 <p>Check the iText tutorial and documentation for setting access flags, password, encryption strength and other parameters.</p>
-<h3 id="watermarks-wzxhzdk62wzxhzdk63">Watermarks <a id="pdf-watermark"></a></h3>
+<h3 id="watermarks-wzxhzdk63wzxhzdk64">Watermarks <a id="pdf-watermark"></a></h3>
 <p>In addition to the <a href="#pdf-postprocess">PDF Post-processing</a> options, consider the following workarounds:</p>
 <ul>
 <li>
@@ -442,14 +442,14 @@ Here is some sample code that uses iText
 <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>
-<h3 id="extensions-wzxhzdk64wzxhzdk65">Extensions <a id="pdf-extensions"></a></h3>
+<h3 id="extensions-wzxhzdk65wzxhzdk66">Extensions <a id="pdf-extensions"></a></h3>
 <p>The PDF Renderer supports some PDF 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:pdf</span><span class="o">=</span><span class="s">&quot;http://xmlgraphics.apache.org/fop/extensions/pdf&quot;</span><span class="o">&gt;</span>
 </pre></div>
 
 
-<h4 id="embedded-fileswzxhzdk66wzxhzdk67">Embedded Files<a id="pdf-embedded-file"></a></h4>
+<h4 id="embedded-fileswzxhzdk67wzxhzdk68">Embedded Files<a id="pdf-embedded-file"></a></h4>
 <p>It is possible to attach/embed arbitrary files into a PDF file. You can give a name and a description of the file. Example:</p>
 <p><fo:declarations>
     <pdf:embedded-file filename="image.jpg" src="url(file:///C:/Temp/myimage.jpg)" description="My image"/>
@@ -462,9 +462,9 @@ Here is some sample code that uses iText
 
 
 <p>Note: Not all PDF Viewers (including some Acrobat Versions) will open the embedded file when clicking on the link. In that case, the user will have to open he attachment via the separate list of file attachments.</p>
-<h2 id="postscript-wzxhzdk72wzxhzdk73">PostScript <a id="ps"></a></h2>
+<h2 id="postscript-wzxhzdk73wzxhzdk74">PostScript <a id="ps"></a></h2>
 <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>
-<h3 id="configuration-wzxhzdk74wzxhzdk75">Configuration <a id="ps-configuration"></a></h3>
+<h3 id="configuration-wzxhzdk75wzxhzdk76">Configuration <a id="ps-configuration"></a></h3>
 <p>The PostScript renderer configuration currently allows the following settings:</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/postscript&quot;</span><span class="nt">&gt;</span>
   <span class="nt">&lt;auto-rotate-landscape&gt;</span>false<span class="nt">&lt;/auto-rotate-landscape&gt;</span>
@@ -483,7 +483,7 @@ Here is some sample code that uses iText
 <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>
 <p>The default value for the "rendering" setting is "quality". Setting it to "size" optimizes rendering for smaller file sizes which can involve minor compromises in rendering quality. For example, solid borders are then painted as plain rectangles instead of the elaborate painting instructions required for mixed-color borders.</p>
-<h3 id="limitations-wzxhzdk76wzxhzdk77">Limitations <a id="ps-limitations"></a></h3>
+<h3 id="limitations-wzxhzdk77wzxhzdk78">Limitations <a id="ps-limitations"></a></h3>
 <ul>
 <li>
 <p>Images and SVG may not be displayed correctly. SVG support is far from being complete. No image transparency is available.</p>
@@ -498,10 +498,10 @@ Here is some sample code that uses iText
 <p>PPD support is still missing.</p>
 </li>
 </ul>
-<h2 id="pcl-wzxhzdk78wzxhzdk79">PCL <a id="pcl"></a></h2>
+<h2 id="pcl-wzxhzdk79wzxhzdk80">PCL <a id="pcl"></a></h2>
 <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>
-<h3 id="references-wzxhzdk80wzxhzdk81">References <a id="pcl-references"></a></h3>
+<h3 id="references-wzxhzdk81wzxhzdk82">References <a id="pcl-references"></a></h3>
 <ul>
 <li>
 <p><a href="http://en.wikipedia.org/wiki/Printer_Control_Language">WikiPedia entry on PCL</a> </p>
@@ -510,7 +510,7 @@ Here is some sample code that uses iText
 <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>
-<h3 id="limitations-wzxhzdk82wzxhzdk83">Limitations <a id="pcl-limitations"></a></h3>
+<h3 id="limitations-wzxhzdk83wzxhzdk84">Limitations <a id="pcl-limitations"></a></h3>
 <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>
@@ -537,7 +537,7 @@ Here is some sample code that uses iText
 <p>Currently, there's no support for clipping and image transparency, largely because PCL 5 has certain limitations.</p>
 </li>
 </ul>
-<h3 id="configuration-wzxhzdk84wzxhzdk85">Configuration <a id="pcl-configuration"></a></h3>
+<h3 id="configuration-wzxhzdk85wzxhzdk86">Configuration <a id="pcl-configuration"></a></h3>
 <p>The PCL renderer configuration currently allows the following settings:</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/x-pcl&quot;</span><span class="nt">&gt;</span>
   <span class="nt">&lt;rendering&gt;</span>quality<span class="nt">&lt;/rendering&gt;</span>
@@ -551,14 +551,14 @@ Here is some sample code that uses iText
 <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>
-<h3 id="extensions-wzxhzdk86wzxhzdk87">Extensions <a id="pcl-extensions"></a></h3>
+<h3 id="extensions-wzxhzdk87wzxhzdk88">Extensions <a id="pcl-extensions"></a></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 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>
 
 
-<h4 id="page-source-tray-selectionwzxhzdk88wzxhzdk89">Page Source (Tray selection)<a id="pcl-page-source"></a></h4>
+<h4 id="page-source-tray-selectionwzxhzdk89wzxhzdk90">Page Source (Tray selection)<a id="pcl-page-source"></a></h4>
 <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>
@@ -569,7 +569,7 @@ Here is some sample code that uses iText
 
 
 <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>
-<h4 id="output-binwzxhzdk90wzxhzdk91">Output Bin<a id="pcl-output-bin"></a></h4>
+<h4 id="output-binwzxhzdk91wzxhzdk92">Output Bin<a id="pcl-output-bin"></a></h4>
 <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>
 <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:output-bin=</span><span class="s">&quot;2&quot;</span><span class="nt">&gt;</span>
@@ -580,7 +580,7 @@ Here is some sample code that uses iText
 
 
 <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>
-<h4 id="page-duplex-modewzxhzdk92wzxhzdk93">Page Duplex Mode<a id="pcl-duplex-mode"></a></h4>
+<h4 id="page-duplex-modewzxhzdk93wzxhzdk94">Page Duplex Mode<a id="pcl-duplex-mode"></a></h4>
 <p>The duplex-mode extension attribute on fo:simple-page-master allows to select the duplex mode to be used for a particular simple-page-master. 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:duplex-mode=</span><span class="s">&quot;0&quot;</span><span class="nt">&gt;</span>
@@ -591,7 +591,7 @@ Here is some sample code that uses iText
 
 
 <p>Note: the duplex is a positive integer and the value depends on the target printer. Not all PCL printers support duplexing. Usually, "0" is simplex, "1" is duplex (long-edge binding), "2" is duplex (short-edge binding). Consult the technical reference for your printer for all available values.</p>
-<h2 id="afp-wzxhzdk94wzxhzdk95">AFP <a id="afp"></a></h2>
+<h2 id="afp-wzxhzdk95wzxhzdk96">AFP <a id="afp"></a></h2>
 <p>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>
 <p>The mapping of XSL-FO elements to the major MO:DCA structures is as follows:</p>
 <table>
@@ -617,7 +617,7 @@ Here is some sample code that uses iText
 </tbody>
 </table>
 <p>FOP creates exactly one Document per Printfile with an optional Resource Group at the beginning. FOP does not create document indices.</p>
-<h3 id="references-wzxhzdk96wzxhzdk97">References <a id="afp-references"></a></h3>
+<h3 id="references-wzxhzdk97wzxhzdk98">References <a id="afp-references"></a></h3>
 <ul>
 <li>
 <p><a href="http://en.wikipedia.org/wiki/Advanced_Function_Presentation">AFP (Advanced Function Presentation)</a> </p>
@@ -629,7 +629,7 @@ Here is some sample code that uses iText
 <p><a href="http://wiki.apache.org/xmlgraphics-fop/AFPOutput">Technical notes on AFP output in FOP</a> </p>
 </li>
 </ul>
-<h3 id="limitations-wzxhzdk98wzxhzdk99">Limitations <a id="afp-limitations"></a></h3>
+<h3 id="limitations-wzxhzdk99wzxhzdk100">Limitations <a id="afp-limitations"></a></h3>
 <p>This list is most likely badly incomplete.</p>
 <ul>
 <li>
@@ -639,10 +639,10 @@ Here is some sample code that uses iText
 <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>
-<h3 id="deployment-in-older-environments-wzxhzdk100wzxhzdk101">Deployment in older environments <a id="afp-compatibility"></a></h3>
+<h3 id="deployment-in-older-environments-wzxhzdk101wzxhzdk102">Deployment in older environments <a id="afp-compatibility"></a></h3>
 <p>There are still a big number of older (or limited) MO:DCA/IPDS environments in production out there. AFP has grown in functionality over time and not every environment supports the latest features. We're trying to make AFP output work in as many environments as possible. However, to make AFP output work on older environments it is recommended to set to configuration to 1 bit per pixel (see below on how to do this). In this case, all images are converted to bi-level images using IOCA function set 10 (FS10) and are enclosed in page-segments since some implementation cannot deal with IOCA objects directly. If a higher number of bits per pixel is configured, FOP has to switch to at least FS11 which may not work everywhere.</p>
-<h3 id="configuration-wzxhzdk102wzxhzdk103">Configuration <a id="afp-configuration"></a></h3>
-<h4 id="fontswzxhzdk104wzxhzdk105">Fonts<a id="afp-font-config"></a></h4>
+<h3 id="configuration-wzxhzdk103wzxhzdk104">Configuration <a id="afp-configuration"></a></h3>
+<h4 id="fontswzxhzdk105wzxhzdk106">Fonts<a id="afp-font-config"></a></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 for the AFP Renderer is application/x-afp which means the AFP Renderer section in the FOP configuration file looks like:</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/x-afp&quot;</span><span class="nt">&gt;</span>
   <span class="c">&lt;!-- AFP Renderer --&gt;</span>
@@ -798,19 +798,19 @@ A CID-keyed font (Type 0, double-byte ou
 </pre></div>
 
 
-<h4 id="output-resolutionwzxhzdk107wzxhzdk108">Output Resolution<a id="afp-renderer-resolution-config"></a></h4>
+<h4 id="output-resolutionwzxhzdk108wzxhzdk109">Output Resolution<a id="afp-renderer-resolution-config"></a></h4>
 <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>
 
 
-<h4 id="line-width-correctionwzxhzdk110wzxhzdk111">Line Width Correction<a id="afp-line-width-correction-config"></a></h4>
+<h4 id="line-width-correctionwzxhzdk111wzxhzdk112">Line Width Correction<a id="afp-line-width-correction-config"></a></h4>
 <p>The default line width in AFP is device dependent. This means that a line width specified in, say, a SVG source file may not render the way it was intended. The output AFP line with can be corrected by the <line-width-correction/> configuration element. Example:</p>
 <div class="codehilite"><pre>  <span class="nt">&lt;line-width-correction&gt;</span>2.5<span class="nt">&lt;/line-width-correction&gt;</span>
 </pre></div>
 
 
-<h4 id="imageswzxhzdk113wzxhzdk114">Images<a id="afp-image-config"></a></h4>
+<h4 id="imageswzxhzdk114wzxhzdk115">Images<a id="afp-image-config"></a></h4>
 <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>
@@ -855,7 +855,7 @@ A CID-keyed font (Type 0, double-byte ou
 </pre></div>
 
 
-<h4 id="goca-vector-graphicswzxhzdk116wzxhzdk117">GOCA (Vector Graphics)<a id="afp-goca-config"></a></h4>
+<h4 id="goca-vector-graphicswzxhzdk117wzxhzdk118">GOCA (Vector Graphics)<a id="afp-goca-config"></a></h4>
 <p>Not all AFP implementations support GOCA. Some also have bugs related to GOCA. Therefore, it is desirable to have some control over the generation of GOCA graphics.</p>
 <p>GOCA is enabled by default. You can disable GOCA entirely in which case the AFP support falls back to generating bitmaps for vector graphics. Example:</p>
 <div class="codehilite"><pre>  <span class="o">&lt;</span><span class="n">goca</span> <span class="n">enabled</span><span class="o">=</span><span class="s">&quot;false&quot;</span><span class="o">/&gt;</span>
@@ -868,24 +868,27 @@ A CID-keyed font (Type 0, double-byte ou
 
 
 <p>If you disable GOCA or let text render as shapes, the size of the generated AFP usually increases considerably.</p>
-<h4 id="shadingwzxhzdk118wzxhzdk119">Shading<a id="afp-shading-config"></a></h4>
+<h4 id="shadingwzxhzdk119wzxhzdk120">Shading<a id="afp-shading-config"></a></h4>
 <p>By default, filled rectangles are painted using their given color using a PTOCA I-axis rule (DIR). But not all environments handle these colors correctly. That's why a setting is supported that paints the rectangles using an ordered dither pattern (bi-level) with an inline IOCA FS10 image that is used together with the "replicate and trim" mapping. The optional "shading" element can be used to control the shading mode. Its default value is "color". To enable the dithered mode, use "dithered". Example:</p>
 <div class="codehilite"><pre>  <span class="nt">&lt;shading&gt;</span>dithered<span class="nt">&lt;/shading&gt;</span>
 </pre></div>
 
 
-<h4 id="resource-group-filewzxhzdk120wzxhzdk121">Resource Group File<a id="afp-resource-group-file"></a></h4>
+<h4 id="resource-group-filewzxhzdk121wzxhzdk122">Resource Group File<a id="afp-resource-group-file"></a></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 may be specified with the <resource-group-file/> configuration element. Example:</p>
 <div class="codehilite"><pre>  <span class="nt">&lt;resource-group-file&gt;</span>external_resources.afp<span class="nt">&lt;/resource-group-file&gt;</span>
 </pre></div>
 
 
 <p>Be careful when using this option not to overwrite existing resource files from previous rendering runs.</p>
-<h4 id="resource-level-defaultswzxhzdk123wzxhzdk124">Resource Level Defaults<a id="afp-resource-level-defaults"></a></h4>
+<h4 id="resource-level-defaultswzxhzdk124wzxhzdk125">Resource Level Defaults<a id="afp-resource-level-defaults"></a></h4>
 <p>By default, bitmap image objects (or page segments derived from them) are put in the print-file-level resource group and GOCA graphics are inlined for compatibility with the AFP Workbench tool.</p>
 <p>It is possible to override these defaults, either per image (see the <a href="#afp-foreign-attributes-resource">afp:resource-level</a> extension attribute below) or by specifying different defaults in the configuration:</p>
-<p><default-resource-levels goca="print-file" bitmap="inline"/>
-"goca" refers to GOCA graphics and "bitmap" refers to IOCA images. The possible values for the attributes are "inline" and "print-file". In the future, additional possibilities may be added.</p>
+<div class="codehilite"><pre><span class="o">&lt;</span><span class="n">default</span><span class="o">-</span><span class="n">resource</span><span class="o">-</span><span class="n">levels</span> <span class="n">goca</span><span class="o">=</span><span class="s">&quot;print-file&quot;</span> <span class="n">bitmap</span><span class="o">=</span><span class="s">&quot;inline&quot;</span><span class="o">/&gt;</span>
+</pre></div>
+
+
+<p>"goca" refers to GOCA graphics and "bitmap" refers to IOCA images. The possible values for the attributes are "inline" and "print-file". In the future, additional possibilities may be added.</p>
 <h3 id="extensions-wzxhzdk126wzxhzdk127">Extensions <a id="afp-extensions"></a></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>
 <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>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfa.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfa.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfa.html Tue Dec  4 05:02:22 2012
@@ -341,25 +341,29 @@ $(document).ready(function () {
         <div id="items">
         </div>
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/1.1/">1.1</a></div> -->
-      	<div class="section-content"><h1 id="apachewzxhzdk0-fop-pdfa-iso-19005">Apache&trade; FOP: PDF/A (ISO 19005)</h1>
+      	<div class="section-content"><h1 id="apachewzxhzdk1-fop-pdfa-iso-19005">Apache&trade; FOP: PDF/A (ISO 19005)</h1>
 <p><authors><person email="jeremias@apache.org" name="Jeremias Märki"></person></authors></p>
-<h2 id="overview-wzxhzdk5wzxhzdk6">Overview <a id="overview"></a></h2>
+<h2 id="overview-wzxhzdk6wzxhzdk7">Overview <a id="overview"></a></h2>
 <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>
-<h2 id="implementation-status-wzxhzdk7wzxhzdk8">Implementation Status <a id="status"></a></h2>
+<h2 id="implementation-status-wzxhzdk8wzxhzdk9">Implementation Status <a id="status"></a></h2>
 <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 based on PDF-A-1b and adds accessibility features (such as Tagged PDF). This format is available within the limitation described on the <a href="accessibility.html">Accessibility page</a> .</p>
-<h2 id="usage-command-line-wzxhzdk9wzxhzdk10">Usage (command line) <a id="command-line"></a></h2>
+<h2 id="usage-command-line-wzxhzdk10wzxhzdk11">Usage (command line) <a id="command-line"></a></h2>
 <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>
 <p>PDF/A-1a is enabled by specifying "-pdfprofile PDF/A-1a".</p>
-<h2 id="usage-embedded-wzxhzdk11wzxhzdk12">Usage (embedded) <a id="embedded"></a></h2>
+<h2 id="usage-embedded-wzxhzdk12wzxhzdk13">Usage (embedded) <a id="embedded"></a></h2>
 <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 class=".">userAgent.getRendererOptions().put("pdf-a-mode", "PDF/A-1b");
-Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent);
-</p>
+<div class="codehilite"><pre><span class="n">userAgent</span><span class="o">.</span><span class="n">getRendererOptions</span><span class="p">()</span><span class="o">.</span><span class="n">put</span><span class="p">(</span><span class="s">&quot;pdf-a-mode&quot;</span><span class="p">,</span> <span class="s">&quot;PDF/A-1b&quot;</span><span class="p">);</span>
+<span class="n">Fop</span> <span class="n">fop</span> <span class="o">=</span> <span class="n">fopFactory</span><span class="o">.</span><span class="n">newFop</span><span class="p">(</span><span class="n">MimeConstants</span><span class="o">.</span><span class="n">MIME_PDF</span><span class="p">,</span> <span class="n">userAgent</span><span class="p">);</span>
+<span class="p">[</span><span class="o">..</span><span class="p">]</span>
+</pre></div>
+
+
+<p>If one of the validation rules of PDF/A is violated, an PDFConformanceException (descendant of RuntimeException) is thrown.</p>
 <p>For PDF/A-1a, just use the string "PDF/A-1a" instead of "PDF/A-1b".</p>
-<h2 id="pdfa-in-action-wzxhzdk13wzxhzdk14">PDF/A in Action <a id="rules"></a></h2>
+<h2 id="pdfa-in-action-wzxhzdk14wzxhzdk15">PDF/A in Action <a id="rules"></a></h2>
 <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>
@@ -385,9 +389,9 @@ Fop fop = fopFactory.newFop(MimeConstant
 There are additional requirements if you want to enabled PDF/A-1a (Tagged PDF). This is particularly the specification of the natural language and alternative descriptions for images. Please refer to the <a href="accessibility.html">Accessibility page</a> for details.</p>
 </li>
 </ul>
-<h2 id="pdf-profile-compatibility-wzxhzdk15wzxhzdk16">PDF profile compatibility <a id="profile-compatibility"></a></h2>
+<h2 id="pdf-profile-compatibility-wzxhzdk16wzxhzdk17">PDF profile compatibility <a id="profile-compatibility"></a></h2>
 <p>The PDF profiles "PDF/X-3:2003" and "PDF/A-1b" (or "PDF/A-1a") are compatible and can both be activated at the same time.</p>
-<h2 id="interoperability-wzxhzdk17wzxhzdk18">Interoperability <a id="interoperability"></a></h2>
+<h2 id="interoperability-wzxhzdk18wzxhzdk19">Interoperability <a id="interoperability"></a></h2>
 <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>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfx.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfx.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfx.html Tue Dec  4 05:02:22 2012
@@ -341,24 +341,28 @@ $(document).ready(function () {
         <div id="items">
         </div>
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/1.1/">1.1</a></div> -->
-      	<div class="section-content"><h1 id="apachewzxhzdk0-fop-pdfx-iso-15930">Apache&trade; FOP: PDF/X (ISO 15930)</h1>
+      	<div class="section-content"><h1 id="apachewzxhzdk1-fop-pdfx-iso-15930">Apache&trade; FOP: PDF/X (ISO 15930)</h1>
 <p><authors><person email="jeremias@apache.org" name="Jeremias Märki"></person></authors></p>
-<h2 id="overview-wzxhzdk5wzxhzdk6">Overview <a id="overview"></a></h2>
+<h2 id="overview-wzxhzdk6wzxhzdk7">Overview <a id="overview"></a></h2>
 <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>
-<h2 id="implementation-status-wzxhzdk9wzxhzdk10">Implementation Status <a id="status"></a></h2>
+<h2 id="implementation-status-wzxhzdk10wzxhzdk11">Implementation Status <a id="status"></a></h2>
 <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>
-<h2 id="usage-command-line-wzxhzdk11wzxhzdk12">Usage (command line) <a id="command-line"></a></h2>
+<h2 id="usage-command-line-wzxhzdk12wzxhzdk13">Usage (command line) <a id="command-line"></a></h2>
 <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>
-<h2 id="usage-embedded-wzxhzdk13wzxhzdk14">Usage (embedded) <a id="embedded"></a></h2>
+<h2 id="usage-embedded-wzxhzdk14wzxhzdk15">Usage (embedded) <a id="embedded"></a></h2>
 <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 class=".">FOUserAgent userAgent = fopFactory.newFOUserAgent();
-userAgent.getRendererOptions().put("pdf-x-mode", "PDF/X-3:2003");
-Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent);
-</p>
-<h2 id="pdfx-in-action-wzxhzdk15wzxhzdk16">PDF/X in Action <a id="rules"></a></h2>
+<div class="codehilite"><pre><span class="n">FOUserAgent</span> <span class="n">userAgent</span> <span class="o">=</span> <span class="n">fopFactory</span><span class="o">.</span><span class="n">newFOUserAgent</span><span class="p">();</span>
+<span class="n">userAgent</span><span class="o">.</span><span class="n">getRendererOptions</span><span class="p">()</span><span class="o">.</span><span class="n">put</span><span class="p">(</span><span class="s">&quot;pdf-x-mode&quot;</span><span class="p">,</span> <span class="s">&quot;PDF/X-3:2003&quot;</span><span class="p">);</span>
+<span class="n">Fop</span> <span class="n">fop</span> <span class="o">=</span> <span class="n">fopFactory</span><span class="o">.</span><span class="n">newFop</span><span class="p">(</span><span class="n">MimeConstants</span><span class="o">.</span><span class="n">MIME_PDF</span><span class="p">,</span> <span class="n">userAgent</span><span class="p">);</span>
+<span class="p">[</span><span class="o">..</span><span class="p">]</span>
+</pre></div>
+
+
+<p>If one of the validation rules of PDF/X is violated, an PDFConformanceException (descendant of RuntimeException) is thrown.</p>
+<h2 id="pdfx-in-action-wzxhzdk16wzxhzdk17">PDF/X in Action <a id="rules"></a></h2>
 <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>
@@ -380,7 +384,7 @@ Fop fop = fopFactory.newFop(MimeConstant
 <p>PDF is forced to version 1.4 if PDF/X-3:2003 is activated.</p>
 </li>
 </ul>
-<h2 id="pdf-profile-compatibility-wzxhzdk17wzxhzdk18">PDF profile compatibility <a id="profile-compatibility"></a></h2>
+<h2 id="pdf-profile-compatibility-wzxhzdk18wzxhzdk19">PDF profile compatibility <a id="profile-compatibility"></a></h2>
 <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>
       

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/releaseNotes_1.1.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/releaseNotes_1.1.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/releaseNotes_1.1.html Tue Dec  4 05:02:22 2012
@@ -347,135 +347,135 @@ $(document).ready(function () {
 <h2 id="changes-to-the-code-base-wzxhzdk2wzxhzdk3">Changes to the Code Base <a id="Changes+to+the+Code+Base"></a></h2>
 <ul>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Update to use of checkstyle-5.5 as default configuration. Remove checkstyle-4.0 configuration. Also, import environment build properties before local properties, so that latter can refer to former. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53083">53083</a> .</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Update to use of checkstyle-5.5 as default configuration. Remove checkstyle-4.0 configuration. Also, import environment build properties before local properties, so that latter can refer to former. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53083">53083</a> .</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Invoke JVM in headless mode from FOP command scripts and JS shell to prevent stealing focus from GUI applications. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50062">50062</a> .</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Invoke JVM in headless mode from FOP command scripts and JS shell to prevent stealing focus from GUI applications. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50062">50062</a> .</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Support list-block in marker, thus preventing NPE. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52763">52763</a> .</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Support list-block in marker, thus preventing NPE. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52763">52763</a> .</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Allow https scheme URI for PDF external action target. Committed by GA. Thanks to Paul Huemer. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51599">51599</a> .</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Allow https scheme URI for PDF external action target. Committed by GA. Thanks to Paul Huemer. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51599">51599</a> .</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Fixed incorrect rejection of fo:wrapper inside fo:inline inside fo:footnote-body. Committed by GA. Thanks to Alberto Simões. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53005">53005</a> .</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Fixed incorrect rejection of fo:wrapper inside fo:inline inside fo:footnote-body. Committed by GA. Thanks to Alberto Simões. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53005">53005</a> .</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Added support for PDF Object Streams. When accessibility is enabled and PDF version 1.5 selected, the structure tree will be stored in object streams in order to reduce the size of the final PDF. Committed by VH. Thanks to Peter Hancock.</p>
+<p><img alt="add" src="../images/add.jpg" /> Added support for PDF Object Streams. When accessibility is enabled and PDF version 1.5 selected, the structure tree will be stored in object streams in order to reduce the size of the final PDF. Committed by VH. Thanks to Peter Hancock.</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Fixed bug that caused a configured and installed SVG font to be stroked, also added an event indicating when fonts are stroked. Committed by MH. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52849">52849</a> .</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Fixed bug that caused a configured and installed SVG font to be stroked, also added an event indicating when fonts are stroked. Committed by MH. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52849">52849</a> .</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Improved support for empty flow-name mapping. Committed by PH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50391">50391</a> .</p>
+<p><img alt="add" src="../images/add.jpg" /> Improved support for empty flow-name mapping. Committed by PH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50391">50391</a> .</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Add support for different flow-name of fo:region-body in FOP Committed by CB. Thanks to Peter Hancock. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50391">50391</a> .</p>
+<p><img alt="add" src="../images/add.jpg" /> Add support for different flow-name of fo:region-body in FOP Committed by CB. Thanks to Peter Hancock. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50391">50391</a> .</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Allow JPEG images to be embedded in an AFP document as is, without being decoded and encoded. Committed by PH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52089">52089</a> .</p>
+<p><img alt="add" src="../images/add.jpg" /> Allow JPEG images to be embedded in an AFP document as is, without being decoded and encoded. Committed by PH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52089">52089</a> .</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Fix for when the last simple-page-master referenced in a page-sequence-master is not chosen when force-page-count=odd. Committed by PH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51962">51962</a> .</p>
+<p><img alt="add" src="../images/add.jpg" /> Fix for when the last simple-page-master referenced in a page-sequence-master is not chosen when force-page-count=odd. Committed by PH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51962">51962</a> .</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Upgraded all tests to JUnit 4. Committed by VH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51928">51928</a> .</p>
+<p><img alt="add" src="../images/add.jpg" /> Upgraded all tests to JUnit 4. Committed by VH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51928">51928</a> .</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Added support for resolution of relative URIs against a specified xml:base during property refinement. Committed by AD. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=48334">48334</a> .</p>
+<p><img alt="add" src="../images/add.jpg" /> Added support for resolution of relative URIs against a specified xml:base during property refinement. Committed by AD. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=48334">48334</a> .</p>
 </li>
 </ul>
 <h3 id="changes-to-the-user-configuration-wzxhzdk4wzxhzdk5">Changes to the User Configuration <a id="Changes+to+the+User+Configuration"></a></h3>
 <ul>
-<li><icon alt="add" src="../images/add.jpg"></icon>Added configuration option to set the version of the output PDF document. Committed by VH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51385">51385</a> .</li>
+<li><img alt="add" src="../images/add.jpg" /> Added configuration option to set the version of the output PDF document. Committed by VH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51385">51385</a> .</li>
 </ul>
 <h3 id="changes-to-the-font-subsystem-wzxhzdk6wzxhzdk7">Changes to the Font Subsystem <a id="Changes+to+the+Font+Subsystem"></a></h3>
 <ul>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Add support for OpenType advanced typographic tables (GDEF, GSUB, GPOS). Committed by GA.</p>
+<p><img alt="add" src="../images/add.jpg" /> Add support for OpenType advanced typographic tables (GDEF, GSUB, GPOS). Committed by GA.</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Changes the way PostScript handles Graphics2D images such that if the language is set to level 3, the image is stored as an embedded file which has no length limit. Previously it was stored as an array which has a implementation limit of 65535 elements. Committed by PH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51760">51760</a> .</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Changes the way PostScript handles Graphics2D images such that if the language is set to level 3, the image is stored as an embedded file which has no length limit. Previously it was stored as an array which has a implementation limit of 65535 elements. Committed by PH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51760">51760</a> .</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Improved support for EBCDIC encoded double byte fonts fo AFP. Committed by PH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51530">51530</a> .</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Improved support for EBCDIC encoded double byte fonts fo AFP. Committed by PH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51530">51530</a> .</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Reinstated support for being able to specify a font cache filepath in the fop user configuration. Committed by AC.</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Reinstated support for being able to specify a font cache filepath in the fop user configuration. Committed by AC.</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Added convenience support for the flushing of the Fop font cache file from the command line. Committed by AC.</p>
+<p><img alt="add" src="../images/add.jpg" /> Added convenience support for the flushing of the Fop font cache file from the command line. Committed by AC.</p>
 </li>
 </ul>
 <h3 id="changes-to-the-image-support-wzxhzdk8wzxhzdk9">Changes to the Image Support <a id="Changes+to+the+Image+Support"></a></h3>
 <ul>
-<li><icon alt="fix" src="../images/fix.jpg"></icon>Support use of ImageLoaderRawPNG decoder in order to prevent re-encoding of PNG images (and unnecssary output file bloat). Committed by GA. Thanks to Luis Bernardo, Matthias Reischenbacher. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=40676">40676</a> .</li>
+<li><img alt="fix" src="../images/fix.jpg" /> Support use of ImageLoaderRawPNG decoder in order to prevent re-encoding of PNG images (and unnecssary output file bloat). Committed by GA. Thanks to Luis Bernardo, Matthias Reischenbacher. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=40676">40676</a> .</li>
 </ul>
 <h3 id="changes-to-the-layout-engine-wzxhzdk10wzxhzdk11">Changes to the Layout Engine <a id="Changes+to+the+Layout+Engine"></a></h3>
 <ul>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Fix for break before (break-before) not respected on blocks nested in inlines. Committed by GA. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=45715">45715</a> .</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Fix for break before (break-before) not respected on blocks nested in inlines. Committed by GA. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=45715">45715</a> .</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Ensure square image is appropriately scaled. Committed by GA. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52514">52514</a> .</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Ensure square image is appropriately scaled. Committed by GA. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52514">52514</a> .</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Add support for complex scripts, including: full bidi support, support for advanced typographic tables, advanced support for number conversion. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=32789">32789</a> , <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49008">49008</a> , <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49687">49687</a> .</p>
+<p><img alt="add" src="../images/add.jpg" /> Add support for complex scripts, including: full bidi support, support for advanced typographic tables, advanced support for number conversion. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=32789">32789</a> , <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49008">49008</a> , <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49687">49687</a> .</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Implemented non-standard behavior for basic-link areas, such that they take into account the heights of their descendants areas. Committed by VH.</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Implemented non-standard behavior for basic-link areas, such that they take into account the heights of their descendants areas. Committed by VH.</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Fix for keep-together does not apply to fo:table-cell. Committed by VH.</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Fix for keep-together does not apply to fo:table-cell. Committed by VH.</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Fix for keep-together on a table containing row-spanning cells that was not honored. Committed by VH.</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Fix for keep-together on a table containing row-spanning cells that was not honored. Committed by VH.</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Fix forpadding-start ignored when table-header/footer is repeated. Committed by VH. Thanks to Matthias Reischenbacher. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50196">50196</a> .</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Fix forpadding-start ignored when table-header/footer is repeated. Committed by VH. Thanks to Matthias Reischenbacher. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50196">50196</a> .</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Fix for correct behavior of keep-together.within-line in case there are nested inlines Committed by AD. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49848">49848</a> .</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Fix for correct behavior of keep-together.within-line in case there are nested inlines Committed by AD. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49848">49848</a> .</p>
 </li>
 </ul>
 <h3 id="changes-to-renderers-output-formats-wzxhzdk12wzxhzdk13">Changes to Renderers (Output Formats) <a id="Changes+to+Renderers+%28Output+Formats%29"></a></h3>
 <ul>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Added possibility to embed TrueType fonts in PostScript. Committed by VH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52338">52338</a> .</p>
+<p><img alt="add" src="../images/add.jpg" /> Added possibility to embed TrueType fonts in PostScript. Committed by VH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52338">52338</a> .</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Add extension to place code just before PostScript %PageTrailer. Committed by GA. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53295">53295</a> .</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Add extension to place code just before PostScript %PageTrailer. Committed by GA. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53295">53295</a> .</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Added support for 128bit encryption in PDF output. Committed by VH. Thanks to Michael Rubin.</p>
+<p><img alt="add" src="../images/add.jpg" /> Added support for 128bit encryption in PDF output. Committed by VH. Thanks to Michael Rubin.</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Added an IFDocumentHandler filter for triggering rendering events. Created an Event that captures an end page event with the page number. Committed by PH.</p>
+<p><img alt="add" src="../images/add.jpg" /> Added an IFDocumentHandler filter for triggering rendering events. Created an Event that captures an end page event with the page number. Committed by PH.</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>AFP GOCA: Changed the way FOP fonts are selected based on Batik's GVT fonts to match the behaviour of PDF/PS output. Committed by JM.</p>
+<p><img alt="fix" src="../images/fix.jpg" /> AFP GOCA: Changed the way FOP fonts are selected based on Batik's GVT fonts to match the behaviour of PDF/PS output. Committed by JM.</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Added option to place AFP NOPs right before the end of a named page group (page-sequence), rather than after the start. Committed by JM.</p>
+<p><img alt="add" src="../images/add.jpg" /> Added option to place AFP NOPs right before the end of a named page group (page-sequence), rather than after the start. Committed by JM.</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Added option for PostScript output to optimize for file size rather than quality. Committed by JM.</p>
+<p><img alt="add" src="../images/add.jpg" /> Added option for PostScript output to optimize for file size rather than quality. Committed by JM.</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>AFP GOCA: Added option to disable GOCA and to control text painting inside GOCA graphics. Committed by JM.</p>
+<p><img alt="add" src="../images/add.jpg" /> AFP GOCA: Added option to disable GOCA and to control text painting inside GOCA graphics. Committed by JM.</p>
 </li>
 <li>
-<p><icon alt="fix" src="../images/fix.jpg"></icon>Increased maximum possible PDF size from 2GB to around 9GB (hard maximum imposed by the PDF specification). Committed by JM.</p>
+<p><img alt="fix" src="../images/fix.jpg" /> Increased maximum possible PDF size from 2GB to around 9GB (hard maximum imposed by the PDF specification). Committed by JM.</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Added support for CIE Lab colors (from XSL-FO 2.0 WD). Committed by JM.</p>
+<p><img alt="add" src="../images/add.jpg" /> Added support for CIE Lab colors (from XSL-FO 2.0 WD). Committed by JM.</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Initial work on spot colors (aka named colors) for PDF output. Committed by JM. Thanks to Patrick Jaromin. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49403">49403</a> .</p>
+<p><img alt="add" src="../images/add.jpg" /> Initial work on spot colors (aka named colors) for PDF output. Committed by JM. Thanks to Patrick Jaromin. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49403">49403</a> .</p>
 </li>
 <li>
-<p><icon alt="add" src="../images/add.jpg"></icon>Added ability to embed an external AFP page segment resource file (AFP output only). Committed by JM. Thanks to Peter Hancock. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49379">49379</a> .</p>
+<p><img alt="add" src="../images/add.jpg" /> Added ability to embed an external AFP page segment resource file (AFP output only). Committed by JM. Thanks to Peter Hancock. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49379">49379</a> .</p>
 </li>
 </ul></div>
       </div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/servlets.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/servlets.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/servlets.html Tue Dec  4 05:02:22 2012
@@ -418,11 +418,12 @@ This example servlet should not be used 
 
 <span class="sr">//</span><span class="n">Send</span> <span class="n">content</span> <span class="n">to</span> <span class="n">Browser</span>
 <span class="n">response</span><span class="o">.</span><span class="n">getOutputStream</span><span class="p">()</span><span class="o">.</span><span class="nb">write</span><span class="p">(</span><span class="n">out</span><span class="o">.</span><span class="n">toByteArray</span><span class="p">());</span>
-<span class="n">response</span><span class="o">.</span><span class="n">getOutputStream</span><span class="p">()</span><span class="o">.</span><span class="n">flush</span><span class="p">();</span><span class="n">Buffering</span> <span class="n">the</span> <span class="n">generated</span> <span class="n">PDF</span> <span class="n">in</span> <span class="n">a</span> <span class="n">ByteArrayOutputStream</span> <span class="n">is</span> <span class="n">done</span> <span class="n">to</span> <span class="n">avoid</span> <span class="n">potential</span> <span class="n">problems</span> <span class="n">with</span> <span class="n">the</span> <span class="n">Acrobat</span> <span class="n">Reader</span> <span class="n">Plug</span><span class="o">-</span><span class="n">in</span> <span class="n">in</span> <span class="n">Microsoft</span> <span class="n">Internet</span> <span class="n">Explorer</span><span class="o">.</span>
+<span class="n">response</span><span class="o">.</span><span class="n">getOutputStream</span><span class="p">()</span><span class="o">.</span><span class="n">flush</span><span class="p">();</span>
 </pre></div>
 
 
-<p>The <code>Source</code> instance used above is simply an example. If you have to read the XML from a string, supply a <code>new StreamSource(new
+<p>Buffering the generated PDF in a ByteArrayOutputStream is done to avoid potential problems with the Acrobat Reader Plug-in in Microsoft Internet Explorer.
+The <code>Source</code> instance used above is simply an example. If you have to read the XML from a string, supply a <code>new StreamSource(new
           StringReader(xmlstring))</code> . Constructing and reparsing an XML string is generally less desirable than using a SAXSource if you generate your XML. You can alternatively supply a DOMSource as well. You may also use dynamically generated XSL if you like.</p>
 <p>Because you have an explicit <code>Transformer</code> object, you can also use it to explicitely set parameters for the transformation run.</p>
 <h3 id="custom-configuration-wzxhzdk19wzxhzdk20">Custom configuration <a id="cfg"></a></h3>



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


Mime
View raw message