You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by gi...@apache.org on 2026/10/08 14:07:35 UTC
(xmlgraphics-website) branch asf-site updated: Automatic Site Publish by Buildbot
This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/xmlgraphics-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new c768c20f Automatic Site Publish by Buildbot
c768c20f is described below
commit c768c20fa26d4c56364e248da3da229ae7ee6544
Author: buildbot <us...@infra.apache.org>
AuthorDate: Thu Oct 8 14:07:30 2026 +0000
Automatic Site Publish by Buildbot
---
output/batik/dev/test.html | 8 ++++----
output/batik/tools/browser.html | 2 +-
output/batik/tools/rasterizer.html | 2 +-
output/batik/using/architecture.html | 2 +-
output/batik/using/dom-api.html | 4 ++--
output/batik/using/extending.html | 4 ++--
output/batik/using/index.html | 2 +-
output/batik/using/scripting/security.html | 8 ++++----
output/batik/using/swing.html | 8 ++++----
output/batik/using/transcoder.html | 2 +-
output/commons/changes.html | 6 +++---
output/commons/image-loader.html | 2 +-
output/fop/changes.html | 18 +++++++++---------
output/fop/dev/design/areas.html | 12 ++++++------
output/fop/dev/design/breakpos.html | 2 +-
output/fop/dev/design/embedding.html | 4 ++--
output/fop/dev/design/extending.html | 2 +-
output/fop/dev/design/layout.html | 28 ++++++++++++++--------------
output/fop/dev/design/optimise.html | 2 +-
output/fop/dev/design/pdf-library.html | 4 ++--
output/fop/dev/design/properties.html | 2 +-
output/fop/dev/design/renderers.html | 6 +++---
output/fop/dev/design/startup.html | 2 +-
output/fop/dev/design/svg.html | 2 +-
output/fop/dev/design/useragent.html | 4 ++--
output/fop/dev/extensions.html | 2 +-
output/fop/dev/implement.html | 2 +-
output/fop/dev/release.html | 2 +-
output/fop/dev/svg.html | 2 +-
output/fop/dev/testing.html | 6 +++---
output/fop/faq.html | 8 ++++----
output/fop/fo.html | 2 +-
output/fop/knownissues.html | 4 ++--
output/fop/news.html | 4 ++--
output/fop/team.html | 2 +-
output/fop/trunk/configuration.html | 2 +-
output/fop/trunk/embedding.html | 4 ++--
output/fop/trunk/events.html | 2 +-
output/fop/trunk/extensions.html | 2 +-
output/fop/trunk/fonts.html | 2 +-
output/fop/trunk/hyphenation.html | 2 +-
output/fop/trunk/metadata.html | 2 +-
output/fop/trunk/output.html | 6 +++---
output/fop/trunk/pdfa.html | 2 +-
output/fop/trunk/pdfx.html | 2 +-
output/fop/trunk/running.html | 2 +-
output/fop/trunk/servlets.html | 6 +++---
47 files changed, 103 insertions(+), 103 deletions(-)
diff --git a/output/batik/dev/test.html b/output/batik/dev/test.html
index 120416a4..ded16eb9 100644
--- a/output/batik/dev/test.html
+++ b/output/batik/dev/test.html
@@ -241,7 +241,7 @@ This is another implementation of the <code>TestReportProcessor</code> interface
<h2 id="managingATestSuite">Managing test suites</h2>
<p>The infrastructure is designed to make it easy to create, update and modify test suites. This section describes how to describe a set of tests to be run and how to actually run that test suite.</p>
<h3 id="Describing-a-test-suite">Describing a test suite</h3>
-<p>Test suites can be described in XML (XML-in refered to earlier in this document). The general format for describing a test suite is:</p>
+<p>Test suites can be described in XML (XML-in referred to earlier in this document). The general format for describing a test suite is:</p>
<div class="highlight"><pre><span></span><code><span class="nt"><testSuite</span> <span class="na">id=</span><span class="s">"testSuiteA"</span> <span class="na">name=</span><span class="s">"MyFavoriteTestSuite"</span><span class="nt">></span>
<span class="c"><!-- Set of tests to be run --></span>
<span class="nt"><test</span> <span class="na">id=</span><span class="s">"t1"</span> <span class="na">class=</span><span class="s">"myFavoriteTestClassA"</span><span class="nt">/></span>
@@ -310,7 +310,7 @@ This is another implementation of the <code>TestReportProcessor</code> interface
<span class="nt"><arg</span> <span class="na">class=</span><span class="s">"org.apache.batik.test.xml.XSLXMLReportConsumer"</span><span class="nt">></span>
<span class="c"><!-- Stylesheet --></span>
<span class="nt"><arg</span> <span class="na">class=</span><span class="s">"java.lang.String"</span> <span class="na">value=</span><span class="s">"file:test-resources/org/apache/batik/test/svg/HTMLReport.xsl"</span><span class="nt">/></span>
- <span class="c"><!-- Ouput Directory --></span>
+ <span class="c"><!-- Output Directory --></span>
<span class="nt"><arg</span> <span class="na">class=</span><span class="s">"java.lang.String"</span> <span class="na">value=</span><span class="s">"test-reports/html"</span><span class="nt">/></span>
<span class="c"><!-- Output file prefix --></span>
<span class="nt"><arg</span> <span class="na">class=</span><span class="s">"java.lang.String"</span> <span class="na">value=</span><span class="s">"RegardResult"</span><span class="nt">/></span>
@@ -338,7 +338,7 @@ This is another implementation of the <code>TestReportProcessor</code> interface
<p>In addition, the <code>regard</code> rule runs a specific set of tests by default, so that you do not need to pass any <em>testRun</em> file argument.</p>
<p><strong> <code>regard</code> is the project’s safeguard against regressions</strong>.</p>
<h2 id="regard">regard: the Batik regression test suite</h2>
-<p>The regard test suite contains all the regression tests for the Batik project. The <code>regard</code> tool is a specific test suite description, <code>regard.xml</code> (which you can find in the <code>test-resources/org/apache/batik/test</code> directory). That file contains a set of test suite files which sould be run.</p>
+<p>The regard test suite contains all the regression tests for the Batik project. The <code>regard</code> tool is a specific test suite description, <code>regard.xml</code> (which you can find in the <code>test-resources/org/apache/batik/test</code> directory). That file contains a set of test suite files which should be run.</p>
<p>The following describes how to use the regard tool and some of the most important tests in the regard test suite.</p>
<h3 id="Running-regard">Running regard</h3>
<p>The regard tool lets you run either all the tests or any specific test you want in the test suite. To run all the tests in the regard test suite, type the following at the command line, for Windows:</p>
@@ -401,7 +401,7 @@ This is another implementation of the <code>TestReportProcessor</code> interface
<p>build regard</p>
<p>Check the newly generated HTML report in the <code>test-reports/html</code> directory: there should no longer be any test failure.</p>
<h4 id="Daily-usage">Daily usage</h4>
-<p>Once the intial set up has been done, you can use regard by simply updating your Git copy, including the test-references. If no change occurs, your test will keep passing with your reference images. If a test fails (e.g., if someone checks in a new reference image from a platform different than the one you are using, you will have to check if it is because of system specific reasons or if there is a bigger problem.</p>
+<p>Once the initial set up has been done, you can use regard by simply updating your Git copy, including the test-references. If no change occurs, your test will keep passing with your reference images. If a test fails (e.g., if someone checks in a new reference image from a platform different than the one you are using, you will have to check if it is because of system specific reasons or if there is a bigger problem.</p>
<h3 id="SVG-generator-tests">SVG generator tests</h3>
<p>Regard contains over 100 tests for checking regressions on the SVG generator. If you use <code>svggen</code> as an argument to regard, all the SVG generator tests will be run (because <code>regard.xml</code> points to <code>test-resources/org/apache/batik/svggen/regsvggen.xml</code>, which is a test suite description for the SVG generator and that file’s root <code>testSuite</code> element has the “svggen” ID).</p>
<h2 id="writingNewTests">Writing new tests</h2>
diff --git a/output/batik/tools/browser.html b/output/batik/tools/browser.html
index 853028ef..a0156a84 100644
--- a/output/batik/tools/browser.html
+++ b/output/batik/tools/browser.html
@@ -285,7 +285,7 @@ For Windows, type the following at the command prompt:</p>
<p><img alt="Screenshot of Squiggle showing the location bar" src="images/svgviewerLocationBar.png"></p>
<h2 id="browsing">Browsing SVG files</h2>
<p>As with HTML content, it is common to navigate back and forth between SVG files (remember that SVG files contain hyperlinks, just like HTML does) and, as described later in this document, it is possible to <a href="#zoomInOut">zoom</a> into SVG documents, <a href="#panning">pan</a> and <a href="#rotating">rotate</a>.</p>
-<p><img alt="Screnshot of Squiggle showing the 'Go' menu" src="images/svgviewerBrowsing.png"></p>
+<p><img alt="Screenshot of Squiggle showing the 'Go' menu" src="images/svgviewerBrowsing.png"></p>
<p>Squiggle offers multiple features to help you browse SVG files:</p>
<p>Navigating between files
:
diff --git a/output/batik/tools/rasterizer.html b/output/batik/tools/rasterizer.html
index 2f925cf1..22e56889 100644
--- a/output/batik/tools/rasterizer.html
+++ b/output/batik/tools/rasterizer.html
@@ -257,7 +257,7 @@ specifies the <a href="http://www.faqs.org/rfcs/rfc3066.html">RFC 3066</a> langu
specifies the quality of the output image, as a floating point number in the range 0 < <em>quality</em> < 1 when generating JPEG images,</p>
<p><strong><code>-indexed</code></strong> <em><code>1|2|4|8</code></em>
:
-specifies the number of bits per pixel of the output image, using an adaptive pallete, resulting in an indexed image when generating PNG images,</p>
+specifies the number of bits per pixel of the output image, using an adaptive palette, resulting in an indexed image when generating PNG images,</p>
<p><strong><code>-dpi</code></strong> <em><code>resolution</code></em>
:
specifies the resolution of the output image in dots per inch,</p>
diff --git a/output/batik/using/architecture.html b/output/batik/using/architecture.html
index 8fc73515..8d267513 100644
--- a/output/batik/using/architecture.html
+++ b/output/batik/using/architecture.html
@@ -218,7 +218,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>The <strong>Bridge</strong> module is rarely used directly. It is responsible for creating and maintaining an appropriate object corresponding to an SVG element. The bridge converts an SVG document into the internal representation Batik uses for graphics (GVT, the Graphic Vector Toolkit).</p>
</li>
<li>
-<p>The <a href="../using/transcoder.html">transcoder</a> is a module that provides a generic API for transcoding an input to an output. This module transcodes an input stream or a document into a particular ouput format, used for converting SVG documents to other types.</p>
+<p>The <a href="../using/transcoder.html">transcoder</a> is a module that provides a generic API for transcoding an input to an output. This module transcodes an input stream or a document into a particular output format, used for converting SVG documents to other types.</p>
</li>
</ul>
<h2 id="lowLevelComponents">Low level modules</h2>
diff --git a/output/batik/using/dom-api.html b/output/batik/using/dom-api.html
index a3320ffb..0aea119f 100644
--- a/output/batik/using/dom-api.html
+++ b/output/batik/using/dom-api.html
@@ -273,10 +273,10 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>Batik provides several ways to use an SVG DOM tree. Two modules can be immediately used to render your SVG document.</p>
<p>JSVGCanvas
:
-The <a href="../javadoc/org/apache/batik/swing/JSVGCanvas.html">JSVGCanvas</a> is a Swing component that can display SVG document. A SVG document can be specified using a URI or an SVG DOM tree (using the <a href="../javadoc/org/apache/batik/swing/JSVGCanvas.html#setSVGDocument(Document)">setSVGDocument</a> method). For futher information about the <code>JSVGCanvas</code>, see the <a href="../using/swing.html">Swing components module documentation</a>.</p>
+The <a href="../javadoc/org/apache/batik/swing/JSVGCanvas.html">JSVGCanvas</a> is a Swing component that can display SVG document. A SVG document can be specified using a URI or an SVG DOM tree (using the <a href="../javadoc/org/apache/batik/swing/JSVGCanvas.html#setSVGDocument(Document)">setSVGDocument</a> method). For further information about the <code>JSVGCanvas</code>, see the <a href="../using/swing.html">Swing components module documentation</a>.</p>
<dl>
<dt>ImageTranscoder</dt>
-<dd>The <a href="../javadoc/org/apache/batik/transcoder/image/ImageTranscoder.html">ImageTranscoder</a> is a transcoder that can take a URI, an <code>InputStream</code> or an SVG DOM tree and produces a raster image (such JPEG, PNG or TIFF). By creating a <a href="../javadoc/org/apache/batik/transcoder/TranscoderInput.html">TranscoderInput</a> object with the SVG DOM tree, you will be able to transform your SVG content to a raster image. For futher information, see the <a href="../using/ [...]
+<dd>The <a href="../javadoc/org/apache/batik/transcoder/image/ImageTranscoder.html">ImageTranscoder</a> is a transcoder that can take a URI, an <code>InputStream</code> or an SVG DOM tree and produces a raster image (such JPEG, PNG or TIFF). By creating a <a href="../javadoc/org/apache/batik/transcoder/TranscoderInput.html">TranscoderInput</a> object with the SVG DOM tree, you will be able to transform your SVG content to a raster image. For further information, see the <a href="../using [...]
</dl>
</div>
</div>
diff --git a/output/batik/using/extending.html b/output/batik/using/extending.html
index c3cd53b8..ced987bd 100644
--- a/output/batik/using/extending.html
+++ b/output/batik/using/extending.html
@@ -204,7 +204,7 @@ If you need your elements to use a custom element subclass in the DOM tree (for
<p>Doing this gives you the opportunity to override the standard methods on DOM elements, or to provide additional methods to your DOM elements. For example, you may wish to add specialized get and set methods for attributes on your custom elements, so that they can be manipulated more easily than just using the string-based <code>getAttribute</code> and <code>setAttribute</code> methods provided by DOM Core.</p>
<p>Having your custom elements be rendered
:
-Probably the most common reason to develop custom elements is to add new rendering primitives to the SVG language. In this case you must provide an <a href="#bridgeExtension">extension to the Batik bridge</a>. The bridge extension is resposible for constructing the class(es) that will handle the rendering of the new primitive in Batik.</p>
+Probably the most common reason to develop custom elements is to add new rendering primitives to the SVG language. In this case you must provide an <a href="#bridgeExtension">extension to the Batik bridge</a>. The bridge extension is responsible for constructing the class(es) that will handle the rendering of the new primitive in Batik.</p>
<p>In most cases it will also be necessary to write a DOM extension to make the element behave like other SVG elements (most notably for support of styling).</p>
<h3 id="domExtension">Writing a Batik DOM extension</h3>
<p>The ability to extend the elements used in the SVG DOM tree allows users to provide implementations for nodes that can be used in place of Batik’s default implementation of a node. This may be done for a variety of reasons, but is most commonly done to extend the behavior of standard node calls (such as to include styling in attribute lookup), or to implement the DOM interface for an element.</p>
@@ -329,7 +329,7 @@ A <a href="../javadoc/org/apache/batik/ext/awt/image/spi/StreamRegistryEntry.htm
<p>The <code>ParsedURLData</code> class holds all the data and implements all the stream handling commands for the <code>ParsedURL</code> class. This allows <code>ParsedURLProtocolHandler</code> s to return custom subclasses for particular protocols.</p>
<h2 id="interpreters">Additional script interpreters</h2>
<p>While conforming SVG browsers need support only ECMAScript as a scripting language, Batik can support any scripting language given the right glue to connect it to the rest of the system.</p>
-<p>Script interpreters are also handled via the Service Provider Interface, The interface that needs to be implemented to expose a new interpreter to Batik is <a href="../javadoc/org/apache/batik/script/InterpreterFactory.html">InterpreterFactory</a>. This class has two methods: <code>getMimeType</code>, which returns a string that specifies what script type this intepreter handles (specifically, what the <code>type</code> attribute of <code>script</code> elements must be for them to be [...]
+<p>Script interpreters are also handled via the Service Provider Interface, The interface that needs to be implemented to expose a new interpreter to Batik is <a href="../javadoc/org/apache/batik/script/InterpreterFactory.html">InterpreterFactory</a>. This class has two methods: <code>getMimeType</code>, which returns a string that specifies what script type this interpreter handles (specifically, what the <code>type</code> attribute of <code>script</code> elements must be for them to be [...]
<p>Batik comes with implementations of <code>Interpreter</code> and <code>IntepreterFactory</code> to support TCL and Python script in SVG documents, if the Jacl and Jython distributions are installed, respectively. See the classes in the <code>org.apache.batik.script.jacl</code> and <code>org.apache.batik.script.jython</code> packages to guidance on how to implement the interpreter interfaces, and the <a href="../install.html">installation notes</a> on what jar files are needed for TCL [...]
</div>
</div>
diff --git a/output/batik/using/index.html b/output/batik/using/index.html
index a5e108d1..5fc0ed77 100644
--- a/output/batik/using/index.html
+++ b/output/batik/using/index.html
@@ -204,7 +204,7 @@ The <a href="../using/dom-api.html">DOM API</a> page explains how to use the DOM
The <a href="../using/parsers.html">Parsers</a> page describes the parser classes that can be used for parsing the microsyntaxes of SVG (such as path data and transform lists).</p>
<p>Scripting
:
-The scripting pages (<a href="../using/scripting/ecmascript.html">Scriping with ECMAScript</a>, <a href="../using/scripting/java.html">Scripting with Java</a> and <a href="../using/scripting/security.html">Security</a>) document how to programmatically manipulate SVG documents, and how script interpreters can be used and extended in Batik.</p>
+The scripting pages (<a href="../using/scripting/ecmascript.html">Scripting with ECMAScript</a>, <a href="../using/scripting/java.html">Scripting with Java</a> and <a href="../using/scripting/security.html">Security</a>) document how to programmatically manipulate SVG documents, and how script interpreters can be used and extended in Batik.</p>
<p>SVG generator
:
The <a href="../using/svg-generator.html">SVG Generator</a> page documents the <code>SVGGraphics2D</code> class, which can be used to construct SVG documents from Java2D drawing commands.</p>
diff --git a/output/batik/using/scripting/security.html b/output/batik/using/scripting/security.html
index 4c48120a..2ce13dd8 100644
--- a/output/batik/using/scripting/security.html
+++ b/output/batik/using/scripting/security.html
@@ -245,10 +245,10 @@ Batik provides the following set of <code>ScriptSecurity</code> implementations:
The script resource should not be loaded.</p>
<p>EmbededScriptSecurity
:
-The script resource will only be loaded if it is embeded in the SVG document referencing it. This means that script attributes (such as <code>onclick</code> on a <code>rect</code> element), inline <code>script</code> elements and <code>script</code> elements using a <code>data:</code> URL as its <code>xlink:href</code> attribute value will be allowed. All other script resources should not be loaded.</p>
+The script resource will only be loaded if it is embedded in the SVG document referencing it. This means that script attributes (such as <code>onclick</code> on a <code>rect</code> element), inline <code>script</code> elements and <code>script</code> elements using a <code>data:</code> URL as its <code>xlink:href</code> attribute value will be allowed. All other script resources should not be loaded.</p>
<p>DefaultScriptSecurity
:
-The script resource will only be loaded if it is embeded in the SVG document (see the description of <code>EmbededScriptSecurity</code>) or if it is coming from the same location as the document referencing the script. If the document comes from a network server, then any script coming from that server will be allowed. If the document comes from the file system, then only scripts under the same directory root as the SVG document will be allowed.</p>
+The script resource will only be loaded if it is embedded in the SVG document (see the description of <code>EmbededScriptSecurity</code>) or if it is coming from the same location as the document referencing the script. If the document comes from a network server, then any script coming from that server will be allowed. If the document comes from the file system, then only scripts under the same directory root as the SVG document will be allowed.</p>
<p>RelaxedScriptSecurity
:
Scripts from any location can be loaded.</p>
@@ -258,10 +258,10 @@ Scripts from any location can be loaded.</p>
No external references are allowed.</p>
<p>EmbededExternalResourceSecurity
:
-Only resources embeded into the file are allowed (i.e., references through the <code>data:</code> protocol).</p>
+Only resources embedded into the file are allowed (i.e., references through the <code>data:</code> protocol).</p>
<p>DefaultExternalResourceSecurity
:
-Embeded external resources (see above) and resources coming from the same location as the document referencing them are allowed.</p>
+Embedded external resources (see above) and resources coming from the same location as the document referencing them are allowed.</p>
<p>RelaxedExternalResourceSecurity
:
Resources from any location can be loaded.</p>
diff --git a/output/batik/using/swing.html b/output/batik/using/swing.html
index fed911cf..1e062bce 100644
--- a/output/batik/using/swing.html
+++ b/output/batik/using/swing.html
@@ -189,7 +189,7 @@ $(document).ready(function () {
}
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
<h1 id="batik-swing-components">Batik Swing components</h1>
-<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 a [...]
+<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 a [...]
<h2 id="creatingJSVGCanvas">Creating a JSVGCanvas</h2>
<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/">JavaBea [...]
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>).</p>
@@ -309,10 +309,10 @@ If you try this example, do not forget to set your <code>CLASSPATH</code> so tha
<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>
<p><code>SVGDocumentLoaderListener</code>
:
-The <a href="../javadoc/org/apache/batik/swing/svg/SVGDocumentLoaderListener">SVGDocumentLoaderListener</a> provides a set of methods that can be used to track <a href="../javadoc/org/apache/batik/swing/svg/SVGDocumentLoaderEvent">SVGDocumentLoaderEvent</a> events. It describes the loading phase: contructing an SVG DOM tree using an SVG file.</p>
+The <a href="../javadoc/org/apache/batik/swing/svg/SVGDocumentLoaderListener">SVGDocumentLoaderListener</a> provides a set of methods that can be used to track <a href="../javadoc/org/apache/batik/swing/svg/SVGDocumentLoaderEvent">SVGDocumentLoaderEvent</a> events. It describes the loading phase: constructing an SVG DOM tree using an SVG file.</p>
<p><code>GVTTreeBuilderListener</code>
:
-The <a href="../javadoc/org/apache/batik/swing/svg/GVTTreeBuilderListener">GVTTreeBuilderListener</a> provides a set of methods that can be used to track <a href="../javadoc/org/apache/batik/swing/svg/GVTTreeBuilderEvent">GVTTreeBuilderEvent</a> events. It describes the building phase: contructing a GVT (Graphics Vector Toolkit) tree using an SVG DOM tree. The GVT tree will then be used to render the document.</p>
+The <a href="../javadoc/org/apache/batik/swing/svg/GVTTreeBuilderListener">GVTTreeBuilderListener</a> provides a set of methods that can be used to track <a href="../javadoc/org/apache/batik/swing/svg/GVTTreeBuilderEvent">GVTTreeBuilderEvent</a> events. It describes the building phase: constructing a GVT (Graphics Vector Toolkit) tree using an SVG DOM tree. The GVT tree will then be used to render the document.</p>
<p><code>SVGLoadEventDispatcherListener</code>
:
The <a href="../javadoc/org/apache/batik/swing/svg/SVGLoadEventDispatcherListener">SVGLoadEventDispatcherListener</a> provides a set of methods that can be used to track <a href="../javadoc/org/apache/batik/swing/svg/SVGLoadEventDispatcherEvent">SVGLoadEventDispatcherEvent</a> events. It describes the DOM <code>SVGLoad</code> event dispatch phase.</p>
@@ -329,7 +329,7 @@ The <a href="../javadoc/org/apache/batik/bridge/UpdateManagerListener">UpdateMan
<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>
<h2 id="interactor">Adding an Interactor</h2>
-<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 inte [...]
+<p>The <code>JSVGCanvas</code> provides a set of built-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 inte [...]
</div>
</div>
<div class="clear"></div>
diff --git a/output/batik/using/transcoder.html b/output/batik/using/transcoder.html
index 94ca7ea6..464287ba 100644
--- a/output/batik/using/transcoder.html
+++ b/output/batik/using/transcoder.html
@@ -272,7 +272,7 @@ The <a href="../javadoc/org/apache/batik/transcoder/ErrorHandler.html">ErrorHand
<div class="highlight"><pre><span></span><code><span class="n">t</span><span class="p">.</span><span class="na">addTranscodingHint</span><span class="p">(</span><span class="n">JPEGTranscoder</span><span class="p">.</span><span class="na">KEY_WIDTH</span><span class="p">,</span> <span class="k">new</span> <span class="n">Float</span><span class="p">(</span><span class="mi">100</span><span class="p">));</span>
</code></pre></div>
-<p>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>
+<p>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 aspect ratio of the SVG document.</p>
<h3 id="selectAreaOfIntrest">Selecting an area of interest</h3>
<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.</p>
<div class="highlight"><pre><span></span><code><span class="kn">import</span> <span class="nn">java.io.*</span><span class="p">;</span>
diff --git a/output/commons/changes.html b/output/commons/changes.html
index a1e164e9..a53a6138 100644
--- a/output/commons/changes.html
+++ b/output/commons/changes.html
@@ -242,7 +242,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<li><img alt="fix" src="/images/fix.jpg"> Fix performancy penalty caused by excessive DeflaterOutputStream.write(byte) calls, thanks to Andre Klemann</li>
<li><img alt="fix" src="/images/fix.jpg"> Include ps-setpagedevice when dsc-compliant is false</li>
<li><img alt="fix" src="/images/fix.jpg"> UndeclaredThrowableException while loading images</li>
-<li><img alt="update" src="/images/update.jpg"> Add PreloaderRawPNG to handle images ImageIO cant</li>
+<li><img alt="update" src="/images/update.jpg"> Add PreloaderRawPNG to handle images ImageIO can't</li>
<li><img alt="update" src="/images/update.jpg"> Add support for PDF/A-3</li>
<li><img alt="update" src="/images/update.jpg"> Support CMYK JPEG in AFP</li>
<li><img alt="update" src="/images/update.jpg"> Support PDF/UA</li>
@@ -324,7 +324,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p><img alt="fix" src="/images/fix.jpg">Fixes gradient fill opacity incorrectly inherits stroke opacity of previous svg element. Committed by LB. </p>
</li>
<li>
-<p><img alt="add" src="/images/fix.jpg">Little endian support for tiff images. Commited by LB. Thanks to JM and RM. See Issue
+<p><img alt="add" src="/images/fix.jpg">Little endian support for tiff images. Committed by LB. Thanks to JM and RM. See Issue
[54195] (https://issues.apache.org/bugzilla/show_bug.cgi?id=54196)</p>
</li>
<li>
@@ -582,7 +582,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p><img alt="fix" src="/images/fix.jpg">Fixed two cases of unclosed input streams in image loader code. Committed by JM.</p>
</li>
<li>
-<p><img alt="fix" src="/images/fix.jpg">Bugfix for unhandled NumberFormatException in Glpyhs when a unknown glyph name starting with "u" is found. Committed by JM.</p>
+<p><img alt="fix" src="/images/fix.jpg">Bugfix for unhandled NumberFormatException in Glyphs when a unknown glyph name starting with "u" is found. Committed by JM.</p>
</li>
<li>
<p><img alt="fix" src="/images/fix.jpg">Bugfix for ImageEncodingHelper which produced false results if an image's sample model used BGR instead of RGB. Committed by JM.</p>
diff --git a/output/commons/image-loader.html b/output/commons/image-loader.html
index 794346a1..c4a04d1c 100644
--- a/output/commons/image-loader.html
+++ b/output/commons/image-loader.html
@@ -304,7 +304,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>Normally, if you implement an <code>ImagePreloader</code> you will also need to implement the respective <code>ImageLoader/ImageLoaderFactory</code>, or vice versa.</p>
</blockquote>
<h2 id="ImageLoader">ImageLoader and ImageLoaderFactory</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 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 functional. 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 recommended, 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>
<h3 id="ImageConverter">ImageConverter</h3>
diff --git a/output/fop/changes.html b/output/fop/changes.html
index 1b0a0d35..7706e4ce 100644
--- a/output/fop/changes.html
+++ b/output/fop/changes.html
@@ -1932,7 +1932,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>FOP-2326: CMYK TIFF is rendered using RGB colourspace in Postscript output; patch submitted by Simon Steiner (xgc jar updated)</p>
</li>
<li>
-<p>FOP-2323: NPE caused by missing local subroutine index in private dictonary of OTF font</p>
+<p>FOP-2323: NPE caused by missing local subroutine index in private dictionary of OTF font</p>
</li>
<li>
<p>FOP-2322: Type1 Font with Custom Encoding not visible in Postscript output; Patch submitted by Simon Steiner</p>
@@ -2430,7 +2430,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p><img alt="fix" src="/images/fix.jpg"> Restore lookup on Event message lookup field part. Add locale field to Event to enable locale dependent deferred bundle load during lookup field part substitution. Committed by GA. See issue <a href="https://issues.apache.org/jira/browse/FOP-2040">FOP-2040</a>.</p>
</li>
<li>
-<p><img alt="fix" src="/images/fix.jpg"> Bug in AFP font metrics that performed integer arithmetic when it should have been double arithemetic. Committed by MH.</p>
+<p><img alt="fix" src="/images/fix.jpg"> Bug in AFP font metrics that performed integer arithmetic when it should have been double arithmetic. Committed by MH.</p>
</li>
<li>
<p><img alt="fix" src="/images/fix.jpg"> Bring clone() in line with the recommendations in Object.clone(). Committed by GA. Thanks to Simon Pepping. See issue <a href="https://issues.apache.org/jira/browse/FOP-1836">FOP-1836</a>.</p>
@@ -2598,7 +2598,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p><img alt="fix" src="/images/fix.jpg"> Fix incorrect SVG line dash pattern with PDF output format. Committed by GA. Thanks to Luis Bernardo. See issue <a href="https://issues.apache.org/jira/browse/FOP-2079">FOP-2079</a>.</p>
</li>
<li>
-<p><img alt="fix" src="/images/fix.jpg"> Support use of ImageLoaderRawPNG decoder in order to prevent re-encoding of PNG images (and unnecssary output file bloat). Committed by GA. Thanks to Luis Bernardo, Matthias Reischenbacher. See issue <a href="https://issues.apache.org/jira/browse/FOP-1256">FOP-1256</a>.</p>
+<p><img alt="fix" src="/images/fix.jpg"> Support use of ImageLoaderRawPNG decoder in order to prevent re-encoding of PNG images (and unnecessary output file bloat). Committed by GA. Thanks to Luis Bernardo, Matthias Reischenbacher. See issue <a href="https://issues.apache.org/jira/browse/FOP-1256">FOP-1256</a>.</p>
</li>
<li>
<p><img alt="update" src="/images/update.jpg"> Fix interoperability issue with Adobe reader regarding use of multiple filters. Committed by GA. Thanks to Luis Bernardo. See issue <a href="https://issues.apache.org/jira/browse/FOP-1256">FOP-1256</a>.</p>
@@ -2724,7 +2724,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p><img alt="fix" src="/images/fix.jpg"> Fix invalid PostScript file being created when font-size is 0. Committed by GA. Thanks to Robert Meyer. See issue <a href="https://issues.apache.org/jira/browse/FOP-2068">FOP-2068</a>.</p>
</li>
<li>
-<p><img alt="fix" src="/images/fix.jpg"> Stop outputting the Type entry for structure elements in order to create a smaller PDF ouptut when accessibility is enabled. Committed by VH. Thanks to Martin Koegler.</p>
+<p><img alt="fix" src="/images/fix.jpg"> Stop outputting the Type entry for structure elements in order to create a smaller PDF output when accessibility is enabled. Committed by VH. Thanks to Martin Koegler.</p>
</li>
<li>
<p><img alt="fix" src="/images/fix.jpg"> Support fractional line widths in AFP renderer, fixing problem with SVG line drawing. Committed by GA. Thanks to Luis Bernardo. See issue <a href="https://issues.apache.org/jira/browse/FOP-2063">FOP-2063</a>.</p>
@@ -2742,7 +2742,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p><img alt="fix" src="/images/fix.jpg"> Take leading derived space before/after into account when computing rows for TXT renderer. Committed by GA. See issue <a href="https://issues.apache.org/jira/browse/FOP-1985">FOP-1985</a>.</p>
</li>
<li>
-<p><img alt="fix" src="/images/fix.jpg"> Improved fix of a bug relating to PCL painter thread safetly. Previous fix in rev 895012 worked by synchronizing methods of a static instance of Java2DFontMetrics. This fix uses a unique instance for per thread. Committed by PH. See issue <a href="https://issues.apache.org/jira/browse/FOP-1718">FOP-1718</a>.</p>
+<p><img alt="fix" src="/images/fix.jpg"> Improved fix of a bug relating to PCL painter thread safely. Previous fix in rev 895012 worked by synchronizing methods of a static instance of Java2DFontMetrics. This fix uses a unique instance for per thread. Committed by PH. See issue <a href="https://issues.apache.org/jira/browse/FOP-1718">FOP-1718</a>.</p>
</li>
<li>
<p><img alt="fix" src="/images/fix.jpg"> Fixed a bug in AFP where an ArrayOutofBoundsException is throwqn when embedding a Page Segment. Committed by PH.</p>
@@ -3561,7 +3561,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p><img alt="add" src="/images/add.jpg"> 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>
</li>
<li>
-<p><img alt="add" src="/images/add.jpg"> Added support for the natural language indentifier ("Lang" in the document catalog) for PDF documents based on the language/country values on fo:page-sequence. Committed by JM.</p>
+<p><img alt="add" src="/images/add.jpg"> Added support for the natural language identifier ("Lang" in the document catalog) for PDF documents based on the language/country values on fo:page-sequence. Committed by JM.</p>
</li>
<li>
<p><img alt="add" src="/images/add.jpg"> PostScript output now generates the bounding box DSC comments for the whole document. Committed by JM.</p>
@@ -3688,7 +3688,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p><img alt="fix" src="/images/fix.jpg"> Fixed a problem with disappearing footnotes inside hyphenated inlines (and footnotes with hyphenated inline child). Committed by LF.</p>
</li>
<li>
-<p><img alt="fix" src="/images/fix.jpg"> Fix PDF Genaration for non-ASCII compatible locales. Committed by JM. Thanks to Martin Kögler. See issue <a href="https://issues.apache.org/jira/browse/FOP-1294">FOP-1294</a>.</p>
+<p><img alt="fix" src="/images/fix.jpg"> Fix PDF Generation for non-ASCII compatible locales. Committed by JM. Thanks to Martin Kögler. See issue <a href="https://issues.apache.org/jira/browse/FOP-1294">FOP-1294</a>.</p>
</li>
<li>
<p><img alt="fix" src="/images/fix.jpg"> Fix several exceptions when break-before/after is set on the first/last row of a table. Committed by VH.</p>
@@ -3981,7 +3981,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p><img alt="add" src="/images/add.jpg"> Added support for RFC2397 "data" URLs. Committed by JM. Thanks to Richard Wheeldon. See issue <a href="https://issues.apache.org/jira/browse/FOP-1125">FOP-1125</a>.</p>
</li>
<li>
-<p><img alt="add" src="/images/add.jpg"> The font loading code now reads the encoding value from the XML font metrics file so that fonts like Symbol and ZapfDingbats can be embedded explicitely (Required by PDF/A). Committed by JM.</p>
+<p><img alt="add" src="/images/add.jpg"> The font loading code now reads the encoding value from the XML font metrics file so that fonts like Symbol and ZapfDingbats can be embedded explicitly (Required by PDF/A). Committed by JM.</p>
</li>
<li>
<p><img alt="add" src="/images/add.jpg"> Added feature: support for white-space shorthand Committed by AD.</p>
@@ -4141,7 +4141,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p><img alt="fix" src="/images/fix.jpg"> Changed the way resolutions are handled. The single resolution in the user agent got split up into source and target resolutions. For more info, see the updated documentation. Note: backwards-incompatible change! Committed by JM.</p>
</li>
<li>
-<p><img alt="fix" src="/images/fix.jpg"> Bugfix: Some content inside a table-header may not have been renderered on pages n > 1 in certain conditions. Committed by JM. See issue <a href="https://issues.apache.org/jira/browse/FOP-1109">FOP-1109</a>..</p>
+<p><img alt="fix" src="/images/fix.jpg"> Bugfix: Some content inside a table-header may not have been rendered on pages n > 1 in certain conditions. Committed by JM. See issue <a href="https://issues.apache.org/jira/browse/FOP-1109">FOP-1109</a>..</p>
</li>
<li>
<p><img alt="fix" src="/images/fix.jpg"> Fixed a bug where an empty line, i.e. a block containing only a , was not rendered at all. Committed by MM.</p>
diff --git a/output/fop/dev/design/areas.html b/output/fop/dev/design/areas.html
index 3fe98f61..06d1f5d0 100644
--- a/output/fop/dev/design/areas.html
+++ b/output/fop/dev/design/areas.html
@@ -1794,20 +1794,20 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p><authors><person email="keiron@aftexsw.com" name="Keiron Liddle"></person></authors></p>
<h2 id="intro">Introduction</h2>
<p>The Area Tree is an internal representation of the result document, representing pages and their contents. To make the concepts clearer and easier to understand, the code to implement the area tree matches the areas defined in the XSL-FO specification.</p>
-<p>The area tree is created by the layout managers once the layout is decided for a page. Once a completed page is finished it can then be added to the area tree. From that point forward, the area tree model can then handle the new page. The data in the area tree must be minimal and independant. This means that the data uses less memory and can be serialized to an output stream if needed.</p>
-<p>The Area Tree consists of a set of pages, which the actual implemenation places in a set of page sequences.</p>
+<p>The area tree is created by the layout managers once the layout is decided for a page. Once a completed page is finished it can then be added to the area tree. From that point forward, the area tree model can then handle the new page. The data in the area tree must be minimal and independent. This means that the data uses less memory and can be serialized to an output stream if needed.</p>
+<p>The Area Tree consists of a set of pages, which the actual implementation places in a set of page sequences.</p>
<h2 id="structure">Structure</h2>
<p>The area tree is a root element that has a list of page-viewport-areas. Each page viewport has a page-reference-area which holds the contents of the page. To handle the processing better FOP does not maintain a list at the root level but lets the area tree model handle each page as it is added.</p>
<h2 id="page">Page</h2>
<p>A page consists of a page+viewport pair.</p>
<p>The PageViewPort and Page with the regions is created by the LayoutMasterSet. The contents are then placed by the layout managers. Once the layout of a page is complete then it is added to the Area Tree.</p>
<p>Inside the page is a set of RegionViewport+Region pairs for each region on the page.</p>
-<p>A page is made up of five area regions. These are before, start, body, end and after. Each region has a viewport and contains the areas produced from the children in the FO object heirarchy.</p>
+<p>A page is made up of five area regions. These are before, start, body, end and after. Each region has a viewport and contains the areas produced from the children in the FO object hierarchy.</p>
<p>For the body area there are more subdivisions for before floats, footnotes and the main reference area. The main reference area is made from span areas which have normal flow reference areas as children. The flow areas are then created inside these normal flow reference areas.</p>
-<p>Since the layout is done inside a page, the page is created from the pagemaster with all the appropriate areas. The layout manager then uses the page to add areas into the normal flow reference areas and floats and footnotes. After adding the areas for the body region then the other regions can be done layed out and added.</p>
+<p>Since the layout is done inside a page, the page is created from the pagemaster with all the appropriate areas. The layout manager then uses the page to add areas into the normal flow reference areas and floats and footnotes. After adding the areas for the body region then the other regions can be done laid out and added.</p>
<h2 id="block">Block Areas</h2>
<p>Block level areas contain either other blocks or line areas (which is a special block area).</p>
-<p>A block is either positoned or stacked with other block areas.</p>
+<p>A block is either positioned or stacked with other block areas.</p>
<p>Block areas are created and/or returned by all top level elements in the flow. The spacing between block areas is handled by an empty block area. A block area is stacked with other block areas in a particular direction, it has a size and it contains line areas made from a group of inline areas and/or block areas.</p>
<h2 id="line-area">Line Areas</h2>
<p>A line areas is simply a collection of inline areas that are stacked in the inline progression direction. A line area has a height and a start position. The line area is rendered by handling each inline area.</p>
@@ -1836,7 +1836,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<h2 id="forward-references">Forward References</h2>
<p>The Area Tree maintains a set of mappings from the reference to pages.</p>
<p>The PageViewPort holds the list of forward references that need resolving so that if a references is resolved during layout the page can be easily found and then fixed. Once all the forward references are resolved then the page is ready to be rendered.</p>
-<p>To layout a page any areas that cannot be resolved need to reserve space. Once the inline area is resolved then the complete line should be adjusted to accomodate any change in space used by the area.</p>
+<p>To layout a page any areas that cannot be resolved need to reserve space. Once the inline area is resolved then the complete line should be adjusted to accommodate any change in space used by the area.</p>
<h2 id="caching">Caching</h2>
<p>We may need to cache pages due to forward references or when keeping all pages.</p>
<p>This is done by serializing the Page. The PageViewport is retained to be used as a key for page references and backward references. The Page is serialized to an object stream and then all of the page contents are released. The Page is then recoved by reading from the object stream.</p>
diff --git a/output/fop/dev/design/breakpos.html b/output/fop/dev/design/breakpos.html
index a5077df3..7130a679 100644
--- a/output/fop/dev/design/breakpos.html
+++ b/output/fop/dev/design/breakpos.html
@@ -1801,7 +1801,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>Once break possibilities have been generated, the galley-level layout manager selects the best one and passes it back to the LayoutManager which generated it to create the area. A LayoutManager is responsible for storing enough information in its Position objects to be able to create the corresponding areas.</p>
<h2 id="A-walk-through">A walk-through</h2>
<p>Layout Managers are created from the top down. First the page sequence creates a PageLM and a FlowLM. The PageLM will manage finding the right page model (with help from the PageSequenceMaster) and managing the balancing act between before-floats, footnotes and the normal text flow. The FlowLM will manage the normal content in the main flow. We can think of it as a <em>galley</em> manager.</p>
-<p>In general, each LM asks its child LMs to return sucessive break possibilities. It passes some information to the child in a flags object and it gets back a break possibility which contains the size in the stacking direction as well as information about such things as anchors, break conditions and span conditions which can change the reference area environment. This process continues down to the lowest level of the layout manager hierarchy which corresponds to atomic inline-level FOs [...]
+<p>In general, each LM asks its child LMs to return successive break possibilities. It passes some information to the child in a flags object and it gets back a break possibility which contains the size in the stacking direction as well as information about such things as anchors, break conditions and span conditions which can change the reference area environment. This process continues down to the lowest level of the layout manager hierarchy which corresponds to atomic inline-level FOs [...]
<p>Each layout manager will repeatedly call getNextBreakPoss on its current child LM until the child returns a BP with the ISLAST flag set. Then the layout manager moves on to its next child LM (ie, it asks the next child FO to generate a layout manager.) Galley level layout managers which are Line and Flow will return to their parent layout managers either when they have finished their content or when they encounter a a BP which will fill one of their areas.</p>
<p>The break possibilities are generated from the bottom up. All inline content must first be broken into lines which are then stacked into block areas. This is done by the LineLayoutManager, which creates line areas. The LineLM asks its child LM to generate a break possibility, which represents a place where the line can end. This initially means each potential line-end (primarily spaces or forced linefeeds and a few other potential line-end characters such as hard hyphens.) The text LM [...]
<p>Variable size content is taken into account from the bottom up. Each LM returns a range of sizes in the stacking direction, based on property values. For text, this comes from variable word-space values or letter-space values. For other inline objects, it may include variable space-start and space-end values (after calculation of the entire sequence of space specifiers at a particular break possibility.)</p>
diff --git a/output/fop/dev/design/embedding.html b/output/fop/dev/design/embedding.html
index 150dfd70..ac792b4f 100644
--- a/output/fop/dev/design/embedding.html
+++ b/output/fop/dev/design/embedding.html
@@ -1800,7 +1800,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>Possible meanings for a user agent:</p>
<ul>
<li>
-<p>something that makes decisions where the specifiction indicates that the user agent should decide</p>
+<p>something that makes decisions where the specification indicates that the user agent should decide</p>
</li>
<li>
<p>FOP as the user agent, represented by a class that handles various setup and decision values</p>
@@ -1889,7 +1889,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<h3 id="Setting-Up">Setting Up</h3>
<p>The Driver handles the XML input. The user agent information is through the FOUserAgent. Handle logging through the user agent. Options could also be handled through the user agent, using mime type selection for renderer options.</p>
<h3 id="Others">Others</h3>
-<p>Render to more than one renderer at once (maybe not from the command line). For example you could generate a PDF for the archive and the PS for the printer in one run. It would probably be faster than converting the PDF to PostScript afterwards. Make the fo tree reuseable. If the fonts are the same then use the same area tree to output to different renderers.</p>
+<p>Render to more than one renderer at once (maybe not from the command line). For example you could generate a PDF for the archive and the PS for the printer in one run. It would probably be faster than converting the PDF to PostScript afterwards. Make the fo tree reusable. If the fonts are the same then use the same area tree to output to different renderers.</p>
<p>Several code pieces for resolving URLs and/or file locations are scattered all over FOP and Batik. These should be replaced with an URIResolver invocation to unify behaviour and remove redundancies.</p>
</div>
</div>
diff --git a/output/fop/dev/design/extending.html b/output/fop/dev/design/extending.html
index 50e7972a..fd02ca26 100644
--- a/output/fop/dev/design/extending.html
+++ b/output/fop/dev/design/extending.html
@@ -1797,7 +1797,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<h2 id="Extensions">Extensions</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 oth [...]
+<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 passes 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 ot [...]
<p>FO Area - This is where an extension creates an normal or extended area in the Area Tree. This is useful when the normal FO objects cannot create the area in the way that is needed.</p>
<p>Resolveable - In some cases it may require information to be resolved for information such as page numbers. This can apply to the XML Document, FO Area or output document extensions.</p>
<ul>
diff --git a/output/fop/dev/design/layout.html b/output/fop/dev/design/layout.html
index b0c2117d..a351b7a4 100644
--- a/output/fop/dev/design/layout.html
+++ b/output/fop/dev/design/layout.html
@@ -1809,7 +1809,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>The issue here is that we wish to recycle the Area Tree memory as much as possible. The problem is that forward references prevent pages from being resolved until the forward references are resolved. If memory is insufficient to store unresolved pages, Area Tree fragments must be serialized until resolved.</p>
<p>FOP developers have discussed adding the capability of using an Area Tree to render to more than one output target in the same run, which would be a complicating factor in disposal of pages as they are rendered.</p>
<h2 id="lm">Layout Managers</h2>
-<p>The layout managers are set up from the hierarchy of the formatting object tree. A manager represents a hierachy of area producing objects. A manager is able to handle the block area(s) that it creates and organise or split areas for page breaks.</p>
+<p>The layout managers are set up from the hierarchy of the formatting object tree. A manager represents a hierarchy of area producing objects. A manager is able to handle the block area(s) that it creates and organise or split areas for page breaks.</p>
<p>Normally any object that creates a block area will have an associated layout manager. Other cases are tables and lists, these objects will also have layout managers that will manager the group of layout managers that make up the object.</p>
<p>A layout manager is also able to determine height (min/max/optimum) and keep status. This will be used when organising the layout on a page. The manager will be able to determine the next place a break can be made and then be able to organise the height.</p>
<p>A layout manager is essentially a bridge between the formatting objects and the area tree. It will keep a list of line areas inside block areas. Each line area will contain a list of inline areas that is able to be adjusted if the need arises.</p>
@@ -1840,16 +1840,16 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>Once the areas for the page are finalised then the spacing will need to be adjusted. The available height on the page is compared with the min and max spacing. All of the spacing in all the areas on the page is then adjusted by the appropriate percentage value.</p>
<h2 id="multi-column">Multi-Column Pages</h2>
<p>In the case of multi-column pages the column breaks and eventually the page break must be found in a slightly different way.</p>
-<p>The columns need to be layed out completely from first to last but this can only be done after a rough estimate of all the elements on the page in case of before floats or footnotes.</p>
-<p>So first the complete page is layed out with all columns filled with areas and the spacing at a minimum. Then if there are any before floats or footnotes then the availabe space is adjusted. Then each the best break is found for each column starting from the first column. If any before floats or footnotes are removed as a result of the new breaks and optimised spacing then all the columns should still be layed out for the same column height.</p>
+<p>The columns need to be laid out completely from first to last but this can only be done after a rough estimate of all the elements on the page in case of before floats or footnotes.</p>
+<p>So first the complete page is laid out with all columns filled with areas and the spacing at a minimum. Then if there are any before floats or footnotes then the available space is adjusted. Then each the best break is found for each column starting from the first column. If any before floats or footnotes are removed as a result of the new breaks and optimised spacing then all the columns should still be laid out for the same column height.</p>
<h2 id="page-complete">Completing Page</h2>
-<p>After the region body has been finished the static areas can be layed out. The width of the static area is set and the height is inifinite, that is all block areas should be placed in the area and their visibility is controlled be other factors.</p>
+<p>After the region body has been finished the static areas can be laid out. The width of the static area is set and the height is infinite, that is all block areas should be placed in the area and their visibility is controlled be other factors.</p>
<p>The area tree for the region body will contain the information about markers that may be necessary for the retrieve marker.</p>
<p>The ordering of the area tree must be adjusted so that the areas are before, start, body, end and after in that order. The body region should be in the order before float, main then footnote.</p>
<h2 id="line-area">Line Areas</h2>
-<p>Creating a line areas uses a similair concept. Each inline area is placed across the available space until there is no room left. The line is then split by considering all keeps and spacing.</p>
+<p>Creating a line areas uses a similar concept. Each inline area is placed across the available space until there is no room left. The line is then split by considering all keeps and spacing.</p>
<p>Each word (group of adjacent character inline areas) will have keeps based on hyphenation. The line break is at the lowest keep value starting from the end of the line.</p>
-<p>Once a line has been layed out for a particular width then that line is fixed for the page (except for unresolved page references).</p>
+<p>Once a line has been laid out for a particular width then that line is fixed for the page (except for unresolved page references).</p>
<h2 id="before-float-footnote">Before Floats and Footnotes</h2>
<p>The before float region and footnote region are handled by the page layoutmanger. These regions will handle the addition and removal of the separator regions when before floats/footnotes area added and removed.</p>
<p>Footnotes and Before Floats are placed in special areas in the body region of the page. The size of these areas is determined by the content. This in turn effects the available size of the main reference area that contains the flow.</p>
@@ -1860,10 +1860,10 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>This means that the float needs to be handled by the block layout manager so that it can adjust the available inline progression dimension for the relevant line areas.</p>
<h2 id="unresolved-area">Unresolved Areas</h2>
<p>Once the layout of the page is complete there may be unresolved areas.</p>
-<p>Page number citations and links may require following pages to be layed out before they can be resolved. These will remain in the area tree as unresolved areas.</p>
+<p>Page number citations and links may require following pages to be laid out before they can be resolved. These will remain in the area tree as unresolved areas.</p>
<p>As each page is completed the list of unresolved id's will be checked and if the id can be resolved it will be. Once all id's are resolved then the page can be rendered.</p>
<p>Each page contains a map of all unresolved id's and the corresponding areas.</p>
-<p>In the case of page number citations, the areas reserves the equivalent of 3 number nines in the current font. When the area is resolved then the area is adjusted to its proper size and the line area is re-aligned to accomodate the change.</p>
+<p>In the case of page number citations, the areas reserves the equivalent of 3 number nines in the current font. When the area is resolved then the area is adjusted to its proper size and the line area is re-aligned to accommodate the change.</p>
<h2 id="id-link-area">ID and Link Areas</h2>
<p>Any formatting object that has an ID or any inline link defines an area that will be required when rendering and resolving id references.</p>
<p>This area is stored in the parent area and may be a shape that exists in more than one page, for example over a page break. This shape consists of the boundary of all inline (or block) areas that the shape is defined for.</p>
@@ -1912,8 +1912,8 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
</ul>
<p>Once the layout has been finalised then this information can be discarded.</p>
<h2 id="page-area">Page Areas</h2>
-<p>Contains inforamtion about all the block areas in the body, before area and footer area.</p>
-<p>Has a list of the unresolved page references and a list of id refences that can be used to obtain the area associated with that id.</p>
+<p>Contains information about all the block areas in the body, before area and footer area.</p>
+<p>Has a list of the unresolved page references and a list of id references that can be used to obtain the area associated with that id.</p>
<h2 id="test-cases">Test Cases</h2>
<p>Here a few layout possibilities areas explored to determine how the layout process will handle these situations.</p>
<h3 id="test-simple">Simple Pages</h3>
@@ -1921,7 +1921,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<h3 id="test-before-float-footnote">Before Floats/Footnotes</h3>
<p>After filling the page with the block areas then the new body height is used to find the best position to break. Before each line area or block area is remove any associated before floats and footnotes are removed. This will then adjust the available space on the page and may allow for a different breaking point. Areas are removed towards the new breaking point until the areas fit on the page. When finding the optimum spacing the removal of before floats and footnotes must also be ons [...]
<h3 id="test-multi-column">Multicolumn</h3>
-<p>First the page is filled with all columns for the intial page area. Then each column is adjusted for the new height starting from the first column. The best break for the column is found then the next column is considered, any left over areas a pre-pended to the next column. Once all the columns are finished then all the columns are adjusted to fit in the same height columns. This handles the situation where before floats or footnotes may have been removed.</p>
+<p>First the page is filled with all columns for the initial page area. Then each column is adjusted for the new height starting from the first column. The best break for the column is found then the next column is considered, any left over areas a pre-pended to the next column. Once all the columns are finished then all the columns are adjusted to fit in the same height columns. This handles the situation where before floats or footnotes may have been removed.</p>
<h3 id="test-last-page">Last Page</h3>
<p>If in the process of adding areas to a page it is found that there are no more areas in the flow then this page will need to be changed to the last page (if applicable). The areas are then placed on a last page.</p>
<h2 id="status">Status</h2>
@@ -1986,7 +1986,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<td></td>
</tr>
<tr>
-<td>Fine-tuning line breaking and hypenation</td>
+<td>Fine-tuning line breaking and hyphenation</td>
<td>Medium</td>
<td></td>
</tr>
@@ -2008,12 +2008,12 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<tr>
<td>Border collapsing on tables</td>
<td>Low</td>
-<td>RenderX hasnt implemented this (17/03/04)</td>
+<td>RenderX hasn't implemented this (17/03/04)</td>
</tr>
<tr>
<td>Fine-tuning all other borders</td>
<td>Low</td>
-<td>Not sure what Joerg means by this, border collapse priorties? Dashed and dotted borders have been implemented in PDF</td>
+<td>Not sure what Joerg means by this, border collapse priorities? Dashed and dotted borders have been implemented in PDF</td>
</tr>
<tr>
<td>BIDI support</td>
diff --git a/output/fop/dev/design/optimise.html b/output/fop/dev/design/optimise.html
index 30ecbfdc..9ddc28af 100644
--- a/output/fop/dev/design/optimise.html
+++ b/output/fop/dev/design/optimise.html
@@ -1797,7 +1797,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>A top level block area, immediately below the flow, can be added to the page layout as soon as the element is complete.</p>
<p>The fo elements used to construct a page can be discarded as soon as the layout for the page is complete. Some information may be stored in the area tree of the page in order to handle unresolved page references and links.</p>
<p>Once the layout of a page has been completed, all elements are fully resolved, then the page can be rendered. Some renderers may support out of order rendering of pages.</p>
-<p>The main problem that will remain is that any page with forward references will need to be stored until the refence is resolved. This means that the information contained in the page should be as minimal as possible.</p>
+<p>The main problem that will remain is that any page with forward references will need to be stored until the reference is resolved. This means that the information contained in the page should be as minimal as possible.</p>
<p>Line areas can be optimised once the layout for the line has been finalised. Consecutive characters with the same properties can be combined into a "word" to hold the information with limited overhead.</p>
<p>If there are a large number of pages where forward references cannot be resolved the a method of writing a page onto disk could be used to save memory. The easiest way to achieve this is to make the page and all children serializable.</p>
</div>
diff --git a/output/fop/dev/design/pdf-library.html b/output/fop/dev/design/pdf-library.html
index 12faedb3..a070aae4 100644
--- a/output/fop/dev/design/pdf-library.html
+++ b/output/fop/dev/design/pdf-library.html
@@ -1792,7 +1792,7 @@ $(document).ready(function () {
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
<h1 id="apache-fop-design-pdf-library">Apache™ FOP Design: PDF Library</h1>
<h2 id="intro">Introduction</h2>
-<p>The PDF Library is an independant package of classes in Apache™ FOP. These class provide a simple way to construct documents and add the contents. The classes are found in <code>org.apache.fop.pdf.*</code>.</p>
+<p>The PDF Library is an independent package of classes in Apache™ FOP. These class provide a simple way to construct documents and add the contents. The classes are found in <code>org.apache.fop.pdf.*</code>.</p>
<h2 id="PDF-Document">PDF Document</h2>
<p>This is where most of the document is created and put together.</p>
<p>It sets up the header, trailer and resources. Each page is made and added to the document. There are a number of methods that can be used to create/add certain PDF objects to the document.</p>
@@ -1814,7 +1814,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>A pdf link can be added for an area on the page. This link can then point to an external destination or a position on any page in the document.</p>
<h3 id="Patterns">Patterns</h3>
<p>The fill and stroke of graphical objects can be set with a colour, pattern or gradient.</p>
-<p>The are a number of other features for handling pdf markup relevent to creating PDF files for FOP.</p>
+<p>The are a number of other features for handling pdf markup relevant to creating PDF files for FOP.</p>
</div>
</div>
<div class="clear"></div>
diff --git a/output/fop/dev/design/properties.html b/output/fop/dev/design/properties.html
index c04e3a3a..f352800d 100644
--- a/output/fop/dev/design/properties.html
+++ b/output/fop/dev/design/properties.html
@@ -1872,7 +1872,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<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>If the returned Property value is of the correct type (specified 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="property-list-struct">Structure of the PropertyList</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>
diff --git a/output/fop/dev/design/renderers.html b/output/fop/dev/design/renderers.html
index 261a1911..fc22017d 100644
--- a/output/fop/dev/design/renderers.html
+++ b/output/fop/dev/design/renderers.html
@@ -1796,7 +1796,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>A renderer is primarily designed to convert a given area tree into the output document format. It should be able to produce pages and fill the pages with the text and graphical content. Usually the output is sent to an output stream.</p>
<p>Some output formats may support extra information that is not available from the area tree or depends on the destination of the document.</p>
<p>Each renderer is given an area tree to render to its output format. The area tree is simply a representation of the pages and the placement of text and graphical objects on those pages.</p>
-<p>The renderer will be given each page as it is ready and an output stream to write the data out. All pages are supplied in the order they appear in the document. In order to save memory it is possble to render the pages out of order. Any page that is not ready to be rendered is setup by the renderer first so that it can reserve a space or reference for when the page is ready to be rendered.The renderer is responsible for managing the output format and associated data and flow.</p>
+<p>The renderer will be given each page as it is ready and an output stream to write the data out. All pages are supplied in the order they appear in the document. In order to save memory it is possible to render the pages out of order. Any page that is not ready to be rendered is setup by the renderer first so that it can reserve a space or reference for when the page is ready to be rendered.The renderer is responsible for managing the output format and associated data and flow.</p>
<h2 id="issues">Design Issues</h2>
<h3 id="issue-renderers-responsible">Renderers are Responsible</h3>
<p>Each renderer is totally responsible for its output format.</p>
@@ -1804,7 +1804,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<h2 id="fonts">Fonts</h2>
<p>Because font metrics (and therefore layout) are obtained in two different ways depending on the renderer, the renderer actually sets up the fonts being used. The font metrics are used during the layout process to determine the size of characters.</p>
<h2 id="context">Render Context</h2>
-<p>The render context is used by handlers. It contains information about the current state of the renderer, such as the page, the position, and any other miscellanous objects that are required to draw into the page.</p>
+<p>The render context is used by handlers. It contains information about the current state of the renderer, such as the page, the position, and any other miscellaneous objects that are required to draw into the page.</p>
<h2 id="XML-Handling">XML Handling</h2>
<p>A document may contain information in the form of XML for an image or instream foreign object. This XML is handled through the user agent. A standard extension for PDF is the SVG handler.</p>
<p>If there is XML in the SVG namespace it is given to the handler which renders the SVG into the pdf document at the given location. This separation means that other XML handlers can easily be added.</p>
@@ -1907,7 +1907,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
</table>
<h2 id="add">Adding a Renderer</h2>
<p>You can add other renderers by implementing the Renderer interface. However, the AbstractRenderer does most of what is needed, including iterating through the tree parts, so it is probably better to extend this. This means that you only need to implement the basic functionality such as text, images, and lines. AbstractRenderer's methods can easily be overridden to handle things in a different way or do some extra processing.</p>
-<p>The relevent AreaTree structures that will need to be rendered are:</p>
+<p>The relevant AreaTree structures that will need to be rendered are:</p>
<ul>
<li>
<p>Page</p>
diff --git a/output/fop/dev/design/startup.html b/output/fop/dev/design/startup.html
index d8749f36..8546ae8f 100644
--- a/output/fop/dev/design/startup.html
+++ b/output/fop/dev/design/startup.html
@@ -1792,7 +1792,7 @@ $(document).ready(function () {
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
<h1 id="apache-fop-design-startup-environment-control">Apache™ FOP Design: Startup, Environment, Control</h1>
<h2 id="intro">Introduction</h2>
-<p>Startup is the process of getting Apache™ FOP bootstrapped and creating basic objects. Environment includes acquiring user options, instantiating any frameworks, setting up logging, etc. Control includes the basic logic for tieing the various subsystems together properly.</p>
+<p>Startup is the process of getting Apache™ FOP bootstrapped and creating basic objects. Environment includes acquiring user options, instantiating any frameworks, setting up logging, etc. Control includes the basic logic for tying the various subsystems together properly.</p>
<h2 id="status">Status</h2>
<h3 id="status-todo">To Do</h3>
<ul>
diff --git a/output/fop/dev/design/svg.html b/output/fop/dev/design/svg.html
index d6d019a3..5077e87e 100644
--- a/output/fop/dev/design/svg.html
+++ b/output/fop/dev/design/svg.html
@@ -1802,7 +1802,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>Normally batik converts text into a set of curved shapes.</p>
<p>This is handled as any other shapes when rendering to the output. This is not always desirable as the shapes have very fine curves. This can cause the output to look a bit bad in PDF and PS (it can be drawn properly but is not by default). These curves also require much more data than the original text.</p>
<p>To handle this there is a PDFTextElementBridge that is set when using the bridge in batik. If the text is simple enough for the text to be drawn in the PDF as with all other text then this sets the TextPainter to use the PDFTextPainter. This inserts the text directly into the PDF using the drawString method on the PDFGraphics2D.</p>
-<p>Text is considered simple if the font is available, the font size is useable and there are no tspans or other complications. This can make the resulting PDF significantly smaller.</p>
+<p>Text is considered simple if the font is available, the font size is usable and there are no tspans or other complications. This can make the resulting PDF significantly smaller.</p>
<h2 id="PDF-Links">PDF Links</h2>
<p>To support links in PDF another batik element bridge is used. The PDFAElementBridge creates a PDFANode which inserts a link into the PDF document via the PDFGraphics2D.</p>
<p>Since links are positioned on the page without any transforms then we need to transform the coordinates of the link area so that they match the current position of the a element area. This transform may also need to account for the svg being positioned on the page.</p>
diff --git a/output/fop/dev/design/useragent.html b/output/fop/dev/design/useragent.html
index e989e8f8..d80b47f7 100644
--- a/output/fop/dev/design/useragent.html
+++ b/output/fop/dev/design/useragent.html
@@ -1840,7 +1840,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>using color property as border colour</p>
</li>
<li>
-<p>interpretting all border styles (except outset) as solid</p>
+<p>interpreting all border styles (except outset) as solid</p>
</li>
<li>
<p>thin, medium and thick values for border width</p>
@@ -1918,7 +1918,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>initial "pause-after", "pause-before" and "voice-family" value</p>
</li>
<li>
-<p>treating fixed as scroll on background attachement</p>
+<p>treating fixed as scroll on background attachment</p>
</li>
<li>
<p>media usage of auto</p>
diff --git a/output/fop/dev/extensions.html b/output/fop/dev/extensions.html
index 43d26898..086bdbe3 100644
--- a/output/fop/dev/extensions.html
+++ b/output/fop/dev/extensions.html
@@ -1793,7 +1793,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<h1 id="apache-fop-development-adding-an-extension">Apache™ FOP Development: Adding an Extension</h1>
<h2 id="overview">Overview</h2>
<p>For documentation of standard Apache™ FOP extensions, see the <a href="../trunk/extensions.html">User FOP Extensions</a> document.</p>
-<p>If the default funtionality of FOP needs to be extended for some reason then you can write an extension.</p>
+<p>If the default functionality of FOP needs to be extended for some reason then you can write an extension.</p>
<p>There are three types of extensions possible:</p>
<ul>
<li>
diff --git a/output/fop/dev/implement.html b/output/fop/dev/implement.html
index 86eb6de0..0801d3b8 100644
--- a/output/fop/dev/implement.html
+++ b/output/fop/dev/implement.html
@@ -1826,7 +1826,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
</tr>
<tr>
<td><code>fo.pagination.PageSequence.format()</code> creates a <em>layoutmgr.PageLayoutManager</em>, passing the AreaTree and PageSequence objects to it, then calls its <code>run()</code> method.</td>
-<td><code>fo.pagination.PageSequence.addFlow()</code> programatically adds a Flow object to the page sequence.</td>
+<td><code>fo.pagination.PageSequence.addFlow()</code> programmatically adds a Flow object to the page sequence.</td>
</tr>
<tr>
<td>.</td>
diff --git a/output/fop/dev/release.html b/output/fop/dev/release.html
index b82a28bc..b91c15f1 100644
--- a/output/fop/dev/release.html
+++ b/output/fop/dev/release.html
@@ -1824,7 +1824,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>Update version number in <code>build.xml</code>, <code>releasedist.xml</code> and all <code>pom.xml</code> (not to be merged back into main).</p>
</li>
<li>
-<p>Update dependancy versions in <code>pom.xml</code> to release versions.</p>
+<p>Update dependency versions in <code>pom.xml</code> to release versions.</p>
</li>
<li>
<p>Commit and push changes</p>
diff --git a/output/fop/dev/svg.html b/output/fop/dev/svg.html
index 8df797ed..641294d3 100644
--- a/output/fop/dev/svg.html
+++ b/output/fop/dev/svg.html
@@ -1867,7 +1867,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
</li>
<li>
<p><em>PDFDocumentGraphics2D</em></p>
-<p>used to create a pdf document and inherits from PDFGraphics2D to do the rest of the drawing. Used by the transcoder to create a standalone pdf document from an svg. Can be used independantly the same as any Graphics2D.</p>
+<p>used to create a pdf document and inherits from PDFGraphics2D to do the rest of the drawing. Used by the transcoder to create a standalone pdf document from an svg. Can be used independently the same as any Graphics2D.</p>
</li>
<li>
<p><em>PDFTranscoder</em></p>
diff --git a/output/fop/dev/testing.html b/output/fop/dev/testing.html
index d7f9f6a3..9cc448b7 100644
--- a/output/fop/dev/testing.html
+++ b/output/fop/dev/testing.html
@@ -1804,13 +1804,13 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p><warning>The "functional" testing section on this page is currently inoperative.</warning></p>
<h2 id="Running-and-Using-Tests">Running and Using Tests</h2>
<p>Testing is an important part of getting FOP to operate correctly and conform to the necessary standards.</p>
-<p>A testing system has been set up that works with as a build target when developing with FOP. A developer can run the tests after making changes to the code, the aim is to have the tests run to verfiy that nothing working has been broken.</p>
+<p>A testing system has been set up that works with as a build target when developing with FOP. A developer can run the tests after making changes to the code, the aim is to have the tests run to verify that nothing working has been broken.</p>
<p>To setup the testing the developer must place a reference fop.jar in the "<cvs_repository>/test/reference/" directory. This jar will be dynamically loaded to create the reference output.</p>
<h3 id="W3C-TestSuite">W3C TestSuite</h3>
<p>The testing is set up so that you can download the testsuite from <a href="http://www.w3.org/Style/XSL/TestSuite/">http://www.w3.org/Style/XSL/TestSuite/</a>, unzip the file into the base directory of FOP. Then you can uncomment the lines in the build.xml file in the test target and itwill run through all the tests in the testsuite distribution.</p>
<h3 id="Writing-a-Test">Writing a Test</h3>
-<p>A test belongs to one of a few catagories. A basic test should excercise one element in a number of situations such as changing a property. This should have at least one normal value, one border value and one invalid value. If the property can be of different types then this should also be included.</p>
-<p>A bug test is a test that is specifically aimed at a problem with FOP. That is, the test is not excercising the specification but rather a problem with FOP in handling a particular situation that is not exposed with the other testing.</p>
+<p>A test belongs to one of a few categories. A basic test should exercise one element in a number of situations such as changing a property. This should have at least one normal value, one border value and one invalid value. If the property can be of different types then this should also be included.</p>
+<p>A bug test is a test that is specifically aimed at a problem with FOP. That is, the test is not exercising the specification but rather a problem with FOP in handling a particular situation that is not exposed with the other testing.</p>
<p>A system test is one that tests the abitlity of FOP to handle a number of different elements together.</p>
<p>A test can consist of a complete fo document or a part of the document such as some elements that will be placed into the flow of a standard document.</p>
<h3 id="Submitting-a-Test">Submitting a Test</h3>
diff --git a/output/fop/faq.html b/output/fop/faq.html
index 7379d2f3..1625eb1c 100644
--- a/output/fop/faq.html
+++ b/output/fop/faq.html
@@ -1989,7 +1989,7 @@ then please <a href="bugs.html#issues_new">Open a New Bug</a>.</p>
<h3 id="keep-together">3.10. FOP behaves differently from earlier versions when keep-together="always" is set on table cells</h3>
<p>Support for inline-level keeps has been added in FOP 0.95, and setting <code>keep-together="always"</code> also implicitly sets <code>keep-together.within-line="always"</code>, which forbids FOP to break the text into multiple lines. Set <code>keep-together.within-column="always"</code> on table-cell instead. It’s a good idea not to use the shorthand <code>keep-together="always"</code> at all!</p>
<h3 id="row-height-constraint">3.11. FOP tells me: "The contents of row 1 are taller than they should be". What does that mean?</h3>
-<p>This is usually caused by setting a "height" on a table-row or table-cell and when the content is higher than the specified height. By setting "height" (a so-called corresponding property) you <a href="http://www.w3.org/TR/xsl11/#d0e4413">implicitely set</a> block-progression-dimension.minimum, block-progression-dimension.optimum and block-progression-dimension.maximum to the same value. You'll get some information about that in the warning message. Look for something like: "MinOptMax [...]
+<p>This is usually caused by setting a "height" on a table-row or table-cell and when the content is higher than the specified height. By setting "height" (a so-called corresponding property) you <a href="http://www.w3.org/TR/xsl11/#d0e4413">implicitly set</a> block-progression-dimension.minimum, block-progression-dimension.optimum and block-progression-dimension.maximum to the same value. You'll get some information about that in the warning message. Look for something like: "MinOptMax[ [...]
<p>Assuming you set the height on the table-row to 14pt and your content is 75pt high, a constraint (maximum=14pt) is violated. Normally, you just want to make sure with the "height" property that the row has a minimum height. If that is so, the right solution is to specify block-progression-dimension.minimum="14pt" instead of height="14pt".</p>
<h3 id="page-number-align">3.12. Page numbers are not properly right aligned.</h3>
<p>This happens for <code>fo:page-number-citation</code> elements if the citation occurs before FOP formatted the requested page, usually in TOC or index pages. It is caused by the problem that FOP has to guess how much space the yet unknown page number will occupy, and usually the guesses are somewhat off.</p>
@@ -2064,7 +2064,7 @@ then please <a href="bugs.html#issues_new">Open a New Bug</a>.</p>
<p>This usually means the selected font doesn't have a glyph for the character.</p>
<p>The standard text fonts supplied with Acrobat Reader have mostly glyphs for characters from the ISO Latin 1 character set. For a variety of reasons, even those are not completely guaranteed to work, for example you can't use the fi ligature from the standard serif font. Check the <a href="1.1/output.html#pdf-fonts">overview</a> for the default PDF fonts.</p>
<p>If you use your own fonts, the font must have a glyph for the desired character. Furthermore the font must be available on the machine where the PDF is viewed or it must have been embedded in the PDF file. See <a href="1.1/fonts.html">embedding fonts</a>.</p>
-<p>For most symbols, it is better to select the symbol font explicitely, for example in order to get the symbol for the mathematical empty set, write:</p>
+<p>For most symbols, it is better to select the symbol font explicitly, for example in order to get the symbol for the mathematical empty set, write:</p>
<div class="highlight"><pre><span></span><code><span class="nt"><fo:inline</span> <span class="na">font-family=</span><span class="s">"Symbol"</span><span class="nt">></span><span class="ni">&#x2205;</span><span class="nt"></fo:inline></span>
</code></pre></div>
@@ -2135,7 +2135,7 @@ then please <a href="bugs.html#issues_new">Open a New Bug</a>.</p>
<h3 id="xslt-current-date">8.17. (XSLT) How can I use the current date and time in my document?</h3>
<p>See <a href="fo.html#xslt-date">Current Date and Time</a>.</p>
<h3 id="xhtml-to-pdf">8.18. Can I use FOP to convert XHTML or HTML files to PDF?</h3>
-<p>You will get better results if you transform your source XML directly into XSLFO. It is tempting to use the XML->XHTML->XSLFO approach, because this apparently means there's only one transformation to maintain, but XHTML and publishing grade PDF are dissimilar enough that an "generic" XHTML->XSLFO(PDF) usually wont cut it, because the XHTML already lacks information from the original XML. It may be worthwhile to go from the source XML to an intermediate custom XML which on on [...]
+<p>You will get better results if you transform your source XML directly into XSLFO. It is tempting to use the XML->XHTML->XSLFO approach, because this apparently means there's only one transformation to maintain, but XHTML and publishing grade PDF are dissimilar enough that an "generic" XHTML->XSLFO(PDF) usually won't cut it, because the XHTML already lacks information from the original XML. It may be worthwhile to go from the source XML to an intermediate custom XML which on o [...]
<h3 id="xhtml-to-pdf2">8.19. I know it may be a bad idea to use FOP to convert XHTML or HTML files to PDF, but I want to do it anyway. Are there any tools available to help me?</h3>
<p>The <a href="resources.html">FOP Resources page</a> has links to a tool called <a href="http://html2fo.sourceforge.net/">html2fo</a> which can be used to make such a transformation. In addition, there are tools on the Antenna House <a href="http://www.antennahouse.com/XSLsample/XSLsample.htm">XSL-FO Tutorial and Sample</a> page.</p>
<h2 id="dev-help">9. Development-related Questions.</h2>
@@ -2173,7 +2173,7 @@ then please <a href="bugs.html#issues_new">Open a New Bug</a>.</p>
<p>Question about how to use FOP, how to perform certain tasks with FOP or how to integrate FOP into another application should be posted to fop-user.</p>
</li>
<li>
-<p>XSLT specific stuff sould go to the <a href="http://www.mulberrytech.com/xsl/xsl-list/">XSL list</a>. This includes problems with the language and XSLT HOW-TOs.</p>
+<p>XSLT specific stuff should go to the <a href="http://www.mulberrytech.com/xsl/xsl-list/">XSL list</a>. This includes problems with the language and XSLT HOW-TOs.</p>
</li>
<li>
<p>Problems specific to a certain XSLT processor, like Xalan, Saxon or MSXML, should be handled by processor specific lists. This includes problems with deployment, processor specific extensions, suspected bugs and processor specific APIs. Note that JDK 1.4 and later come with an XML parser and an XSLT processor which may be the source of the problem.</p>
diff --git a/output/fop/fo.html b/output/fop/fo.html
index 97066e51..f8fcdaf3 100644
--- a/output/fop/fo.html
+++ b/output/fop/fo.html
@@ -1802,7 +1802,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>For other non-ASCII characters, such as the Euro symbol, checkbox, etc., see the <a href="http://www.unicode.org/charts/charindex.html">Unicode Reference By Name</a> document that is found at the <a href="http://www.unicode.org">Unicode Consortium</a> site.</p>
<p>After finding the correct Unicode codepoint to represent the character, use <a href="http://www.w3.org/TR/2000/REC-xml-20001006#sec-references">XML Character References</a> to put the character into your source XML, XSLT or FO. See the non-breaking-space comments above for an example of the syntax using decimal notation. The following hexadecimal example will result in a Euro sign:</p>
<p><code>&#x20AC;</code></p>
-<p>Getting your XML correctly encoded is only part of the job. If you want the character to display or print correctly (and you probably do), then the selected font must contain the necessary glyph. Because of differences between font encoding methods, and limitations in some font technologies, this can be a troublesome issue, especially for symbol characters. The FOP example file <a href="fo/fonts.fo.pdf">Base-14 Font Character Mapping</a> is a very useful resource in sorting these issu [...]
+<p>Getting your XML correctly encoded is only part of the job. If you want the character to display or print correctly (and you probably do), then the selected font must contain the necessary glyph. Because of differences between font encoding methods, and limitations in some font technologies, this can be a troublesome issue, especially for symbol characters. The FOP example file <a href="fo/fonts.fo.pdf">Base-14 Font Character Mapping</a> is a very useful resource in sorting these issu [...]
<p>An alternative to encoding the character and making it available through a font is to use an embedded graphic to represent the character: GIF, PNG, SVG, etc.</p>
<h3 id="xml-entity-chars">Entity Characters</h3>
<p>The handful of basic XML character entities that do exist are the ampersand, apostrophe, less-than, greater-than, and single-quote characters. These are needed to distinguish markup tags from content, and to distinguish character entities from content. To avoid parser complaints about illegal characters and entities in your input, ensure that ampersands in text and attributes are written as <code>&amp;</code>, "<" is written as <code>&lt;</code>, and ">" as <code>&gt [...]
diff --git a/output/fop/knownissues.html b/output/fop/knownissues.html
index 79e3aa38..59e940ef 100644
--- a/output/fop/knownissues.html
+++ b/output/fop/knownissues.html
@@ -1854,7 +1854,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>Page breaking currently doesn't support changing available IPD between pages of a single page-sequence. Element list generation has to be reset to redetermine line breaks in this case.</p>
<p><strong>page-breaking_6.xml</strong> (Overflow handing is incomplete):</p>
<p>Line breaking is not 100% correct when there's too little space. Overflows are not detected and warned.</p>
-<p><strong>page-height_indefinite_simple.xml</strong> (Indefinite page height handling is imcomplete):</p>
+<p><strong>page-height_indefinite_simple.xml</strong> (Indefinite page height handling is incomplete):</p>
<p>A RuntimeException is thrown for a page of indefinite height. Lots of warnings.</p>
<p><strong>page-number-citation_background-image.xml</strong> (page-number-citation: Problem with background-image):</p>
<p>Background-images on page-number-citations are not placed correctly.</p>
@@ -1871,7 +1871,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p><strong>table-cell_empty_area_with_marker.xml</strong> (table-cell empty area with marker.xml):</p>
<p>A table-cell producing an empty area does currently not add any markers to a page. See TODO entry in AreaAdditionUtil.</p>
<p><strong>table_border-width_conditionality.xml</strong> (Border conditionality on table):</p>
-<p>The code should be ok, but the test case uses shorthands and therefore is probably not expressing the indended outcome according to the spec. The test case should be revisited.</p>
+<p>The code should be ok, but the test case uses shorthands and therefore is probably not expressing the intended outcome according to the spec. The test case should be revisited.</p>
<p><strong>block_shy_linebreaking_hyph.xml</strong> (Soft hyphen with normal hyphenation enabled):</p>
<p>A soft hyphen should be a preferred as break compared to a normal hyphenation point but is not.</p>
<p><strong>keep_within-page_multi-column_overflow.xml</strong> (Page-keep not respected in multi-column layout):</p>
diff --git a/output/fop/news.html b/output/fop/news.html
index cec6fa14..7c693dc2 100644
--- a/output/fop/news.html
+++ b/output/fop/news.html
@@ -1996,7 +1996,7 @@ Changes since 0.20.4 include:</p>
<p>Added support for PDF encryption</p>
</li>
<li>
-<p>Perfomance tuning</p>
+<p>Performance tuning</p>
</li>
<li>
<p>Fixed link hotspot positioning</p>
@@ -2070,7 +2070,7 @@ See the full text of the <a href="http://marc.theaimsgroup.com/?l=fop-user&m
</item></p>
<h2 id="news-2002-11-23">23 Nov 2002: EXLSFO project has been created</h2>
<p><item date="2002-11-23" title="EXLSFO project has been created">
-The EXSLFO project is a community effort to define functional extensions to thet XSL Formatting Objects specification. See the <a href="http://exslfo.sourceforge.net">EXSLFO website</a> for details.
+The EXSLFO project is a community effort to define functional extensions to the XSL Formatting Objects specification. See the <a href="http://exslfo.sourceforge.net">EXSLFO website</a> for details.
</item></p>
<h2 id="news-2002-11-22">22 Nov 2002: New Committer</h2>
<p><item date="2002-11-22" title="New Committer">
diff --git a/output/fop/team.html b/output/fop/team.html
index 41d1a41b..85f6c9e2 100644
--- a/output/fop/team.html
+++ b/output/fop/team.html
@@ -1838,7 +1838,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p><a href="mailto:matthias@apache.org">Matthias Reischenbacher</a> (MR) is a software developer from Austria and co-founder of Expert Communication Systems GmbH, Munich/Germany. He works on a web-based XML Content Management System that uses FOP for generating PDFs of simple one page product datasheets to publications with thousands of pages in all kinds of formats and layouts.</p>
</li>
<li>
-<p><a href="mailto:tcho@club-internet.fr">Pascal Sancho</a> (PS) is an XML developper from Aix-en-Provence (France). He works on software solutions for rendering various kind of documents on various supports, more specifically taking care of PDF generation with FOP.</p>
+<p><a href="mailto:tcho@club-internet.fr">Pascal Sancho</a> (PS) is an XML developer from Aix-en-Provence (France). He works on software solutions for rendering various kind of documents on various supports, more specifically taking care of PDF generation with FOP.</p>
</li>
<li>
<p><a href="mailto:ssteiner@apache.org">Simon Steiner</a> (SS) is a Python/Java developer from England.</p>
diff --git a/output/fop/trunk/configuration.html b/output/fop/trunk/configuration.html
index 7892b29c..47489d2d 100644
--- a/output/fop/trunk/configuration.html
+++ b/output/fop/trunk/configuration.html
@@ -1993,7 +1993,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<span class="err"></fop</span><span class="nt">></span>
</code></pre></div>
-<p>You can pass a ICC file via the image-loading to convert RGB images to CMYK. For PDF or PS output you would need to set a custom penalty so ImageIO is used, this isnt needed for AFP output.</p>
+<p>You can pass a ICC file via the image-loading to convert RGB images to CMYK. For PDF or PS output you would need to set a custom penalty so ImageIO is used, this isn't needed for AFP output.</p>
<div class="highlight"><pre><span></span><code><span class="nt"><image-loading</span> <span class="na">icc-converter=</span><span class="s">"USSheetfedCoated.icc"</span><span class="nt">></span>
<span class="nt"><penalty</span> <span class="na">value=</span><span class="s">"-1000"</span> <span class="na">class=</span><span class="s">"org.apache.xmlgraphics.image.loader.impl.imageio.ImageLoaderImageIO"</span><span class="nt">/></span>
<span class="nt"></image-loading></span>
diff --git a/output/fop/trunk/embedding.html b/output/fop/trunk/embedding.html
index 2ded7dc5..88416c09 100644
--- a/output/fop/trunk/embedding.html
+++ b/output/fop/trunk/embedding.html
@@ -2048,7 +2048,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
</li>
<li>
-<p>Set <strong>your own Document Handler</strong>. This feature can be used for several purposes, the most likey usage of which would probably be binding a MIME type when the output is Intermediate Format (see <a href="#documenthandlers">Document Handlers</a>). This also allows advanced users to create their own implementation of the document handler.</p>
+<p>Set <strong>your own Document Handler</strong>. This feature can be used for several purposes, the most likely usage of which would probably be binding a MIME type when the output is Intermediate Format (see <a href="#documenthandlers">Document Handlers</a>). This also allows advanced users to create their own implementation of the document handler.</p>
<div class="highlight"><pre><span></span><code><span class="n">userAgent</span><span class="p">.</span><span class="na">setDocumentHandlerOverride</span><span class="p">(</span><span class="n">documentHandler</span><span class="p">);</span> <span class="c1">// documentHandler is an instance of org.apache.fop.render.intermediate.IFDocumentHandler</span>
</code></pre></div>
@@ -2089,7 +2089,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<h3 id="object-reuse">Object reuse</h3>
<p>Fop instances shouldn't (and can't) be reused. Please recreate Fop and FOUserAgent instances for each rendering run using the FopFactory. This is a cheap operation as all reusable information is held in the FopFactory. That's why it's so important to reuse the FopFactory instance.</p>
<h3 id="awt">AWT issues</h3>
-<p>If your XSL-FO files contain SVG then Apache Batik will be used. When Batik is initialised it uses certain classes in <code>java.awt</code> that intialise the Java AWT classes. This means that a daemon thread is created by the JVM and on Unix it will need to connect to a DISPLAY.</p>
+<p>If your XSL-FO files contain SVG then Apache Batik will be used. When Batik is initialised it uses certain classes in <code>java.awt</code> that initialise the Java AWT classes. This means that a daemon thread is created by the JVM and on Unix it will need to connect to a DISPLAY.</p>
<p>The thread means that the Java application may not automatically quit when finished, you will need to call <code>System.exit()</code>. These issues should be fixed in the JDK 1.4.</p>
<p>If you run into trouble running FOP on a head-less server, please see the <a href="graphics.html#batik">notes on Batik</a>.</p>
<h3 id="render-info">Getting information on the rendering process</h3>
diff --git a/output/fop/trunk/events.html b/output/fop/trunk/events.html
index 8106981c..411e985f 100644
--- a/output/fop/trunk/events.html
+++ b/output/fop/trunk/events.html
@@ -1959,7 +1959,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>FATAL: a fatal error which causes an exception in the end and FOP will stop processing.</p>
</li>
</ol>
-<p>Event listeners can choose to ignore certain events based on their event severity. Please note that you may recieve an event "twice" in a specific case: if there is a fatal error an event is generated and sent to the listeners. After that an exception is thrown with the same information and processing stops. If the fatal event is shown to the user and the following exception is equally presented to the user it may appear that the event is duplicated. Of course, the same information is [...]
+<p>Event listeners can choose to ignore certain events based on their event severity. Please note that you may receive an event "twice" in a specific case: if there is a fatal error an event is generated and sent to the listeners. After that an exception is thrown with the same information and processing stops. If the fatal event is shown to the user and the following exception is equally presented to the user it may appear that the event is duplicated. Of course, the same information is [...]
<h3 id="plug-ins">Plug-ins to the event subsystem</h3>
<p>The event subsystem is extensible. There are a number of extension points:</p>
<ul>
diff --git a/output/fop/trunk/extensions.html b/output/fop/trunk/extensions.html
index fb77b042..f1ccab03 100644
--- a/output/fop/trunk/extensions.html
+++ b/output/fop/trunk/extensions.html
@@ -1901,7 +1901,7 @@ The redesigned code makes use of the <a href="http://www.w3.org/TR/xsl11/#fo_ret
<p>This function will construct a color in device-specific CMYK color space. The numbers must be between 0.0 and 1.0. For output formats that don't support device-specific color space the CMYK value is converted to an sRGB value.</p>
<h3 id="pseudo-color-profiles">#CMYK pseudo-profile</h3>
<p><code>color rgb-icc(numeric, numeric, numeric, #CMYK, numeric, numeric, numeric, numeric)</code></p>
-<p>The <code>rgb-icc</code> function will respond to a pseudo-profile called "#CMYK" which indicates a device-specific CMYK color space. The "#CMYK" profile is implicitely available and doesn't have to be (and cannot be) defined through an <code>fo:color-profile</code> element. It is provided for compatibility with certain commercial XSL-FO implementations. Please note that this is not part of the official specification but rather a convention. The following two color specifications are [...]
+<p>The <code>rgb-icc</code> function will respond to a pseudo-profile called "#CMYK" which indicates a device-specific CMYK color space. The "#CMYK" profile is implicitly available and doesn't have to be (and cannot be) defined through an <code>fo:color-profile</code> element. It is provided for compatibility with certain commercial XSL-FO implementations. Please note that this is not part of the official specification but rather a convention. The following two color specifications are e [...]
<ul>
<li>
<p><code>cmyk(0%,0%,20%,40%)</code></p>
diff --git a/output/fop/trunk/fonts.html b/output/fop/trunk/fonts.html
index 1ea176ed..14744bff 100644
--- a/output/fop/trunk/fonts.html
+++ b/output/fop/trunk/fonts.html
@@ -1908,7 +1908,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<h2 id="missing-fonts">Missing Fonts</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">Missing Glyphs</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' [...]
+<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 glyph 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' [...]
<h2 id="awt">System Fonts</h2>
<p>Support for system fonts relies on 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 renderers that supports system fonts (see above table) and you're missing a font, you can just install it in your operating system and it should be available for these renderers. Please note that this is not true for output formats, such as PDF or PostScript, that only support custom fonts.</p>
diff --git a/output/fop/trunk/hyphenation.html b/output/fop/trunk/hyphenation.html
index 350e2d34..eab83eb5 100644
--- a/output/fop/trunk/hyphenation.html
+++ b/output/fop/trunk/hyphenation.html
@@ -1881,7 +1881,7 @@ This element is unused and not even read. It should be considered a documentatio
<p>the period character (.) represents a word boundary, i.e. either the beginning or ending of a word</p>
</li>
<li>
-<p>numeric characters represent a scoring system for indicating the acceptability of a hyphen in this location. Odd numbers represent an acceptable location for a hyphen, with higher values overriding lower inhibiting values. Even numbers indicate an unacceptable location, with higher values overriding lower values indicating an acceptable position. A value of zero (inhibiting) is implied when there is no number present. Generally patterns are constructed so that valuse greater than 4 ar [...]
+<p>numeric characters represent a scoring system for indicating the acceptability of a hyphen in this location. Odd numbers represent an acceptable location for a hyphen, with higher values overriding lower inhibiting values. Even numbers indicate an unacceptable location, with higher values overriding lower values indicating an acceptable position. A value of zero (inhibiting) is implied when there is no number present. Generally patterns are constructed so that values greater than 4 ar [...]
Here are some examples from the English patterns file:</p>
</li>
<li>
diff --git a/output/fop/trunk/metadata.html b/output/fop/trunk/metadata.html
index 08330733..068894a6 100644
--- a/output/fop/trunk/metadata.html
+++ b/output/fop/trunk/metadata.html
@@ -1792,7 +1792,7 @@ $(document).ready(function () {
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
<h1 id="apache-fop-metadata">Apache™ FOP: Metadata</h1>
<h2 id="overview">Overview</h2>
-<p>Document metadata is an important tool for categorizing and finding documents. Various formats support different kinds of metadata representation and to different levels. One of the more popular and flexible means of representing document or object metadata is <a href="http://www.adobe.com/products/xmp/">XMP (eXtensible Metadata Platform, specified by Adobe)</a>. PDF 1.4 introduced the use of XMP. The XMP specification lists recommendation for embedding XMP metdata in other document a [...]
+<p>Document metadata is an important tool for categorizing and finding documents. Various formats support different kinds of metadata representation and to different levels. One of the more popular and flexible means of representing document or object metadata is <a href="http://www.adobe.com/products/xmp/">XMP (eXtensible Metadata Platform, specified by Adobe)</a>. PDF 1.4 introduced the use of XMP. The XMP specification lists recommendation for embedding XMP metadata in other document [...]
<h2 id="xmp-in-fo">Embedding XMP in an XSL-FO document</h2>
<p>As noted above, there's no officially recommended way to embed metadata in XSL-FO. Apache™ FOP supports embedding XMP in XSL-FO. Currently, only support for document-level metadata is implemented. Object-level metadata will be implemented when there's interest.</p>
<p>Document-level metadata can be specified in the <code>fo:declarations</code> element. XMP specification recommends to use <code>x:xmpmeta</code>, <code>rdf:RDF</code>, and <code>rdf:Description</code> elements as shown in example below. Both <code>x:xmpmeta</code> and <code>rdf:RDF</code> elements are recognized as the top-level element introducing an XMP fragment (as per the XMP specification).</p>
diff --git a/output/fop/trunk/output.html b/output/fop/trunk/output.html
index 9662e230..d766ebb5 100644
--- a/output/fop/trunk/output.html
+++ b/output/fop/trunk/output.html
@@ -2064,7 +2064,7 @@ FO document using the <code>pdf:info</code> extension element as a child of <cod
<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">AFP</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 FOP AFP Renderer deals with creating documents conforming to the IBM AFP document architecture also referred to as MO:DCA (Mixed Object Document Content Architecture).</p>
<p>The mapping of XSL-FO elements to the major MO:DCA structures is as follows:</p>
<table>
<thead>
@@ -2483,7 +2483,7 @@ FO document using the <code>pdf:info</code> extension element as a child of <cod
<h3 id="afp-foreign-attributes">Foreign Attributes</h3>
<h4 id="afp-foreign-attributes-resource">Resource</h4>
-<p>The resource foreign attributes provides the ability to name and control where data object resources (e.g. images/scalable vector graphics) will reside in the AFP output. The afp foreign attributes are only used in conjuntion with <fo:external-graphic/> and <instream-foreign-object/>. Example:</p>
+<p>The resource foreign attributes provides the ability to name and control where data object resources (e.g. images/scalable vector graphics) will reside in the AFP output. The afp foreign attributes are only used in conjunction with <fo:external-graphic/> and <instream-foreign-object/>. Example:</p>
<div class="highlight"><pre><span></span><code><span class="nt"><fo:root</span> <span class="na">xmlns:fo=</span><span class="s">"http://www.w3.org/1999/XSL/Format"</span>
<span class="na">xmlns:afp=</span><span class="s">"http://xmlgraphics.apache.org/fop/extensions/afp"</span><span class="nt">></span>
...
@@ -2659,7 +2659,7 @@ FO document using the <code>pdf:info</code> extension element as a child of <cod
<h2 id="sandbox">Output Formats in the Sandbox</h2>
<p>Due to the state of certain renderers we moved some of them to a "sandbox" area until they are ready for more serious use. The renderers and FOEventHandlers in the sandbox can be found under src/sandbox and are compiled into build/fop-sandbox.jar during the main build. The output formats in the sandbox are marked as such below.</p>
<h3 id="mif">MIF</h3>
-<p><warning>The MIF handler is in the sandbox and not yet functional in FOP Trunk!!! Please help us ressurrect this feature.</warning>
+<p><warning>The MIF handler is in the sandbox and not yet functional in FOP Trunk!!! Please help us resurrect this feature.</warning>
This format is the Maker Interchange Format which is used by Adobe Framemaker.</p>
<h3 id="svg">SVG</h3>
<p><warning>The SVG renderer is in the sandbox and may not work as expected in FOP Trunk!!! Please help us improve this feature.</warning>
diff --git a/output/fop/trunk/pdfa.html b/output/fop/trunk/pdfa.html
index 5136abd6..ec03bfb1 100644
--- a/output/fop/trunk/pdfa.html
+++ b/output/fop/trunk/pdfa.html
@@ -1862,7 +1862,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>PDF is forced to version 1.4 if PDF/A-1 is activated.</p>
</li>
<li>
-<p>No filter must be specified explicitely for metadata objects. Metadata must be embedded in clear text so non-PDF-aware applications can extract the XMP metadata.</p>
+<p>No filter must be specified explicitly for metadata objects. Metadata must be embedded in clear text so non-PDF-aware applications can extract the XMP metadata.</p>
</li>
</ul>
<p><note>There are additional requirements if you want to enabled PDF/A-1a (Tagged PDF). This is particularly the specification of the natural language and alternative descriptions for images. Please refer to the <a href="accessibility.html">Accessibility page</a> for details.</note></p>
diff --git a/output/fop/trunk/pdfx.html b/output/fop/trunk/pdfx.html
index ba901a56..3512b515 100644
--- a/output/fop/trunk/pdfx.html
+++ b/output/fop/trunk/pdfx.html
@@ -1794,7 +1794,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p><authors><person email="jeremias@apache.org" name="Jeremias Märki"></person></authors></p>
<h2 id="overview">Overview</h2>
<p><warning>Support for PDF/X is available beginning with version 0.93. This feature is new and may not be 100% complete, yet. Feedback is welcome.</warning></p>
-<p>PDF/X is a standard which faciliates prepress digital data exchange using PDF. Currently, PDF/X-3:2003 and PDF/X-4 are implemented out of the many different flavours of PDF/X profiles. PDF/X-3:2003 is documented in <a href="http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=39940&ICS1=37&ICS2=100&ICS3=99">ISO 15930-6:2003(E)</a>. More info on PDF/X can be found on the <a href="http://www.pdfx.info/">PDF/X info site</a>.</p>
+<p>PDF/X is a standard which facilitates prepress digital data exchange using PDF. Currently, PDF/X-3:2003 and PDF/X-4 are implemented out of the many different flavours of PDF/X profiles. PDF/X-3:2003 is documented in <a href="http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=39940&ICS1=37&ICS2=100&ICS3=99">ISO 15930-6:2003(E)</a>. More info on PDF/X can be found on the <a href="http://www.pdfx.info/">PDF/X info site</a>.</p>
<h2 id="status">Implementation Status</h2>
<p><strong>PDF/X-3:2003</strong> and <strong>PDF/X-4</strong> are implemented to the degree that FOP supports the creation of the elements described in ISO 15930-6.</p>
<p>An important restriction of the current implementation is that all normal RGB colors specified in XSL-FO and SVG are left unchanged in the sRGB color space (XSL-FO and SVG both use sRGB as their default color space). There's no conversion to a CMYK color space. Although sRGB is a calibrated color space, its color space has a different size than a CMYK color space which makes the conversion a lossy conversion and can lead to unwanted results. Although the use of the calibrated sRGB has [...]
diff --git a/output/fop/trunk/running.html b/output/fop/trunk/running.html
index b595926a..973b6714 100644
--- a/output/fop/trunk/running.html
+++ b/output/fop/trunk/running.html
@@ -1945,7 +1945,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p>FOP expects to find <code>fop.jar</code> in the <code>build</code> subdirectory of the base directory, and adds it to the classpath. Subsequently FOP adds all <code>jar</code> files in the lib directory to the classpath. The lib directory is either the <code>lib</code> subdirectory of the base directory, or, if that does not exist, the base directory itself.</p>
<p>If the system property <code>fop.optional.lib</code> contains the name of a directory, then all <code>jar</code> files in that directory are also added to the classpath. See the methods <code>getJARList</code> and <code>checkDependencies</code> in <code>org.apache.fop.cli.Main</code>.</p>
<h2 id="check-input">Using Xalan to Check XSL-FO Input</h2>
-<p>FOP sessions that use -xml and -xsl input instead of -fo input are actually controlling two distinct conversions: Tranforming XML to XSL-FO, then formatting the XSL-FO to PDF (or another FOP output format). Although FOP controls both of these processes, the first is included merely as a convenience and for performance reasons. Only the second is part of FOP's core processing. If a user has a problem running FOP, it is important to determine which of these two processes is causing the [...]
+<p>FOP sessions that use -xml and -xsl input instead of -fo input are actually controlling two distinct conversions: Transforming XML to XSL-FO, then formatting the XSL-FO to PDF (or another FOP output format). Although FOP controls both of these processes, the first is included merely as a convenience and for performance reasons. Only the second is part of FOP's core processing. If a user has a problem running FOP, it is important to determine which of these two processes is causing the [...]
<p><note>The user is always responsible to provide correct XSL-FO code to FOP.</note></p>
<p>In the case of using -xml and -xsl input, although the user is responsible for the XSL-FO code that is FOP's input, it is not visible to the user. To make the intermediate FO file visible, the FOP distribution includes the "-foout" option which causes FOP to run only the first (transformation) step, and write the results to a file. (See also the Xalan command-line below)</p>
<p><note>When asking for help on the FOP mailing lists, <em>never</em> attach XML and XSL to illustrate the issue. Always run the XSLT step (-foout) and send the resulting XSL-FO file instead. Of course, be sure that the XSL-FO file is correct before sending it.</note></p>
diff --git a/output/fop/trunk/servlets.html b/output/fop/trunk/servlets.html
index 697163a4..0f4dd4f6 100644
--- a/output/fop/trunk/servlets.html
+++ b/output/fop/trunk/servlets.html
@@ -1830,7 +1830,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
</code></pre></div>
<p><note>There are numerous problems with the code snippet above. Its purpose is only to demonstrate the basic concepts. See below for details.</note></p>
-<h3 id="xslt">Adding XSL tranformation (XSLT)</h3>
+<h3 id="xslt">Adding XSL transformation (XSLT)</h3>
<p>A common requirement is to transform an XML source to XSL-FO using an XSL transformation. It is recommended to use JAXP for this task. The following snippet shows the basic code:</p>
<div class="highlight"><pre><span></span><code><span class="kd">private</span> <span class="n">TransformerFactory</span> <span class="n">tFactory</span> <span class="o">=</span> <span class="n">TransformerFactory</span><span class="p">.</span><span class="na">newInstance</span><span class="p">();</span>
@@ -1873,7 +1873,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<p><note>Buffering the generated PDF in a ByteArrayOutputStream is done to avoid potential problems with the Acrobat Reader Plug-in in Microsoft Internet Explorer.</note></p>
<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
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>
+<p>Because you have an explicit <code>Transformer</code> object, you can also use it to explicitly set parameters for the transformation run.</p>
<h3 id="cfg">Custom configuration</h3>
<p>You can easily set up your own FOUserAgent as demonstrated on the <a href="embedding.html">Embedding page</a>.</p>
<h3 id="performance">Improving performance</h3>
@@ -1936,7 +1936,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
<span class="o">[</span><span class="p">..</span><span class="o">]</span>
-<span class="c1">//The stylesheet for the JAXP Transfomer</span>
+<span class="c1">//The stylesheet for the JAXP Transformer</span>
<span class="n">Source</span> <span class="n">xsltSrc</span> <span class="o">=</span> <span class="k">this</span><span class="p">.</span><span class="na">uriResolver</span><span class="p">.</span><span class="na">resolve</span><span class="p">(</span>
<span class="s">"servlet-context:/xslt/mystylesheet.xsl"</span><span class="p">,</span> <span class="kc">null</span><span class="p">);</span>
<span class="n">Transformer</span> <span class="n">transformer</span> <span class="o">=</span> <span class="k">this</span><span class="p">.</span><span class="na">transFactory</span><span class="p">.</span><span class="na">newTransformer</span><span class="p">(</span><span class="n">xsltSrc</span><span class="p">);</span>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org