xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r835960 [9/18] - 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:04:05 GMT
Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/extensions.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/extensions.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/extensions.html Wed Oct 24 04:04:00 2012
@@ -330,34 +330,35 @@ $(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/1.1/">1.1</a></div> -->
-      	<div class="section-content"><p><version>$Revision$</version></p>
+      	<div class="section-content"><h1 id="standard-apachewzxhzdk0-fop-extensions">Standard Apache&trade; FOP Extensions</h1>
+<p><version>$Revision$</version></p>
 <p>By "extension", we mean any data that can be placed in the input XML document that is not addressed by the XSL-FO standard. By having a mechanism for supporting extensions, Apache&trade; FOP is able to add features that are not covered in the specification.</p>
 <p>The extensions documented here are included with FOP, and are automatically available to you. If you wish to add an extension of your own to FOP, please see the <a href="../dev/extensions.html">Developers' Extension Page</a> .
 All extensions require the correct use of an appropriate namespace in your input document.</p>
-<h1 id="svg-wzxhzdk3wzxhzdk4">SVG  <a id="svg"></a></h1>
+<h1 id="svg-wzxhzdk4wzxhzdk5">SVG  <a id="svg"></a></h1>
 <p>Please see the <a href="graphics.html#svg">SVG documentation</a> for more details.</p>
-<h1 id="fo-extensions-wzxhzdk5wzxhzdk6">FO Extensions  <a id="fo-extensions"></a></h1>
-<h2 id="namespace-wzxhzdk7wzxhzdk8">Namespace # <a id="fox-namespace"></a></h2>
+<h2 id="fo-extensions-wzxhzdk6wzxhzdk7">FO Extensions  <a id="fo-extensions"></a></h2>
+<h3 id="namespace-wzxhzdk8wzxhzdk9">Namespace # <a id="fox-namespace"></a></h3>
 <p>By convention, FO extensions in FOP use the "fox" namespace prefix. To use any of the FO extensions, add a namespace entry for <code>http://xmlgraphics.apache.org/fop/extensions</code> to the root element:
 <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
                xmlns:fox="http://xmlgraphics.apache.org/fop/extensions"></p>
-<h2 id="pdf-bookmarks-wzxhzdk10wzxhzdk11">PDF Bookmarks # <a id="bookmarks"></a></h2>
+<h2 id="pdf-bookmarks-wzxhzdk11wzxhzdk12">PDF Bookmarks # <a id="bookmarks"></a></h2>
 <p>In old versions of Apache FOP there was a <code>fox:outline</code> element which was used to create outlines in PDF files. The redesigned code makes use of the <a href="http://www.w3.org/TR/xsl11/#fo_bookmark-tree">bookmark feature defined in the W3C XSL 1.1 standard</a> .</p>
-<h2 id="anchors-or-named-destinations-wzxhzdk12wzxhzdk13">Anchors or Named Destinations # <a id="named-destinations"></a></h2>
+<h3 id="anchors-or-named-destinations-wzxhzdk13wzxhzdk14">Anchors or Named Destinations # <a id="named-destinations"></a></h3>
 <p>Use the fox:destination element to define "named destinations" inside a PDF document. These are useful as fragment identifiers, e.g. "http://server/document.pdf#anchor-name". fox:destination elements can be placed almost anywhere in the fo document, including a child of root, a block-level element, or an inline-level element. For the destination to actually work, it must correspond to an "id" attribute on some fo element within the document. In other words, the "id" attribute actually creates the "view" within the PDF document. The fox:destination simply gives that view an independent name.
 <fox:destination internal-destination="table-of-contents"/>
 ...
 <fo:block id="table-of-contents">Table of Contents</fo:block><warning>It is possible that in some future release of FOP, <em>all</em> elements with "id" attributes will generate named-destinations, which will eliminate the need for fox:destination.</warning></p>
-<h2 id="table-continuation-label-wzxhzdk19wzxhzdk20">Table Continuation Label # <a id="table-continue-label"></a></h2>
+<h2 id="table-continuation-label-wzxhzdk20wzxhzdk21">Table Continuation Label # <a id="table-continue-label"></a></h2>
 <p>This extension element hasn't been reimplemented for the redesigned code, yet.</p>
-<h2 id="foxorphan-content-limit-and-foxwidow-content-limit-wzxhzdk21wzxhzdk22">fox:orphan-content-limit and fox:widow-content-limit # <a id="widow-orphan-content-limit"></a></h2>
+<h3 id="foxorphan-content-limit-and-foxwidow-content-limit-wzxhzdk22wzxhzdk23">fox:orphan-content-limit and fox:widow-content-limit # <a id="widow-orphan-content-limit"></a></h3>
 <p>The two proprietary extension properties, fox:orphan-content-limit and fox:widow-content-limit, are used to improve the layout of list-blocks and tables. If you have a table with many entries, you don't want a single row to be left over on a page. You will want to make sure that at least two or three lines are kept together. The properties take an absolute length which specifies the area at the beginning (fox:widow-content-limit) or at the end (fox:orphan-content-limit) of a table or list-block. The properties are inherited and only have an effect on fo:table and fo:list-block. An example: fox:widow-content-limit="3 * 1.2em" would make sure the you'll have at least three lines (assuming line-height="1.2") together on a table or list-block.</p>
-<h2 id="foxexternal-document-wzxhzdk23wzxhzdk24">fox:external-document # <a id="external-document"></a></h2>
+<h3 id="foxexternal-document-wzxhzdk24wzxhzdk25">fox:external-document # <a id="external-document"></a></h3>
 <p>This feature is incomplete. Support for multi-page documents will be added shortly. At the moment, only single-page images will work. And this will not work with RTF output.
 This is a proprietary extension element which allows to add whole images as pages to an FO document. For example, if you have a scanned document or a fax as multi-page TIFF file, you can append or insert this document using the <code>fox:external-document</code> element. Each page of the external document will create one full page in the target format.</p>
 <p>The <code>fox:external-document</code> element is structurally a peer to <code>fo:page-sequence</code> , so wherever you can put an <code>fo:page-sequence</code> you could also place a <code>fox:external-document</code> . Therefore, the specified contents for <code>fo:root</code> change to:</p>
 <p><code>(layout-master-set, declarations?, bookmark-tree?, (page-sequence|page-sequence-wrapper|fox:external-document|fox:destination)+)</code> </p>
-<h3 id="specification-wzxhzdk25wzxhzdk26">Specification ## <a id="Specification"></a></h3>
+<h4 id="specification-wzxhzdk26wzxhzdk27">Specification ## <a id="Specification"></a></h4>
 <p>The <code>fox:external-document</code> extension formatting object is used to specify how to create a (sub-)sequence of pages within a document. The content of these pages comes from the individual subimages/pages of an image or paged document (for example: multi-page TIFF in the form of faxes or scanned documents, or PDF files). The formatting object creates the necessary areas to display one image per page.</p>
 <p>In terms of page numbers, the behaviour is the same as for <code>fo:page-sequence</code> . The placement of the image inside the page is similar to that of <code>fo:external-graphic</code> or <code>fo:instream-foreign-object</code> , i.e. the viewport (and therefore the page size) is defined by either the intrinsic size of the image or by the size properties that apply to this formatting object.</p>
 <p>Content: EMPTY</p>
@@ -420,16 +421,16 @@ This is a proprietary extension element 
 </ul>
 <p>Datatype "page-set": Value: auto | <integer-range>, Default: "auto" which means all pages/subimages of the document. <integer-range> allows values such as "7" or "1-3"
  <code>fox:external-document</code> is not suitable for concatenating FO documents. For this, XInclude is recommended.</p>
-<h2 id="free-form-transformation-for-foblock-container-wzxhzdk29wzxhzdk30">Free-form Transformation for fo:block-container # <a id="transform"></a></h2>
+<h2 id="free-form-transformation-for-foblock-container-wzxhzdk30wzxhzdk31">Free-form Transformation for fo:block-container # <a id="transform"></a></h2>
 <p>For <code>fo:block-container</code> elements whose <code>absolute-position</code> set to "absolute" or "fixed" you can use the extension attribute <code>fox:transform</code> to apply a free-form transformation to the whole block-container. The content of the <code>fox:transform</code> attribute is the same as for <a href="http://www.w3.org/TR/SVG/coords.html#TransformAttribute">SVG's transform attribute</a> . The transformation specified here is performed in addition to other implicit transformations of the block-container (resulting from top, left and other properties) and after them.</p>
 <p>Examples: <code>fox:transform="rotate(45)"</code> would rotate the block-container by 45 degrees clock-wise around its upper-left corner. <code>fox:transform="translate(10000,0)"</code> would move the block-container to the right by 10 points (=10000 millipoints, FOP uses millipoints internally!).
 This extension attribute doesn't work for all output formats! It's currently only supported for PDF, PS and Java2D-based renderers.</p>
-<h2 id="color-functions-wzxhzdk31wzxhzdk32">Color functions # <a id="color-functions"></a></h2>
+<h2 id="color-functions-wzxhzdk32wzxhzdk33">Color functions # <a id="color-functions"></a></h2>
 <p>XSL-FO supports specifying color using the rgb(), rgb-icc() and system-color() functions. Apache FOP provides additional color functions for special use cases. Please note that using these functions compromises the interoperability of an FO document.</p>
-<h3 id="cmyk-wzxhzdk33wzxhzdk34">cmyk() ## <a id="color-function-cmyk"></a></h3>
+<h4 id="cmyk-wzxhzdk34wzxhzdk35">cmyk() ## <a id="color-function-cmyk"></a></h4>
 <p><code>color cmyk(numeric, numeric, numeric, numeric)</code> </p>
 <p>This function will construct a color in device-specific CMYK color space. The numbers must be between 0.0 and 1.0. For output formats that don't support device-specific color space the CMYK value is converted to an sRGB value.</p>
-<h3 id="cmyk-pseudo-profile-wzxhzdk35wzxhzdk36">#CMYK pseudo-profile ## <a id="pseudo-color-profiles"></a></h3>
+<h4 id="cmyk-pseudo-profile-wzxhzdk36wzxhzdk37">#CMYK pseudo-profile ## <a id="pseudo-color-profiles"></a></h4>
 <p><code>color rgb-icc(numeric, numeric, numeric, #CMYK, numeric, numeric, numeric, numeric)</code> </p>
 <p>The <code>rgb-icc</code> function will respond to a pseudo-profile called "#CMYK" which indicates a device-specific CMYK color space. The "#CMYK" profile is implicitely available and doesn't have to be (and cannot be) defined through an <code>fo:color-profile</code> element. It is provided for compatibility with certain commercial XSL-FO implementations. Please note that this is not part of the official specification but rather a convention. The following two color specifications are equivalent:</p>
 <ul>
@@ -440,27 +441,27 @@ This extension attribute doesn't work fo
 <p><code>rgb-icc(153, 153, 102, #CMYK, 0, 0, 0.2, 0.4)</code> </p>
 </li>
 </ul>
-<h2 id="prepress-support-wzxhzdk37wzxhzdk38">Prepress Support # <a id="prepress"></a></h2>
+<h3 id="prepress-support-wzxhzdk38wzxhzdk39">Prepress Support # <a id="prepress"></a></h3>
 <p>This section defines a number of extensions related to <a href="http://en.wikipedia.org/wiki/Prepress">prepress</a> support. <code>fox:scale</code> defines a general scale factor for the generated pages. <code>fox:bleed</code> defines the <a href="http://en.wikipedia.org/wiki/Bleed_%28printing%29">bleed area</a> for a page. <code>fox:crop-offset</code> defines the outer edges of the area in which crop marks, registration marks, color bars and page information are placed. For details, please read on below.
 Those extensions have been implemented in the PDF and Java2D renderers only.</p>
-<h3 id="foxscale-wzxhzdk39wzxhzdk40">fox:scale ## <a id="scale"></a></h3>
+<h3 id="foxscale-wzxhzdk40wzxhzdk41">fox:scale ## <a id="scale"></a></h3>
 <p>Value: <number>{1,2}</p>
 <p>Initial: 1</p>
 <p>Applies to: fo:simple-page-master</p>
 <p>This property specifies a scale factor along resp. the x and y axes. If only one number is provided it is used for both the x and y scales. A scale factor smaller than 1 shrinks the page. A scale factor greater than 1 enlarges the page.</p>
-<h3 id="foxbleed-wzxhzdk42wzxhzdk43">fox:bleed ## <a id="bleed"></a></h3>
+<h4 id="foxbleed-wzxhzdk43wzxhzdk44">fox:bleed ## <a id="bleed"></a></h4>
 <p>Value: <length>{1,4}</p>
 <p>Initial: 0pt</p>
 <p>Applies to: fo:simple-page-master</p>
 <p>If there is only one value, it applies to all sides. If there are two values, the top and bottom bleed widths are set to the first value and the right and left bleed widths are set to the second. If there are three values, the top is set to the first value, the left and right are set to the second, and the bottom is set to the third. If there are four values, they apply to the top, right, bottom, and left, respectively. (Corresponds to <a href="http://www.w3.org/TR/xsl11/#padding">the definition of padding</a> ).</p>
 <p>This extension indirectly defines the BleedBox and is calculated by expanding the TrimBox by the bleed widths. The lengths must be non-negative.</p>
-<h3 id="foxcrop-offset-wzxhzdk45wzxhzdk46">fox:crop-offset ## <a id="cropOffset"></a></h3>
+<h4 id="foxcrop-offset-wzxhzdk46wzxhzdk47">fox:crop-offset ## <a id="cropOffset"></a></h4>
 <p>Value: <length>{1,4}</p>
 <p>Initial: bleed (see below)</p>
 <p>Applies to: fo:simple-page-master</p>
 <p>Same behaviour as with fox:bleed. The initial value is set to the same values as the fox:bleed property.</p>
 <p>This extension indirectly defines the MediaBox and is calculated by expanding the TrimBox by the crop offsets. The lengths must be non-negative.</p>
-<h3 id="foxcrop-box-wzxhzdk48wzxhzdk49">fox:crop-box ## <a id="cropBox"></a></h3>
+<h4 id="foxcrop-box-wzxhzdk49wzxhzdk50">fox:crop-box ## <a id="cropBox"></a></h4>
 <p>Value: [trim-box | bleed-box | media-box]</p>
 <p>Initial: media-box</p>
 <p>Applies to: fo:simple-page-master</p>

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 Wed Oct 24 04:04:00 2012
@@ -330,8 +330,9 @@ $(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/1.1/">1.1</a></div> -->
-      	<div class="section-content"><p><version>$Revision$</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>
-<h1 id="summary-wzxhzdk15wzxhzdk16">Summary  <a id="intro"></a></h1>
+      	<div class="section-content"><h1 id="apachetm-fop-fonts">Apache(tm) FOP: Fonts</h1>
+<p><version>$Revision$</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-wzxhzdk15wzxhzdk16">Summary  <a id="intro"></a></h2>
 <p>The following table summarizes the font capabilities of the various Apache� FOP renderers:</p>
 <table>
 <thead>
@@ -409,7 +410,7 @@ $(document).ready(function () {
 </tr>
 </tbody>
 </table>
-<h1 id="base-14-fonts-wzxhzdk17wzxhzdk18">Base-14 Fonts  <a id="Base-14+Fonts"></a></h1>
+<h2 id="base-14-fonts-wzxhzdk17wzxhzdk18">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>
@@ -443,14 +444,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>
-<h1 id="missing-fonts-wzxhzdk19wzxhzdk20">Missing Fonts  <a id="missing-fonts"></a></h1>
+<h2 id="missing-fonts-wzxhzdk19wzxhzdk20">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>
-<h1 id="missing-glyphs-wzxhzdk21wzxhzdk22">Missing Glyphs  <a id="missing-glyphs"></a></h1>
+<h2 id="missing-glyphs-wzxhzdk21wzxhzdk22">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>
-<h1 id="java2dawtoperating-system-fonts-wzxhzdk23wzxhzdk24">Java2D/AWT/Operating System Fonts  <a id="awt"></a></h1>
+<h2 id="java2dawtoperating-system-fonts-wzxhzdk23wzxhzdk24">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>
-<h1 id="custom-fonts-wzxhzdk25wzxhzdk26">Custom Fonts  <a id="custom"></a></h1>
+<h2 id="custom-fonts-wzxhzdk25wzxhzdk26">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>
@@ -462,7 +463,7 @@ $(document).ready(function () {
 <p><a href="http://partners.adobe.com/asn/developer/technotes/fonts.html">Adobe Font Technote</a> </p>
 </li>
 </ul>
-<h1 id="basic-font-configuration-wzxhzdk27wzxhzdk28">Basic font configuration  <a id="basics"></a></h1>
+<h2 id="basic-font-configuration-wzxhzdk27wzxhzdk28">Basic font configuration  <a id="basics"></a></h2>
 <p>If you want FOP to use custom fonts, you need to tell it where to find them. This is done in the configuration file and once per renderer (because each output format is a little different). In the basic form, you can either tell FOP to find your operating system fonts or you can specify directories that it will search for support fonts. These fonts will then automatically be registered.</p>
 <p><renderers>
    <renderer mime="application/pdf">
@@ -482,7 +483,7 @@ $(document).ready(function () {
 </renderers>Review the documentation for <a href="configuration.html">FOP Configuration</a> for instructions on making the FOP configuration available to FOP when it runs. Otherwise, FOP has no way of finding your custom font information. It is currently not possible to easily configure fonts from Java code.</p>
 <h1 id="advanced-font-configuration-wzxhzdk37wzxhzdk38">Advanced font configuration  <a id="advanced"></a></h1>
 <p>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>
-<h2 id="type-1-font-metrics-wzxhzdk39wzxhzdk40">Type 1 Font Metrics # <a id="type1-metrics"></a></h2>
+<h3 id="type-1-font-metrics-wzxhzdk39wzxhzdk40">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
@@ -630,7 +631,7 @@ Alternatively, the individual sub-fonts 
 <p>If relative URLs are specified, they are evaluated relative to the value of the "font-base" setting. If there is no "font-base" setting, the fonts are evaluated relative to the base directory.</p>
 </li>
 </ul>
-<h2 id="auto-detect-and-auto-embed-feature-wzxhzdk57wzxhzdk58">Auto-Detect and auto-embed feature # <a id="autodetect"></a></h2>
+<h3 id="auto-detect-and-auto-embed-feature-wzxhzdk57wzxhzdk58">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>
@@ -640,10 +641,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>
-<h3 id="the-font-cache-wzxhzdk59wzxhzdk60">The font cache ## <a id="font-cache"></a></h3>
+<h4 id="the-font-cache-wzxhzdk59wzxhzdk60">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>
-<h2 id="embedding-wzxhzdk61wzxhzdk62">Embedding # <a id="embedding"></a></h2>
+<h3 id="embedding-wzxhzdk61wzxhzdk62">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>
@@ -682,7 +683,7 @@ At the moment, you can only match fonts 
 <p>When embedding TrueType fonts (ttf) or TrueType Collections (ttc), a subset of the original font, containing only the glyphs used, is embedded in the output document. That's the default, but if you specify encoding-mode="single-byte" (see above), the complete font is embedded.</p>
 </li>
 </ul>
-<h2 id="substitution-wzxhzdk71wzxhzdk72">Substitution # <a id="substitution"></a></h2>
+<h3 id="substitution-wzxhzdk71wzxhzdk72">Substitution # <a id="substitution"></a></h3>
 <p>When a <substitutions/> section is defined in the configuration, FOP will re-map any font-family references found in your FO input to a given substitution font.</p>
 <ul>
 <li>
@@ -725,7 +726,7 @@ At the moment, you can only match fonts 
 </li>
 </ul>
 <p>Character-by-Character is NOT yet supported!</p>
-<h1 id="font-list-command-line-tool-wzxhzdk90wzxhzdk91">Font List Command-Line Tool  <a id="font-list"></a></h1>
+<h2 id="font-list-command-line-tool-wzxhzdk90wzxhzdk91">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/graphics.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/graphics.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/graphics.html Wed Oct 24 04:04:00 2012
@@ -330,8 +330,9 @@ $(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/1.1/">1.1</a></div> -->
-      	<div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="introduction-wzxhzdk2wzxhzdk3">Introduction  <a id="introduction"></a></h1>
+      	<div class="section-content"><h1 id="apachetm-fop-graphics-formats">Apache(tm) FOP: Graphics Formats</h1>
+<p><version>$Revision: 1298724 $</version></p>
+<h2 id="introduction-wzxhzdk2wzxhzdk3">Introduction  <a id="introduction"></a></h2>
 <p>Some noteworthy features of the image handling subsystem are:</p>
 <ul>
 <li>
@@ -345,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> does not reside in Apache FOP, but in <a href="http://xmlgraphics.apache.org/commons/">XML Graphics Commons</a> .</p>
-<h1 id="overview-of-graphics-support-wzxhzdk4wzxhzdk5">Overview of Graphics Support  <a id="support-overview"></a></h1>
+<h2 id="overview-of-graphics-support-wzxhzdk4wzxhzdk5">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>
@@ -530,12 +531,12 @@ $(document).ready(function () {
 <p>[2]: Supported without the need to decode the image, but only for certain subtypes.</p>
 </li>
 </ul>
-<h1 id="graphics-packages-wzxhzdk8wzxhzdk9">Graphics Packages  <a id="packages"></a></h1>
-<h2 id="xml-graphics-commons-native-wzxhzdk10wzxhzdk11">XML Graphics Commons Native # <a id="native"></a></h2>
+<h2 id="graphics-packages-wzxhzdk8wzxhzdk9">Graphics Packages  <a id="packages"></a></h2>
+<h3 id="xml-graphics-commons-native-wzxhzdk10wzxhzdk11">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>
-<h2 id="fop-native-wzxhzdk12wzxhzdk13">FOP Native # <a id="fop-native"></a></h2>
+<h3 id="fop-native-wzxhzdk12wzxhzdk13">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>
-<h2 id="apache-batik-wzxhzdk14wzxhzdk15">Apache Batik # <a id="batik"></a></h2>
+<h3 id="apache-batik-wzxhzdk14wzxhzdk15">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>
@@ -552,41 +553,41 @@ 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>
-<h2 id="image-io-wzxhzdk18wzxhzdk19">Image I/O # <a id="imageio"></a></h2>
+<h3 id="image-io-wzxhzdk18wzxhzdk19">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>
-<h1 id="details-on-image-formats-wzxhzdk20wzxhzdk21">Details on image formats  <a id="image-formats"></a></h1>
-<h2 id="bmp-wzxhzdk22wzxhzdk23">BMP # <a id="bmp"></a></h2>
+<h2 id="details-on-image-formats-wzxhzdk20wzxhzdk21">Details on image formats  <a id="image-formats"></a></h2>
+<h3 id="bmp-wzxhzdk22wzxhzdk23">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>
-<h2 id="emf-wzxhzdk24wzxhzdk25">EMF # <a id="emf"></a></h2>
+<h3 id="emf-wzxhzdk24wzxhzdk25">EMF # <a id="emf"></a></h3>
 <p>Windows Enhanced Metafiles (EMF) are only supported in RTF output where they are embedded without decoding.</p>
-<h2 id="eps-wzxhzdk26wzxhzdk27">EPS # <a id="eps"></a></h2>
+<h3 id="eps-wzxhzdk26wzxhzdk27">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>
-<h2 id="gif-wzxhzdk28wzxhzdk29">GIF # <a id="gif"></a></h2>
+<h3 id="gif-wzxhzdk28wzxhzdk29">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>
-<h2 id="jpeg-wzxhzdk31wzxhzdk32">JPEG # <a id="jpeg"></a></h2>
+<h3 id="jpeg-wzxhzdk31wzxhzdk32">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>
-<h2 id="png-wzxhzdk34wzxhzdk35">PNG # <a id="png"></a></h2>
+<h3 id="png-wzxhzdk34wzxhzdk35">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>
-<h2 id="svg-wzxhzdk37wzxhzdk38">SVG # <a id="svg"></a></h2>
-<h3 id="introduction-wzxhzdk39wzxhzdk40">Introduction ## <a id="svg-intro"></a></h3>
+<h3 id="svg-wzxhzdk37wzxhzdk38">SVG # <a id="svg"></a></h3>
+<h4 id="introduction-wzxhzdk39wzxhzdk40">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>
 <h3 id="placing-svg-graphics-into-pdf-wzxhzdk41wzxhzdk42">Placing SVG Graphics into PDF ## <a id="svg-pdf-graphics"></a></h3>
 <p>The SVG is rendered into PDF by using PDF commands to draw and fill lines and curves. This means that the graphical objects created with this remain as vector graphics. The same applies to PostScript output. For other output formats the SVG graphic may be converted to a bitmap image.</p>
 <p>There are a number of SVG things that cannot be converted directly into PDF. Parts of the graphic such as effects, patterns and images are inserted into the PDF as a raster graphic. The resolution of these raster images can be controlled through the "target resolution" setting in the <a href="configuration.html">configuration</a> .</p>
 <p>Currently transparency is limited in PDF so some SVG images that contain effects or graphics with transparent areas may not be displayed correctly.</p>
-<h3 id="placing-svg-text-into-pdf-and-postscript-wzxhzdk43wzxhzdk44">Placing SVG Text into PDF and PostScript ## <a id="svg-pdf-text"></a></h3>
+<h4 id="placing-svg-text-into-pdf-and-postscript-wzxhzdk43wzxhzdk44">Placing SVG Text into PDF and PostScript ## <a id="svg-pdf-text"></a></h4>
 <p>If possible, Batik will use normal PDF or PostScript text when inserting text. It does this by checking if the text can be drawn normally and the font is supported. This example svg <a href="../dev/svg/text.svg">text.svg</a> / <a href="../dev/svg/text.pdf">text.pdf</a> / <a href="../dev/svg/text.png">text.png</a> shows how various types and effects with text are handled. Note that SVG font support is not yet implemented. Furthermore, text handling in PostScript output is inferior to PDF output - more text will be painted as shapes in PS than in PDF.</p>
 <p>When there's no support to paint text using native text operations, text is converted and drawn as a set of shapes by Batik, using the stroking text painter. This means that a typical character will have about 10 curves (each curve consists of at least 20 characters). This can make the output files large and when it is viewed the viewer may not normally draw those fine curves very well (In Adobe Acrobat, turning on "Smooth Line Art" in the preferences will fix this). Copy/paste functionality will not be supported in this case. If the text is inserted into the output file using the inbuilt text commands it will use a single character.</p>
 <p>Note that because SVG text can be rendered as either text or a vector graphic, you may need to consider settings in your viewer for both. The Acrobat viewer has both "smooth line art" and "smooth text" settings that may need to be set for SVG images to be displayed nicely on your screen (see Edit / Preferences / Display). This setting will not affect the printing of your document, which should be OK in any case, but will only affect the quality of the screen display.</p>
-<h3 id="font-selection-notes-wzxhzdk45wzxhzdk46">Font selection notes ## <a id="svg-font-selection"></a></h3>
+<h4 id="font-selection-notes-wzxhzdk45wzxhzdk46">Font selection notes ## <a id="svg-font-selection"></a></h4>
 <p>Apache Batik uses the AWT/Java2D subsystem as font source while FOP has its own font subsystem. Great care has been taken that font selection does the best possible choices. But it must be noted when creating PDF or PostScript that a font used in SVG graphics needs to be registered with the operating system as well as in FOP's configuration. By using FOP's font auto-detection, you simply have to install the font in the operating system and not care about anything else. This is less of an issue if you create formats like TIFFs, PNGs or PCL because in these cases SVG graphics are usually rendered to bitmaps which means that on both sides (Batik and FOP), AWT/Java2D is used as the single font source.</p>
 <p>Whenever an SVG is converted into a PDF or PostScript file, the font that has been used inside Batik has to be mapped to a font used by the actual output format. Features like font substitution in FOP may need to be taken into account but can also be an advantage when working around font mapping issues. Like for XSL-FO content, you'll get a warning if a particular font could not be found and had to be substituted, or if a particular glyph is missing in a font.</p>
-<h3 id="scaling-wzxhzdk47wzxhzdk48">Scaling ## <a id="svg-scaling"></a></h3>
+<h4 id="scaling-wzxhzdk47wzxhzdk48">Scaling ## <a id="svg-scaling"></a></h4>
 <p>Currently, SVG images are rendered with the dimensions specified <em>in the SVG file</em> , within the viewport specified in the fo:external-graphic element. For everything to work properly, the two should be equal. The SVG standard leaves this issue as an implementation detail. Additional scaling options are available through XSL-FO means.</p>
 <p>If you use pixels to specify the size of an SVG graphic the "source resolution" setting in the <a href="configuration.html">configuration</a> will be used to determine the size of a pixel. The use of pixels to specify sizes is discouraged as they may be interpreted differently in different environments.</p>
-<h3 id="known-problems-wzxhzdk49wzxhzdk50">Known Problems ## <a id="svg-problems"></a></h3>
+<h4 id="known-problems-wzxhzdk49wzxhzdk50">Known Problems ## <a id="svg-problems"></a></h4>
 <ul>
 <li>
 <p>Soft mask transparency is combined with white so that it looks better on PDF 1.3 viewers but this causes the soft mask to be slightly lighter or darker on PDF 1.4 viewers.</p>
@@ -601,18 +602,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>
-<h2 id="tiff-wzxhzdk51wzxhzdk52">TIFF # <a id="tiff"></a></h2>
+<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>
-<h2 id="wmf-wzxhzdk54wzxhzdk55">WMF # <a id="wmf"></a></h2>
+<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>
-<h1 id="graphics-resolution-wzxhzdk56wzxhzdk57">Graphics Resolution  <a id="resolution"></a></h1>
+<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>
-<h1 id="page-selection-for-multi-page-formats-wzxhzdk58wzxhzdk59">Page selection for multi-page formats  <a id="page-selection"></a></h1>
+<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>
-<h1 id="image-caching-wzxhzdk62wzxhzdk63">Image caching  <a id="caching"></a></h1>
+<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/1.1/hyphenation.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/hyphenation.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/hyphenation.html Wed Oct 24 04:04:00 2012
@@ -330,9 +330,10 @@ $(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/1.1/">1.1</a></div> -->
-      	<div class="section-content"><p><version>$Revision$</version></p>
-<h1 id="hyphenation-support-wzxhzdk2wzxhzdk3">Hyphenation Support  <a id="support"></a></h1>
-<h2 id="introduction-wzxhzdk4wzxhzdk5">Introduction # <a id="intro"></a></h2>
+      	<div class="section-content"><h1 id="apachetm-fop-hyphenation">Apache(tm) FOP: Hyphenation</h1>
+<p><version>$Revision$</version></p>
+<h2 id="hyphenation-support-wzxhzdk2wzxhzdk3">Hyphenation Support  <a id="support"></a></h2>
+<h3 id="introduction-wzxhzdk4wzxhzdk5">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 Apache&trade; 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>
@@ -342,7 +343,7 @@ If you have made improvements to an exis
 <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>
 <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>
-<h2 id="installing-custom-hyphenation-patterns-wzxhzdk14wzxhzdk15">Installing Custom Hyphenation Patterns # <a id="install"></a></h2>
+<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>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/index.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/index.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/index.html Wed Oct 24 04:04:00 2012
@@ -330,13 +330,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/1.1/">1.1</a></div> -->
-      	<div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="introduction-wzxhzdk2wzxhzdk3">Introduction  <a id="intro"></a></h1>
+      	<div class="section-content"><h1 id="apachetm-fop-version-11">Apache(tm) FOP Version 1.1</h1>
+<p><version>$Revision: 1298724 $</version></p>
+<h2 id="introduction-wzxhzdk2wzxhzdk3">Introduction  <a id="intro"></a></h2>
 <p>This is Version 1.1 of Apache FOP. FOP 1.1 contains many bug fixes and a number of improvements, including important features such as support for Complex Scripts (e.g., Arabic, Hebrew, Indic, and Southeast Asian scripts). To see what has changed since the last release, please visit <a href="releaseNotes_1.1.html">Release Notes</a>.</p>
 <p>This release implements a substantial subset of the W3C XSL-FO 1.1 Recommendation. For a detailed overview of FOP's compliance with this recommendation, see <a href="../compliance.html">Compliance</a>.</p>
-<h1 id="upgrading-from-an-earlier-version-wzxhzdk4wzxhzdk5">Upgrading from an earlier version  <a id="upgrading"></a></h1>
+<h2 id="upgrading-from-an-earlier-version-wzxhzdk4wzxhzdk5">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>
-<h1 id="download-wzxhzdk6wzxhzdk7">Download  <a id="download"></a></h1>
+<h2 id="download-wzxhzdk6wzxhzdk7">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/1.1/intermediate.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/intermediate.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/intermediate.html Wed Oct 24 04:04:00 2012
@@ -330,15 +330,16 @@ $(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/1.1/">1.1</a></div> -->
-      	<div class="section-content"><p><version>$Revision$</version>
+      	<div class="section-content"><h1 id="apachetm-fop-intermediate-format">Apache(tm) FOP: Intermediate Format</h1>
+<p><version>$Revision$</version>
 Please note that the intermediate formats described here are <strong>advanced features</strong> and can be ignored by most users of Apache FOP.</p>
 <h1 id="introduction-wzxhzdk4wzxhzdk5">Introduction  <a id="introduction"></a></h1>
 <p>Apache&trade; FOP now provides two different so-called intermediate formats. The first one (let's call it the area tree XML format) is basically a 1:1 XML representation of FOP's area tree as 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> . Even though the area tree is mentioned in the XSL-FO specification, this part is not standardized. Therefore, the area tree XML format is a FOP-proprietary XML file format. The area tree XML can be generated through the area tree XML Renderer (the XMLRenderer).</p>
 <p>The second intermediate format (which we shall name exactly like this: the intermediate format) is a recent addition which tries to meet a slightly different set of goals. It is highly optimized for speed.</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>
-<h1 id="which-intermediate-format-to-choose-wzxhzdk7wzxhzdk8">Which Intermediate Format to choose?  <a id="which-if"></a></h1>
+<h2 id="which-intermediate-format-to-choose-wzxhzdk7wzxhzdk8">Which Intermediate Format to choose?  <a id="which-if"></a></h2>
 <p>Both formats have their use cases, so the choice you will make will depend on your particular situation. Here is a list of strengths and use cases for both formats:</p>
-<h2 id="area-tree-xml-at-xml-wzxhzdk9wzxhzdk10">Area Tree XML (AT XML) # <a id="strengths-at"></a></h2>
+<h3 id="area-tree-xml-at-xml-wzxhzdk9wzxhzdk10">Area Tree XML (AT XML) # <a id="strengths-at"></a></h3>
 <ul>
 <li>
 <p>1:1 representation of FOP's area tree in XML.</p>
@@ -350,7 +351,7 @@ Please note that the intermediate format
 <p>Used in FOP's layout engine test suite for regression testing.</p>
 </li>
 </ul>
-<h2 id="intermediate-format-if-wzxhzdk11wzxhzdk12">Intermediate Format (IF) # <a id="strengths-if"></a></h2>
+<h3 id="intermediate-format-if-wzxhzdk11wzxhzdk12">Intermediate Format (IF) # <a id="strengths-if"></a></h3>
 <ul>
 <li>
 <p>Highly optimized for speed.</p>
@@ -369,7 +370,7 @@ Please note that the intermediate format
 </li>
 </ul>
 <p>More technical information about the two formats can be found on the <a href="http://wiki.apache.org/xmlgraphics-fop/AreaTreeIntermediateXml/NewDesign">FOP Wiki</a> .</p>
-<h1 id="architectural-overview-wzxhzdk13wzxhzdk14">Architectural Overview  <a id="architecture"></a></h1>
+<h2 id="architectural-overview-wzxhzdk13wzxhzdk14">Architectural Overview  <a id="architecture"></a></h2>
 <p><figure alt="Diagram with an architectural overview over the intermediate formats" src="images/if-architecture-overview.png"></figure></p>
 <h1 id="usage-of-the-area-tree-xml-format-at-xml-wzxhzdk17wzxhzdk18">Usage of the Area Tree XML format (AT XML)  <a id="usage"></a></h1>
 <p>As already mentioned, the area tree XML format 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.</p>
@@ -404,14 +405,14 @@ try {
 }
 This example simply reads an area tree 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 area tree XML 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>
-<h2 id="concatenating-documents-wzxhzdk19wzxhzdk20">Concatenating Documents # <a id="concat"></a></h2>
+<h3 id="concatenating-documents-wzxhzdk19wzxhzdk20">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/atxml/ExampleConcat.java">ExampleConcat.java</a> example shows you can easily parse multiple area tree 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>
-<h2 id="modifying-documents-wzxhzdk21wzxhzdk22">Modifying Documents # <a id="modifying"></a></h2>
+<h3 id="modifying-documents-wzxhzdk21wzxhzdk22">Modifying Documents # <a id="modifying"></a></h3>
 <p>One of the most important use cases for this format is obviously modifying the area tree XML before finally rendering it to the target format. You can easily use XSLT to process the AT XML file according to your needs. Please note, that we will currently not formally describe the area tree XML 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.
 The area tree XML format is sensitive to changes in whitespace. If you're not careful, the modified file may not render correctly.</p>
 <h2 id="advanced-use-wzxhzdk23wzxhzdk24">Advanced Use # <a id="advanced"></a></h2>
 <p>The generation of the area tree 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>
-<h1 id="usage-of-the-intermediate-format-if-wzxhzdk25wzxhzdk26">Usage of the Intermediate Format (IF)  <a id="usage-if"></a></h1>
+<h2 id="usage-of-the-intermediate-format-if-wzxhzdk25wzxhzdk26">Usage of the Intermediate Format (IF)  <a id="usage-if"></a></h2>
 <p>The Intermediate Format (IF) is generated by the <strong>IFSerializer</strong> (MIME type: <strong>application/X-fop-intermediate-format</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.</p>
 <p>The IFSerializer is an implementation of the <strong>IFDocumentHandler</strong> and <strong>IFPainter</strong> interfaces. The <strong>IFRenderer</strong> class is responsible for converting FOP's area tree into calls against these two interfaces.</p>
 <ul>
@@ -455,13 +456,13 @@ try {
     out.close();
 }
 This example simply reads an intermediate file and renders it to a PDF file. Here IFParser.parse() is used, but you can also just get a SAX ContentHandler by using the IFParser.getContentHandler() method.</p>
-<h2 id="concatenating-documents-wzxhzdk27wzxhzdk28">Concatenating Documents # <a id="concat-if"></a></h2>
+<h3 id="concatenating-documents-wzxhzdk27wzxhzdk28">Concatenating Documents # <a id="concat-if"></a></h3>
 <p>This initial example is obviously not very useful. It would be faster to create the PDF file directly (without the intermediate step). 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 intermediate files in a row and use the IFConcatenator class to concatenate page sequences from multiple source files to a single output file. This particular example does the concatenation on the level of the IFDocumentHandler interface. You could also do this in XSLT or using SAX on the XML level. Whatever suits your process best.</p>
-<h2 id="modifying-documents-wzxhzdk29wzxhzdk30">Modifying Documents # <a id="modifying-if"></a></h2>
+<h3 id="modifying-documents-wzxhzdk29wzxhzdk30">Modifying Documents # <a id="modifying-if"></a></h3>
 <p>One of the most important use cases for this format is obviously modifying the intermediate format before finally rendering it to the target format. You can easily use XSLT to process the IF file according to your needs.</p>
 <p>There is an XML Schema (located under <a href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/intermediate-format-ng/">src/documentation/intermediate-format-ng</a> ) that helps you verify that your modified content is correct.</p>
 <p>For certain output formats there's a caveat: Formats like AFP and PCL do not support arbitrary transformations on the IF's "viewport" and "g" elements. Possible are only rotations in 90 degree steps and translations.</p>
-<h2 id="advanced-use-wzxhzdk31wzxhzdk32">Advanced Use # <a id="advanced-if"></a></h2>
+<h3 id="advanced-use-wzxhzdk31wzxhzdk32">Advanced Use # <a id="advanced-if"></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. So rather than just passing in a StreamResult to IFSerializer's setResult() method, you can also use a SAXResult or a DOMResult. And as you've already seen , the IFParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to start the parsing process (see <code>getContentHandler()</code> ).</p></div>
       </div>
       

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/knownissues_overview.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/knownissues_overview.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/knownissues_overview.html Wed Oct 24 04:04:00 2012
@@ -330,8 +330,9 @@ $(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/1.1/">1.1</a></div> -->
-      	<div class="section-content"><p><version>$Revision$</version></p>
-<h1 id="known-issues-wzxhzdk2wzxhzdk3">Known issues  <a id="Known+issues"></a></h1>
+      	<div class="section-content"><h1 id="apachetm-fop-known-issues">Apache(tm) FOP: Known Issues</h1>
+<p><version>$Revision$</version></p>
+<h2 id="known-issues-wzxhzdk2wzxhzdk3">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>
@@ -343,11 +344,11 @@ $(document).ready(function () {
 </li>
 </ul>
 <p>Apache&trade; 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>
-<h2 id="fo-tree-wzxhzdk6wzxhzdk7">FO Tree # <a id="FO+Tree"></a></h2>
+<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>demo-test-failure.fo</strong> (demo test failure):<br></br> <em>TODO: Add missing description in disabled-testcases.xml!</em> </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>
-<h2 id="layout-engine-wzxhzdk12wzxhzdk13">Layout Engine # <a id="Layout+Engine"></a></h2>
+<h3 id="layout-engine-wzxhzdk12wzxhzdk13">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>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>
 <p><strong>block_font-stretch.xml</strong> (font-stretch NYI):<br></br>Font-stretch is not implemented, yet.</p>
@@ -383,7 +384,7 @@ $(document).ready(function () {
 <p><strong>keep_within-page_multi-column_overflow.xml</strong> (Page-keep not respected in multi-column layout):<br></br>The block should cause overflow in the last column on the page, rather than be broken.</p>
 <p><strong>block-container_reference-orientation_bug36391.xml</strong> (Block Container Reference Orientation Bug):<br></br>An assert is failing</p>
 <p><strong>simple-page-master_writing-mode_rl_region-body_writing-mode-lr.xml</strong> (Writing mode problems):<br></br>Test erroneously depends upon incorrect implementation of writing-mode trait derivation on fo:region-*.</p>
-<h2 id="other-known-issues-wzxhzdk84wzxhzdk85">Other known issues # <a id="Other+known+issues"></a></h2>
+<h3 id="other-known-issues-wzxhzdk84wzxhzdk85">Other known issues # <a id="Other+known+issues"></a></h3>
 <p>This section lists some other issues that post-date the release of FOP 1.0. For known issues that pre-date FOP 1.0, see <a href="http://issues.apache.org/bugzilla/buglist.cgi?chfieldto=2010-07-20&amp;chfield=%5BBug%20creation%5D&amp;query_format=advanced&amp;chfieldfrom=2001-01-01&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_status=NEEDINFO&amp;product=Fop">older bugs that remain open</a> . For all open issues that post-date FOP 1.0, see <a href="http://issues.apache.org/bugzilla/buglist.cgi?chfieldto=Now&amp;chfield=%5BBug%20creation%5D&amp;query_format=advanced&amp;chfieldfrom=2010-07-20&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_status=NEEDINFO&amp;product=Fop">newer bugs that remain open</a> .</p>
 <ul>
 <li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/metadata.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/metadata.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/metadata.html Wed Oct 24 04:04:00 2012
@@ -330,12 +330,13 @@ $(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/1.1/">1.1</a></div> -->
-      	<div class="section-content"><h1 id="overview-wzxhzdk0wzxhzdk1">Overview  <a id="overview"></a></h1>
+      	<div class="section-content"><h1 id="apachetm-fop-metadata">Apache(tm) FOP: Metadata</h1>
+<h2 id="overview-wzxhzdk0wzxhzdk1">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>
-<h1 id="embedding-xmp-in-an-xsl-fo-document-wzxhzdk2wzxhzdk3">Embedding XMP in an XSL-FO document  <a id="xmp-in-fo"></a></h1>
+<h2 id="embedding-xmp-in-an-xsl-fo-document-wzxhzdk2wzxhzdk3">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>
-<h2 id="example-wzxhzdk5wzxhzdk6">Example # <a id="xmp-example"></a></h2>
+<h3 id="example-wzxhzdk5wzxhzdk6">Example # <a id="xmp-example"></a></h3>
 <p class="."></p>
 <h1 id="implementation-in-apache-fop-wzxhzdk7wzxhzdk8">Implementation in Apache FOP  <a id="xmp-impl-in-fop"></a></h1>
 <p>Currently, XMP support is only available for PDF output.</p>
@@ -430,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>
-<h1 id="links-wzxhzdk9wzxhzdk10">Links  <a id="links"></a></h1>
+<h2 id="links-wzxhzdk9wzxhzdk10">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>



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


Mime
View raw message