xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r840642 [6/6] - in /websites/staging/xmlgraphics/trunk/content: ./ fop/ fop/0.95/ fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/ fop/trunk/
Date Tue, 04 Dec 2012 05:02:25 GMT
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/extending.html
--- websites/staging/xmlgraphics/trunk/content/fop/dev/design/extending.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/extending.html Tue Dec  4 05:02:22 2012
@@ -341,11 +341,11 @@ $(document).ready(function () {
         <div id="items">
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/">Dev</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/design/">Design</a></div> -->
-      	<div class="section-content"><h1 id="apachewzxhzdk0-fop-design-extensions">Apache&trade; FOP Design: Extensions</h1>
+      	<div class="section-content"><h1 id="apachewzxhzdk2-fop-design-extensions">Apache&trade; FOP Design: Extensions</h1>
 <p><authors><person email="keiron@aftexsw.com" name="Keiron Liddle"></person></authors></p>
-<h2 id="introduction-wzxhzdk5wzxhzdk6">Introduction <a id="intro"></a></h2>
+<h2 id="introduction-wzxhzdk7wzxhzdk8">Introduction <a id="intro"></a></h2>
 <p>Apache&trade; FOP provides an extension mechanism to add extra functionality. There are a number of different types of extensions that apply to different steps when converting FO into the rendered output.</p>
-<h2 id="extensions-wzxhzdk8wzxhzdk9">Extensions <a id="Extensions"></a></h2>
+<h2 id="extensions-wzxhzdk10wzxhzdk11">Extensions <a id="Extensions"></a></h2>
 <p>SVG Graphic - This applies to svg and any other xml document that can be converted into svg in the output. All that is required is the element mapping for the xml and a converter that changes the document into svg. This conversion is done in the FO Tree. The conversion is done by the top level element of the namespace or in the case of an external image a Converter.</p>
 <p>XML Document - Instead of converting the document into svg it can be passed directly to the renderer. The renderer will need to have a handler for the xml document. This handler can add information directly to the output document.</p>
 <p>Output Document - This is used to add document level information to the output result. Such an extension will set information that is passed to the output document. The area tree handles these extensions and passs along the information to the renderer. The extension may contain resolveable objects. The extension can be passed to the renderer once resolve either immediately, after the next page or at the end of the document. This is so that the extension can be handled according to other associated data.</p>
@@ -359,21 +359,27 @@ $(document).ready(function () {
 <p>Separate page number display for a subsection. ie. - master document is page 4 of 7, but subsection is page 2 of 3.</p>
-<h2 id="examples-wzxhzdk10wzxhzdk11">Examples <a id="Examples"></a></h2>
+<h2 id="examples-wzxhzdk12wzxhzdk13">Examples <a id="Examples"></a></h2>
 <p>Plan - The plan extension is a simple SVG graphic extension. Given a plan document either inside an InstreamForeignObject or as an external graphic, it converts the plan document into an svg graphic. The svg graphic is then passed through the Area Tree to the Renderer. The Renderer then renders the svg graphic as normal.</p>
 <p>PDF Outline - This is output document extension. If rendering to pdf and this extensionis used then the bookmark information is passed to the pdf document. This information is then set on the document.</p>
 <p>PDF Additions - This can be done with an XML Document extension. A simple xml document is defined that provides the appropriate information. When the document is rendered a handler converts the document into PDF markup.</p>
-<p>For example:
-<my:script-link script="app.execMenuItem('AcroSrch:Query');">
+<p>For example:</p>
+<div class="codehilite"><pre><span class="nt">&lt;my:script-link</span> <span class="na">script=</span><span class="s">&quot;app.execMenuItem(&#39;AcroSrch:Query&#39;);&quot;</span><span class="nt">&gt;</span>
-to result in a text box referencing the following PDF action:
-/S /JavaScript
-/JS (app.execMenuItem("AcroSrch:Query");)</p>
+<span class="nt">&lt;/my:script-link&gt;</span>
+<p>to result in a text box referencing the following PDF action:</p>
+<div class="codehilite"><pre><span class="o">&lt;&lt;</span>
+<span class="sr">/S /</span><span class="n">JavaScript</span>
+<span class="o">/</span><span class="n">JS</span> <span class="p">(</span><span class="n">app</span><span class="o">.</span><span class="n">execMenuItem</span><span class="p">(</span><span class="s">&quot;AcroSrch:Query&quot;</span><span class="p">);)</span>
+<span class="o">&gt;&gt;</span>
 <h1 id="status-wzxhzdk14wzxhzdk15">Status <a id="status"></a></h1>
 <h3 id="to-do-wzxhzdk16wzxhzdk17">To Do <a id="status-todo"></a></h3>
 <h3 id="work-in-progress-wzxhzdk18wzxhzdk19">Work In Progress <a id="status-wip"></a></h3>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/properties.html
--- websites/staging/xmlgraphics/trunk/content/fop/dev/design/properties.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/properties.html Tue Dec  4 05:02:22 2012
@@ -343,9 +343,9 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/">Dev</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/design/">Design</a></div> -->
       	<div class="section-content"><h1 id="apache-fop-design-properties">Apache™ FOP Design: Properties</h1>
 <p><authors><person email="" name="Karen Lease"></person></authors></p>
-<h2 id="introduction-wzxhzdk4wzxhzdk5">Introduction <a id="intro"></a></h2>
+<h2 id="introduction-wzxhzdk5wzxhzdk6">Introduction <a id="intro"></a></h2>
 <p>As the input XSL-FO is being parsed and the FO Tree is being built, the attributes of the FO elements are passed by the parser to the related FO object. The java object that represent the FO object then converts the attributes into properties that are stored in the FO Tree.</p>
-<h2 id="issues-wzxhzdk6wzxhzdk7">Issues <a id="issues"></a></h2>
+<h2 id="issues-wzxhzdk7wzxhzdk8">Issues <a id="issues"></a></h2>
 <p>The following are some issues when dealing with properties:</p>
@@ -364,7 +364,7 @@ $(document).ready(function () {
 <p>Expressions: XSL-FO expressions can be included in properties.</p>
-<h2 id="overview-of-processing-wzxhzdk8wzxhzdk9">Overview of Processing <a id="process-overview"></a></h2>
+<h2 id="overview-of-processing-wzxhzdk9wzxhzdk10">Overview of Processing <a id="process-overview"></a></h2>
 <p>The general flow of property processing is as follows:</p>
@@ -377,10 +377,10 @@ $(document).ready(function () {
 <p>FObj.handleAttrs then cross-references the returned PropertyList with the FObj, creates a PropertyManager to facilitate downstream processing of the PropertyList, and handles the special case of the writing-mode property.</p>
-<h2 id="propertylistbuilder-wzxhzdk10wzxhzdk11">PropertyListBuilder <a id="plb"></a></h2>
+<h2 id="propertylistbuilder-wzxhzdk11wzxhzdk12">PropertyListBuilder <a id="plb"></a></h2>
 <p>Each plb object contains a hash of property names and <em>their</em> respective Makers. It may also contain element-specific property maker hashes; these are based on the <em>local name</em> of the flow object, ie. <em>table-row</em> , not <em>fo:table-row</em> . If an element-specific property mapping exists, it is preferred to the generic mapping.</p>
 <p>The PLB loops through each attribute in the list, finds an appropriate "Maker" for it, then calls the Maker to convert the attribute value into a Property object of the correct type, and stores that Property in the PropertyList.</p>
-<h2 id="property-datatypes-wzxhzdk12wzxhzdk13">Property datatypes <a id="datatypes"></a></h2>
+<h2 id="property-datatypes-wzxhzdk13wzxhzdk14">Property datatypes <a id="datatypes"></a></h2>
 <p>The property datatypes are defined in the org.apache.fop.datatypes package, except Number and String which are java primitives. The FOP datatypes are:</p>
@@ -411,57 +411,60 @@ $(document).ready(function () {
 <p>The <em>org.apache.fop.fo.Property</em> class is the superclass for all Property subclasses. There is a subclass for each kind of property datatype. These are named using the datatype name plus the word Property, resulting in NumberProperty, StringProperty, and so on. There is also a class EnumProperty which uses an <code>int</code> primitive to hold enumerated values. There is no corresponding Enum datatype class.</p>
 <p>The Property class provides a "wrapper" around any possible property value. Code manipulating property values (in layout for example) usually knows what kind (or kinds) of datatypes are acceptable for a given property and will use the appropriate accessor.</p>
 <p>The base Property class defines accessor methods for all FO property datatypes, such as getNumber(), getColorType(), getSpace(), getEnum(), etc. It doesn't define accessors for SVG types, since these are handled separately (at least for now.) In the base Property class, all of these methods return null, except getEnum which returns 0. Individual subclasses return a value of the appropriate type, such as Length or ColorType. A subclass may also choose to return a reasonable value for other accessor types. For example, a SpaceProperty will return the optimum value if asked for a Length.</p>
-<h2 id="property-makers-wzxhzdk14wzxhzdk15">Property Makers <a id="makers"></a></h2>
+<h2 id="property-makers-wzxhzdk15wzxhzdk16">Property Makers <a id="makers"></a></h2>
 <p>The Property class contains a nested class called <em>Maker</em> . This is the base class for all other property Makers. It provides basic framework functionality which is overridden by the code generated by properties.xsl from the *properties.xml files. In particular it provides basic expression evaluation, using PropertyParser class in the org.apache.fop.fo.expr package.</p>
 <p>Other Property subclasses such as LengthProperty define their own nested Maker classes (subclasses of Property.Maker). These handle conversion from the Property subclass returned from expression evaluation into the appropriate subclass for the property.</p>
 <p>For each generic or specific property definition in the properties.xml files, a new subclass of one of the Maker classes is created. Note that no new Property subclasses are created, only new PropertyMaker subclasses. Once the property value has been parsed and stored, it has no specific functionality. Only the Maker code is specific. Maker subclasses define such aspects as keyword substitutions, whether the property can be inherited or not, which enumerated values are legal, default values, corresponding properties and specific datatype conversions.</p>
 <p>The PLB finds a "Maker" for the property based on the attribute name and the element name. Most Makers are generic and handle the attribute on any element, but it's possible to set up an element-specific property Maker. The attribute name to Maker mappings are automatically created during the code generation phase by processing the XML property description files.</p>
-<h2 id="processing-the-attribute-list-wzxhzdk16wzxhzdk17">Processing the attribute list <a id="attribute-list"></a></h2>
+<h2 id="processing-the-attribute-list-wzxhzdk17wzxhzdk18">Processing the attribute list <a id="attribute-list"></a></h2>
 <p>The PLB first looks to see if the font-size property is specified, since it sets up relative units which can be used in other property specifications. Each attribute is then handled in turn. If the attribute specifies part of a compound property such as space-before.optimum, the PLB looks to see if the attribute list also contains the "base" property (space-before in this case) and processes that first.</p>
-<h2 id="how-the-property-maker-works-wzxhzdk18wzxhzdk19">How the Property Maker works <a id="maker-design"></a></h2>
+<h2 id="how-the-property-maker-works-wzxhzdk19wzxhzdk20">How the Property Maker works <a id="maker-design"></a></h2>
 <p>There is a family of Maker objects for each of the property datatypes, such as Length, Number, Enumerated, Space, etc. But since each Property has specific aspects such as whether it's inherited, its default value, its corresponding properties, etc. there is usually a specific Maker for each Property. All these Maker classes are created during the code generation phase by processing (using XSLT) the XML property description files to create Java classes.</p>
 <p>The Maker first checks for "keyword" values for a property. These are things like "thin, medium, thick" for the border-width property. The datatype is really a Length but it can be specified using these keywords whose actual value is determined by the "User Agent" rather than being specified in the XSL standard. For FOP, these values are currently defined in foproperties.xml. The keyword value is just a string, so it still needs to be parsed as described next.</p>
 <p>The Maker also checks to see if the property is an Enumerated type and then checks whether the value matches one of the specified enumeration values.</p>
 <p>Otherwise the Maker uses the property parser in the fo.expr package to evaluate the attribute value and return a Property object. The parser interprets the expression language and performs numeric operations and function call evaluations.</p>
 <p>If the returned Property value is of the correct type (specificed in foproperties.xml, where else?), the Maker returns it. Otherwise, it may be able to convert the returned type into the correct type.</p>
 <p>Some kinds of property values can't be fully resolved during FO tree building because they depend on layout information. This is the case of length values specified as percentages and of the special proportional-column-width(x) specification for table-column widths. These are stored as special kinds of Length objects which are evaluated during layout. Expressions involving "em" units which are relative to font-size <em>are</em> resolved during the FO tree building however.</p>
-<h2 id="structure-of-the-propertylist-wzxhzdk20wzxhzdk21">Structure of the PropertyList <a id="property-list-struct"></a></h2>
+<h2 id="structure-of-the-propertylist-wzxhzdk21wzxhzdk22">Structure of the PropertyList <a id="property-list-struct"></a></h2>
 <p>The PropertyList extends HashMap and its basic function is to associate Property value objects with Property names. The Property objects are all subclasses of the base Property class. Each one simply contains a reference to one of the property datatype objects. Property provides accessors for all known datatypes and various subclasses override the accessor(s) which are reasonable for the datatype they store.</p>
 <p>The PropertyList itself provides various ways of looking up Property values to handle such issues as inheritance and corresponding properties.</p>
 <p>The main logic is:<br></br>If the property is a writing-mode relative property (using start, end, before or after in its name), the corresponding absolute property value is returned if it's explicitly set on this FO.<br></br>Otherwise, the writing-mode relative value is returned if it's explicitly set. If the property is inherited, the process repeats using the PropertyList of the FO's parent object. (This is easy because each PropertyList points to the PropertyList of the nearest ancestor FO.) If the property isn't inherited or no value is found at any level, the initial value is returned.</p>
-<h2 id="implementing-standard-properties-wzxhzdk26wzxhzdk27">Implementing Standard Properties <a id="property-spec"></a></h2>
+<h2 id="implementing-standard-properties-wzxhzdk27wzxhzdk28">Implementing Standard Properties <a id="property-spec"></a></h2>
 <p>Because the properties defined in the standard are basically static, FOP currently builds the source code for the related Property classes from an XML data file. All properties are specified in src/codegen/foproperties.xml. The related classes are created automatically during the build process by applying an XSLT stylesheet to the foproperties.xml file.</p>
-<h3 id="generic-properties-wzxhzdk28wzxhzdk29">Generic properties <a id="generic"></a></h3>
+<h3 id="generic-properties-wzxhzdk29wzxhzdk30">Generic properties <a id="generic"></a></h3>
 <p>In the properties xml files, one can define generic property definitions which can serve as a basis for individual property definitions. There are currently several generic properties defined in foproperties.xml. An example is GenericColor, which defines basic properties for all ColorType properties. Since the generic specification doesn't include the inherited or default elements, these should be set in each property which is based on GenericColor. Here is an example:</p>
-<p><code>&lt;property type='generic'&gt;
-    &lt;name&gt;background-color&lt;/name&gt;
-    &lt;use-generic&gt;GenericColor&lt;/use-generic&gt;
-    &lt;inherited&gt;false&lt;/inherited&gt;
-    &lt;default&gt;transparent&lt;/default&gt;
-  &lt;/property&gt;</code> </p>
+<div class="codehilite"><pre> `<span class="nt">&lt;property</span> <span class="na">type=</span><span class="s">&#39;generic&#39;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;name&gt;</span>background-color<span class="nt">&lt;/name&gt;</span>
+    <span class="nt">&lt;use-generic&gt;</span>GenericColor<span class="nt">&lt;/use-generic&gt;</span>
+    <span class="nt">&lt;inherited&gt;</span>false<span class="nt">&lt;/inherited&gt;</span>
+    <span class="nt">&lt;default&gt;</span>transparent<span class="nt">&lt;/default&gt;</span>
+  <span class="nt">&lt;/property&gt;</span>`
 <p>A generic property specification can include all of the elements defined for the property element in the DTD, including the description of components for compound properties, and the specification of keyword shorthands.</p>
 <p>Generic property specifications can be based on other generic specifications. An example is GenericCondPadding template which is based on the GenericCondLength definition but which extends it by adding an inherited element and a default value for the length component.</p>
 <p>Generic properties can specify enumerated values, as in the GenericBorderStyle template. This means that the list of values, which is used by 8 properties (the "absolute" and "writing-mode-relative" variants for each BorderStyle property) is only specified one time.</p>
 <p>When a property includes a "use-generic" element and includes no other elements (except the "name" element), then no class is generated for the property. Instead the generated mapping will associate this property directly with an instance of the generic Maker.</p>
 <p>A generic class may also be hand-coded, rather than generated from the properties file. Properties based on such a generic class are indicated by the attribute <code>ispropclass='true'</code> on the <em>use-generic</em> element.</p>
 <p>This is illustrated by the SVG properties, most of which use one of the Property subclasses defined in the <em>org.apache.fop.svg</em> package. Although all of these properties are now declared in svgproperties.xml, no specific classes are generated. Classes are only generated for those SVG properties which are not based on generic classes defined in svg.</p>
-<h3 id="element-specific-properties-wzxhzdk30wzxhzdk31">Element-specific properties <a id="element-specific"></a></h3>
+<h3 id="element-specific-properties-wzxhzdk31wzxhzdk32">Element-specific properties <a id="element-specific"></a></h3>
 <p>Properties may be defined for all flow objects or only for particular flow objects. A PropertyListBuilder object will always look first for a Property.Maker for the flow object before looking in the general list. These are specified in the <code>element-property-list</code> section of the properties.xml files. The <code>localname</code> element children of this element specify for which flow-object elements the property should be registered.</p>
 <p><em>NOTE</em> : All the properties for an object or set of objects must be specified in a single element-property-list element. If the same localname appears in several element lists, the later set of properties will hide the earlier ones! Use the <em>ref</em> functionality if the same property is to be used in different sets of element-specific mappings.</p>
-<h3 id="reference-properties-wzxhzdk32wzxhzdk33">Reference properties <a id="reference"></a></h3>
+<h3 id="reference-properties-wzxhzdk33wzxhzdk34">Reference properties <a id="reference"></a></h3>
 <p>A property element may have a type attribute with the value <code>ref</code> . The content of the <em>name</em> child element is the name of the referenced property (not its class-name!). This indicates that the property specification has already been given, either in this same specification file or in a different one (indicated by the <code>family</code> attribute). The value of the family attribute is <em>XX</em> where the file <em>XXproperties.xml</em> defines the referenced property. For example, some SVG objects may have properties defined for FO. Rather than defining them again with a new name, the SVG properties simply reference the defined FO properties. The generating mapping for the SVG properties will use the FO Maker classes.</p>
-<h3 id="corresponding-properties-wzxhzdk34wzxhzdk35">Corresponding properties <a id="corresponding"></a></h3>
+<h3 id="corresponding-properties-wzxhzdk35wzxhzdk36">Corresponding properties <a id="corresponding"></a></h3>
 <p>Some properties have both <em>absolute</em> and <em>writing-mode-relative</em> forms. In general, the absolute forms are equivalent to CSS properties, and the writing-mode-relative forms are based on DSSSL. FO files may use either or both forms. In FOP code, a request for an absolute form will retrieve that value if it was specified on the FO; otherwise the corresponding relative property will be used if it was specified. However, a request for a relative form will only use the specified relative value if the corresponding absolute value was <em>not</em> specified for that FO.</p>
 <p>Corresponding properties are specified in the properties.xml files using the element <code>corresponding</code> , which has at least one <code>propval</code> child and may have a <code>propexpr</code> child, if the corresponding value is calculated based on several other properties, as for <code>start-indent</code> .</p>
 <p><em>NOTE</em> : most current FOP code accesses the absolute variants of these properties, notably for padding, border, height and width attributes. However it does use start-indent and end-indent, rather than the "absolute" margin properties.</p>
-<h2 id="mapping-wzxhzdk36wzxhzdk37">Mapping <a id="mapping"></a></h2>
+<h2 id="mapping-wzxhzdk37wzxhzdk38">Mapping <a id="mapping"></a></h2>
 <p>The XSL script <code>propmap.xsl</code> is used to generate property mappings based on both foproperties.xml and svgproperties.xml. The mapping classes in the main fop packages simply load these automatically generated mappings. The mapping code still uses the static "maker" function of the generated object to obtain a Maker object. However, for all generated classes, this method returns an instance of the class itself (which is a subclass of Property.Maker) and not an instance of a separate nested Maker class.</p>
 <p>For most SVG properties which use the SVG Property classes directly, the generated mapper code calls the "maker" method of the SVG Property class, which returns an instance of its nested Maker class.</p>
 <p>The property generation also handles element-specific property mappings as specified in the properties XML files.</p>
-<h2 id="enumerated-values-wzxhzdk38wzxhzdk39">Enumerated values <a id="enumerated"></a></h2>
+<h2 id="enumerated-values-wzxhzdk39wzxhzdk40">Enumerated values <a id="enumerated"></a></h2>
 <p>For any property whose datatype is <code>Enum</code> or which contains possible enumerated values, FOP code may need to access enumeration constants. These are defined in the interfaces whose name is the same as the generated class name for the property, for example <code>BorderBeforeStyle.NONE</code> . These interface classes are generated by the XSL script <code>enumgen.xsl</code> . A separate interface defining the enumeration constants is always generated for every property which uses the constants, even if the constants themselves are defined in a generic class, as in BorderStyle.</p>
 <p>If a subproperty or component of a compound property has enumerated values, the constants are defined in a nested interface whose name is the name of the subproperty (using appropriate capitalization rules). For example, the keep properties may have values of AUTO or FORCE or an integer value. These are defined for each kind of keep property. For example, the keep-together property is a compound property with the components within-line, within-column and within-page. Since each component may have the values AUTO or FORCE, the KeepTogether interface defines three nested interfaces, one for each component, and each defines these two constants. An example of a reference in code to the constant is <code>KeepTogether.WithinPage.AUTO</code> .</p>
-<h2 id="compound-property-types-wzxhzdk40wzxhzdk41">Compound property types <a id="compound"></a></h2>
+<h2 id="compound-property-types-wzxhzdk41wzxhzdk42">Compound property types <a id="compound"></a></h2>
 <p>Some XSL FO properties are specified by compound datatypes. In the FO file, these are defined by a group of attributes, each having a name of the form <code>property.component</code> , for example <code>space-before.minimum</code> . These are several compound datatypes:</p>
@@ -479,9 +482,9 @@ $(document).ready(function () {
 <p>These are described in the properties.xml files using the element <code>compound</code> which has <code>subproperty</code> children. A subproperty element is much like a property element, although it may not have an <code>inherited</code> child element, as only a complete property object may be inherited.</p>
 <p>Specific datatype classes exist for each compound property. Each component of a compound datatype is itself stored as a Property object. Individual components may be accessed either by directly performing a get operation on the name, using the "dot" notation, eg. <code>get("space-before.optimum")</code> ; or by using an accessor on the compound property, eg. <code>get("space-before").getOptimum()</code> . In either case, the result is a Property object, and the actual value may be accessed (in this example) by using the "getLength()" accessor.</p>
-<h2 id="refinement-wzxhzdk42wzxhzdk43">Refinement <a id="refine"></a></h2>
+<h2 id="refinement-wzxhzdk43wzxhzdk44">Refinement <a id="refine"></a></h2>
 <p>The <strong>Refinement</strong> step is part of reading and using the properties which may happen immediately or during the layout process. FOP does not currently use a separate Refinement process, but tends to handle refining steps as the FO Tree is built.</p>
-<h2 id="refined-fo-tree-wzxhzdk44wzxhzdk45">Refined FO Tree <a id="refined-fo-tree"></a></h2>
+<h2 id="refined-fo-tree-wzxhzdk45wzxhzdk46">Refined FO Tree <a id="refined-fo-tree"></a></h2>
 <p>The Refined FO Tree is the result of the Refinement process.</p></div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/index.html
--- websites/staging/xmlgraphics/trunk/content/fop/dev/index.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/index.html Tue Dec  4 05:02:22 2012
@@ -349,9 +349,9 @@ $(document).ready(function () {
 <p>The main development happens on "FOP Trunk".
 The SVN repository URL for the trunk is:<br></br> <code>http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/</code> </p>
 <h1 id="getting-involved-wzxhzdk9wzxhzdk10">Getting Involved <a id="involved"></a></h1>
-<h3 id="understand-apache-roles-wzxhzdk11wzxhzdk12">Understand Apache Roles <a id="apache-roles"></a></h3>
+<h2 id="understand-apache-roles-wzxhzdk11wzxhzdk12">Understand Apache Roles <a id="apache-roles"></a></h2>
 <p>Review the <a href="http://xml.apache.org/roles.html">Apache Project Roles and Responsibilities</a> document for an understanding of the various roles of contributors within the community.</p>
-<h3 id="how-you-can-help-wzxhzdk13wzxhzdk14">How you can help <a id="fop-tasks"></a></h3>
+<h2 id="how-you-can-help-wzxhzdk13wzxhzdk14">How you can help <a id="fop-tasks"></a></h2>
 <p>There are many different ways that you can help with FOP development. The following is a non-exhaustive list of ways that <em>non-programmers</em> can help. Remember that an hour spent on the tasks below is an hour that a programmer can devote to fixing bugs or adding features instead:</p>
@@ -390,7 +390,7 @@ The SVN repository URL for the trunk is:
 <h3 id="understand-fop-related-standards-wzxhzdk15wzxhzdk16">Understand FOP-related standards <a id="fop-standards"></a></h3>
 <p>At the moment FOP is mainly a tool to render XSL-FO files to pdf. Therefore if you want to contribute to FOP you should become familiar with these standards. You can find links at <a href="../resources.html#specs">Specifications</a> .</p>
-<h3 id="review-the-developer-documentation-wzxhzdk17wzxhzdk18">Review the Developer Documentation <a id="doc"></a></h3>
+<h2 id="review-the-developer-documentation-wzxhzdk17wzxhzdk18">Review the Developer Documentation <a id="doc"></a></h2>
 <h3 id="understand-fops-design-wzxhzdk19wzxhzdk20">Understand FOP's Design <a id="design"></a></h3>
 <p>The design for FOP is specified under the <a href="design/index.html">Design</a> section. This is where the information on how FOP is developed and designed internally will be kept.</p>
 <p>Another place where we write design documentation is the <a href="http://wiki.apache.org/xmlgraphics-fop/DeveloperPages">FOP Wiki</a> .

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/events.html
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/events.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/events.html Tue Dec  4 05:02:22 2012
@@ -365,12 +365,13 @@ $(document).ready(function () {
 <p>The <code>EventFormatter</code> class can be used to translate the events into human-readable, localized messages.</p>
 <p>A full example of what is shown here can be found in the <code>examples/embedding/java/embedding/events</code> directory in the FOP distribution. The example can also be accessed <a href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/examples/embedding/java/embedding/events/">via the web</a> .</p>
 <h3 id="writing-an-eventlistener-wzxhzdk14wzxhzdk15">Writing an EventListener <a id="write-listener"></a></h3>
-<p>The following code sample shows a very simple EventListener. It basically just sends all events to System.out (stdout) or System.err (stderr) depending on the event severity.
-    import org.apache.fop.events.Event;
-    import org.apache.fop.events.EventFormatter;
-    import org.apache.fop.events.EventListener;
-    import org.apache.fop.events.model.EventSeverity;</p>
-<div class="codehilite"><pre><span class="sr">/** A simple event listener that writes the events to stdout and stderr. */</span>
+<p>The following code sample shows a very simple EventListener. It basically just sends all events to System.out (stdout) or System.err (stderr) depending on the event severity.</p>
+<div class="codehilite"><pre><span class="nb">import</span> <span class="n">org</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">fop</span><span class="o">.</span><span class="n">events</span><span class="o">.</span><span class="n">Event</span><span class="p">;</span>
+<span class="nb">import</span> <span class="n">org</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">fop</span><span class="o">.</span><span class="n">events</span><span class="o">.</span><span class="n">EventFormatter</span><span class="p">;</span>
+<span class="nb">import</span> <span class="n">org</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">fop</span><span class="o">.</span><span class="n">events</span><span class="o">.</span><span class="n">EventListener</span><span class="p">;</span>
+<span class="nb">import</span> <span class="n">org</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">fop</span><span class="o">.</span><span class="n">events</span><span class="o">.</span><span class="n">model</span><span class="o">.</span><span class="n">EventSeverity</span><span class="p">;</span>
+<span class="sr">/** A simple event listener that writes the events to stdout and stderr. */</span>
 <span class="n">public</span> <span class="n">class</span> <span class="n">SysOutEventListener</span> <span class="n">implements</span> <span class="n">EventListener</span> <span class="p">{</span>
     <span class="sr">/** {@inheritDoc} */</span>

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

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/output.html
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/output.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/output.html Tue Dec  4 05:02:22 2012
@@ -341,11 +341,11 @@ $(document).ready(function () {
         <div id="items">
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/trunk/">Trunk</a></div> -->
-      	<div class="section-content"><h1 id="apachewzxhzdk40-fop-output-formats">Apache&trade; FOP Output Formats</h1>
+      	<div class="section-content"><h1 id="apachewzxhzdk41-fop-output-formats">Apache&trade; FOP Output Formats</h1>
 <p><authors><person email="keiron@aftexsw.com" name="Keiron Liddle"></person><person email="" name="Art Welch"></person></authors></p>
 <p>Apache&trade; FOP supports multiple output formats by using a different renderer for each format. The renderers do not all have the same set of capabilities, sometimes because of the output format itself, sometimes because some renderers get more development attention than others.</p>
-<h2 id="general-information-wzxhzdk48wzxhzdk49">General Information <a id="general"></a></h2>
-<h3 id="fonts-wzxhzdk50wzxhzdk51">Fonts <a id="general-fonts"></a></h3>
+<h2 id="general-information-wzxhzdk49wzxhzdk50">General Information <a id="general"></a></h2>
+<h3 id="fonts-wzxhzdk51wzxhzdk52">Fonts <a id="general-fonts"></a></h3>
 <p>Most FOP renderers use a FOP-specific system for font registration. However, the Java2D/AWT and print renderers use the Java AWT package, which gets its font information from the operating system registration. This can result in several differences, including actually using different fonts, and having different font metrics for the same font. The net effect is that the layout of a given FO document can be quite different between renderers that do not use the same font information.</p>
 <p>Theoretically, there's some potential to make the output of the PDF/PS renderers match the output of the Java2D-based renderers. If FOP used the font metrics from its own font subsystem but still used Java2D for text painting in the Java2D-based renderers, this could probably be achieved. However, this approach hasn't been implemented, yet.</p>
 <p>With a work-around, it is possible to match the PDF/PS output in a Java2D-based renderer pretty closely. The clue is to use the <a href="intermediate.html">intermediate format</a> . The trick is to layout the document using FOP's own font subsystem but then render the document using Java2D. Here are the necessary steps (using the command-line):</p>
@@ -369,7 +369,7 @@ $(document).ready(function () {
 <p><code>fop -atin myfile.at.xml -tiff myfile.tiff</code> </p>
-<h3 id="output-to-a-printer-or-other-device-wzxhzdk52wzxhzdk53">Output to a Printer or Other Device <a id="general-direct-output"></a></h3>
+<h3 id="output-to-a-printer-or-other-device-wzxhzdk53wzxhzdk54">Output to a Printer or Other Device <a id="general-direct-output"></a></h3>
 <p>The most obvious way to print your document is to use the FOP <a href="#print">print renderer</a> , which uses the Java2D API (AWT). However, you can also send output from the Postscript renderer directly to a Postscript device, or output from the PCL renderer directly to a PCL device.</p>
 <p>Here are Windows command-line examples for Postscript and PCL:
 fop ... -ps \computername\printerfop ... -pcl \computername\printer
@@ -377,12 +377,12 @@ Here is some Java code to accomplish the
 proc = Runtime.getRuntime().exec("lp -d" + print_queue + " -o -dp -");
 out = proc.getOutputStream();
 Set the output MIME type to "application/x-pcl" (MimeConstants.MIME_PCL) and it happily sends the PCL to the UNIX printer queue.</p>
-<h2 id="pdf-wzxhzdk54wzxhzdk55">PDF <a id="pdf"></a></h2>
+<h2 id="pdf-wzxhzdk55wzxhzdk56">PDF <a id="pdf"></a></h2>
 <p>PDF is the best supported output format. It is also the most accurate with text and layout. This creates a PDF document that is streamed out as each page is rendered. This means that the internal page index information is stored near the end of the document. The PDF version supported is 1.4. PDF versions are forwards/backwards compatible.</p>
 <p>Note that FOP does not currently support PDF/A-1a. Support for <a href="accessibility.html">Tagged PDF</a> , <a href="pdfa.html">PDF/A-1b</a> and <a href="pdfx.html">PDF/X</a> has recently been added, however.</p>
-<h3 id="fonts-wzxhzdk56wzxhzdk57">Fonts <a id="pdf-fonts"></a></h3>
+<h3 id="fonts-wzxhzdk57wzxhzdk58">Fonts <a id="pdf-fonts"></a></h3>
 <p>PDF has a set of fonts that are always available to all PDF viewers; to quote from the PDF Specification: <em>"PDF prescribes a set of 14 standard fonts that can be used without prior definition. These include four faces each of three Latin text typefaces (Courier, Helvetica, and Times), as well as two symbolic fonts (Symbol and ITC Zapf Dingbats). These fonts, or suitable substitute fonts with the same metrics, are guaranteed to be available in all PDF viewer applications."</em> </p>
-<h3 id="post-processing-wzxhzdk58wzxhzdk59">Post-processing <a id="pdf-postprocess"></a></h3>
+<h3 id="post-processing-wzxhzdk59wzxhzdk60">Post-processing <a id="pdf-postprocess"></a></h3>
 <p>FOP does not currently support several desirable PDF features: watermarks and signatures. One workaround is to use Adobe Acrobat (the full version, not the Reader) to process the file manually or with scripting that it supports.</p>
 <p>Another popular post-processing tool is <a href="http://www.lowagie.com/iText">iText</a> , which has tools for adding security features, document properties, watermarks, and many other features to PDF files.
 <warning>Caveat: iText may swallow PDF bookmarks. But <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37589">Jens Stavnstrup tells us</a> that this doesn't happen if you use iText's PDFStamper.</warning>
@@ -432,7 +432,7 @@ Here is some sample code that uses iText
 <p>Check the iText tutorial and documentation for setting access flags, password, encryption strength and other parameters.</p>
-<h3 id="watermarks-wzxhzdk62wzxhzdk63">Watermarks <a id="pdf-watermark"></a></h3>
+<h3 id="watermarks-wzxhzdk63wzxhzdk64">Watermarks <a id="pdf-watermark"></a></h3>
 <p>In addition to the <a href="#pdf-postprocess">PDF Post-processing</a> options, consider the following workarounds:</p>
@@ -442,14 +442,14 @@ Here is some sample code that uses iText
 <p>(submitted by Trevor Campbell) Place an image in a region that overlaps the flowing text. For example, make region-before large enough to contain your image. Then include a block (if necessary, use an absolutely positioned block-container) containing the watermark image in the static-content for the region-before. Note that the image will be drawn on top of the normal content.</p>
-<h3 id="extensions-wzxhzdk64wzxhzdk65">Extensions <a id="pdf-extensions"></a></h3>
+<h3 id="extensions-wzxhzdk65wzxhzdk66">Extensions <a id="pdf-extensions"></a></h3>
 <p>The PDF Renderer supports some PDF specific extensions which can be embedded into the input FO document. To use the extensions the appropriate namespace must be declared in the fo:root element like this:</p>
 <div class="codehilite"><pre><span class="o">&lt;</span><span class="n">fo:root</span> <span class="n">xmlns:fo</span><span class="o">=</span><span class="s">&quot;http://www.w3.org/1999/XSL/Format&quot;</span>
          <span class="n">xmlns:pdf</span><span class="o">=</span><span class="s">&quot;http://xmlgraphics.apache.org/fop/extensions/pdf&quot;</span><span class="o">&gt;</span>
-<h4 id="embedded-fileswzxhzdk66wzxhzdk67">Embedded Files<a id="pdf-embedded-file"></a></h4>
+<h4 id="embedded-fileswzxhzdk67wzxhzdk68">Embedded Files<a id="pdf-embedded-file"></a></h4>
 <p>It is possible to attach/embed arbitrary files into a PDF file. You can give a name and a description of the file. Example:</p>
 <div class="codehilite"><pre><span class="nt">&lt;fo:declarations&gt;</span>
   <span class="nt">&lt;pdf:embedded-file</span> <span class="na">filename=</span><span class="s">&quot;image.jpg&quot;</span> <span class="na">src=</span><span class="s">&quot;url(file:///C:/Temp/myimage.jpg)&quot;</span> <span class="na">description=</span><span class="s">&quot;My image&quot;</span><span class="nt">/&gt;</span>
@@ -465,9 +465,9 @@ Here is some sample code that uses iText
 <p>Note: Not all PDF Viewers (including some Acrobat Versions) will open the embedded file when clicking on the link. In that case, the user will have to open he attachment via the separate list of file attachments.</p>
-<h2 id="postscript-wzxhzdk68wzxhzdk69">PostScript <a id="ps"></a></h2>
+<h2 id="postscript-wzxhzdk69wzxhzdk70">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-wzxhzdk70wzxhzdk71">Configuration <a id="ps-configuration"></a></h3>
+<h3 id="configuration-wzxhzdk71wzxhzdk72">Configuration <a id="ps-configuration"></a></h3>
 <p>The PostScript renderer configuration currently allows the following settings:</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/postscript&quot;</span><span class="nt">&gt;</span>
   <span class="nt">&lt;auto-rotate-landscape&gt;</span>false<span class="nt">&lt;/auto-rotate-landscape&gt;</span>
@@ -486,7 +486,7 @@ Here is some sample code that uses iText
 <p>The default value for the "safe-set-page-device" setting is "false". Setting it to "true" will cause the renderer to invoke a postscript macro which guards against the possibility of invalid/unsupported postscript key/values being issued to the implementing postscript page device.</p>
 <p>The default value for the "dsc-compliant" setting is "true". Setting it to "false" will break DSC compliance by minimizing the number of setpagedevice calls in the postscript document output. This feature may be useful when unwanted blank pages are experienced in your postscript output. This problem is caused by the particular postscript implementation issuing unwanted postscript subsystem initgraphics/erasepage calls on each setpagedevice call.</p>
 <p>The default value for the "rendering" setting is "quality". Setting it to "size" optimizes rendering for smaller file sizes which can involve minor compromises in rendering quality. For example, solid borders are then painted as plain rectangles instead of the elaborate painting instructions required for mixed-color borders.</p>
-<h3 id="limitations-wzxhzdk72wzxhzdk73">Limitations <a id="ps-limitations"></a></h3>
+<h3 id="limitations-wzxhzdk73wzxhzdk74">Limitations <a id="ps-limitations"></a></h3>
 <p>Images and SVG may not be displayed correctly. SVG support is far from being complete. No image transparency is available.</p>
@@ -501,10 +501,10 @@ Here is some sample code that uses iText
 <p>PPD support is still missing.</p>
-<h2 id="pcl-wzxhzdk74wzxhzdk75">PCL <a id="pcl"></a></h2>
+<h2 id="pcl-wzxhzdk75wzxhzdk76">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-wzxhzdk76wzxhzdk77">References <a id="pcl-references"></a></h3>
+<h3 id="references-wzxhzdk77wzxhzdk78">References <a id="pcl-references"></a></h3>
 <p><a href="http://en.wikipedia.org/wiki/Printer_Control_Language">WikiPedia entry on PCL</a> </p>
@@ -513,7 +513,7 @@ Here is some sample code that uses iText
 <p><a href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=bpl04568">Technical reference documents on PCL from Hewlett-Packard</a> </p>
-<h3 id="limitations-wzxhzdk78wzxhzdk79">Limitations <a id="pcl-limitations"></a></h3>
+<h3 id="limitations-wzxhzdk79wzxhzdk80">Limitations <a id="pcl-limitations"></a></h3>
 <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>
@@ -540,7 +540,7 @@ Here is some sample code that uses iText
 <p>Currently, there's no support for clipping and image transparency, largely because PCL 5 has certain limitations.</p>
-<h3 id="configuration-wzxhzdk80wzxhzdk81">Configuration <a id="pcl-configuration"></a></h3>
+<h3 id="configuration-wzxhzdk81wzxhzdk82">Configuration <a id="pcl-configuration"></a></h3>
 <p>The PCL renderer configuration currently allows the following settings:</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/vnd.hp-PCL&quot;</span><span class="nt">&gt;</span>
   <span class="nt">&lt;rendering&gt;</span>quality<span class="nt">&lt;/rendering&gt;</span>
@@ -554,14 +554,14 @@ Here is some sample code that uses iText
 <p>The default value for the "text-rendering" setting is "auto" which paints the base fonts using PCL fonts. Non-base fonts are painted as bitmaps through Java2D. If the mix of painting methods results in unwelcome output, you can set this to "bitmap" which causes all text to be rendered as bitmaps.</p>
 <p>The default value for the "disable-pjl" setting is "false". This means that the PCL renderer usually generates PJL commands before and after the document in order to switch a printer into PCL language. PJL commands can be disabled if you set this value to "true".</p>
 <p>You can control the output resolution for the PCL using the "target resolution" setting on the FOUserAgent. The actual value will be rounded up to the next supported PCL resolution. Currently, only 300 and 600 dpi are supported which should be enough for most use cases. Note that this setting directly affects the size of the output file and the print quality.</p>
-<h3 id="extensions-wzxhzdk82wzxhzdk83">Extensions <a id="pcl-extensions"></a></h3>
+<h3 id="extensions-wzxhzdk83wzxhzdk84">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>
-<h4 id="page-source-tray-selectionwzxhzdk84wzxhzdk85">Page Source (Tray selection)<a id="pcl-page-source"></a></h4>
+<h4 id="page-source-tray-selectionwzxhzdk85wzxhzdk86">Page Source (Tray selection)<a id="pcl-page-source"></a></h4>
 <p>The page-source extension attribute on fo:simple-page-master allows to select the paper tray the sheet for a particular simple-page-master is to be taken from. Example:</p>
 <div class="codehilite"><pre><span class="nt">&lt;fo:layout-master-set&gt;</span>
   <span class="nt">&lt;fo:simple-page-master</span> <span class="na">master-name=</span><span class="s">&quot;simple&quot;</span> <span class="na">pcl:paper-source=</span><span class="s">&quot;2&quot;</span><span class="nt">&gt;</span>
@@ -572,7 +572,7 @@ Here is some sample code that uses iText
 <p>Note: the tray number is a positive integer and the value depends on the target printer. Not all PCL printers support the same paper trays. Usually, "1" is the default tray, "2" is the manual paper feed, "3" is the manual envelope feed, "4" is the "lower" tray and "7" is "auto-select". Consult the technical reference for your printer for all available values.</p>
-<h4 id="output-binwzxhzdk86wzxhzdk87">Output Bin<a id="pcl-output-bin"></a></h4>
+<h4 id="output-binwzxhzdk87wzxhzdk88">Output Bin<a id="pcl-output-bin"></a></h4>
 <p>The <code>output-bin</code> extension attribute on fo:simple-page-master allows to select the output bin into which the printed output should be fed. Example:</p>
 <div class="codehilite"><pre><span class="nt">&lt;fo:layout-master-set&gt;</span>
   <span class="nt">&lt;fo:simple-page-master</span> <span class="na">master-name=</span><span class="s">&quot;simple&quot;</span> <span class="na">pcl:output-bin=</span><span class="s">&quot;2&quot;</span><span class="nt">&gt;</span>
@@ -583,7 +583,7 @@ Here is some sample code that uses iText
 <p>Note: the output bin number is a positive integer and the value depends on the target printer. Not all PCL printers support the same output bins. Usually, "1" is the upper output bin, "2" is the lower (rear) output bin. Consult the technical reference for your printer for all available values.</p>
-<h4 id="page-duplex-modewzxhzdk88wzxhzdk89">Page Duplex Mode<a id="pcl-duplex-mode"></a></h4>
+<h4 id="page-duplex-modewzxhzdk89wzxhzdk90">Page Duplex Mode<a id="pcl-duplex-mode"></a></h4>
 <p>The duplex-mode extension attribute on fo:simple-page-master allows to select the duplex mode to be used for a particular simple-page-master. Example:</p>
 <div class="codehilite"><pre><span class="nt">&lt;fo:layout-master-set&gt;</span>
   <span class="nt">&lt;fo:simple-page-master</span> <span class="na">master-name=</span><span class="s">&quot;simple&quot;</span> <span class="na">pcl:duplex-mode=</span><span class="s">&quot;0&quot;</span><span class="nt">&gt;</span>
@@ -594,7 +594,7 @@ Here is some sample code that uses iText
 <p>Note: the duplex is a positive integer and the value depends on the target printer. Not all PCL printers support duplexing. Usually, "0" is simplex, "1" is duplex (long-edge binding), "2" is duplex (short-edge binding). Consult the technical reference for your printer for all available values.</p>
-<h2 id="afp-wzxhzdk90wzxhzdk91">AFP <a id="afp"></a></h2>
+<h2 id="afp-wzxhzdk91wzxhzdk92">AFP <a id="afp"></a></h2>
 <p>The FOP AFP Renderer deals with creating documents conforming to the IBM AFP document architecture also refered to as MO:DCA (Mixed Object Document Content Architecture).</p>
 <p>The mapping of XSL-FO elements to the major MO:DCA structures is as follows:</p>
@@ -620,7 +620,7 @@ Here is some sample code that uses iText
 <p>FOP creates exactly one Document per Printfile with an optional Resource Group at the beginning. FOP does not create document indices.</p>
-<h3 id="references-wzxhzdk92wzxhzdk93">References <a id="afp-references"></a></h3>
+<h3 id="references-wzxhzdk93wzxhzdk94">References <a id="afp-references"></a></h3>
 <p><a href="http://en.wikipedia.org/wiki/Advanced_Function_Presentation">AFP (Advanced Function Presentation)</a> </p>
@@ -632,7 +632,7 @@ Here is some sample code that uses iText
 <p><a href="http://wiki.apache.org/xmlgraphics-fop/AFPOutput">Technical notes on AFP output in FOP</a> </p>
-<h3 id="limitations-wzxhzdk94wzxhzdk95">Limitations <a id="afp-limitations"></a></h3>
+<h3 id="limitations-wzxhzdk95wzxhzdk96">Limitations <a id="afp-limitations"></a></h3>
 <p>This list is most likely badly incomplete.</p>
@@ -642,10 +642,10 @@ Here is some sample code that uses iText
 <p>Only IBM outline and raster fonts and to a limited extend the original fonts built into FOP are supported. Support for TrueType fonts may be added later.</p>
-<h3 id="deployment-in-older-environments-wzxhzdk96wzxhzdk97">Deployment in older environments <a id="afp-compatibility"></a></h3>
+<h3 id="deployment-in-older-environments-wzxhzdk97wzxhzdk98">Deployment in older environments <a id="afp-compatibility"></a></h3>
 <p>There are still a big number of older (or limited) MO:DCA/IPDS environments in production out there. AFP has grown in functionality over time and not every environment supports the latest features. We're trying to make AFP output work in as many environments as possible. However, to make AFP output work on older environments it is recommended to set to configuration to 1 bit per pixel (see below on how to do this). In this case, all images are converted to bi-level images using IOCA function set 10 (FS10) and are enclosed in page-segments since some implementation cannot deal with IOCA objects directly. If a higher number of bits per pixel is configured, FOP has to switch to at least FS11 which may not work everywhere.</p>
-<h3 id="configuration-wzxhzdk98wzxhzdk99">Configuration <a id="afp-configuration"></a></h3>
-<h4 id="fontswzxhzdk100wzxhzdk101">Fonts<a id="afp-font-config"></a></h4>
+<h3 id="configuration-wzxhzdk99wzxhzdk100">Configuration <a id="afp-configuration"></a></h3>
+<h4 id="fontswzxhzdk101wzxhzdk102">Fonts<a id="afp-font-config"></a></h4>
 <p>The AFP Renderer requires special configuration particularly related to fonts. AFP Render configuration is done through the normal FOP configuration file. The MIME type for the AFP Renderer is application/x-afp which means the AFP Renderer section in the FOP configuration file looks like:</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/x-afp&quot;</span><span class="nt">&gt;</span>
   <span class="c">&lt;!-- AFP Renderer --&gt;</span>
@@ -801,13 +801,13 @@ A CID-keyed font (Type 0, double-byte ou
-<h4 id="output-resolutionwzxhzdk102wzxhzdk103">Output Resolution<a id="afp-renderer-resolution-config"></a></h4>
+<h4 id="output-resolutionwzxhzdk103wzxhzdk104">Output Resolution<a id="afp-renderer-resolution-config"></a></h4>
 <p>By default the AFP Renderer creates output with a resolution of 240 dpi. This can be overridden by the <renderer-resolution/> configuration element. Example:</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer-resolution&gt;</span>240<span class="nt">&lt;/renderer-resolution&gt;</span>
-<h4 id="imageswzxhzdk105wzxhzdk106">Images<a id="afp-image-config"></a></h4>
+<h4 id="imageswzxhzdk106wzxhzdk107">Images<a id="afp-image-config"></a></h4>
 <p>By default the AFP Renderer converts all images to 8 bit grey level. This can be overridden by the <images/> configuration element. Example:</p>
 <div class="codehilite"><pre><span class="o">&lt;</span><span class="n">images</span> <span class="n">mode</span><span class="o">=</span><span class="s">&quot;color&quot;</span> <span class="o">/&gt;</span>
@@ -853,7 +853,7 @@ A CID-keyed font (Type 0, double-byte ou
 <p>IOCA image data placed in the AFP Resource Group (i.e. non-inline images) is wrapped in a Page Segment for single-bit and monochrome images.</p>
-<h4 id="goca-vector-graphicswzxhzdk108wzxhzdk109">GOCA (Vector Graphics)<a id="afp-goca-config"></a></h4>
+<h4 id="goca-vector-graphicswzxhzdk109wzxhzdk110">GOCA (Vector Graphics)<a id="afp-goca-config"></a></h4>
 <p>Not all AFP implementations support GOCA. Some also have bugs related to GOCA. Therefore, it is desirable to have some control over the generation of GOCA graphics.</p>
 <p>GOCA is enabled by default. You can disable GOCA entirely in which case the AFP support falls back to generating bitmaps for vector graphics. Example:</p>
 <div class="codehilite"><pre><span class="o">&lt;</span><span class="n">goca</span> <span class="n">enabled</span><span class="o">=</span><span class="s">&quot;false&quot;</span><span class="o">/&gt;</span>
@@ -866,24 +866,27 @@ A CID-keyed font (Type 0, double-byte ou
 <p>If you disable GOCA or let text render as shapes, the size of the generated AFP usually increases considerably.</p>
-<h4 id="shadingwzxhzdk110wzxhzdk111">Shading<a id="afp-shading-config"></a></h4>
+<h4 id="shadingwzxhzdk111wzxhzdk112">Shading<a id="afp-shading-config"></a></h4>
 <p>By default, filled rectangles are painted using their given color using a PTOCA I-axis rule (DIR). But not all environments handle these colors correctly. That's why a setting is supported that paints the rectangles using an ordered dither pattern (bi-level) with an inline IOCA FS10 image that is used together with the "replicate and trim" mapping. The optional "shading" element can be used to control the shading mode. Its default value is "color". To enable the dithered mode, use "dithered". Example:</p>
 <div class="codehilite"><pre><span class="nt">&lt;shading&gt;</span>dithered<span class="nt">&lt;/shading&gt;</span>
-<h4 id="resource-group-filewzxhzdk112wzxhzdk113">Resource Group File<a id="afp-resource-group-file"></a></h4>
+<h4 id="resource-group-filewzxhzdk113wzxhzdk114">Resource Group File<a id="afp-resource-group-file"></a></h4>
 <p>By default the AFP Renderer will place all data resource objects such as images within the document of the main output datastream. An external resource group file where document resources may be specified with the <resource-group-file/> configuration element. Example:</p>
 <div class="codehilite"><pre><span class="nt">&lt;resource-group-file&gt;</span>external_resources.afp<span class="nt">&lt;/resource-group-file&gt;</span>
 <p>Be careful when using this option not to overwrite existing resource files from previous rendering runs.</p>
-<h4 id="resource-level-defaultswzxhzdk115wzxhzdk116">Resource Level Defaults<a id="afp-resource-level-defaults"></a></h4>
+<h4 id="resource-level-defaultswzxhzdk116wzxhzdk117">Resource Level Defaults<a id="afp-resource-level-defaults"></a></h4>
 <p>By default, bitmap image objects (or page segments derived from them) are put in the print-file-level resource group and GOCA graphics are inlined for compatibility with the AFP Workbench tool.</p>
 <p>It is possible to override these defaults, either per image (see the <a href="#afp-foreign-attributes-resource">afp:resource-level</a> extension attribute below) or by specifying different defaults in the configuration:</p>
-<p><default-resource-levels goca="print-file" bitmap="inline"/>
-"goca" refers to GOCA graphics and "bitmap" refers to IOCA images. The possible values for the attributes are "inline" and "print-file". In the future, additional possibilities may be added.</p>
+<div class="codehilite"><pre><span class="o">&lt;</span><span class="n">default</span><span class="o">-</span><span class="n">resource</span><span class="o">-</span><span class="n">levels</span> <span class="n">goca</span><span class="o">=</span><span class="s">&quot;print-file&quot;</span> <span class="n">bitmap</span><span class="o">=</span><span class="s">&quot;inline&quot;</span><span class="o">/&gt;</span>
+<p>"goca" refers to GOCA graphics and "bitmap" refers to IOCA images. The possible values for the attributes are "inline" and "print-file". In the future, additional possibilities may be added.</p>
 <h3 id="extensions-wzxhzdk118wzxhzdk119">Extensions <a id="afp-extensions"></a></h3>
 <p>The AFP Renderer supports some AFP specific extensions which can be embedded into the input fo document. To use the extensions the appropriate namespace must be declared in the fo:root element like this:</p>
 <div class="codehilite"><pre><span class="o">&lt;</span><span class="n">fo:root</span> <span class="n">xmlns:fo</span><span class="o">=</span><span class="s">&quot;http://www.w3.org/1999/XSL/Format&quot;</span>

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

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

View raw message