You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by bu...@apache.org on 2012/10/23 17:05:47 UTC
svn commit: r835892 [3/17] - 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/
Modified: websites/staging/xmlgraphics/trunk/content/batik/using/swing.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/swing.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/swing.html Tue Oct 23 15:05:41 2012
@@ -160,7 +160,7 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/batik/">Batik</a> » <a href="/batik/using/">Using</a></div> -->
<div class="section-content"><p>The goal of the Batik Swing component module is to provide a Swing component that can used to display SVG documents. With the <a href="../javadoc/org/apache/batik/swing/JSVGCanvas.html">JSVGCanvas</a> class, you can easily display an SVG document (from a URI or a DOM tree) and allow the user to manipulate it, such as rotating, zooming, panning, selecting text or activating hyperlinks. First this document explains how to create a <code>JSVGCanvas</code> and integrate it in to a Swing application. Then, it descibes some advanced features such as the listener mechanism used to track all events that occurred while displaying or manipulating an SVG document.</p>
-<h1 id="creatingJSVGCanvas">Creating a JSVGCanvas</h1>
+<h1 id="creating-a-jsvgcanvas-wzxhzdk1wzxhzdk2">Creating a JSVGCanvas <a id="#creatingJSVGCanvas"></a></h1>
<p>The following example illustrates how to create a <code>JSVGCanvas</code> , which is a Swing component that follows the Swing design rule. This means that the component is not thread safe and all operations on the component or the document it is displaying must be performed as described in <a href="http://java.sun.com/docs/books/tutorial/uiswing/overview/threads.html">the Swing tutorial</a> . The <code>JSVGCanvas</code> is also a <a href="http://java.sun.com/products/javabeans/">JavaBean</a> , so it can be used in visual application builders.
If you try this example, do not forget to set your <code>CLASSPATH</code> so that it contains the Batik classes and resources, as well as Xerces ( <code>lib/xerces_2_5_0.jar</code> ) and the XML APIs jars ( <code>lib/xml-apis.jar</code> and <code>lib/xml-apis-ext.jar</code> ).import java.awt.<em>;
import java.awt.event.</em>;
@@ -270,7 +270,7 @@ import org.apache.batik.swing.svg.GVTTre
<p>}<div class="figure"> <img alt="Screenshot of the example SVGApplication program" src="images/svgapplication.png" title="" /> </div></p>
-<h1 id="eventhandling">Handling events</h1>
+<h1 id="handling-events-wzxhzdk5wzxhzdk6">Handling events <a id="#eventhandling"></a></h1>
<p>Each time you set a URI or an SVG DOM tree to be displayed in a <code>JSVGCanvas</code> (using the <code>setURI</code> or <code>setSVGDocument</code> method), the specified document is first parsed (in case of a URI), built, rendered and optionally updated. The proper way to be notified of these different phases is to implement a listener and attach it to the component. There are five types of listener:</p>
<dl>
<dt><code>SVGDocumentLoaderListener</code></dt>
@@ -294,7 +294,7 @@ import org.apache.batik.swing.svg.GVTTre
<p>These listeners give a complete description of the different steps of the five phases (including error states). Adapter classes are available to ease the creation of new listener implementationâ <a href="../javadoc/org/apache/batik/swing/svg/SVGDocumentLoaderAdapter.html">SVGDocumentLoaderAdapter</a> , <a href="../javadoc/org/apache/batik/swing/svg/GVTTreeBuilderListenerAdapter.html">GVTTreeBuilderListenerAdapter</a> , <a href="../javadoc/org/apache/batik/swing/svg/SVGLoadEventDispatcherAdapter.html">SVGLoadEventDispatcherAdapter</a> , <a href="../javadoc/org/apache/batik/swing/gvt/GVTTreeRendererAdapter.html">GVTTreeRendererAdapter</a> and <a href="../javadoc/org/apache/batik/bridge/UpdateManagerAdapter.html">UpdateManagerAdapter</a> ,</p>
<p>For static documents, you can assume that the JSVGCanvas has completed its job (parsing, building and rendering) when the <code>gvtRenderingCompleted</code> method call is called, following a <code>setURI</code> or a <code>setSVGDocument</code> method call.</p>
<p>In the case of dynamic documents, the end of the computation (parsing, building, SVGLoad dispatch, initial rendering and updates) is marked by a call to the <code>updateManagerStopped</code> method.</p>
-<h1 id="interactor">Adding an Interactor</h1>
+<h1 id="adding-an-interactor-wzxhzdk7wzxhzdk8">Adding an Interactor <a id="#interactor"></a></h1>
<p>The <code>JSVGCanvas</code> provides a set of build-in interactors that let the users manipulate the displayed document, including ones for zooming, panning and rotating. Interactors catch user input to the <code>JSVGCanvas</code> component and translate them into behaviour. If you want to add new behaviors to the <code>JSVGCanvas</code> , you can implement the <a href="../javadoc/org/apache/batik/swing/gvt/Interactor.html">Interactor</a> interface. Then, you can register this new interactor to the component by adding an element to the <code>List</code> returned by the <code>getInteractors()</code> method of the canvas.</p></div>
</div>
Modified: websites/staging/xmlgraphics/trunk/content/batik/using/transcoder.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/transcoder.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/transcoder.html Tue Oct 23 15:05:41 2012
@@ -160,7 +160,7 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/batik/">Batik</a> » <a href="/batik/using/">Using</a></div> -->
<div class="section-content"><p>The goal of the transcoder API (package <code>org.apache.batik.transcoder</code> ) is to provide a generic API for transcoding an input to an output. First, this document explains the basic transcoder API that <a href="../javadoc/org/apache/batik/transcoder/Transcoder.html">Transcoder</a> , <a href="../javadoc/org/apache/batik/transcoder/TranscoderInput.html">TranscoderInput</a> and <a href="../javadoc/org/apache/batik/transcoder/TranscoderOutput.html">TranscoderOutput</a> define, and thus all transcoders have in common. Next, it describes how to use the image transcoder API (package <code>org.apache.batik.transcoder.image</code> ), which lets you rasterize an SVG document fragment to a raster image such as JPEG, PNG or TIFF.</p>
-<h1 id="transcoderAPI">The transcoder API</h1>
+<h1 id="the-transcoder-api-wzxhzdk3wzxhzdk4">The transcoder API <a id="#transcoderAPI"></a></h1>
<p>The <code>org.apache.batik.transcoder</code> package defines 5 major classes:</p>
<dl>
<dt>Transcoder</dt>
@@ -174,9 +174,9 @@ $(document).ready(function () {
<dt>ErrorHandler</dt>
<dd>The <a href="../javadoc/org/apache/batik/transcoder/ErrorHandler.html">ErrorHandler</a> class provides a way to get any errors or warnings that might occur while transcoding. A default implementation is provided but you can, for example, implement your own handler that displays a dialog instead of stack trace.</dd>
</dl>
-<h1 id="howtousetranscoderAPI">How to use the image transcoder API</h1>
+<h1 id="how-to-use-the-image-transcoder-api-wzxhzdk5wzxhzdk6">How to use the image transcoder API <a id="#howtousetranscoderAPI"></a></h1>
<p>The <code>org.apache.batik.transcoder.image</code> package provides an easy way to transcode an SVG document to a raster image such as JPEG, PNG or TIFF. Additional raster image formats can be added by subclassing the <code>ImageTranscoder</code> class and implementing the <code>writeImage</code> method. Although, in next sections, the examples will use the JPEG transcoder, the PNG transcoder works the same way.</p>
-<h2 id="createImage">Creating an image</h2>
+<h2 id="creating-an-image-wzxhzdk7wzxhzdk8">Creating an image # <a id="#createImage"></a></h2>
<p>The following example, using the <code>JPEGTranscoder</code> , shows how to transform an SVG document to a JPEG image.
import java.io.*;</p>
<p>import org.apache.batik.transcoder.image.JPEGTranscoder;
@@ -230,11 +230,11 @@ java SaveAsJPEG filename.svg</p>
<p>Inspect the output file <code>out.jpg</code> .</p>
</li>
</ol>
-<h2 id="defineSizeOfImage">Defining the size of the image</h2>
+<h2 id="defining-the-size-of-the-image-wzxhzdk9wzxhzdk10">Defining the size of the image # <a id="#defineSizeOfImage"></a></h2>
<p>By adding the following line of code to the previous example, you will specify the raster image size (in pixels). The transcoding hint <code>KEY_WIDTH</code> lets you specify the raster image width. If the raster image height is not provided (using the <code>KEY_HEIGHT</code> ), the transcoder will compute the raster image height by keeping the aspect ratio of the SVG document.
t.addTranscodingHint(JPEGTranscoder.KEY_WIDTH, new Float(100));
The transcoder will have the same behavior if you specify the <code>KEY_HEIGHT</code> without initializing the <code>KEY_WIDTH</code> . In all cases (even if both keys are provided), the transcoder will preserve the apsect ratio of the SVG document.</p>
-<h2 id="selectAreaOfIntrest">Selecting an area of interest</h2>
+<h2 id="selecting-an-area-of-interest-wzxhzdk11wzxhzdk12">Selecting an area of interest # <a id="#selectAreaOfIntrest"></a></h2>
<p>The image transcoder lets you specify an area of interest (that is, a part of the SVG document). The key <code>KEY_AOI</code> allows you to select the region of the SVG document to render. The value of this key must be a <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/awt/Rectangle.html">java.awt.Rectangle</a> specified in pixels, using the coordinate space of the SVG document. The following example shows how you can split an SVG document into 4 tiles.
import java.io.<em>;
import java.awt.</em>;</p>
@@ -309,7 +309,7 @@ java SaveAsJPEGTiles</p>
<p>Inspect the output files <code>tileTopRight.jpg</code> , <code>tileTopRight.jpg</code> , <code>tileBottomRight.jpg</code> and <code>tileBottomLeft.jpg</code> .</p>
</li>
</ol>
-<h2 id="otherTransHints">Other transcoding hints</h2>
+<h2 id="other-transcoding-hints-wzxhzdk13wzxhzdk14">Other transcoding hints # <a id="#otherTransHints"></a></h2>
<p>The <code>ImageTranscoder</code> provides additional <code>TranscodingHints</code> that let you customize the generated images.</p>
<dl>
<dt><code>ImageTranscoder.KEY_MEDIA</code></dt>
@@ -333,7 +333,7 @@ trans.addTranscodingHint(ImageTranscoder
<dd>This hint lets you choose a background color. For example:
trans.addTranscodingHint(ImageTranscoder.KEY_BACKGROUND_COLOR, Color.white);</dd>
</dl>
-<h2 id="genImagefromSVGDOM">Generating an image from an SVG DOM tree</h2>
+<h2 id="generating-an-image-from-an-svg-dom-tree-wzxhzdk15wzxhzdk16">Generating an image from an SVG DOM tree # <a id="#genImagefromSVGDOM"></a></h2>
<p>The following code creates and saves an SVG DOM tree to a raster image.
import java.io.*;</p>
<p>import org.apache.batik.transcoder.image.JPEGTranscoder;
Modified: websites/staging/xmlgraphics/trunk/content/commons/bugs.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/commons/bugs.html (original)
+++ websites/staging/xmlgraphics/trunk/content/commons/bugs.html Tue Oct 23 15:05:41 2012
@@ -130,7 +130,7 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/commons/">Commons</a></div> -->
<div class="section-content"><p><version>$Revision: 911792 $</version></p>
<p>Information on this page applies to enhancement requests and other trackable issues as well as bugs.</p>
-<h1 id="issues_existing">Reported Issues</h1>
+<h1 id="reported-issues-wzxhzdk2wzxhzdk3">Reported Issues <a id="#issues_existing"></a></h1>
<p>A list of unresolved reported bugs can be found at <a href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=XMLGraphicsCommons&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=">XML Graphics Commons Open Bugs (Bugzilla)</a> . If you have an interest in an issue already reported, please consider the following:</p>
<ul>
<li>
@@ -140,7 +140,7 @@ $(document).ready(function () {
<p>If you would like to track the status of the issue, consider adding your email address to the list of "CC" recipients, so that you will receive an email as changes are made to the issue.</p>
</li>
</ul>
-<h1 id="issues_new">Unreported Issues (Reporting New Issues)</h1>
+<h1 id="unreported-issues-reporting-new-issues-wzxhzdk4wzxhzdk5">Unreported Issues (Reporting New Issues) <a id="#issues_new"></a></h1>
<p>User reports of bugs and requests for enhancements are extremely important parts of XML Graphics Commons development, and we appreciate the time you take to help us track these issues down.</p>
<ul>
<li>
Modified: websites/staging/xmlgraphics/trunk/content/commons/changes.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/commons/changes.html (original)
+++ websites/staging/xmlgraphics/trunk/content/commons/changes.html Tue Oct 23 15:05:41 2012
@@ -129,10 +129,10 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/commons/">Commons</a></div> -->
<div class="section-content"><p><a href="changes.rss"></a> </p>
-<h1 id="introduction">Introduction and explanation of symbols</h1>
+<h1 id="introduction-and-explanation-of-symbols-wzxhzdk0wzxhzdk1">Introduction and explanation of symbols <a id="#introduction"></a></h1>
<p>Changes are sorted by "type" and then chronologically with the most recent at the top. These symbols denote the various action types:<icon alt="add" src="images/add.jpg"></icon>=add,<icon alt="fix" src="images/fix.jpg"></icon>=fix,<icon alt="remove" src="images/remove.jpg"></icon>=remove,<icon alt="update" src="images/update.jpg"></icon>=update</p>
-<h1 id="version_Trunk">Version Trunk (n/a)</h1>
-<h2 id="Code_Trunk">Changes to the Code Base</h2>
+<h1 id="version-trunk-na-wzxhzdk10wzxhzdk11">Version Trunk (n/a) <a id="#version_Trunk"></a></h1>
+<h2 id="changes-to-the-code-base-wzxhzdk12wzxhzdk13">Changes to the Code Base # <a id="#Code_Trunk"></a></h2>
<ul>
<li>
<p><icon alt="fix" src="images/fix.jpg"></icon>Support rdf:resource attributes in XMP. Committed by GA. Thanks to Brian Carlson. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50497">50497</a> .</p>
@@ -168,12 +168,12 @@ $(document).ready(function () {
<p><icon alt="update" src="images/update.jpg"></icon>Various code style fixes Committed by JM. Thanks to Glenn Adams. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49703">49703</a> .</p>
</li>
</ul>
-<h2 id="contributors_Trunk">Contributors to this release</h2>
+<h2 id="contributors-to-this-release-wzxhzdk14wzxhzdk15">Contributors to this release # <a id="#contributors_Trunk"></a></h2>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Glenn Adams (GA), Jeremias Märki (JM), (PH).</p>
<p>This is a list of other contributors:<br></br>Brian Carlson, Florian Barbera Vila Bollain, Glenn Adams, JM and Mehdi Houshmand, Joshua Marquart, Sebastian Bazley.</p>
-<h1 id="version_1.4">Version 1.4 (7 July 2010)</h1>
-<h2 id="Code_1.4">Changes to the Code Base</h2>
+<h1 id="version-14-7-july-2010-wzxhzdk20wzxhzdk21">Version 1.4 (7 July 2010) <a id="#version_1.4"></a></h1>
+<h2 id="changes-to-the-code-base-wzxhzdk22wzxhzdk23">Changes to the Code Base # <a id="#Code_1.4"></a></h2>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added getter and setter for enabling/disabling comments in PSGenerator. Committed by JM. Thanks to Julien Aymé. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49250">49250</a> .</p>
@@ -263,12 +263,12 @@ $(document).ready(function () {
<p><icon alt="update" src="images/update.jpg"></icon>Moved method disableClipping from AbstractPSDocumentGraphics2D to PSGraphics2D. Committed by JM. Thanks to Julien Aymé. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49337">49337</a> .</p>
</li>
</ul>
-<h2 id="contributors_1.4">Contributors to this release</h2>
+<h2 id="contributors-to-this-release-wzxhzdk24wzxhzdk25">Contributors to this release # <a id="#contributors_1.4"></a></h2>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Adrian Cumiskey (AC), Chris Bowditch (CB), Jeremias Märki (JM), Max Berger (MB), Vincent Hennebert (VH).</p>
<p>This is a list of other contributors:<br></br>Andrey Koltunov, Calixte Denizet, JiÅà Kunhart, Julien Aymé, Peter Hancock, Venkat Reddy.</p>
-<h1 id="version_1.3.1">Version 1.3.1 (11 June 2008)</h1>
-<h2 id="Code_1.3.1">Changes to the Code Base</h2>
+<h1 id="version-131-11-june-2008-wzxhzdk30wzxhzdk31">Version 1.3.1 (11 June 2008) <a id="#version_1.3.1"></a></h1>
+<h2 id="changes-to-the-code-base-wzxhzdk32wzxhzdk33">Changes to the Code Base # <a id="#Code_1.3.1"></a></h2>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added fallbacks for Type 1 fonts which don't have the normal "one", "two" etc. glyphs, but actually only provide "oneoldstyle", "twooldstyle" etc. Committed by JM.</p>
@@ -307,11 +307,11 @@ $(document).ready(function () {
<p><icon alt="fix" src="images/fix.jpg"></icon>Bugfix for EOFException when pre-loading very small PNG images (file size < 88 bytes). Committed by JM.</p>
</li>
</ul>
-<h2 id="contributors_1.3.1">Contributors to this release</h2>
+<h2 id="contributors-to-this-release-wzxhzdk34wzxhzdk35">Contributors to this release # <a id="#contributors_1.3.1"></a></h2>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Jeremias Märki (JM), Max Berger (MB).</p>
-<h1 id="version_1.3">Version 1.3 (07 Feb 2008)</h1>
-<h2 id="Code_1.3">Changes to the Code Base</h2>
+<h1 id="version-13-07-feb-2008-wzxhzdk38wzxhzdk39">Version 1.3 (07 Feb 2008) <a id="#version_1.3"></a></h1>
+<h2 id="changes-to-the-code-base-wzxhzdk40wzxhzdk41">Changes to the Code Base # <a id="#Code_1.3"></a></h2>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Image Loading: Support for passing in SAXSource instance. Committed by JM. Thanks to Adam Strzelecki. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=44466">44466</a> .</p>
@@ -353,12 +353,12 @@ $(document).ready(function () {
<p><icon alt="update" src="images/update.jpg"></icon>PostScript: Improved PSImageUtils by introducing the ImageEncoder interface and allowing for streams instead of byte arrays for data transfer which can lower memory consumption. Committed by JM.</p>
</li>
</ul>
-<h2 id="contributors_1.3">Contributors to this release</h2>
+<h2 id="contributors-to-this-release-wzxhzdk42wzxhzdk43">Contributors to this release # <a id="#contributors_1.3"></a></h2>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Chris Bowditch (CB), Jeremias Märki (JM).</p>
<p>This is a list of other contributors:<br></br>Adam Strzelecki, Adrian Cumiskey, Max Berger, Sergey Orlov.</p>
-<h1 id="version_1.2">Version 1.2 (21 July 2007)</h1>
-<h2 id="Code_1.2">Changes to the Code Base</h2>
+<h1 id="version-12-21-july-2007-wzxhzdk48wzxhzdk49">Version 1.2 (21 July 2007) <a id="#version_1.2"></a></h1>
+<h2 id="changes-to-the-code-base-wzxhzdk50wzxhzdk51">Changes to the Code Base # <a id="#Code_1.2"></a></h2>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added support for CMYK and GRAY color spaces for PSGenerator (moved there from PSGraphics2D). Committed by JM. Thanks to Adrian Cumiskey. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=42507">42507</a> .</p>
@@ -370,12 +370,12 @@ $(document).ready(function () {
<p><icon alt="fix" src="images/fix.jpg"></icon>Fixed the PDF/A namespace according to ISO-19005-1:2005/Cor.1:2007 and deprecated the use of the draft PDF/A namespace used by Adobe Acrobat 7.x. Committed by JM.</p>
</li>
</ul>
-<h2 id="contributors_1.2">Contributors to this release</h2>
+<h2 id="contributors-to-this-release-wzxhzdk52wzxhzdk53">Contributors to this release # <a id="#contributors_1.2"></a></h2>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Jeremias Märki (JM).</p>
<p>This is a list of other contributors:<br></br>Adrian Cumiskey.</p>
-<h1 id="version_1.1">Version 1.1 (22 Dec 2006)</h1>
-<h2 id="Code_1.1">Changes to the Code Base</h2>
+<h1 id="version-11-22-dec-2006-wzxhzdk58wzxhzdk59">Version 1.1 (22 Dec 2006) <a id="#version_1.1"></a></h1>
+<h2 id="changes-to-the-code-base-wzxhzdk60wzxhzdk61">Changes to the Code Base # <a id="#Code_1.1"></a></h2>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added the start of an XMP metadata framework. Committed by JM.</p>
@@ -396,19 +396,19 @@ $(document).ready(function () {
<p><icon alt="fix" src="images/fix.jpg"></icon>Bugfix: The generation of the PostScript setdash command was assuming that only integer values can be used but that isn't the case. Committed by JM.</p>
</li>
</ul>
-<h2 id="contributors_1.1">Contributors to this release</h2>
+<h2 id="contributors-to-this-release-wzxhzdk62wzxhzdk63">Contributors to this release # <a id="#contributors_1.1"></a></h2>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Jeremias Märki (JM).</p>
<p>This is a list of other contributors:<br></br>Max Berger.</p>
-<h1 id="version_1.0">Version 1.0 (17 Apr 2006)</h1>
-<h2 id="Code_1.0">Changes to the Code Base</h2>
+<h1 id="version-10-17-apr-2006-wzxhzdk68wzxhzdk69">Version 1.0 (17 Apr 2006) <a id="#version_1.0"></a></h1>
+<h2 id="changes-to-the-code-base-wzxhzdk70wzxhzdk71">Changes to the Code Base # <a id="#Code_1.0"></a></h2>
<ul>
<li><icon alt="add" src="images/add.jpg"></icon>Initial release with several components from Batik and FOP: Image codecs, Image writer abstraction, I/O classes, Java2D helpers, PostScript library with Graphics2D implementation. Committed by JM.</li>
</ul>
-<h2 id="contributors_1.0">Contributors to this release</h2>
+<h2 id="contributors-to-this-release-wzxhzdk72wzxhzdk73">Contributors to this release # <a id="#contributors_1.0"></a></h2>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Jeremias Märki (JM).</p>
-<h1 id="all-committers">All Committers</h1>
+<h1 id="all-committers-wzxhzdk76wzxhzdk77">All Committers <a id="#all-committers"></a></h1>
<p>This is a list of all people who have ever participated as committers on this project.</p>
<ul>
<li>
Modified: websites/staging/xmlgraphics/trunk/content/commons/download.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/commons/download.html (original)
+++ websites/staging/xmlgraphics/trunk/content/commons/download.html Tue Oct 23 15:05:41 2012
@@ -128,9 +128,9 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/commons/">Commons</a></div> -->
- <div class="section-content"><h1 id="release">Download a Release</h1>
+ <div class="section-content"><h1 id="download-a-release-wzxhzdk0wzxhzdk1">Download a Release <a id="#release"></a></h1>
<p>Source ("-src") and binary ("-bin") distributions can be downloaded from a <a href="http://www.apache.org/dyn/closer.cgi/xmlgraphics/commons">Apache™ XML Graphics Commons Distribution Mirror</a> .</p>
-<h1 id="svn">Download from Subversion</h1>
+<h1 id="download-from-subversion-wzxhzdk3wzxhzdk4">Download from Subversion <a id="#svn"></a></h1>
<p>The latest source code is available directly from the Subversion repository:</p>
<table>
<thead>
Modified: websites/staging/xmlgraphics/trunk/content/commons/image-loader.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/commons/image-loader.html (original)
+++ websites/staging/xmlgraphics/trunk/content/commons/image-loader.html Tue Oct 23 15:05:41 2012
@@ -128,7 +128,7 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/commons/">Commons</a></div> -->
- <div class="section-content"><h1 id="overview">Overview</h1>
+ <div class="section-content"><h1 id="overview-wzxhzdk0wzxhzdk1">Overview <a id="#overview"></a></h1>
<p>Apache™ XML Graphics Commons contains a unified framework for loading and processing images (bitmap and vector). The package name is <code>org.apache.xmlgraphics.image.loader</code> . Key features:</p>
<ul>
<li>
@@ -170,8 +170,8 @@ $(document).ready(function () {
<p>An image cache speeds up the processing for images that are requested multiple times.</p>
</li>
</ul>
-<h1 id="tutorial">Tutorial</h1>
-<h2 id="manager-setup">Setting up the manager</h2>
+<h1 id="tutorial-wzxhzdk3wzxhzdk4">Tutorial <a id="#tutorial"></a></h1>
+<h2 id="setting-up-the-manager-wzxhzdk5wzxhzdk6">Setting up the manager # <a id="#manager-setup"></a></h2>
<p>Before we can start to work with the package we need to set up the <code>ImageManager</code> . It provides convenience methods to load and convert images and holds the image cache.</p>
<p>The <code>ImageManager</code> needs an <code>ImageContext</code> . This interface provides the <code>ImageManager</code> with important context and configuration data. Currently this is only the source resolution. The <code>ImageManager</code> and <code>ImageContext</code> are intended to be shared within an application.</p>
<p>import org.apache.xmlgraphics.image.loader.ImageContext;
@@ -180,7 +180,7 @@ import org.apache.xmlgraphics.image.load
<p class="."></p>
<p>ImageManager imageManager = new ImageManager(new DefaultImageContext());
In this example, <code>DefaultImageContext</code> is used. You may need to write your own implementation of <code>ImageContext</code> for your use case.</p>
-<h2 id="preloading">Preloading an image</h2>
+<h2 id="preloading-an-image-wzxhzdk7wzxhzdk8">Preloading an image # <a id="#preloading"></a></h2>
<p>In order to load an image, it needs to be "preloaded" first, i.e. the image content type is detected and the intrinsic size of the image is determined. The result of this process is an <code>ImageInfo</code> instance which contains the URI, MIME type and intrinsic size. In most cases, this is done without loading the whole image (see SPI section below for information on exceptions to this rule).</p>
<p>Preloading is normally done through the <code>ImageManager</code> 's <code>getImageInfo()</code> method. For this operation an <code>ImageSessionContext</code> needs to be provided. It is responsible for supplying JAXP <code>Source</code> objects, URI resolution and providing other information needed for the image operations. In simple cases you can simply use <code>DefaultImageSessionContext</code> , but often you will want to write your own implementation of <code>ImageSessionContext</code> . In that case, it's recommended to subclass <code>AbstractImageSessionContext</code> which lets you avoid rewriting a lot of code for providing <code>Source</code> objects.</p>
<p>import org.apache.xmlgraphics.image.loader.ImageInfo;
@@ -188,7 +188,7 @@ import org.apache.xmlgraphics.image.load
import org.apache.xmlgraphics.image.loader.impl.DefaultImageSessionContext;</p>
<p class="."></p>
<p>ImageInfo info = imageManager.getImageInfo(uri, sessionContext);</p>
-<h2 id="loading">Loading an image</h2>
+<h2 id="loading-an-image-wzxhzdk9wzxhzdk10">Loading an image # <a id="#loading"></a></h2>
<p>Once the image is "preloaded", it can be fully loaded in the form/flavor that is needed by the consuming application. The required flavor is indicated through the <code>ImageFlavor</code> class. If you want the image as a bitmap image in memory, you could request an <code>ImageFlavor.RENDERED_IMAGE</code> . Again, the <code>ImageSessionContext</code> will be needed.</p>
<p>import org.apache.xmlgraphics.image.loader.Image;
import org.apache.xmlgraphics.image.loader.ImageFlavor;</p>
@@ -213,10 +213,10 @@ import org.apache.xmlgraphics.image.load
throw new IllegalStateException("Unexpected flavor");
}
While each <code>BufferedImage</code> is also a <code>RenderedImage</code> , it can be more efficient to also specify <code>ImageFlavor.BUFFERED_IMAGE</code> in the flavor array.</p>
-<h1 id="tipsntricks">Tips & Tricks</h1>
+<h1 id="tips-tricks-wzxhzdk11wzxhzdk12">Tips & Tricks <a id="#tipsntricks"></a></h1>
<p>If you are loading bitmap images and you get an error like <code>"Cannot load image (no suitable loader/converter combination available) for
myimage.tif (image/tiff)</code> , you maybe be missing the necessary ImageIO codec to decode the image. A number of well-written codecs can be found in <a href="https://jai-imageio.dev.java.net/">JAI Image I/O Tools Project</a> . Just download the distribution and add the JAR to the classpath. ImageIO will automatically pick up the new codecs and they will subsequently be available to the image framework.</p>
-<h1 id="spi">Service Provider Interface (SPI, Plug-ins)</h1>
+<h1 id="service-provider-interface-spi-plug-ins-wzxhzdk13wzxhzdk14">Service Provider Interface (SPI, Plug-ins) <a id="#spi"></a></h1>
<p>The whole image framework is designed to be highly extensible. There are various extension points where new functionality can be added. The three main SPI interfaces are:</p>
<ul>
<li>
@@ -231,23 +231,23 @@ import org.apache.xmlgraphics.image.load
</ul>
<p>If you plan to write an implementation of one of the above interfaces, please also take a look at the existing implementations for reference.</p>
<p>Throughout the SPI, you'll find a <code>Map</code> parameter (hints) in the most important methods. That's a way to supply additional information to the implementation by the caller. For example, the source and target resolutions from the image (session) context is stored in the hints. The implementation should not rely on the presence of specialized information and should always have sensible defaults to rely on in this case.</p>
-<h2 id="ImagePreloader">ImagePreloader</h2>
+<h2 id="imagepreloader-wzxhzdk15wzxhzdk16">ImagePreloader # <a id="#ImagePreloader"></a></h2>
<p>The first task is identifying whether the implementation supports the given image. If the image is loaded using an ImageInputStream it is important to always reset the stream position to the beginning of the file at the end of the <code>preloadImage()</code> method, because all registered preloaders are check in turn until one implementation signals that it supports the format. In that case, it has to extract only the minimal information from the image necessary to identify the image's intrinsic size. For most formats, this is doable without loading the whole image into memory.</p>
<p>However, for some formats (like MathML or WMF), loading the whole image at preloading time is hard to avoid since the image's size can only be determined that way. In such a case, the <code>ImagePreloader</code> implementations shall pass the loaded document to the respective <code>ImageLoader</code> through the custom objects that can be attached to the <code>ImageInfo</code> object. If the preloader loads the whole document, it shall close the given <code>Source</code> object (calling <code>ImageUtil.closeQuietly(Source)</code> ).</p>
<p>The priority the implementation reports is used to sort all registered implementations. This is to fine-tune the inner workings and to optimize performance since some formats are usually used more frequently than others.
Normally, if you implement an <code>ImagePreloader</code> you will also need to implement the respective <code>ImageLoader/ImageLoaderFactory</code> , or vice versa.</p>
-<h2 id="ImageLoader">ImageLoader and ImageLoaderFactory</h2>
+<h2 id="imageloader-and-imageloaderfactory-wzxhzdk17wzxhzdk18">ImageLoader and ImageLoaderFactory # <a id="#ImageLoader"></a></h2>
<p>The factory interface has been created to allow checking if some library that an implementation depends on is really in the classpath so it can report back that the <code>ImageLoader</code> is not funtional. The factory also reports what kind of image formats it supports and which image flavors it can return. There can be a complex relationship between the two. It is recommmended, however, to write smaller implementations rather than big, almighty ones.</p>
<p>The usage penalty is used when constructing image conversion pipelines. There can be multiple ways to provide an image in one of the supported flavors and this value helps to make the best decision.</p>
<p>While the factory basically just provides information and creates new <code>ImageLoader</code> instances, the image loaders are doing the actual leg work of decoding the images. The image flavor returned by the loader must match the flavor that is returned by <code>getTargetFlavor()</code> .</p>
-<h2 id="ImageConverter">ImageConverter</h2>
+<h2 id="imageconverter-wzxhzdk19wzxhzdk20">ImageConverter # <a id="#ImageConverter"></a></h2>
<p>The image converter is responsible to transform one image representation into another. Bundled implementations support these conversions: Java2D to bitmap, bitmap to Java2D and RenderedImage to "raw" PNG. Ideas for additional image converters could be: PDF to Java2D, EPS to Java2D or MathML to SVG or Java2D.</p>
<p>Each ImageConverter comes with a usage penalty which is used when constructing conversion pipelines so the pipeline with the least penalty value can be chosen. This is necessary as the consuming application my support multiple image flavors and there can be multiple ways to convert an image in one of the requested image flavors. Internally, <a href="http://en.wikipedia.org/wiki/Dijkstra%27s_algorithm">Dijkstra's shortest path algorithm</a> is used to find the best path using the penalties as "way lengths".</p>
-<h1 id="customization">Customization</h1>
-<h2 id="source-reuse">Disabling Source Re-use</h2>
+<h1 id="customization-wzxhzdk21wzxhzdk22">Customization <a id="#customization"></a></h1>
+<h2 id="disabling-source-re-use-wzxhzdk23wzxhzdk24">Disabling Source Re-use # <a id="#source-reuse"></a></h2>
<p>By default, the Source object being used during the pre-loading stage is re-used when the image is fully loaded later (assuming an ImageSessionContext is used that descends from AbstractImageSessionContext). That means that a stream is only opened once and the image loading framework tries to re-wind the stream when it has to re-read portions of the stream when loading the complete image.</p>
<p>In some situations, this behavior may be undesired. Therefore, it can be disabled through a system property ( <code>org.apache.xmlgraphics.image.loader.impl.AbstractImageSessionContext.no-source-reuse</code> ). Set it to "true" and that feature will be disabled.</p>
-<h2 id="plugin-penalties">Adjusting plug-in penalties</h2>
+<h2 id="adjusting-plug-in-penalties-wzxhzdk25wzxhzdk26">Adjusting plug-in penalties # <a id="#plugin-penalties"></a></h2>
<p>Every image loader plug-in has a hard-coded usage penalty that influences which solution is chosen if there are multiple possibilities to load an image. Sometimes, though, these penalties need to be tweaked. The <code>ImageImplRegistry</code> (reachable through <code>ImageManager.getRegistry()</code> ) supports storing additional penalty values. An example:
ImageImplRegistry registry = imageManager.getRegistry();
registry.setAdditionalPenalty(
Modified: websites/staging/xmlgraphics/trunk/content/commons/index.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/commons/index.html (original)
+++ websites/staging/xmlgraphics/trunk/content/commons/index.html Tue Oct 23 15:05:41 2012
@@ -128,11 +128,11 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/commons/">Commons</a></div> -->
- <div class="section-content"><h1 id="Overview">Overview</h1>
+ <div class="section-content"><h1 id="overview-wzxhzdk0wzxhzdk1">Overview <a id="#Overview"></a></h1>
<p>Apache™ XML Graphics Commons is a library that consists of several reusable components used by <a href="http://xmlgraphics.apache.org/batik/">Apache Batik</a> and <a href="http://xmlgraphics.apache.org/fop/">Apache FOP</a> . Many of these components can easily be used separately outside the domains of SVG and XSL-FO. You will find components such as a PDF library, an RTF library, Graphics2D implementations that let you generate PDF & PostScript files, and much more.</p>
<p>The Apache™ XML Graphics Commons project is part of the <a href="http://www.apache.org">Apache™</a> Software Foundation, which is a wider community of users and developers of open source projects.</p>
<p>In the Wiki, we have a <a href="http://wiki.apache.org/xmlgraphics/XmlGraphicsCommonComponents">Roadmap for Apache XML Graphics Commons</a> . This roadmap is the place to describe new ideas for the project.</p>
-<h1 id="features">Features</h1>
+<h1 id="features-wzxhzdk5wzxhzdk6">Features <a id="#features"></a></h1>
<p>Components which have been ported from <a href="http://xmlgraphics.apache.org/batik/">Apache Batik</a> and <a href="http://xmlgraphics.apache.org/fop/">Apache FOP</a> include:</p>
<table>
<thead>
@@ -190,32 +190,32 @@ $(document).ready(function () {
</tr>
</tbody>
</table>
-<h1 id="News">News</h1>
+<h1 id="news-wzxhzdk7wzxhzdk8">News <a id="#News"></a></h1>
<p>RSS Feed: <a href="subproject-news-feed.rss"></a> </p>
-<h2 id="news-2010-07-07">7 Jul 2010: Version 1.4 Released</h2>
+<h2 id="7-jul-2010-version-14-released-wzxhzdk9wzxhzdk10">7 Jul 2010: Version 1.4 Released # <a id="#news-2010-07-07"></a></h2>
<p><item date="2010-07-07" title="Version 1.4 Released">
This release adds the option to generate smaller PostScript files, support for the AdobeStandardCyrillic encoding, RefinedImageFlavor, TexturePaint support for PSGraphics2D (PostScript tiling patterns), improvements to the XMP framework, optimization for PostScript state handling in (E)PSDocumentGraphics2D, and more. In addition it contains a number of bug fixes. For details, please see the <a href="changes.html#version_1.4">Changes</a> page.</p>
<p>We are pleased to note that many new features were contributed from outside the team of committers. Such broader interest ensures the healthy further development of the project.
</item></p>
-<h2 id="news-2008-06-11">11 Jun 2008: Version 1.3.1 Released</h2>
+<h2 id="11-jun-2008-version-131-released-wzxhzdk13wzxhzdk14">11 Jun 2008: Version 1.3.1 Released # <a id="#news-2008-06-11"></a></h2>
<p><item date="2008-06-11" title="Version 1.3.1 Released">
This release is mostly a bugfix release for the image loading framework that has been introduced in version 1.3. For details, please see the <a href="changes.html#version_1.3.1">Changes</a> page.
</item></p>
-<h2 id="news-2008-03-07">7 Mar 2008: Version 1.3 Released</h2>
+<h2 id="7-mar-2008-version-13-released-wzxhzdk17wzxhzdk18">7 Mar 2008: Version 1.3 Released # <a id="#news-2008-03-07"></a></h2>
<p><item date="2008-03-07" title="Version 1.3 Released">
The most important addition in this release is an image loading framework which supports all sorts of different image formats (bitmap and vector) and is highly extensible.</p>
<p>Besides that there were a larger number of smaller additions and bugfixes.</p>
<p>Support for Java 1.3 has been dropped. Java 1.4 or later is required now.
</item></p>
-<h2 id="news-2007-07-21">21 Jul 2007: Version 1.2 Released</h2>
+<h2 id="21-jul-2007-version-12-released-wzxhzdk21wzxhzdk22">21 Jul 2007: Version 1.2 Released # <a id="#news-2007-07-21"></a></h2>
<p><item date="2007-07-21" title="Version 1.2 Released">
This release mainly adds support for CMYK and GRAY color spaces for PSGenerator. For details about other fixes, please see the <a href="changes.html#version_1.2">Changes</a> page.
</item></p>
-<h2 id="news-2006-12-22">22 Dec 2006: Version 1.1 Released</h2>
+<h2 id="22-dec-2006-version-11-released-wzxhzdk25wzxhzdk26">22 Dec 2006: Version 1.1 Released # <a id="#news-2006-12-22"></a></h2>
<p><item date="2006-12-22" title="Version 1.1 Released">
This release adds an XMP metadata framework and brings improvements for the ImageWriter package plus some minor fixes mainly in the PostScript area.
</item></p>
-<h2 id="news-2006-04-17">17 Apr 2006: Version 1.0 Released</h2>
+<h2 id="17-apr-2006-version-10-released-wzxhzdk29wzxhzdk30">17 Apr 2006: Version 1.0 Released # <a id="#news-2006-04-17"></a></h2>
<p><item date="2006-04-17" title="Version 1.0 Released">
This is the first release of Apache XML Graphics Commons. There are currently no known issues with the code.
</item></p></div>
Modified: websites/staging/xmlgraphics/trunk/content/commons/postscript.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/commons/postscript.html (original)
+++ websites/staging/xmlgraphics/trunk/content/commons/postscript.html Tue Oct 23 15:05:41 2012
@@ -128,7 +128,7 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/commons/">Commons</a></div> -->
- <div class="section-content"><h1 id="overview">Overview</h1>
+ <div class="section-content"><h1 id="overview-wzxhzdk0wzxhzdk1">Overview <a id="#overview"></a></h1>
<p>Apache™ XML Graphics Commons contains various tools for writing and processing Adobe PostScript files. This includes:</p>
<ul>
<li>
@@ -142,12 +142,12 @@ $(document).ready(function () {
We don't currently include a PostScript interpreter though we would love to have one. A Java-based PostScript interpreter to keep an eye on is the one from the <a href="http://foray.sourceforge.net">FOray project</a> .</p>
</li>
</ul>
-<h1 id="generator">The PostScript generator</h1>
+<h1 id="the-postscript-generator-wzxhzdk3wzxhzdk4">The PostScript generator <a id="#generator"></a></h1>
<p>The "PSGenerator" class can help writing PostScript files. It deals with things like escaping, saving/tracking/restoring graphics state, writing DSC comments and tracking of DSC resources.</p>
<p>You will rarely interact with the PS generator itself, as it is probably more interesting to generate a PostScript file using Java2D which is described in the following section.</p>
-<h1 id="java2d">Java2D: Graphics2D implementation for generating PostScript and EPS</h1>
+<h1 id="java2d-graphics2d-implementation-for-generating-postscript-and-eps-wzxhzdk5wzxhzdk6">Java2D: Graphics2D implementation for generating PostScript and EPS <a id="#java2d"></a></h1>
<p>We provide two classes (PSDocumentGraphics2D and EPSDocumentGraphics2D) which you can use to generated complete PostScript files using normal Java2D means. The difference between the two classes is that the EPS variant creates a fully compliant Encapsulated PostScript file while the PS variant simply creates a normal DSC-compliant level 2 PostScript file. It depends on your requirement which variant you choose. The PS variant is mostly for printing purposes while the EPS variant is better suited for inclusion in other documents.</p>
-<h2 id="creating-eps">Creating an EPS file</h2>
+<h2 id="creating-an-eps-file-wzxhzdk7wzxhzdk8">Creating an EPS file # <a id="#creating-eps"></a></h2>
<p>Creating an EPS file using the Graphics2D implementation is easy. Instantiate EPSDocumentGraphics2D, set a GraphicContext and set up the output document. Here's an example:</p>
<p>import org.apache.xmlgraphics.java2d.ps.EPSDocumentGraphics2D;</p>
<p class="."></p>
@@ -159,7 +159,7 @@ g2d.setupDocument(out, 400, 200); //400p
<p>g2d.drawRect(10, 10, 50, 50); //paint a rectangle using normal Java2D calls</p>
<p>g2d.finish(); //Wrap up and finalize the EPS file</p>
<p>A complete example for generating an EPS files can be found in the <a href="http://svn.apache.org/viewvc/xmlgraphics/commons/trunk/examples/java/java2d/ps/">"examples" directory</a> in the distribution.</p>
-<h1 id="dsc">DSC parser/processor</h1>
+<h1 id="dsc-parserprocessor-wzxhzdk9wzxhzdk10">DSC parser/processor <a id="#dsc"></a></h1>
<p>Many PostScript files use special comments to structure a document. This allows manipulation of PostScript files without interpreting them. These special comments are defined in the <a href="http://partners.adobe.com/public/developer/en/ps/5001.DSC_Spec.pdf">Document Structuring Conventions</a> . The code in Commons is designed to work with DSC 3.0. For details on how DSC is used, please take a look at the DSC specification.</p>
<p>The DSC support in Commons was primarily developed to implement resource optimization features in <a href="http://xmlgraphics.apache.org/fop/">Apache FOP</a> 's PostScript output support. Resources like images which are used repeatedly in a document should not be written to the PostScript file each time it is used. Instead it is written once at the beginning of the file as a PostScript form. The form is then called whenever the image needs painting.</p>
<p>But the DSC parser could potentially be used for other purposes. The most obvious is extracting a subset of pages from a DSC-compliant file. Assume you want to print only page 45 to 57 of a particular document. There's an example that demonstrates exactly this. Check out the "examples" directory in the distribution. Other potential use cases for the DSC parser are:</p>
Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/anttask.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/anttask.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/anttask.html Tue Oct 23 15:05:41 2012
@@ -332,7 +332,7 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/0.95/">0.95</a></div> -->
<div class="section-content"><p><version>$Revision: 1298724 $</version></p>
<p>Apache™ FOP provides an Ant task for automating the document build process.</p>
-<h1 id="basics">Description</h1>
+<h1 id="description-wzxhzdk4wzxhzdk5">Description <a id="#basics"></a></h1>
<p>The FOP Ant task will convert XSL-FO documents to PDF, PS, PCL etc. output (see <a href="output.html">Output formats</a> for available formats).</p>
<p>To call FOP tasks within Ant, first add a FOP task definition to your Ant build file. One method of defining the task is as follows:</p>
<property name="fop.home" value="....path to your FOP HOME directory..."/>
@@ -352,7 +352,7 @@ $(document).ready(function () {
Then create FOP tasks within your Ant build file, using the FOP task parameters listed below.
-# Parameters for FOP Ant task # {#parameters}
+# Parameters for FOP Ant task <a id="#parameters"></a>
<caption>Parameters specified as attributes</caption>| Attribute | Description | Required |
|-----------|-------------|----------|
@@ -371,7 +371,7 @@ Then create FOP tasks within your Ant bu
|-----------|-------------|----------|
| fileset | [FileSets](http://ant.apache.org/manual/CoreTypes/fileset.html) are used to specify multiple XSL-FO files to be rendered. | Yes, if no fofile attribute is supplied |
-# Examples # {#examples}
+# Examples <a id="#examples"></a>
The following example converts a single XSL-FO file to a PDF document:
Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/changes_0.95.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/changes_0.95.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/changes_0.95.html Tue Oct 23 15:05:41 2012
@@ -331,18 +331,18 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/0.95/">0.95</a></div> -->
<div class="section-content"><p><a href="changes_0.95.rss"></a> </p>
-<h1 id="introduction">Introduction and explanation of symbols</h1>
+<h1 id="introduction-and-explanation-of-symbols-wzxhzdk0wzxhzdk1">Introduction and explanation of symbols <a id="#introduction"></a></h1>
<p>Changes are sorted by "type" and then chronologically with the most recent at the top. These symbols denote the various action types:<icon alt="add" src="../images/add.jpg"></icon>=add,<icon alt="fix" src="../images/fix.jpg"></icon>=fix,<icon alt="remove" src="../images/remove.jpg"></icon>=remove,<icon alt="update" src="../images/update.jpg"></icon>=update</p>
-<h1 id="version_0.95">Version 0.95 (05 August 2008)</h1>
-<h2 id="API_0.95">Changes to the End-User API</h2>
+<h1 id="version-095-05-august-2008-wzxhzdk10wzxhzdk11">Version 0.95 (05 August 2008) <a id="#version_0.95"></a></h1>
+<h2 id="changes-to-the-end-user-api-wzxhzdk12wzxhzdk13">Changes to the End-User API # <a id="#API_0.95"></a></h2>
<ul>
<li><icon alt="fix" src="../images/fix.jpg"></icon>Fixed the -imagein command-line option. Committed by JM.</li>
</ul>
-<h2 id="Code_0.95">Changes to the Code Base</h2>
+<h2 id="changes-to-the-code-base-wzxhzdk14wzxhzdk15">Changes to the Code Base # <a id="#Code_0.95"></a></h2>
<ul>
<li><icon alt="fix" src="../images/fix.jpg"></icon>Fixed potential multi-threading problem concerning the use of DecimalFormat. Committed by JM. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=44887">44887</a> .</li>
</ul>
-<h2 id="Fonts_0.95">Changes to the Font Subsystem</h2>
+<h2 id="changes-to-the-font-subsystem-wzxhzdk16wzxhzdk17">Changes to the Font Subsystem # <a id="#Fonts_0.95"></a></h2>
<ul>
<li>
<p><icon alt="fix" src="../images/fix.jpg"></icon>Fixed text extraction problem with ZapfDingbats and Symbol font in PDF output. Committed by JM.</p>
@@ -351,7 +351,7 @@ $(document).ready(function () {
<p><icon alt="fix" src="../images/fix.jpg"></icon>Fixed NullPointerException when loading a TrueType font using XML font metric files. Committed by JM.</p>
</li>
</ul>
-<h2 id="Images_0.95">Changes to the Image Support</h2>
+<h2 id="changes-to-the-image-support-wzxhzdk18wzxhzdk19">Changes to the Image Support # <a id="#Images_0.95"></a></h2>
<ul>
<li>
<p><icon alt="fix" src="../images/fix.jpg"></icon>Fixed two bugs concerning resolution handling with SVG images and their conversion to bitmaps for RTF output. Committed by JM.</p>
@@ -360,7 +360,7 @@ $(document).ready(function () {
<p><icon alt="fix" src="../images/fix.jpg"></icon>Fixed a performance problem concerning image serialization. Committed by JM.</p>
</li>
</ul>
-<h2 id="Layout_0.95">Changes to the Layout Engine</h2>
+<h2 id="changes-to-the-layout-engine-wzxhzdk20wzxhzdk21">Changes to the Layout Engine # <a id="#Layout_0.95"></a></h2>
<ul>
<li>
<p><icon alt="fix" src="../images/fix.jpg"></icon>Fixed NullPointerException when page-number-citations are used inside a marker. Committed by AD. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=45295">45295</a> .</p>
@@ -372,7 +372,7 @@ $(document).ready(function () {
<p><icon alt="fix" src="../images/fix.jpg"></icon>Various bugfixes for table layout. Committed by VH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=44621">44621</a> .</p>
</li>
</ul>
-<h2 id="Renderers_0.95">Changes to Renderers (Output Formats)</h2>
+<h2 id="changes-to-renderers-output-formats-wzxhzdk22wzxhzdk23">Changes to Renderers (Output Formats) # <a id="#Renderers_0.95"></a></h2>
<ul>
<li>
<p><icon alt="add" src="../images/add.jpg"></icon>Added support for fo:leader for RTF output (no full support!). Fixes problems with empty leaders being used to force empty lines among other issues. Committed by JM. Thanks to Maximilian Aster. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=43825">43825</a> .</p>
@@ -405,7 +405,7 @@ $(document).ready(function () {
<p><icon alt="fix" src="../images/fix.jpg"></icon>Fixed regression causing bad positioning of block-containers if used as descendant of a table-cell. Committed by JM.</p>
</li>
</ul>
-<h2 id="contributors_0.95">Contributors to this release</h2>
+<h2 id="contributors-to-this-release-wzxhzdk24wzxhzdk25">Contributors to this release # <a id="#contributors_0.95"></a></h2>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Andreas Delmelle (AD), Jeremias Märki (JM), Vincent Hennebert (VH).</p>
<p>This is a list of other contributors:<br></br>Maximilian Aster.</p></div>
Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/changes_0.95beta.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/changes_0.95beta.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/changes_0.95beta.html Tue Oct 23 15:05:41 2012
@@ -331,14 +331,14 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/0.95/">0.95</a></div> -->
<div class="section-content"><p><a href="changes_0.95beta.rss"></a> </p>
-<h1 id="introduction">Introduction and explanation of symbols</h1>
+<h1 id="introduction-and-explanation-of-symbols-wzxhzdk0wzxhzdk1">Introduction and explanation of symbols <a id="#introduction"></a></h1>
<p>Changes are sorted by "type" and then chronologically with the most recent at the top. These symbols denote the various action types:<icon alt="add" src="../images/add.jpg"></icon>=add,<icon alt="fix" src="../images/fix.jpg"></icon>=fix,<icon alt="remove" src="../images/remove.jpg"></icon>=remove,<icon alt="update" src="../images/update.jpg"></icon>=update</p>
-<h1 id="version_0.95beta">Version 0.95beta (26 March 2008)</h1>
-<h2 id="API_0.95beta">Changes to the End-User API</h2>
+<h1 id="version-095beta-26-march-2008-wzxhzdk10wzxhzdk11">Version 0.95beta (26 March 2008) <a id="#version_0.95beta"></a></h1>
+<h2 id="changes-to-the-end-user-api-wzxhzdk12wzxhzdk13">Changes to the End-User API # <a id="#API_0.95beta"></a></h2>
<ul>
<li><icon alt="remove" src="../images/remove.jpg"></icon>Removed deprecated methods in the "apps" package that were left-overs from the API discussions. Committed by JM.</li>
</ul>
-<h2 id="Code_0.95beta">Changes to the Code Base</h2>
+<h2 id="changes-to-the-code-base-wzxhzdk14wzxhzdk15">Changes to the Code Base # <a id="#Code_0.95beta"></a></h2>
<ul>
<li>
<p><icon alt="add" src="../images/add.jpg"></icon>Turned on XInclude processing for the main source given on the command line. Committed by MB.</p>
@@ -368,7 +368,7 @@ $(document).ready(function () {
<p><icon alt="fix" src="../images/fix.jpg"></icon>Avoid a NullPointerException in AreaTreeHandler.endDocument(). Committed by JM. Thanks to David Delbecq. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=43910">43910</a> .</p>
</li>
</ul>
-<h2 id="Extensions_0.95beta">Changes to the Bundled Extensions</h2>
+<h2 id="changes-to-the-bundled-extensions-wzxhzdk16wzxhzdk17">Changes to the Bundled Extensions # <a id="#Extensions_0.95beta"></a></h2>
<ul>
<li>
<p><icon alt="add" src="../images/add.jpg"></icon>New extension attribute fox:transform on fo:block-container allows free-form transformation (rotation, scaling etc.) of absolute and fixed block-containers. Supported only for PDF, PS and Java2D-based renderers. Committed by JM.</p>
@@ -377,7 +377,7 @@ $(document).ready(function () {
<p><icon alt="add" src="../images/add.jpg"></icon>Added new extension element: fox:external-document. It allows to add whole documents such as multi-page TIFF images to be inserted as peers to a page-sequence. Each image will make up an entire page. See the documentation for details. Committed by JM.</p>
</li>
</ul>
-<h2 id="Fonts_0.95beta">Changes to the Font Subsystem</h2>
+<h2 id="changes-to-the-font-subsystem-wzxhzdk18wzxhzdk19">Changes to the Font Subsystem # <a id="#Fonts_0.95beta"></a></h2>
<ul>
<li>
<p><icon alt="add" src="../images/add.jpg"></icon>Added support for unusual font encodings (like for Symbol or Cyrillic fonts) of Type 1 fonts in PDF and PostScript output. Committed by JM.</p>
@@ -410,11 +410,11 @@ $(document).ready(function () {
<p><icon alt="update" src="../images/update.jpg"></icon>Improved font auto-detection and handling of AWT-supplied fonts in order to achieve better results when using multiple output formats. Whenever possible, the font names appearing in the operating system can also be used in XSL-FO. Committed by JM.</p>
</li>
</ul>
-<h2 id="Images_0.95beta">Changes to the Image Support</h2>
+<h2 id="changes-to-the-image-support-wzxhzdk20wzxhzdk21">Changes to the Image Support # <a id="#Images_0.95beta"></a></h2>
<ul>
<li><icon alt="fix" src="../images/fix.jpg"></icon>A new image loading framework has been introduced to fix various problems with external graphics and improve performance. Committed by JM.</li>
</ul>
-<h2 id="Layout_0.95beta">Changes to the Layout Engine</h2>
+<h2 id="changes-to-the-layout-engine-wzxhzdk22wzxhzdk23">Changes to the Layout Engine # <a id="#Layout_0.95beta"></a></h2>
<ul>
<li>
<p><icon alt="add" src="../images/add.jpg"></icon>Added support for background on fo:table-column and fo:table-header/footer/body elements. Committed by VH.</p>
@@ -531,7 +531,7 @@ $(document).ready(function () {
<p><icon alt="update" src="../images/update.jpg"></icon>PropertyCache phase 2:<br></br>⢠improvement of the PropertyCache itself should now guarantee acceptable performance of the static caches in multi-session environments, which is a possible problem with synchronizedMap.<br></br>⢠changed CommonFont to use the cache: added CachedCommonFont to contain the properties that are always cacheable CommonFont itself is only cached if the remaining properties are absolutes.<br></br>⢠changed CommonHyphenation, KeepProperty, ColorProperty and FontFamilyProperty to use the cache.<br></br>Committed by AD.</p>
</li>
</ul>
-<h2 id="Renderers_0.95beta">Changes to Renderers (Output Formats)</h2>
+<h2 id="changes-to-renderers-output-formats-wzxhzdk24wzxhzdk25">Changes to Renderers (Output Formats) # <a id="#Renderers_0.95beta"></a></h2>
<ul>
<li>
<p><icon alt="add" src="../images/add.jpg"></icon>Added an option to disable the default sRGB profile in PDF output for those who don't care about color fidelity, but care about PDF file size. Committed by JM.</p>
@@ -591,7 +591,7 @@ $(document).ready(function () {
<p><icon alt="update" src="../images/update.jpg"></icon>PDF Transcoder (SVG) text painting has been completely rewritten. Except for some special cases (with filters for example), all text (including flow text) is now painted using PDF text operators. Committed by JM.</p>
</li>
</ul>
-<h2 id="contributors_0.95beta">Contributors to this release</h2>
+<h2 id="contributors-to-this-release-wzxhzdk26wzxhzdk27">Contributors to this release # <a id="#contributors_0.95beta"></a></h2>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Adrian Cumiskey (AC), Andreas Delmelle (AD), Jeremias Märki (JM), Max Berger (MB), Vincent Hennebert (VH).</p>
<p>This is a list of other contributors:<br></br>Adrian Cumiskey, Andrejus Chaliapinas, Bruno Feurer, ckohrn.at.tng.de, David Churavy, David Delbecq, Gordon Cooke, Justus Piater, Max Berger, Patrick Jaromin, Stefan Ziel, V. Schappert.</p></div>
Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/compiling.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/compiling.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/compiling.html Tue Oct 23 15:05:41 2012
@@ -331,19 +331,19 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/0.95/">0.95</a></div> -->
<div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="build-needed">Do You Need To Build?</h1>
+<h1 id="do-you-need-to-build-wzxhzdk2wzxhzdk3">Do You Need To Build? <a id="#build-needed"></a></h1>
<p>Apache™ FOP distributions are either pre-compiled binary or source. If you are using a binary distribution, it is already built and there is no need to build it again. See the <a href="../download.html">Download Instructions</a> for information about whether a binary or source distribution is best for your needs.</p>
<p>If you got the source code from a repository snapshot or via Subversion you will need to build FOP in any case.</p>
-<h1 id="env">Set Up Your Environment</h1>
-<h2 id="env-jdk">JDK</h2>
+<h1 id="set-up-your-environment-wzxhzdk5wzxhzdk6">Set Up Your Environment <a id="#env"></a></h1>
+<h2 id="jdk-wzxhzdk7wzxhzdk8">JDK # <a id="#env-jdk"></a></h2>
<p>Building FOP requires a minimum Java Development Kit (JDK/SDK) of 1.4 (A Java Runtime Environment is not sufficient).</p>
-<h2 id="env-classpath">CLASSPATH</h2>
+<h2 id="classpath-wzxhzdk9wzxhzdk10">CLASSPATH # <a id="#env-classpath"></a></h2>
<p>There is generally no need to setup a classpath. All libraries needed to compile FOP are included in the source distribution and are referenced by the build script. You will only need to adjust the classpath if you build FOP in some other way. See the build script build.xml for details.</p>
-<h2 id="env-java-home">JAVA_HOME</h2>
+<h2 id="java_home-wzxhzdk11wzxhzdk12">JAVA_HOME # <a id="#env-java-home"></a></h2>
<p>The build script uses <a href="http://ant.apache.org/">Apache Ant</a> , a popular Java-based build tool, which usually requires that the environment variable JAVA_HOME point to your local JDK root directory. This is true even if you use JDK 1.4 or above, which normally does not need this setting.</p>
-<h2 id="env-ant">Apache Ant</h2>
+<h2 id="apache-ant-wzxhzdk13wzxhzdk14">Apache Ant # <a id="#env-ant"></a></h2>
<p><a href="http://ant.apache.org/">Apache Ant</a> (Version 1.7 or later) must be installed in order to build FOP. Following best practices we don't include Ant with FOP anymore. You can find the <a href="http://ant.apache.org/manual/">instructions to install Ant in the Ant manual</a> on the web.</p>
-<h1 id="build-script">Run the Build Script</h1>
+<h1 id="run-the-build-script-wzxhzdk15wzxhzdk16">Run the Build Script <a id="#build-script"></a></h1>
<p>Change to the FOP root directory and build FOP by executing the build script (build.xml) using the "ant" command.
The "ant" command is only available on your system if you've properly <a href="http://ant.apache.org/manual/">installed Apache Ant</a> and added Ant's location to the PATH environment variable.
The file build.xml in the FOP root directory is the blueprint that Ant uses for the build. It contains information for numerous build targets, many of which are building blocks to more useful target, and others which are primarily used by the FOP developers. You may benefit from looking through this file to learn more about the various build targets. To obtain a complete list of useful build targets:
@@ -368,7 +368,7 @@ OR
ant all
To clean the build directory first:
ant clean allIf you want to shorten the build time you can just call the "package" target which doesn't perform any automated tests during the build.</p>
-<h1 id="problems">Troubleshooting</h1>
+<h1 id="troubleshooting-wzxhzdk17wzxhzdk18">Troubleshooting <a id="#problems"></a></h1>
<p>If you have problems building FOP, please try the following:</p>
<ul>
<li>
Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/configuration.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/configuration.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/configuration.html Tue Oct 23 15:05:41 2012
@@ -331,10 +331,10 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/0.95/">0.95</a></div> -->
<div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="general">Configuration File Basics</h1>
+<h1 id="configuration-file-basics-wzxhzdk7wzxhzdk8">Configuration File Basics <a id="#general"></a></h1>
<p>The FOP configuration file is an XML file containing a variety of settings that are useful for controlling FOP's behavior, and for helping it find resources that you wish it to use.</p>
<p>The easiest way to get started using a FOP configuration file is to copy the sample found at <code>{fop-dir}/conf/fop.xconf</code> to a location of your choice, and then to edit it according to your needs. It contains templates for the various configuration options, most of which are commented out. Remove the comments and change the settings for entries that you wish to use. Be sure to follow any instructions, including comments which specify the value range. Also, since the configuration file is XML, be sure to keep it well-formed.</p>
-<h2 id="general-available">Making Configuration Available to FOP</h2>
+<h2 id="making-configuration-available-to-fop-wzxhzdk9wzxhzdk10">Making Configuration Available to FOP # <a id="#general-available"></a></h2>
<p>After creating your configuration file, you must tell FOP how to find it:</p>
<ul>
<li>
@@ -345,7 +345,7 @@ $(document).ready(function () {
</li>
</ul>
<p>See <a href="embedding.html#config-internal">Setting the Configuration Programmatically</a> for instructions on how to do so in an embedded environment.</p>
-<h1 id="general-elements">Summary of the General Configuration Options</h1>
+<h1 id="summary-of-the-general-configuration-options-wzxhzdk11wzxhzdk12">Summary of the General Configuration Options <a id="#general-elements"></a></h1>
<table>
<thead>
<tr>
@@ -449,7 +449,7 @@ $(document).ready(function () {
<default-page-settings height="11in" width="8.26in"/></p>
<p><!-- etc. etc..... -->
</fop></p>
-<h1 id="renderers">Renderer configuration</h1>
+<h1 id="renderer-configuration-wzxhzdk36wzxhzdk37">Renderer configuration <a id="#renderers"></a></h1>
<p>Each Renderer has its own configuration section which is identified by the MIME type the Renderer is written for, ex. "application/pdf" for the PDF Renderer.</p>
<p>The configuration for the PDF Renderer could look like this:</p>
<p><renderers>
@@ -475,7 +475,7 @@ $(document).ready(function () {
<p>The details on the font configuration can be found on the separate <a href="fonts.html">Fonts</a> page. Note especially the section entitled <a href="fonts.html#register">Register Fonts with FOP</a> .</p>
-<h2 id="pdf-renderer">Special Settings for the PDF Renderer</h2>
+<h2 id="special-settings-for-the-pdf-renderer-wzxhzdk56wzxhzdk57">Special Settings for the PDF Renderer # <a id="#pdf-renderer"></a></h2>
<p>The configuration element for the PDF renderer contains two elements. One is for the font configuration (please follow the link above) and one is for the "filter list". The filter list controls how the individual objects in a PDF file are encoded. By default, all objects get "flate" encoded (i.e. simply compressed with the same algorithm that is also used in ZIP files). Most users don't need to change that setting. For debugging purposes, it may be desired not to compress the internal objects at all so the generated PDF commands can be read. In that case, you can simply use the following filter list. The second filter list (type="image") ensures that all images still get compressed but also ASCII-85 encoded so the produced PDF file is still easily readable in a text editor.</p>
<div class="codehilite"><pre><span class="nt"><renderer</span> <span class="na">mime=</span><span class="s">"application/pdf"</span><span class="nt">></span>
<span class="nt"><filterList></span>
@@ -513,7 +513,7 @@ $(document).ready(function () {
</pre></div>
-<h2 id="ps-renderer">Special Settings for the PostScript Renderer</h2>
+<h2 id="special-settings-for-the-postscript-renderer-wzxhzdk58wzxhzdk59">Special Settings for the PostScript Renderer # <a id="#ps-renderer"></a></h2>
<p>Besides the normal font configuration (the same "fonts" element as for the PDF renderer) the PostScript renderer has an additional setting to force landscape pages to be rotated to fit on a page inserted into the printer in portrait mode. Set the value to "true" to activate this feature. The default is "false". Example:</p>
<div class="codehilite"><pre><span class="nt"><renderer</span> <span class="na">mime=</span><span class="s">"application/postscript"</span><span class="nt">></span>
<span class="nt"><auto-rotate-landscape></span>true<span class="nt"></auto-rotate-landscape></span>
@@ -532,7 +532,7 @@ $(document).ready(function () {
</pre></div>
-<h2 id="pcl-renderer">Special Settings for the PCL Renderer</h2>
+<h2 id="special-settings-for-the-pcl-renderer-wzxhzdk60wzxhzdk61">Special Settings for the PCL Renderer # <a id="#pcl-renderer"></a></h2>
<p>Non-standard fonts for the PCL renderer are made available through the Java2D subsystem which means that you don't have to do any custom font configuration in this case but you have to use the font names offered by Java.</p>
<p>Additionally, there are certain settings that control how the renderer handles various elements.
<renderer mime="application/vnd.hp-PCL">
@@ -541,7 +541,7 @@ $(document).ready(function () {
</renderer>
The default value for the "rendering" setting is "speed" which causes borders to be painted as plain rectangles. In this mode, no special borders (dotted, dashed etc.) are available. If you want support for all border modes, set the value to "quality" as indicated above. This will cause the borders to be painted as bitmaps.</p>
<p>The default value for the "text-rendering" setting is "auto" which paints the base fonts using PCL fonts. Non-base fonts are painted as bitmaps through Java2D. If the mix of painting methods results in unwelcome output, you can set this to "bitmap" which causes all text to be rendered as bitmaps.</p>
-<h1 id="when-it-does-not-work-whenitdoesnotwork">When it does not work # {#When+it+does+not+work}</h1>
+<h1 id="when-it-does-not-work-wzxhzdk68wzxhzdk69">When it does not work <a id="#When+it+does+not+work"></a></h1>
<p>FOP searches the configuration file for the information it expects, at the position it expects. When that information is not present, FOP will not complain, it will just continue. When there is other information in the file, FOP will not complain, it will just ignore it. That means that when your configuration information is in the file but in a different XML element, or in a different XML path, than FOP expects, it will be silently ignored.</p>
<p>Check the following possibilities:</p>
<ul>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org