xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r835978 [4/16] - in /websites/staging/xmlgraphics/trunk/content: ./ batik/ batik/dev/ batik/tools/ batik/using/ batik/using/scripting/ commons/ fop/ fop/0.95/ fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/ fop/trunk/
Date Wed, 24 Oct 2012 04:26:12 GMT
Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/fonts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/fonts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/fonts.html Wed Oct 24 04:26:06 2012
@@ -332,7 +332,7 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk1-fop-fonts">Apache&trade; FOP: Fonts</h1>
 <p><version>$Revision: 1298724 $</version><authors><person email="" name="Jeremias Märki"></person><person email="" name="Tore Engvig"></person><person email="" name="Adrian Cumiskey"></person><person email="" name="Max Berger"></person></authors></p>
-<h2 id="summary-wzxhzdk14wzxhzdk15">Summary  <a id="intro"></a></h2>
+<h2 id="summary-wzxhzdk14wzxhzdk15">Summary <a id="intro"></a></h2>
 <p>The following table summarizes the font capabilities of the various FOP renderers:</p>
 <table>
 <thead>
@@ -410,15 +410,15 @@ $(document).ready(function () {
 </tr>
 </tbody>
 </table>
-<h2 id="base-14-fonts-wzxhzdk16wzxhzdk17">Base-14 Fonts  <a id="Base-14+Fonts"></a></h2>
+<h2 id="base-14-fonts-wzxhzdk16wzxhzdk17">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>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-wzxhzdk18wzxhzdk19">Missing Fonts  <a id="Missing+Fonts"></a></h2>
+<h2 id="missing-fonts-wzxhzdk18wzxhzdk19">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="java2dawtoperating-system-fonts-wzxhzdk20wzxhzdk21">Java2D/AWT/Operating System Fonts  <a id="awt"></a></h2>
+<h2 id="java2dawtoperating-system-fonts-wzxhzdk20wzxhzdk21">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-wzxhzdk22wzxhzdk23">Custom Fonts  <a id="custom"></a></h2>
+<h2 id="custom-fonts-wzxhzdk22wzxhzdk23">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>Prior to FOP version 0.94, 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 is still necessary if you want to use a TrueType Collection (*.ttc). Direct support for TrueType collections may be added later. Furthermore, the XML font metrics files are still required if you don't want to embed, but only reference a font.</p>
 <p>Basic information about fonts can be found at:</p>
@@ -430,7 +430,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="basic-font-configuration-wzxhzdk24wzxhzdk25">Basic font configuration  <a id="basics"></a></h2>
+<h2 id="basic-font-configuration-wzxhzdk24wzxhzdk25">Basic font configuration <a id="basics"></a></h2>
 <p>If you want FOP to use custom fonts, you need to tell it where to find them. This is done in the configuration file and once per renderer (because each output format is a little different). In the basic form, you can either tell FOP to find your operating system fonts or you can specify directories that it will search for support fonts. These fonts will then automatically be registered.</p>
 <p><fonts>
   <!-- register all the fonts found in a directory -->
@@ -441,9 +441,9 @@ $(document).ready(function () {
 <p><!-- automatically detect operating system installed fonts -->
   <auto-detect/><br />
 </fonts>Review the documentation for <a href="configuration.html">FOP Configuration</a> for instructions on making the FOP configuration available to FOP when it runs. Otherwise, FOP has no way of finding your custom font information. It is currently not possible to easily configure fonts from Java code.</p>
-<h1 id="advanced-font-configuration-wzxhzdk36wzxhzdk37">Advanced font configuration  <a id="advanced"></a></h1>
+<h1 id="advanced-font-configuration-wzxhzdk36wzxhzdk37">Advanced font configuration <a id="advanced"></a></h1>
 <p>The instructions found above should be sufficient for most users. Below are some additional instructions in case the basic font configuration doesn't lead to the desired results.</p>
-<h3 id="type-1-font-metrics-wzxhzdk38wzxhzdk39">Type 1 Font Metrics # <a id="type1-metrics"></a></h3>
+<h3 id="type-1-font-metrics-wzxhzdk38wzxhzdk39">Type 1 Font Metrics <a id="type1-metrics"></a></h3>
 <p>FOP includes PFMReader, which reads the PFM file that normally comes with a Type 1 font, and generates an appropriate font metrics file for it. To use it, run the class org.apache.fop.fonts.apps.PFMReader:</p>
 <p>Windows:
 java -cp build\fop.jar;lib\avalon-framework.jar;lib\commons-logging.jar;lib\commons-io.jar
@@ -456,7 +456,7 @@ PFMReader [options]:</p>
 <li><strong>-fn <fontname></strong> By default, FOP uses the fontname from the .pfm file when embedding the font. Use the "-fn" option to override this name with one you have chosen. This may be useful in some cases to ensure that applications using the output document (Acrobat Reader for example) use the embedded font instead of a local font with the same name.
 The classpath in the above example has been simplified for readability. You will have to adjust the classpath to the names of the actual JAR files in the lib directory. xml-apis.jar, xercesImpl.jar, xalan.jar and serializer.jar are not necessary for JDK version 1.4 or later.The tool will construct some values (FontBBox, StemV and ItalicAngle) based on assumptions and calculations which are only an approximation to the real values. FontBBox and Italic Angle can be found in the human-readable part of the PFB file or in the AFM file. The PFMReader tool does not yet interpret PFB or AFM files, so if you want to be correct, you may have to adjust the values in the XML file manually. The constructed values however appear to have no visible influence.</li>
 </ul>
-<h2 id="truetype-font-metrics-wzxhzdk40wzxhzdk41">TrueType Font Metrics # <a id="truetype-metrics"></a></h2>
+<h2 id="truetype-font-metrics-wzxhzdk40wzxhzdk41">TrueType Font Metrics <a id="truetype-metrics"></a></h2>
 <p>FOP includes TTFReader, which reads the TTF file and generates an appropriate font metrics file for it. Use it in a similar manner to PFMReader. For example, to create such a metrics file in Windows from the TrueType font at c:\myfonts\cmr10.ttf:
 java -cp build\fop.jar;lib\avalon-framework.jar;lib\commons-logging.jar;lib\commons-io.jar
           org.apache.fop.fonts.apps.TTFReader [options]
@@ -501,7 +501,7 @@ TTFReader [options]:</p>
 <td></td>
 </tr>
 <tr>
-<td>## TrueType Collections Font Metrics # <a id="truetype-collections-metrics"></a></td>
+<td>## TrueType Collections Font Metrics <a id="truetype-collections-metrics"></a></td>
 <td></td>
 <td></td>
 </tr>
@@ -513,7 +513,7 @@ TTFReader [options]:</p>
 java -cp build\fop.jar;lib\avalon-framework.jar;lib\commons-logging.jar;lib\commons-io.jar
           org.apache.fop.fonts.apps.TTFReader -ttcname "MS Mincho"
           msmincho.ttc msminch.xml</p>
-<h2 id="register-fonts-with-fop-wzxhzdk42wzxhzdk43">Register Fonts with FOP # <a id="register"></a></h2>
+<h2 id="register-fonts-with-fop-wzxhzdk42wzxhzdk43">Register Fonts with FOP <a id="register"></a></h2>
 <p>You must tell FOP how to find and use the font metrics files by registering them in the <a href="configuration.html">FOP Configuration</a> . Add entries for your custom fonts, regardless of font type, to the configuration file in a manner similar to the following:</p>
 <p><fonts>
   <!-- register a particular font -->
@@ -564,7 +564,7 @@ java -cp build\fop.jar;lib\avalon-framew
 <p>If relative URLs are specified, they are evaluated relative to the value of the "font-base" setting. If there is no "font-base" setting, the fonts are evaluated relative to the base directory.</p>
 </li>
 </ul>
-<h3 id="auto-detect-and-auto-embedd-feature-wzxhzdk58wzxhzdk59">Auto-Detect and auto-embedd feature # <a id="autodetect"></a></h3>
+<h3 id="auto-detect-and-auto-embedd-feature-wzxhzdk58wzxhzdk59">Auto-Detect and auto-embedd 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>
@@ -574,7 +574,7 @@ Manifest-Version: 1.0</p>
 
 
 <p>This feature allows you to create JAR files containing fonts. The JAR files can be added to fop by providem them in the classpath, e.g. copying them into the lib/ directory.</p>
-<h3 id="embedding-wzxhzdk60wzxhzdk61">Embedding # <a id="embedding"></a></h3>
+<h3 id="embedding-wzxhzdk60wzxhzdk61">Embedding <a id="embedding"></a></h3>
 <p>The PostScript renderer does not yet support TrueType fonts, but can embed Type 1 fonts.The font is simply embedded into the PDF file, it is not converted.
 Font embedding is enabled in the userconfig.xml file and controlled by the embed-url attribute. If you don't specify the embed-url attribute the font will not be embedded, but will only be referenced.
 <warning>Omitting the embed-url attribute for CID-encoded TrueType fonts will currently produce invalid PDF files! If you create the XML font metric file using the "-enc ansi" option, you can omit the embed-url attribute for TrueType fonts but you're restricted to the WinAnsi character set.</warning>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/graphics.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/graphics.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/graphics.html Wed Oct 24 04:26:06 2012
@@ -332,7 +332,7 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-graphics-formats">Apache&trade; FOP: Graphics Formats</h1>
 <p><version>$Revision: 1298724 $</version></p>
-<h2 id="introduction-wzxhzdk3wzxhzdk4">Introduction  <a id="introduction"></a></h2>
+<h2 id="introduction-wzxhzdk3wzxhzdk4">Introduction <a id="introduction"></a></h2>
 <p>After the Apache&trade; FOP 0.94 release, the image handling subsystem has been rewritten in order to improve the range of supported images and image subtypes, to lower the overall memory consumption when handling images, to produce smaller output files and to increase the performance in certain areas. Of course, this causes a few changes most of which the user will probably not notice. The most important changes are:</p>
 <ul>
 <li>
@@ -346,7 +346,7 @@ $(document).ready(function () {
 </li>
 </ul>
 <p>The actual <a href="http://xmlgraphics.apache.org/commons/image-loader.html">image loading framework</a> no longer resides in Apache FOP, but was instead placed in <a href="http://xmlgraphics.apache.org/commons/">XML Graphics Commons</a> .</p>
-<h2 id="overview-of-graphics-support-wzxhzdk6wzxhzdk7">Overview of Graphics Support  <a id="support-overview"></a></h2>
+<h2 id="overview-of-graphics-support-wzxhzdk6wzxhzdk7">Overview of Graphics Support <a id="support-overview"></a></h2>
 <p>The table below summarizes the <em>theoretical</em> support for graphical formats within FOP. In other words, within the constraints of the limitations listed here, these formats <em>should</em> work. However, many of them have not been tested, and there may be limitations that have not yet been discovered or documented. The packages needed to support some formats are not included in the FOP distribution and must be installed separately. Follow the links in the "Support Through" columns for more details.</p>
 <table>
 <thead>
@@ -424,7 +424,7 @@ $(document).ready(function () {
  <a href="http://jai-imageio.dev.java.net/">JAI Image I/O Tools</a> is not the same as the <a href="http://java.sun.com/javase/technologies/desktop/media/jai/">JAI library</a> ! The former simply exposes JAI's codecs using the Image&nbsp;I/O API but does not include all the image manipulation functionality.</p>
 </li>
 </ul>
-<h2 id="map-of-supported-image-formats-by-output-format-wzxhzdk8wzxhzdk9">Map of supported image formats by output format # <a id="format-map"></a></h2>
+<h2 id="map-of-supported-image-formats-by-output-format-wzxhzdk8wzxhzdk9">Map of supported image formats by output format <a id="format-map"></a></h2>
 <p>Not all image formats are supported for all output formats! For example, while you can use EPS (Encapsulated PostScript) files when you generate PostScript output, this format will not be supported by any other output format. Here's an overview of which image formats are supported by which output format:</p>
 <table>
 <thead>
@@ -531,12 +531,12 @@ $(document).ready(function () {
 <p>[2]: Supported without the need to decode the image, but only for certain subtypes.</p>
 </li>
 </ul>
-<h2 id="graphics-packages-wzxhzdk10wzxhzdk11">Graphics Packages  <a id="packages"></a></h2>
-<h3 id="xml-graphics-commons-native-wzxhzdk12wzxhzdk13">XML Graphics Commons Native # <a id="native"></a></h3>
+<h2 id="graphics-packages-wzxhzdk10wzxhzdk11">Graphics Packages <a id="packages"></a></h2>
+<h3 id="xml-graphics-commons-native-wzxhzdk12wzxhzdk13">XML Graphics Commons Native <a id="native"></a></h3>
 <p><a href="http://xmlgraphics.apache.org/commons/">XML Graphics Commons</a> supports a number of graphic file formats natively as basic functionality: all bitmap formats for which there are Image I/O codecs available (JPEG, PNG, GIF, TIFF, etc.), EPS and EMF.</p>
-<h3 id="fop-native-wzxhzdk14wzxhzdk15">FOP Native # <a id="fop-native"></a></h3>
+<h3 id="fop-native-wzxhzdk14wzxhzdk15">FOP Native <a id="fop-native"></a></h3>
 <p>FOP has no native image plug-ins for the image loading framework of its own but currently hosts the Batik-dependent SVG and WMF plug-ins until they can be moved to <a href="http://xmlgraphics.apache.org/batik/">Apache Batik</a> .</p>
-<h3 id="apache-batik-wzxhzdk16wzxhzdk17">Apache Batik # <a id="batik"></a></h3>
+<h3 id="apache-batik-wzxhzdk16wzxhzdk17">Apache Batik <a id="batik"></a></h3>
 <p><a href="http://xmlgraphics.apache.org/batik/">Apache Batik</a> will later receive the SVG and WMF plug-ins for the image loading framework that are currently hosted inside FOP.</p>
 <p>Current FOP distributions include a distribution of the <a href="http://xmlgraphics.apache.org/batik/">Apache Batik</a> . Because Batik's API changes frequently, it is highly recommended that you use the version that ships with FOP, at least when running FOP.
 <warning>Batik must be run in a graphical environment.</warning>
@@ -553,23 +553,23 @@ Batik must be run in a graphical environ
 <p>Install a toolkit which emulates AWT without the need for an underlying X server. One example is the <a href="http://www.eteks.com/pja/en">PJA toolkit</a> , which is free and comes with detailed installation instructions.</p>
 </li>
 </ul>
-<h3 id="image-io-wzxhzdk20wzxhzdk21">Image I/O # <a id="imageio"></a></h3>
+<h3 id="image-io-wzxhzdk20wzxhzdk21">Image I/O <a id="imageio"></a></h3>
 <p>The image loading framework in <a href="http://xmlgraphics.apache.org/commons/">XML Graphics Commons</a> provides a wrapper to load images through the <a href="http://java.sun.com/j2se/1.4.2/docs/guide/imageio/index.html">JDK's Image I/O API</a> (JSR 015). Image I/O allows to dynamically add additional image codecs. An example of such an add-on library are the <a href="http://java.sun.com/products/java-media/jai/">JAI Image I/O Tools</a> available from Sun.</p>
-<h2 id="details-on-image-formats-wzxhzdk22wzxhzdk23">Details on image formats  <a id="image-formats"></a></h2>
-<h3 id="bmp-wzxhzdk24wzxhzdk25">BMP # <a id="bmp"></a></h3>
+<h2 id="details-on-image-formats-wzxhzdk22wzxhzdk23">Details on image formats <a id="image-formats"></a></h2>
+<h3 id="bmp-wzxhzdk24wzxhzdk25">BMP <a id="bmp"></a></h3>
 <p>BMP images are supported through an Image I/O codec. There may be limitations of the codec which are outside the control of Apache FOP.</p>
-<h3 id="emf-wzxhzdk26wzxhzdk27">EMF # <a id="emf"></a></h3>
+<h3 id="emf-wzxhzdk26wzxhzdk27">EMF <a id="emf"></a></h3>
 <p>Windows Enhanced Metafiles (EMF) are only supported in RTF output where they are embedded without decoding.</p>
-<h3 id="eps-wzxhzdk28wzxhzdk29">EPS # <a id="eps"></a></h3>
+<h3 id="eps-wzxhzdk28wzxhzdk29">EPS <a id="eps"></a></h3>
 <p>Apache FOP allows to use EPS files when generating PostScript output only.</p>
 <p>Other output targets can't be supported at the moment because FOP lacks a PostScript interpreter. Furthermore, FOP is currently not able to parse the preview bitmaps sometimes contained in EPS files.</p>
-<h3 id="gif-wzxhzdk30wzxhzdk31">GIF # <a id="gif"></a></h3>
+<h3 id="gif-wzxhzdk30wzxhzdk31">GIF <a id="gif"></a></h3>
 <p>GIF images are supported through an Image&nbsp;I/O codec. Transparency is supported but not guaranteed to work with every output format.</p>
-<h3 id="jpeg-wzxhzdk33wzxhzdk34">JPEG # <a id="jpeg"></a></h3>
+<h3 id="jpeg-wzxhzdk33wzxhzdk34">JPEG <a id="jpeg"></a></h3>
 <p>FOP native support (i.e. the handling of undecoded images) of JPEG does not include all variants, especially those containing unusual color lookup tables and color profiles. If you have trouble with a JPEG image in FOP, try opening it with an image processing program (such as Photoshop or Gimp) and then saving it. Specifying 24-bit color output may also help. For the PDF and PostScript renderers most JPEG images can be passed through without decompression. User reports indicate that grayscale, RGB, and CMYK color spaces are all rendered properly. However, for other output formats, the JPEG images have to be decompressed. Tests have shown that there are some limitation in some Image&nbsp;I/O codecs concerning images in the CMYK color space. Work-arounds are in place but may not always work as expected.</p>
-<h3 id="png-wzxhzdk36wzxhzdk37">PNG # <a id="png"></a></h3>
+<h3 id="png-wzxhzdk36wzxhzdk37">PNG <a id="png"></a></h3>
 <p>PNG images are supported through an Image&nbsp;I/O codec. Transparency is supported but not guaranteed to work with every output format.</p>
-<h3 id="svg-wzxhzdk39wzxhzdk40">SVG # <a id="svg"></a></h3>
+<h3 id="svg-wzxhzdk39wzxhzdk40">SVG <a id="svg"></a></h3>
 <h4 id="introduction-wzxhzdk41wzxhzdk42">Introduction ## <a id="svg-intro"></a></h4>
 <p>FOP uses <a href="#batik">Apache Batik</a> for SVG support. This format can be handled as an <code>fo:instream-foreign-object</code> or in a separate file referenced with <code>fo:external-graphic</code> .
 Batik's SVG Rasterizer utility may also be used to convert standalone SVG documents into PDF. For more information please see the <a href="http://xmlgraphics.apache.org/batik/svgrasterizer.html">SVG Rasterizer documentation</a> on the Batik site.</p>
@@ -599,18 +599,18 @@ Batik's SVG Rasterizer utility may also 
 <p>Uniform transparency for images and other SVG elements that are converted into a raster graphic are not drawn properly in PDF. The image is opaque.</p>
 </li>
 </ul>
-<h3 id="tiff-wzxhzdk51wzxhzdk52">TIFF # <a id="tiff"></a></h3>
+<h3 id="tiff-wzxhzdk51wzxhzdk52">TIFF <a id="tiff"></a></h3>
 <p>FOP can embed TIFF images without decompression into PDF, PostScript and AFP if they have either CCITT T.4, CCITT T.6, or JPEG compression. Otherwise, a TIFF-capable Image&nbsp;I/O codec is necessary for decoding the image.</p>
 <p>There may be some limitation concerning images in the CMYK color space.</p>
-<h3 id="wmf-wzxhzdk54wzxhzdk55">WMF # <a id="wmf"></a></h3>
+<h3 id="wmf-wzxhzdk54wzxhzdk55">WMF <a id="wmf"></a></h3>
 <p>Windows Metafiles (WMF) are supported through classes in <a href="http://xmlgraphics.apache.org/batik/">Apache Batik</a> . At the moment, support for this format is experimental and may not always work as expected.</p>
-<h2 id="graphics-resolution-wzxhzdk56wzxhzdk57">Graphics Resolution  <a id="resolution"></a></h2>
+<h2 id="graphics-resolution-wzxhzdk56wzxhzdk57">Graphics Resolution <a id="resolution"></a></h2>
 <p>Some bitmapped image file formats store a dots-per-inch (dpi) or other resolution values. FOP tries to use this resolution information whenever possible to determine the image's intrinsic size. This size is used during the layout process when it is not superseded by an explicit size on fo:external-graphic (content-width and content-height properties).</p>
 <p>Please note that not all images contain resolution information. If it's not available the source resolution set on the FopFactory (or through the user configuration XML) is used. The default here is 72 dpi.</p>
 <p>Bitmap images are generally embedded into the output format at their original resolution (as is). No resampling of the image is performed. Explicit resampling is on our wishlist, but hasn't been implemented, yet. Bitmaps included in SVG graphics may be resampled to the resolution specified in the "target resolution" setting in the <a href="configuration.html">configuration</a> if SVG filters are applied. This can be used as a work-around to resample images in FO documents.</p>
-<h2 id="page-selection-for-multi-page-formats-wzxhzdk58wzxhzdk59">Page selection for multi-page formats  <a id="page-selection"></a></h2>
+<h2 id="page-selection-for-multi-page-formats-wzxhzdk58wzxhzdk59">Page selection for multi-page formats <a id="page-selection"></a></h2>
 <p>Some image formats such as TIFF support multiple pages/sub-images per file. You can select a particular page using a special URI fragment in the form: <uri>#page=<nr> (for example: <code>http://localhost/images/myimage.tiff#page=3</code> )</p>
-<h2 id="image-caching-wzxhzdk62wzxhzdk63">Image caching  <a id="caching"></a></h2>
+<h2 id="image-caching-wzxhzdk62wzxhzdk63">Image caching <a id="caching"></a></h2>
 <p>FOP caches images between runs. There is one cache per FopFactory instance. The URI is used as a key to identify images which means that when a particular URI appears again, the image is taken from the cache. If you have a servlet that generates a different image each time it is called with the same URI you need to use a constantly changing dummy parameter on the URI to avoid caching.</p>
 <p>The image cache has been improved considerably in the redesigned code. Therefore, resetting the image cache should be a thing of the past. If you still experience OutOfMemoryErrors, please notify us.</p>
 <p>If all else fails, the image cache can be cleared like this: <code>fopFactory.getImageManager().getCache().clearCache();</code> </p></div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/hyphenation.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/hyphenation.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/hyphenation.html Wed Oct 24 04:26:06 2012
@@ -332,18 +332,18 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-hyphenation">Apache&trade; FOP: Hyphenation</h1>
 <p><version>$Revision: 1298724 $</version></p>
-<h2 id="hyphenation-support-wzxhzdk3wzxhzdk4">Hyphenation Support  <a id="support"></a></h2>
-<h3 id="introduction-wzxhzdk5wzxhzdk6">Introduction # <a id="intro"></a></h3>
+<h2 id="hyphenation-support-wzxhzdk3wzxhzdk4">Hyphenation Support <a id="support"></a></h2>
+<h3 id="introduction-wzxhzdk5wzxhzdk6">Introduction <a id="intro"></a></h3>
 <p>Apache&trade; FOP uses Liang's hyphenation algorithm, well known from TeX. It needs language specific pattern and other data for operation.</p>
 <p>Because of <a href="#license-issues">licensing issues</a> (and for convenience), all hyphenation patterns for FOP are made available through the <a href="http://offo.sourceforge.net/hyphenation/index.html">Objects For Formatting Objects</a> project.
 If you have made improvements to an existing FOP hyphenation pattern, or if you have created one from scratch, please consider contributing these to OFFO so that they can benefit other FOP users as well. Please inquire on the <a href="../maillist.html#fop-user">FOP User mailing list</a> .</p>
-<h2 id="license-issues-wzxhzdk8wzxhzdk9">License Issues # <a id="license-issues"></a></h2>
+<h2 id="license-issues-wzxhzdk8wzxhzdk9">License Issues <a id="license-issues"></a></h2>
 <p>Many of the hyphenation files distributed with TeX and its offspring are licenced under the <a href="http://www.latex-project.org/lppl.html">LaTeX Project Public License (LPPL)</a> , which prevents them from being distributed with Apache software. The LPPL puts restrictions on file names in redistributed derived works which we feel can't guarantee. Some hyphenation pattern files have other or additional restrictions, for example against use for commercial purposes.</p>
 <p>Although Apache FOP cannot redistribute hyphenation pattern files that do not conform with its license scheme, that does not necessarily prevent users from using such hyphenation patterns with FOP. However, it does place on the user the responsibility for determining whether the user can rightly use such hyphenation patterns under the hyphenation pattern license.
 <warning>The user is responsible to settle license issues for hyphenation pattern files that are obtained from non-Apache sources.</warning></p>
-<h2 id="sources-of-custom-hyphenation-pattern-files-wzxhzdk12wzxhzdk13">Sources of Custom Hyphenation Pattern Files # <a id="sources"></a></h2>
+<h2 id="sources-of-custom-hyphenation-pattern-files-wzxhzdk12wzxhzdk13">Sources of Custom Hyphenation Pattern Files <a id="sources"></a></h2>
 <p>The most important source of hyphenation pattern files is the <a href="http://www.ctan.org/tex-archive/language/hyphenation/">CTAN TeX Archive</a> .</p>
-<h3 id="installing-custom-hyphenation-patterns-wzxhzdk14wzxhzdk15">Installing Custom Hyphenation Patterns # <a id="install"></a></h3>
+<h3 id="installing-custom-hyphenation-patterns-wzxhzdk14wzxhzdk15">Installing Custom Hyphenation Patterns <a id="install"></a></h3>
 <p>To install a custom hyphenation pattern for use with FOP:</p>
 <ol>
 <li>
@@ -382,7 +382,7 @@ and run Ant with build target <code>jar-
 </li>
 </ol>
 <p><warning>Either of these three options will ensure hyphenation is working when using FOP from the command-line. If FOP is being embedded, remember to add the location(s) of the hyphenation JAR(s) to the CLASSPATH (option 1 and 2) or to set the <a href="configuration.html#hyphenation-dir"><hyphenation-dir></a> configuration option programmatically (option 3).</warning></p>
-<h1 id="hyphenation-patterns-wzxhzdk19wzxhzdk20">Hyphenation Patterns  <a id="patterns"></a></h1>
+<h1 id="hyphenation-patterns-wzxhzdk19wzxhzdk20">Hyphenation Patterns <a id="patterns"></a></h1>
 <p>If you would like to build your own hyphenation pattern files, or modify existing ones, this section will help you understand how to do so. Even when creating a pattern file from scratch, it may be beneficial to start with an existing file and modify it. See <a href="http://offo.sourceforge.net/hyphenation/index.html">OFFO's Hyphenation page</a> for examples. Here is a brief explanation of the contents of FOP's hyphenation patterns:
 <warning>The remaining content of this section should be considered "draft" quality. It was drafted from theoretical literature, and has not been tested against actual FOP behavior. It may contain errors or omissions. Do not rely on these instructions without testing everything stated here. If you use these instructions, please provide feedback on the <a href="../maillist.html#fop-user">FOP User mailing list</a> , either confirming their accuracy, or raising specific problems that we can address.</warning></p>
 <ul>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/index.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/index.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/index.html Wed Oct 24 04:26:06 2012
@@ -332,12 +332,12 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-version-095">Apache&trade; FOP Version 0.95</h1>
 <p><version>$Revision: 1298724 $</version></p>
-<h2 id="introduction-wzxhzdk3wzxhzdk4">Introduction  <a id="intro"></a></h2>
+<h2 id="introduction-wzxhzdk3wzxhzdk4">Introduction <a id="intro"></a></h2>
 <p>The Apache&trade; FOP team is proud to present to you this production quality release. We're still in the process of adding new features. We welcome any feedback you might have and even more, any other form of help to get the project forward.</p>
 <p>This sixth release contains many bug fix release and new features compared to 0.94. To see what has changed since the last release, please visit the <a href="changes_0.95.html">Changes Page</a> and the <a href="releaseNotes_0.95.html">Release Notes</a> .</p>
-<h2 id="upgrading-from-an-earlier-version-wzxhzdk6wzxhzdk7">Upgrading from an earlier version  <a id="upgrading"></a></h2>
+<h2 id="upgrading-from-an-earlier-version-wzxhzdk6wzxhzdk7">Upgrading from an earlier version <a id="upgrading"></a></h2>
 <p>If you're upgrading to this version from an earlier version of FOP, please read the information contained on the <a href="upgrading.html">Upgrading page</a> !</p>
-<h2 id="download-wzxhzdk8wzxhzdk9">Download  <a id="download"></a></h2>
+<h2 id="download-wzxhzdk8wzxhzdk9">Download <a id="download"></a></h2>
 <p>To download this version, please visit the <a href="../download.html">download page</a> .</p></div>
       </div>
       

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/intermediate.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/intermediate.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/intermediate.html Wed Oct 24 04:26:06 2012
@@ -333,10 +333,10 @@ $(document).ready(function () {
       	<div class="section-content"><h1 id="apachewzxhzdk1-fop-intermediate-format">Apache&trade; FOP: Intermediate Format</h1>
 <p><version>$Revision: 1298724 $</version>
 Please note that the intermediate format is an <strong>advanced feature</strong> and can be ignored by most users of Apache&trade; FOP.</p>
-<h1 id="introduction-wzxhzdk5wzxhzdk6">Introduction  <a id="introduction"></a></h1>
+<h1 id="introduction-wzxhzdk5wzxhzdk6">Introduction <a id="introduction"></a></h1>
 <p>The intermediate format (IF) is a proprietary XML format that represents the area tree generated by the layout engine. The area tree is conceptually defined in the <a href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice1.html#section-N742-Formatting">XSL-FO specification in chapter 1.1.2</a> . The IF can be generated through the area tree XML Renderer (the XMLRenderer).</p>
 <p>The intermediate format can be used to generate intermediate documents that are modified before they are finally rendered to their ultimate output format. Modifications include adjusting and changing trait values, adding or modifying area objects, inserting prefabricated pages, overlays, imposition (n-up, rotation, scaling etc.). Multiple IF files can be combined to a single output file.</p>
-<h2 id="usage-of-the-intermediate-format-wzxhzdk7wzxhzdk8">Usage of the Intermediate Format  <a id="usage"></a></h2>
+<h2 id="usage-of-the-intermediate-format-wzxhzdk7wzxhzdk8">Usage of the Intermediate Format <a id="usage"></a></h2>
 <p>As already mentioned, the IF is generated by using the <strong>XMLRenderer</strong> (MIME type: <strong>application/X-fop-areatree</strong> ). So, you basically set the right MIME type for the output format and process your FO files as if you would create a PDF file. However, there is an important detail to consider: The various Renderers don't all use the same font sources. To be able to create the right area tree for the ultimate output file, you need to create the IF file using the right font setup. This is achieved by telling the XMLRenderer to mimic another renderer. This is done by calling the XMLRenderer's mimicRenderer() method with an instance of the ultimate target renderer as the single parameter. This has a consequence: An IF file rendered with the Java2DRenderer may not look as expected when it was actually generated for the PDF renderer. For renderers that use the same font setup, this restriction does not apply (PDF and PS, for example). Generating the inte
 rmediate format file is the first step.</p>
 <p>The second step is to reparse the IF file using the <strong>AreaTreeParser</strong> which is found in the org.apache.fop.area package. The pages retrieved from the IF file are added to an AreaTreeModel instance from where they are normally rendered using one of the available Renderer implementations. You can find examples for the IF processing in the <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/intermediate/"></a> directory in the FOP distribution</p>
 <p>The basic pattern to parse the IF format looks like this:</p>
@@ -368,11 +368,11 @@ try {
 }
 This example simply reads an IF file and renders it to a PDF file. Please note, that in normal FOP operation you're shielded from having to instantiate the FontInfo object yourself. This is normally a task of the AreaTreeHandler which is not present in this scenario. The same applies to the AreaTreeModel instance, in this case an instance of a subclass called RenderPagesModel. RenderPagesModel is ideal in this case as it has very little overhead processing the individual pages. An important line in the example is the call to <code>endDocument()</code> on the AreaTreeModel. This lets the Renderer know that the processing is now finished.</p>
 <p>The intermediate format can also be used from the <a href="running.html#standalone-start">command-line</a> by using the "-atin" parameter for specifying the area tree XML as input file. You can also specify a "mimic renderer" by inserting a MIME type between "-at" and the output file.</p>
-<h3 id="concatenating-documents-wzxhzdk9wzxhzdk10">Concatenating Documents # <a id="concat"></a></h3>
+<h3 id="concatenating-documents-wzxhzdk9wzxhzdk10">Concatenating Documents <a id="concat"></a></h3>
 <p>This initial example is obviously not very useful. It would be faster to create the PDF file directly. As the <a href="http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/examples/embedding/java/embedding/intermediate/ExampleConcat.java">ExampleConcat.java</a> example shows you can easily parse multiple IF files in a row and add the parsed pages to the same AreaTreeModel instance which essentially concatenates all the input document to one single output document.</p>
-<h3 id="modifying-documents-wzxhzdk11wzxhzdk12">Modifying Documents # <a id="modifying"></a></h3>
+<h3 id="modifying-documents-wzxhzdk11wzxhzdk12">Modifying Documents <a id="modifying"></a></h3>
 <p>One of the most important use cases for the intermediate format is obviously modifying the area tree XML before finally rendering it to the target format. You can easily use XSLT to process the IF file according to your needs. Please note, that we will currently not formally describe the intermediate format. You need to have a good understanding its structure so you don't create any non-parseable files. We may add an XML Schema and more detailed documentation at a later time. You're invited to help us with that.</p>
-<h3 id="advanced-use-wzxhzdk13wzxhzdk14">Advanced Use # <a id="advanced"></a></h3>
+<h3 id="advanced-use-wzxhzdk13wzxhzdk14">Advanced Use <a id="advanced"></a></h3>
 <p>The generation of the intermediate format as well as it parsing process has been designed to allow for maximum flexibility and optimization. Please note that you can call <code>setTransformerHandler()</code> on XMLRenderer to give the XMLRenderer your own TransformerHandler instance in case you would like to do custom serialization (to a W3C DOM, for example) and/or to directly modify the area tree using XSLT. The AreaTreeParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to to start the parsing process (see <code>getContentHandler()</code> ).</p></div>
       </div>
       

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/knownissues_overview.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/knownissues_overview.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/knownissues_overview.html Wed Oct 24 04:26:06 2012
@@ -332,7 +332,7 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-known-issues">Apache&trade; FOP: Known Issues</h1>
 <p><version>$Revision: 1298724 $</version></p>
-<h2 id="known-issues-wzxhzdk3wzxhzdk4">Known issues  <a id="Known+issues"></a></h2>
+<h2 id="known-issues-wzxhzdk3wzxhzdk4">Known issues <a id="Known+issues"></a></h2>
 <p>This page lists currently known issues in the current release.</p>
 <p>For additional information on known issues in Apache&trade; FOP, please have a look at the following pages, too:</p>
 <ul>
@@ -344,10 +344,10 @@ $(document).ready(function () {
 </li>
 </ul>
 <p>Apache FOP has an extensive automated testing infrastructure. Parts of this infrastructure are several sets of test cases. When a test case is listed in disabled-testcases.xml it is disabled in the JUnit tests during the normal build process. This indicates a problem in the current codebase. When a bug is fixed or a missing feature is added the entry for the relevant test case(s) are removed.</p>
-<h3 id="fo-tree-wzxhzdk6wzxhzdk7">FO Tree # <a id="FO+Tree"></a></h3>
+<h3 id="fo-tree-wzxhzdk6wzxhzdk7">FO Tree <a id="FO+Tree"></a></h3>
 <p>This section lists disabled test cases in the test suite for the FO tree tests, at the time of the release.</p>
 <p><strong>from-table-column_marker.fo</strong> (Markers and core function evaluation):<br></br>The code currently evaluates this function according to the column in which the marker appears in the source document, rather than the column it is retrieved in.</p>
-<h3 id="layout-engine-wzxhzdk10wzxhzdk11">Layout Engine # <a id="Layout+Engine"></a></h3>
+<h3 id="layout-engine-wzxhzdk10wzxhzdk11">Layout Engine <a id="Layout+Engine"></a></h3>
 <p>This section lists disabled test cases in the test suite for the layout engine tests, at the time of the release.</p>
 <p><strong>basic-link_external-destination_2.xml</strong> (External link around an SVG not properly sized):<br></br>The bpd trait of the inlineparent area for the basic-link is not sized correctly if it wraps an image that is higher than the nominal line.</p>
 <p><strong>block-container_space-before_space-after_3.xml</strong> (Auto-height block-containers produce fences):<br></br>Block-containers with no height currently don't create a fence for spaces as they should (they behave like a normal block).</p>
@@ -388,7 +388,7 @@ $(document).ready(function () {
 <p><strong>table_border-width_conditionality.xml</strong> (Border conditionality on table):<br></br>The code should be ok, but the test case uses shorthands and therefore is probably not expressing the indended outcome according to the spec. The test case should be revisited.</p>
 <p><strong>wrapper_block_id.xml</strong> (fo:wrapper around block-level content (with id)):<br></br>"id" attributes on fo:wrapper around block-level content don't get added to the area tree.</p>
 <p><strong>block_shy_linebreaking_hyph.xml</strong> (Soft hyphen with normal hyphenation enabled):<br></br>A soft hyphen should be a preferred as break compared to a normal hyphenation point but is not.</p>
-<h3 id="other-known-issues-wzxhzdk96wzxhzdk97">Other known issues # <a id="Other+known+issues"></a></h3>
+<h3 id="other-known-issues-wzxhzdk96wzxhzdk97">Other known issues <a id="Other+known+issues"></a></h3>
 <p>This section lists other known issues.</p>
 <ul>
 <li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/metadata.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/metadata.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/metadata.html Wed Oct 24 04:26:06 2012
@@ -331,14 +331,14 @@ $(document).ready(function () {
       <div id="content" class="grid_16">
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-metadata">Apache&trade; FOP: Metadata</h1>
-<h2 id="overview-wzxhzdk1wzxhzdk2">Overview  <a id="overview"></a></h2>
+<h2 id="overview-wzxhzdk1wzxhzdk2">Overview <a id="overview"></a></h2>
 <p>Document metadata is an important tool for categorizing and finding documents. Various formats support different kinds of metadata representation and to different levels. One of the more popular and flexible means of representing document or object metadata is <a href="http://www.adobe.com/products/xmp/">XMP (eXtensible Metadata Platform, specified by Adobe)</a> . PDF 1.4 introduced the use of XMP. The XMP specification lists recommendation for embedding XMP metdata in other document and image formats. Given its flexibility it makes sense to make use this approach in the XSL-FO context. Unfortunately, unlike SVG which also refers to XMP, XSL-FO doesn't recommend a preferred way of specifying document and object metadata. Therefore, there's no portable way to represent metadata in XSL-FO documents. Each implementation does it differently.</p>
-<h2 id="embedding-xmp-in-an-xsl-fo-document-wzxhzdk3wzxhzdk4">Embedding XMP in an XSL-FO document  <a id="xmp-in-fo"></a></h2>
+<h2 id="embedding-xmp-in-an-xsl-fo-document-wzxhzdk3wzxhzdk4">Embedding XMP in an XSL-FO document <a id="xmp-in-fo"></a></h2>
 <p>As noted above, there's no officially recommended way to embed metadata in XSL-FO. Apache&trade; FOP supports embedding XMP in XSL-FO. Currently, only support for document-level metadata is implemented. Object-level metadata will be implemented when there's interest.</p>
 <p>Document-level metadata can be specified in the <code>fo:declarations</code> element. XMP specification recommends to use <code>x:xmpmeta</code> , <code>rdf:RDF</code> , and <code>rdf:Description</code> elements as shown in example below. Both <code>x:xmpmeta</code> and <code>rdf:RDF</code> elements are recognized as the top-level element introducing an XMP fragment (as per the XMP specification).</p>
-<h3 id="example-wzxhzdk6wzxhzdk7">Example # <a id="xmp-example"></a></h3>
+<h3 id="example-wzxhzdk6wzxhzdk7">Example <a id="xmp-example"></a></h3>
 <p class="."></p>
-<h1 id="implementation-in-apache-fop-wzxhzdk8wzxhzdk9">Implementation in Apache FOP  <a id="xmp-impl-in-fop"></a></h1>
+<h1 id="implementation-in-apache-fop-wzxhzdk8wzxhzdk9">Implementation in Apache FOP <a id="xmp-impl-in-fop"></a></h1>
 <p>Currently, XMP support is only available for PDF output.</p>
 <p>Originally, you could set some metadata information through FOP's FOUserAgent by using its set*() methods (like setTitle(String) or setAuthor(String). These values are directly used to set value in the PDF Info object. Since PDF 1.4, adding metadata as an XMP document to a PDF is possible. That means that there are now two mechanisms in PDF that hold metadata.</p>
 <p>Apache FOP now synchronizes the Info and the Metadata object in PDF, i.e. when you set the title and the author through the FOUserAgent, the two values will end up in the (old) Info object and in the new Metadata object as XMP content. If instead of FOUserAgent, you embed XMP metadata in the XSL-FO document (as shown above), the XMP metadata will be used as-is in the PDF Metadata object and some values from the XMP metadata will be copied to the Info object to maintain backwards-compatibility for PDF readers that don't support XMP metadata.</p>
@@ -396,7 +396,7 @@ $(document).ready(function () {
 <td></td>
 </tr>
 <tr>
-<td>## Namespaces # <a id="namespaces"></a></td>
+<td>## Namespaces <a id="namespaces"></a></td>
 <td></td>
 </tr>
 </tbody>
@@ -431,7 +431,7 @@ $(document).ready(function () {
 </table>
 <p>Please refer to the <a href="http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf">XMP Specification</a> for information on other metadata namespaces.</p>
 <p>Property sets (Namespaces) not listed here are simply passed through to the final document (if supported). That is useful if you want to specify a custom metadata schema.</p>
-<h2 id="links-wzxhzdk10wzxhzdk11">Links  <a id="links"></a></h2>
+<h2 id="links-wzxhzdk10wzxhzdk11">Links <a id="links"></a></h2>
 <ul>
 <li>
 <p><a href="http://www.adobe.com/products/xmp/">Adobe's Extensible Metadata Platform (XMP) website</a> </p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/output.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/output.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/output.html Wed Oct 24 04:26:06 2012
@@ -333,8 +333,8 @@ $(document).ready(function () {
       	<div class="section-content"><h1 id="apachewzxhzdk12-fop-output-formats">Apache&trade; FOP Output Formats</h1>
 <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&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-wzxhzdk22wzxhzdk23">General Information  <a id="general"></a></h2>
-<h3 id="fonts-wzxhzdk24wzxhzdk25">Fonts # <a id="general-fonts"></a></h3>
+<h2 id="general-information-wzxhzdk22wzxhzdk23">General Information <a id="general"></a></h2>
+<h3 id="fonts-wzxhzdk24wzxhzdk25">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>
@@ -358,7 +358,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-wzxhzdk26wzxhzdk27">Output to a Printer or Other Device # <a id="general-direct-output"></a></h3>
+<h3 id="output-to-a-printer-or-other-device-wzxhzdk26wzxhzdk27">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
@@ -366,12 +366,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-wzxhzdk28wzxhzdk29">PDF  <a id="pdf"></a></h2>
+<h2 id="pdf-wzxhzdk28wzxhzdk29">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 "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>
-<h3 id="fonts-wzxhzdk30wzxhzdk31">Fonts # <a id="pdf-fonts"></a></h3>
+<h3 id="fonts-wzxhzdk30wzxhzdk31">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-wzxhzdk32wzxhzdk33">Post-processing # <a id="pdf-postprocess"></a></h3>
+<h3 id="post-processing-wzxhzdk32wzxhzdk33">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>
@@ -420,7 +420,7 @@ public static void main(String args[]) {
   }
 }
 Check the iText tutorial and documentation for setting access flags, password, encryption strength and other parameters.</p>
-<h3 id="watermarks-wzxhzdk36wzxhzdk37">Watermarks # <a id="pdf-watermark"></a></h3>
+<h3 id="watermarks-wzxhzdk36wzxhzdk37">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>
@@ -430,9 +430,9 @@ Check the iText tutorial and documentati
 <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>
-<h2 id="postscript-wzxhzdk38wzxhzdk39">PostScript  <a id="ps"></a></h2>
+<h2 id="postscript-wzxhzdk38wzxhzdk39">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-wzxhzdk40wzxhzdk41">Configuration # <a id="ps-configuration"></a></h3>
+<h3 id="configuration-wzxhzdk40wzxhzdk41">Configuration <a id="ps-configuration"></a></h3>
 <p>The PostScript renderer configuration currently allows the following settings:
 <renderer mime="application/postscript">
   <auto-rotate-landscape>false</auto-rotate-landscape>
@@ -446,7 +446,7 @@ The default value for the "auto-rotate-l
 <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>
-<h3 id="limitations-wzxhzdk54wzxhzdk55">Limitations # <a id="ps-limitations"></a></h3>
+<h3 id="limitations-wzxhzdk54wzxhzdk55">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>
@@ -461,10 +461,10 @@ The default value for the "auto-rotate-l
 <p>PPD support is still missing.</p>
 </li>
 </ul>
-<h2 id="pcl-wzxhzdk56wzxhzdk57">PCL  <a id="pcl"></a></h2>
+<h2 id="pcl-wzxhzdk56wzxhzdk57">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-wzxhzdk58wzxhzdk59">References # <a id="pcl-references"></a></h3>
+<h3 id="references-wzxhzdk58wzxhzdk59">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>
@@ -473,7 +473,7 @@ The default value for the "auto-rotate-l
 <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-wzxhzdk60wzxhzdk61">Limitations # <a id="pcl-limitations"></a></h3>
+<h3 id="limitations-wzxhzdk60wzxhzdk61">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>
@@ -500,7 +500,7 @@ The default value for the "auto-rotate-l
 <p>Currently, there's no support for clipping and image transparency, largely because PCL 5 has certain limitations.</p>
 </li>
 </ul>
-<h3 id="configuration-wzxhzdk62wzxhzdk63">Configuration # <a id="pcl-configuration"></a></h3>
+<h3 id="configuration-wzxhzdk62wzxhzdk63">Configuration <a id="pcl-configuration"></a></h3>
 <p>The PCL renderer configuration currently allows the following settings:
 <renderer mime="application/vnd.hp-PCL">
   <rendering>quality</rendering>
@@ -511,7 +511,7 @@ The default value for the "rendering" se
 <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-wzxhzdk72wzxhzdk73">Extensions # <a id="pcl-extensions"></a></h3>
+<h3 id="extensions-wzxhzdk72wzxhzdk73">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>
@@ -529,10 +529,10 @@ The default value for the "rendering" se
 
 
 <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>
-<h2 id="afp-wzxhzdk76wzxhzdk77">AFP  <a id="afp"></a></h2>
+<h2 id="afp-wzxhzdk76wzxhzdk77">AFP <a id="afp"></a></h2>
 <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>
-<h3 id="references-wzxhzdk80wzxhzdk81">References # <a id="afp-references"></a></h3>
+<h3 id="references-wzxhzdk80wzxhzdk81">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>
@@ -541,7 +541,7 @@ The FOP AFP Renderer deals with creating
 <p><a href="http://wiki.apache.org/xmlgraphics-fop/AFPResources">AFP Resources on the FOP WIKI</a> </p>
 </li>
 </ul>
-<h3 id="limitations-wzxhzdk82wzxhzdk83">Limitations # <a id="afp-limitations"></a></h3>
+<h3 id="limitations-wzxhzdk82wzxhzdk83">Limitations <a id="afp-limitations"></a></h3>
 <p>This list is most likely badly incomplete.</p>
 <ul>
 <li>
@@ -551,7 +551,7 @@ The FOP AFP Renderer deals with creating
 <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="configuration-wzxhzdk84wzxhzdk85">Configuration # <a id="afp-configuration"></a></h3>
+<h3 id="configuration-wzxhzdk84wzxhzdk85">Configuration <a id="afp-configuration"></a></h3>
 <h4 id="fonts-wzxhzdk86wzxhzdk87">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:
 <renderer mime="application/x-afp">
@@ -694,7 +694,7 @@ An outline font configuration is simpler
 
 
 <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>
-<h3 id="extensions-wzxhzdk153wzxhzdk154">Extensions # <a id="afp-extensions"></a></h3>
+<h3 id="extensions-wzxhzdk153wzxhzdk154">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>
            <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>
@@ -754,7 +754,7 @@ An outline font configuration is simpler
 
 
 <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>
-<h2 id="rtf-wzxhzdk163wzxhzdk164">RTF  <a id="rtf"></a></h2>
+<h2 id="rtf-wzxhzdk163wzxhzdk164">RTF <a id="rtf"></a></h2>
 <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.
@@ -790,27 +790,27 @@ These are some known restrictions compar
 <p>percentages are not supported everywhere</p>
 </li>
 </ul>
-<h2 id="xml-area-tree-xml-wzxhzdk165wzxhzdk166">XML (Area Tree XML)  <a id="xml"></a></h2>
+<h2 id="xml-area-tree-xml-wzxhzdk165wzxhzdk166">XML (Area Tree XML) <a id="xml"></a></h2>
 <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>
-<h2 id="java2dawt-wzxhzdk167wzxhzdk168">Java2D/AWT  <a id="awt"></a></h2>
+<h2 id="java2dawt-wzxhzdk167wzxhzdk168">Java2D/AWT <a id="awt"></a></h2>
 <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>
-<h2 id="print-wzxhzdk169wzxhzdk170">Print  <a id="print"></a></h2>
+<h2 id="print-wzxhzdk169wzxhzdk170">Print <a id="print"></a></h2>
 <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>
-<h3 id="known-issues-wzxhzdk171wzxhzdk172">Known issues # <a id="print-issues"></a></h3>
+<h3 id="known-issues-wzxhzdk171wzxhzdk172">Known issues <a id="print-issues"></a></h3>
 <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>
-<h2 id="bitmap-tiffpng-wzxhzdk173wzxhzdk174">Bitmap (TIFF/PNG)  <a id="bitmap"></a></h2>
+<h2 id="bitmap-tiffpng-wzxhzdk173wzxhzdk174">Bitmap (TIFF/PNG) <a id="bitmap"></a></h2>
 <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>
-<h3 id="configuration-wzxhzdk175wzxhzdk176">Configuration # <a id="bitmap-configuration"></a></h3>
+<h3 id="configuration-wzxhzdk175wzxhzdk176">Configuration <a id="bitmap-configuration"></a></h3>
 <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>
-<h3 id="tiff-specific-configuration-wzxhzdk184wzxhzdk185">TIFF-specific Configuration # <a id="tiff-configuration"></a></h3>
+<h3 id="tiff-specific-configuration-wzxhzdk184wzxhzdk185">TIFF-specific Configuration <a id="tiff-configuration"></a></h3>
 <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>
@@ -845,7 +845,7 @@ The default value for the "compression" 
 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-wzxhzdk195wzxhzdk196">TXT  <a id="txt"></a></h1>
+<h1 id="txt-wzxhzdk195wzxhzdk196">TXT <a id="txt"></a></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>
@@ -860,15 +860,15 @@ If you want to use CCITT compression, pl
 <p>line-height="10.5pt"</p>
 </li>
 </ul>
-<h2 id="output-formats-in-the-sandbox-wzxhzdk197wzxhzdk198">Output Formats in the Sandbox  <a id="sandbox"></a></h2>
+<h2 id="output-formats-in-the-sandbox-wzxhzdk197wzxhzdk198">Output Formats in the Sandbox <a id="sandbox"></a></h2>
 <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>
-<h3 id="mif-wzxhzdk199wzxhzdk200">MIF # <a id="mif"></a></h3>
+<h3 id="mif-wzxhzdk199wzxhzdk200">MIF <a id="mif"></a></h3>
 <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>
-<h3 id="svg-wzxhzdk203wzxhzdk204">SVG # <a id="svg"></a></h3>
+<h3 id="svg-wzxhzdk203wzxhzdk204">SVG <a id="svg"></a></h3>
 <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>
-<h2 id="wish-list-wzxhzdk207wzxhzdk208">Wish list  <a id="wishlist"></a></h2>
+<h2 id="wish-list-wzxhzdk207wzxhzdk208">Wish list <a id="wishlist"></a></h2>
 <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>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfa.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfa.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfa.html Wed Oct 24 04:26:06 2012
@@ -332,21 +332,21 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-pdfa-iso-19005">Apache&trade; FOP: PDF/A (ISO 19005)</h1>
 <p><version>$Revision: 1298724 $</version><authors><person email="jeremias@apache.org" name="Jeremias Märki"></person></authors></p>
-<h2 id="overview-wzxhzdk7wzxhzdk8">Overview  <a id="overview"></a></h2>
+<h2 id="overview-wzxhzdk7wzxhzdk8">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-wzxhzdk9wzxhzdk10">Implementation Status  <a id="status"></a></h2>
+<h2 id="implementation-status-wzxhzdk9wzxhzdk10">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 not implemented, yet. This is mostly because of the requirement for tagged PDF which is not available in FOP, yet.</p>
-<h2 id="usage-command-line-wzxhzdk11wzxhzdk12">Usage (command line)  <a id="command-line"></a></h2>
+<h2 id="usage-command-line-wzxhzdk11wzxhzdk12">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>
-<h2 id="usage-embedded-wzxhzdk13wzxhzdk14">Usage (embedded)  <a id="embedded"></a></h2>
+<h2 id="usage-embedded-wzxhzdk13wzxhzdk14">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>
-<h2 id="pdfa-in-action-wzxhzdk15wzxhzdk16">PDF/A in Action  <a id="rules"></a></h2>
+<h2 id="pdfa-in-action-wzxhzdk15wzxhzdk16">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>
@@ -371,9 +371,9 @@ Fop fop = fopFactory.newFop(MimeConstant
 <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>
-<h2 id="pdf-profile-compatibility-wzxhzdk17wzxhzdk18">PDF profile compatibility  <a id="profile-compatibility"></a></h2>
+<h2 id="pdf-profile-compatibility-wzxhzdk17wzxhzdk18">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>
-<h2 id="interoperability-wzxhzdk19wzxhzdk20">Interoperability  <a id="interoperability"></a></h2>
+<h2 id="interoperability-wzxhzdk19wzxhzdk20">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/0.95/pdfencryption.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html Wed Oct 24 04:26:06 2012
@@ -332,16 +332,16 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-pdf-encryption">Apache&trade; FOP: PDF encryption.</h1>
 <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>
-<h2 id="overview-wzxhzdk9wzxhzdk10">Overview  <a id="Overview"></a></h2>
+<h2 id="overview-wzxhzdk9wzxhzdk10">Overview <a id="Overview"></a></h2>
 <p>Apache&trade; 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>
-<h2 id="usage-command-line-wzxhzdk12wzxhzdk13">Usage (command line)  <a id="Usage+%28command+line%29"></a></h2>
+<h2 id="usage-command-line-wzxhzdk12wzxhzdk13">Usage (command line) <a id="Usage+%28command+line%29"></a></h2>
 <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>
-<h2 id="usage-embedded-wzxhzdk14wzxhzdk15">Usage (embedded)  <a id="Usage+%28embedded%29"></a></h2>
+<h2 id="usage-embedded-wzxhzdk14wzxhzdk15">Usage (embedded) <a id="Usage+%28embedded%29"></a></h2>
 <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>
@@ -451,13 +451,13 @@ Fop fop = fopFactory.newFop(MimeConstant
 <p>noannotations: Boolean or "true"/"false"</p>
 </li>
 </ol>
-<h2 id="environment-wzxhzdk16wzxhzdk17">Environment  <a id="Environment"></a></h2>
+<h2 id="environment-wzxhzdk16wzxhzdk17">Environment <a id="Environment"></a></h2>
 <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>
-<h2 id="installing-a-crypto-provider-wzxhzdk18wzxhzdk19">Installing a crypto provider  <a id="install_crypto"></a></h2>
+<h2 id="installing-a-crypto-provider-wzxhzdk18wzxhzdk19">Installing a crypto provider <a id="install_crypto"></a></h2>
 <p>The pure Java implementation from <a href="http://www.bouncycastle.org/">Bouncy Castle</a> is easy to install.</p>
 <ol>
 <li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfx.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfx.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfx.html Wed Oct 24 04:26:06 2012
@@ -332,22 +332,22 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-pdfx-iso-15930">Apache&trade; FOP: PDF/X (ISO 15930)</h1>
 <p><version>$Revision: 1298724 $</version><authors><person email="jeremias@apache.org" name="Jeremias Märki"></person></authors></p>
-<h2 id="overview-wzxhzdk7wzxhzdk8">Overview  <a id="overview"></a></h2>
+<h2 id="overview-wzxhzdk7wzxhzdk8">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-wzxhzdk11wzxhzdk12">Implementation Status  <a id="status"></a></h2>
+<h2 id="implementation-status-wzxhzdk11wzxhzdk12">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-wzxhzdk13wzxhzdk14">Usage (command line)  <a id="command-line"></a></h2>
+<h2 id="usage-command-line-wzxhzdk13wzxhzdk14">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-wzxhzdk15wzxhzdk16">Usage (embedded)  <a id="embedded"></a></h2>
+<h2 id="usage-embedded-wzxhzdk15wzxhzdk16">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-wzxhzdk17wzxhzdk18">PDF/X in Action  <a id="rules"></a></h2>
+<h2 id="pdfx-in-action-wzxhzdk17wzxhzdk18">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>
@@ -369,7 +369,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-wzxhzdk19wzxhzdk20">PDF profile compatibility  <a id="profile-compatibility"></a></h2>
+<h2 id="pdf-profile-compatibility-wzxhzdk19wzxhzdk20">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>
       



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


Mime
View raw message