white-space and line-ending fixes

git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@195676 13f79535-47bb-0310-9956-ffa450edef68

33 files changed, 116 insertions, 116 deletions

diff --git a/src/documentation/content/xdocs/compliance.xml b/src/documentation/content/xdocs/compliance.xml
index 26e829118..4afe733cf 100644
--- a/src/documentation/content/xdocs/compliance.xml
+++ b/src/documentation/content/xdocs/compliance.xml
@@ -61,7 +61,7 @@ want it to.</comment>
           <level-3 name="table" compliance-level="1" comply="yes"/>
           <level-3 name="table-body" compliance-level="1" comply="yes"/>
           <level-3 name="table-cell" compliance-level="1" comply="yes">
-            <comment>must contain block-level FOs (cannot contain straight character data</comment> 
+            <comment>must contain block-level FOs (cannot contain straight character data</comment>
           </level-3>
           <level-3 name="table-column" compliance-level="1" comply="yes">
             <comment>you must explicitly specify column widths</comment>
diff --git a/src/documentation/content/xdocs/design/areas.xml b/src/documentation/content/xdocs/design/areas.xml
index 9d30e0dc1..a7d4e4615 100644
--- a/src/documentation/content/xdocs/design/areas.xml
+++ b/src/documentation/content/xdocs/design/areas.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" standalone="no"?> 
+<?xml version="1.0" standalone="no"?>
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
     "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
 
@@ -19,7 +19,7 @@ The code to implement the area tree will attempt to match the areas
 defined in the specification. A number of optimisations may be possible
 for similar areas and groups of areas.
   </p>
-  <p> 
+  <p>
 Since the area tree will be used during the layout by the layout managers
 it will need to store information that affects the layout. The information
 such as spacing and keeps will be held in such a way that it can be
@@ -27,7 +27,7 @@ discarded once the layout is finalised.
   </p>
 <section>
   <title>Structure</title>
-<p> 
+<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
diff --git a/src/documentation/content/xdocs/design/breakpos.xml b/src/documentation/content/xdocs/design/breakpos.xml
index c2eaa1aed..80bf40155 100644
--- a/src/documentation/content/xdocs/design/breakpos.xml
+++ b/src/documentation/content/xdocs/design/breakpos.xml
@@ -35,11 +35,11 @@ non-stacking direction (at least for inline areas, it must have both). Flags
 indicating various conditions (ISFIRST, ISLAST, CAN_BREAK_AFTER,
 FORCE_BREAK_AFTER, ANCHORS etc). A BreakPoss contains a reference to
 the top-level LayoutManager which generated it.
-</p> 
+</p>
 <p>A BreakPoss contains an object implementing
 the BreakPoss.Position interface. This object is specific to the layout
 manager which created the BreakPoss. It should indicate where the
-break occurs and allow the LM to 
+break occurs and allow the LM to
 create an area corresponding to the BP. A higher level LM Position
 must somehow reference or wrap the Position returned by its child LM in its
 BreakPoss object. The layout manager  modifies the flags and dimension
@@ -59,7 +59,7 @@ create the corresponding areas.</p>
   </section>
 <section>
   <title>A walk-through</title>
-<p>Layout Managers are created from the top down. First the 
+<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
diff --git a/src/documentation/content/xdocs/design/extending.xml b/src/documentation/content/xdocs/design/extending.xml
index 35d468422..2796f2e3d 100644
--- a/src/documentation/content/xdocs/design/extending.xml
+++ b/src/documentation/content/xdocs/design/extending.xml
@@ -9,7 +9,7 @@
         <authors>
             <person name="Keiron Liddle" email="keiron@aftexsw.com"/>
         </authors>
-    </header> 
+    </header>
 
     <body>
 <section>
diff --git a/src/documentation/content/xdocs/design/fotree.xml b/src/documentation/content/xdocs/design/fotree.xml
index a4c5c0c1d..e1573037b 100644
--- a/src/documentation/content/xdocs/design/fotree.xml
+++ b/src/documentation/content/xdocs/design/fotree.xml
@@ -2,7 +2,7 @@
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
     "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
 
-<document> 
+<document>
     <header>
         <title>FO Tree</title>
         <subtitle>Design of FO Tree Structure</subtitle>
@@ -14,7 +14,7 @@
     <body>
 <section>
   <title>Introduction</title>
-<p> 
+<p>
 The FO Tree is an internal representation of the input FO document.
 The tree is created by building the elements and attributes from
 the SAX events.
diff --git a/src/documentation/content/xdocs/design/properties.xml b/src/documentation/content/xdocs/design/properties.xml
index bcc4983ce..713ba2ac3 100644
--- a/src/documentation/content/xdocs/design/properties.xml
+++ b/src/documentation/content/xdocs/design/properties.xml
@@ -2,7 +2,7 @@
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
     "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
 
-<document> 
+<document>
     <header>
         <title>Properties</title>
         <subtitle>Properties overview</subtitle>
@@ -11,7 +11,7 @@
         </authors>
     </header>
 
-    <body> 
+    <body>
 
 <section>
   <title>Properties</title>
@@ -19,7 +19,7 @@
     <title>Property datatypes</title>
 <p>The property datatypes are defined in the
 org.apache.fop.datatypes package, except Number and String which are java
-primitives. The FOP datatypes are:</p> 
+primitives. The FOP datatypes are:</p>
 <ul>
 <li>Number</li>
 <li>String</li>
diff --git a/src/documentation/content/xdocs/design/understanding/fo_tree.xml b/src/documentation/content/xdocs/design/understanding/fo_tree.xml
index a03be543c..6dfff2bd3 100644
--- a/src/documentation/content/xdocs/design/understanding/fo_tree.xml
+++ b/src/documentation/content/xdocs/design/understanding/fo_tree.xml
@@ -50,7 +50,7 @@ Object.</p>
         The FO Tree is simply a heirarchy of java objects that
         represent the fo elements from xml. The traversal is done by
         the layout or structure process only in the flow elements.
-      </p> 
+      </p>
 
 <section>
   <title>Properties</title>
diff --git a/src/documentation/content/xdocs/design/understanding/properties.xml b/src/documentation/content/xdocs/design/understanding/properties.xml
index 6261b3d8e..54d952410 100644
--- a/src/documentation/content/xdocs/design/understanding/properties.xml
+++ b/src/documentation/content/xdocs/design/understanding/properties.xml
@@ -28,13 +28,13 @@ the element name. Most Makers are generic and handle the attribute on
 any element, but it's possible to set up an element-specific property
 Maker. The attribute name to Maker mappings are automatically created
 during the code generation phase by processing the XML property
-description files.</p> 
+description files.</p>
 </section>
 
 <section>
   <title>Processing the attribute list</title>
 <p>The PLB first looks to see if the font-size property is specified, since
-it sets up relative units which can be used in other property 
+it sets up relative units which can be used in other property
 specifications. Each attribute is then handled in turn. If the attribute
 specifies part of a compound property such as space-before.optimum, the
 PLB looks to see if the attribute list also contains the "base" property
@@ -59,7 +59,7 @@ 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 
+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
diff --git a/src/documentation/content/xdocs/dev/configuration.xml b/src/documentation/content/xdocs/dev/configuration.xml
index f73a14c5c..c85ad2038 100644
--- a/src/documentation/content/xdocs/dev/configuration.xml
+++ b/src/documentation/content/xdocs/dev/configuration.xml
@@ -2,11 +2,11 @@
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
     "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
 
-<document> 
-  <header> 
-    <title>Configuration</title> 
-  </header> 
-  <body> 
+<document>
+  <header>
+    <title>Configuration</title>
+  </header>
+  <body>
     <section>
       <title>Configuring FOP</title>
       <p>
diff --git a/src/documentation/content/xdocs/dev/examples.xml b/src/documentation/content/xdocs/dev/examples.xml
index 210f42c5a..2542dba56 100644
--- a/src/documentation/content/xdocs/dev/examples.xml
+++ b/src/documentation/content/xdocs/dev/examples.xml
@@ -2,11 +2,11 @@
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
     "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
 
-<document> 
-  <header> 
-    <title>FO Examples</title> 
-  </header> 
-  <body> 
+<document>
+  <header>
+    <title>FO Examples</title>
+  </header>
+  <body>
     <section>
       <title>Example Documents Using FOP</title>
       <p>
diff --git a/src/documentation/content/xdocs/dev/extensions.xml b/src/documentation/content/xdocs/dev/extensions.xml
index 3b7ab1bbf..654976a30 100644
--- a/src/documentation/content/xdocs/dev/extensions.xml
+++ b/src/documentation/content/xdocs/dev/extensions.xml
@@ -2,11 +2,11 @@
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
     "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
 
-<document> 
-  <header> 
-    <title>Extensions to FOP</title> 
-  </header> 
-  <body> 
+<document>
+  <header>
+    <title>Extensions to FOP</title>
+  </header>
+  <body>
     <section>
       <title>Overview</title>
       <p>
diff --git a/src/documentation/content/xdocs/dev/faq.xml b/src/documentation/content/xdocs/dev/faq.xml
index 20c04de65..3a1c56f24 100644
--- a/src/documentation/content/xdocs/dev/faq.xml
+++ b/src/documentation/content/xdocs/dev/faq.xml
@@ -834,7 +834,7 @@ transformer.transform(xmlsource, new SAXResult(driver.getContentHandler()));</so
       <question>Watermarks</question>
       <answer>
         <p>  Answer: see 3.3, or use a a region overlapping the flowing text and put
-  an image there: 
+  an image there:
 </p>
         <p>   > From: Trevor_Campbell@kaz.com.au
     Use the region-before.  Make it large enough to contain your image and then
diff --git a/src/documentation/content/xdocs/dev/fo/embedding.fo b/src/documentation/content/xdocs/dev/fo/embedding.fo
index 4570ad057..7a172a91d 100644
--- a/src/documentation/content/xdocs/dev/fo/embedding.fo
+++ b/src/documentation/content/xdocs/dev/fo/embedding.fo
@@ -1089,7 +1089,7 @@ Clipping
       </fo:block>
 
       <fo:block>
-      
+
       </fo:block>
 
       <fo:block space-before.optimum="5pt" space-after.optimum="5pt" font-weight="bold" font-size="12pt">
@@ -1097,7 +1097,7 @@ Interesting Functionality
       </fo:block>
 
       <fo:block>
-      
+
       </fo:block>
 
     </fo:flow>
diff --git a/src/documentation/content/xdocs/dev/index.xml b/src/documentation/content/xdocs/dev/index.xml
index d73c1bd85..dfb16c81d 100644
--- a/src/documentation/content/xdocs/dev/index.xml
+++ b/src/documentation/content/xdocs/dev/index.xml
@@ -2,11 +2,11 @@
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
     "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
 
-      <document> 
-        <header> 
-          <title>FOP 1.0 development</title> 
-        </header> 
-        <body> 
+      <document>
+        <header>
+          <title>FOP 1.0 development</title>
+        </header>
+        <body>
           <section>
             <title>Introduction</title>
             <p>
@@ -56,13 +56,13 @@ This image is a demonstration of a two page document. The xml data on the left
 is formatted into the two pages on the right. The document contains static areasthat appear on every page, an external graphic in this case an svg document.
 There is a footnote on the first page and a table that goes across both pages.
 </p>
-<p> 
+<p>
 The advantage of XSL is the ability to take an XML document and to format
 the information into a page layout. The XML document can be generated
 in any way, the most common would be to use XSLT. FOP takes the XML
 and formats the data into pages. The pages are then rendered to the
 requested output.
-</p> 
+</p>
 <p>
 This is a real document. The image was created by rendering the document
 to the svg renderer then putting the rendered pages into an svg document
@@ -80,7 +80,7 @@ The goals of the Apache XML FOP Project are to deliver an XSL FO->PDF formatter
     <p>Conformance to the XML 1.0 Recommendation, XSLT 1.0 Recommendation and the XML Namespaces Recommendation is
        understood. Other relevant documents, such as the XPath and XLink Working Drafts, are referenced as necessary. The FOP
        Project will attempt to use the latest version of evolving specifications.
-    </p> 
+    </p>
 
    <p>To reach this aim currently the layout system is being redesigned to
 better handle the formatting of all different types of formatting objects.
diff --git a/src/documentation/content/xdocs/dev/svg.xml b/src/documentation/content/xdocs/dev/svg.xml
index 5ed6ab728..cc83bee3e 100644
--- a/src/documentation/content/xdocs/dev/svg.xml
+++ b/src/documentation/content/xdocs/dev/svg.xml
@@ -2,11 +2,11 @@
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
     "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
 
-<document> 
-  <header> 
-    <title>SVG in FOP</title> 
-  </header> 
-  <body> 
+<document>
+  <header>
+    <title>SVG in FOP</title>
+  </header>
+  <body>
     <section>
       <title>Introduction</title>
       <p>
@@ -70,13 +70,13 @@ to PDF:
     <caption>SVG to PDF examples</caption>
     <tr>
       <th></th>
-      <th>svg file</th> 
-      <th>png file</th> 
-      <th>pdf result</th> 
+      <th>svg file</th>
+      <th>png file</th>
+      <th>pdf result</th>
     </tr>
     <tr>
-      <td>images</td> 
-      <td><link href="svg/images.svg">images.svg</link></td> 
+      <td>images</td>
+      <td><link href="svg/images.svg">images.svg</link></td>
       <td><!--link href="svg/images.png"-->images.png<!--/link--></td>
       <td><link href="svg/images.pdf">images.pdf</link></td>
     </tr>
@@ -123,7 +123,7 @@ You will need Acrobat 5.0 to see transparency.
       <td><link href="fo/embedding.fo">embedding.fo</link></td>
       <td><link href="fo/embedding.fo.pdf">embedding.fo.pdf</link></td>
     </tr>
-  </table> 
+  </table>
           </section>
           <section>
             <title>Important Notes</title>
diff --git a/src/documentation/content/xdocs/dev/svg/text.svg b/src/documentation/content/xdocs/dev/svg/text.svg
index 8ac73ec51..2cdd6179e 100644
--- a/src/documentation/content/xdocs/dev/svg/text.svg
+++ b/src/documentation/content/xdocs/dev/svg/text.svg
@@ -88,7 +88,7 @@
 <line x1="30" y1="80" x2="100" y2="80"/>
 <line x1="50" y1="100" x2="80" y2="100"/>
 </g>
-</g> 
+</g>
   </glyph>
 
  <glyph unicode="P" glyph-name="p" horiz-adv-x="210">
@@ -101,7 +101,7 @@
 <line x1="5" y1="85" x2="40" y2="85"/>
 <line x1="5" y1="110" x2="40" y2="110"/>
 </g>
-</g> 
+</g>
   </glyph>
 
     <hkern g1="F"  g2="O"  k="5"/>
diff --git a/src/documentation/content/xdocs/examples.xml b/src/documentation/content/xdocs/examples.xml
index d29906585..13c0f0737 100644
--- a/src/documentation/content/xdocs/examples.xml
+++ b/src/documentation/content/xdocs/examples.xml
@@ -43,7 +43,7 @@
       </li>
       <li>readme.fo - uses an old version of Fop documentation for a longer example
       </li>
-  
+
       <li>Look also into the directory examples/svg. There you find some very extensive svg examples.
           Just start makedoc.
       </li>
diff --git a/src/documentation/content/xdocs/extensions.xml b/src/documentation/content/xdocs/extensions.xml
index 4a8e75c78..d200ecd41 100644
--- a/src/documentation/content/xdocs/extensions.xml
+++ b/src/documentation/content/xdocs/extensions.xml
@@ -44,8 +44,8 @@ Please see the <link href="svg.html">SVG page</link> for more details.
     </fox:outline>
   <fox:outline>
 </fo:root>]]></source>
-    <p>It works similarly to a basic-link. There is also an external-destination 
-       property, but it isn't supported currently. See the pdfoutline.fo file in 
+    <p>It works similarly to a basic-link. There is also an external-destination
+       property, but it isn't supported currently. See the pdfoutline.fo file in
       docs/examples/fo for a more complete example.</p>
   </section>
   </section>
diff --git a/src/documentation/content/xdocs/faq.xml b/src/documentation/content/xdocs/faq.xml
index 5535db6a4..c730407ec 100644
--- a/src/documentation/content/xdocs/faq.xml
+++ b/src/documentation/content/xdocs/faq.xml
@@ -883,7 +883,7 @@ transformer.transform(xmlsource, new SAXResult(driver.getContentHandler()));</so
       <question>Watermarks</question>
       <answer>
         <p>  Answer: see 3.3, or use a a region overlapping the flowing text and put
-  an image there: 
+  an image there:
 </p>
         <p>   > From: Trevor_Campbell@kaz.com.au
     Use the region-before.  Make it large enough to contain your image and then
diff --git a/src/documentation/content/xdocs/fo/align.fo b/src/documentation/content/xdocs/fo/align.fo
index 6c9449a7a..4887af4b6 100644
--- a/src/documentation/content/xdocs/fo/align.fo
+++ b/src/documentation/content/xdocs/fo/align.fo
@@ -21,9 +21,9 @@
 <fo:page-sequence id="N2528" master-reference="left">
 
 <fo:static-content flow-name="xsl-region-after">
-	<fo:block text-align-last="center" font-size="10pt">
-		<fo:page-number/>
-	</fo:block>
+  <fo:block text-align-last="center" font-size="10pt">
+    <fo:page-number/>
+  </fo:block>
 </fo:static-content>
 
 <fo:flow flow-name="xsl-region-body">
diff --git a/src/documentation/content/xdocs/fo/align2.fo b/src/documentation/content/xdocs/fo/align2.fo
index 8c85414d5..7c9532c25 100644
--- a/src/documentation/content/xdocs/fo/align2.fo
+++ b/src/documentation/content/xdocs/fo/align2.fo
@@ -21,9 +21,9 @@
 <fo:page-sequence id="N2528" master-reference="left">
 
 <fo:static-content flow-name="xsl-region-after">
-	<fo:block text-align-last="center" font-size="10pt">
-		<fo:page-number/>
-	</fo:block>
+  <fo:block text-align-last="center" font-size="10pt">
+    <fo:page-number/>
+  </fo:block>
 </fo:static-content>
 
 <fo:flow flow-name="xsl-region-body">
diff --git a/src/documentation/content/xdocs/fo/embed.fo b/src/documentation/content/xdocs/fo/embed.fo
index 04ec81161..2993552da 100644
--- a/src/documentation/content/xdocs/fo/embed.fo
+++ b/src/documentation/content/xdocs/fo/embed.fo
@@ -24,9 +24,9 @@
 <fo:page-sequence id="N2528" master-reference="left">
 
 <fo:static-content flow-name="xsl-region-after">
-	<fo:block text-align-last="center" font-size="10pt">
-		<fo:page-number/>
-	</fo:block>
+  <fo:block text-align-last="center" font-size="10pt">
+    <fo:page-number/>
+  </fo:block>
 </fo:static-content>
 
 <fo:flow flow-name="xsl-region-body">
diff --git a/src/documentation/content/xdocs/fo/size.fo b/src/documentation/content/xdocs/fo/size.fo
index ae6f763e2..0279c69ef 100644
--- a/src/documentation/content/xdocs/fo/size.fo
+++ b/src/documentation/content/xdocs/fo/size.fo
@@ -21,9 +21,9 @@
 <fo:page-sequence id="N2528" master-reference="left">
 
 <fo:static-content flow-name="xsl-region-after">
-	<fo:block text-align-last="center" font-size="10pt">
-		<fo:page-number/>
-	</fo:block>
+  <fo:block text-align-last="center" font-size="10pt">
+    <fo:page-number/>
+  </fo:block>
 </fo:static-content>
 
 <fo:flow flow-name="xsl-region-body">
diff --git a/src/documentation/content/xdocs/implemented.xml b/src/documentation/content/xdocs/implemented.xml
index 7f690f6ee..a3a700724 100644
--- a/src/documentation/content/xdocs/implemented.xml
+++ b/src/documentation/content/xdocs/implemented.xml
@@ -18,7 +18,7 @@
   </section>
   <section>
     <title>1) Formatting Objects</title>
-    <p>This section follows the table "B Formatting Object Summary" in the xsl:fo specification. At the  
+    <p>This section follows the table "B Formatting Object Summary" in the xsl:fo specification. At the
        end of each sub-section you find listed what is not implemented.</p>
 
     <section>
@@ -37,7 +37,7 @@
         <li>region-before</li>
         <li>region-after</li>
         <li>region-start</li>
-        <li>region-end</li> 
+        <li>region-end</li>
         <li>flow</li>
         <li>static-content</li>
       </ul>
diff --git a/src/documentation/content/xdocs/index.xml b/src/documentation/content/xdocs/index.xml
index 3d77556dd..f58651e4b 100644
--- a/src/documentation/content/xdocs/index.xml
+++ b/src/documentation/content/xdocs/index.xml
@@ -2,32 +2,32 @@
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
     "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
 
-<document> 
-  <header> 
-    <title>FOP</title> 
-  </header> 
-  <body> 
+<document>
+  <header>
+    <title>FOP</title>
+  </header>
+  <body>
     <section>
       <title>Introduction</title>
     <p>FOP (Formatting Objects Processor) is the world's first print formatter driven by XSL formatting
        objects and the world's first output independent formatter. It is a
        Java application that reads a formatting object tree and then
        renders the resulting pages to a specified output. <link href="output.html">Output formats</link>
-       currently supported are PDF, PCL, PS, SVG, XML (area tree representation), 
+       currently supported are PDF, PCL, PS, SVG, XML (area tree representation),
        Print, AWT, MIF and TXT.
-       The primary output target is PDF. 
+       The primary output target is PDF.
     </p>
     <note>
       The PDF files on this site are created using current CVS.
     </note>
-        <figure width="480" height="260" src="images/document.jpg" alt="Render Diagram" /> 
+        <figure width="480" height="260" src="images/document.jpg" alt="Render Diagram" />
     <p>The latest version of Fop is 0.20.4 and it supports the
        <link href="http://www.w3.org/TR/2001/REC-xsl-20011015/">XSL-FO Version 1.0
        W3C Recommendation</link>.
-       You can <link href="download.html">download</link> 
-       Fop including a precompiled version, the source code and many example files to 
+       You can <link href="download.html">download</link>
+       Fop including a precompiled version, the source code and many example files to
        get you started. Pointers to introductions into xsl:fo can be found in the
-       <link href="resources.html">resources</link> section. Please be aware, that 
+       <link href="resources.html">resources</link> section. Please be aware, that
        Fop is at the moment not a full implementation of the basic conformance level
        of the xsl:fo standard. You can find a list of supported flow objects and properties
        in the section <link href="implemented.html">Features</link> and in section
diff --git a/src/documentation/content/xdocs/license.xml b/src/documentation/content/xdocs/license.xml
index 52fb41edc..bf1bdc4ec 100644
--- a/src/documentation/content/xdocs/license.xml
+++ b/src/documentation/content/xdocs/license.xml
@@ -12,7 +12,7 @@
   <section>
     <title>The Apache Software License, Version 1.1</title>
     <p> Copyright (C) 1999-2001 The Apache Software Foundation. All rights reserved.</p>
-    <p> Redistribution and use in source and binary forms, with or without modification, 
+    <p> Redistribution and use in source and binary forms, with or without modification,
         are permitted provided that the following conditions are met:</p>
     <p>1. Redistributions of  source code must  retain the above copyright  notice,
         this list of conditions and the following disclaimer.
@@ -54,7 +54,7 @@
     <p>
        This software  consists of voluntary contributions made  by many individuals
        on  behalf of the Apache Software  Foundation and was  originally created by
-       James Tauber &lt;jtauber@jtauber.com>. For more  information on the Apache 
+       James Tauber &lt;jtauber@jtauber.com>. For more  information on the Apache
        Software Foundation, please see <link href="http://www.apache.org/">http://www.apache.org/</link>.
     </p>
   </section>
diff --git a/src/documentation/content/xdocs/output.xml b/src/documentation/content/xdocs/output.xml
index 528c01605..fee304c53 100644
--- a/src/documentation/content/xdocs/output.xml
+++ b/src/documentation/content/xdocs/output.xml
@@ -3,7 +3,7 @@
     "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
 
 <!-- Output Formats: Renderers -->
-<document> 
+<document>
     <header>
         <title>Output</title>
         <subtitle>Notes about Output Formats: Renderers</subtitle>
@@ -27,7 +27,7 @@ different renderers.
     </p>
 <section>
   <title>Common Information</title>
-    <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.
@@ -39,7 +39,7 @@ output format and associated data and flow.
     </p>
     <p>
 Fonts and Layout - some formats (eg. PDF and AWT) rely on different
-font information. The fonts for these outputs have different sizes 
+font information. The fonts for these outputs have different sizes
 for the same point size. This means that the layout can be quite
 different for the same fo document.
     </p>
diff --git a/src/documentation/content/xdocs/relnotes.xml b/src/documentation/content/xdocs/relnotes.xml
index 3f38ac19b..07ab384b2 100644
--- a/src/documentation/content/xdocs/relnotes.xml
+++ b/src/documentation/content/xdocs/relnotes.xml
@@ -21,7 +21,7 @@
          (which includes Crimson and Xalan).
        </li>
        <li>The following JARs have been updated:
-         Xerces to version 2.0.1, Xalan to version 2.3.1 and Batik to version 1.5beta2. 
+         Xerces to version 2.0.1, Xalan to version 2.3.1 and Batik to version 1.5beta2.
       </li>
       <li>Fop has been compiled with Jimi support this time
         but you still have to download
diff --git a/src/documentation/content/xdocs/resources.xml b/src/documentation/content/xdocs/resources.xml
index 289e68b14..d83145499 100644
--- a/src/documentation/content/xdocs/resources.xml
+++ b/src/documentation/content/xdocs/resources.xml
@@ -1,13 +1,13 @@
 <?xml version="1.0" standalone="no"?>
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
     "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
-  
+
 <!-- FOP Relevant Specifications and links -->
-<document> 
+<document>
   <header>
     <title>Resources</title>
     <subtitle>Resources useful for developing and using FOP</subtitle>
-  </header> 
+  </header>
   <body>
 <section>
   <title>FOP Relevant Specifications and Links</title>
diff --git a/src/documentation/content/xdocs/status.xml b/src/documentation/content/xdocs/status.xml
index d591ed3b1..48e866650 100644
--- a/src/documentation/content/xdocs/status.xml
+++ b/src/documentation/content/xdocs/status.xml
@@ -3,13 +3,13 @@
     "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
 
 <!-- Status -->
- 
+
 <document>
     <header>
         <title>FOP Status</title>
         <subtitle>Current Status of FOP</subtitle>
     </header>
-    
+
     <body>
   <section>
     <title>Status</title>
@@ -21,7 +21,7 @@ maintenance releases while the development is done to address various
 performance and design issues.
 </p>
   </section>
-  
+
   <section>
     <title>Development Status</title>
 <p>
@@ -30,7 +30,7 @@ performance. The new design focusing on making it possible to be conformant
 to the spec and be able to handle large documents. The development effort
 is roughly 50% towards a developers release.
 </p>
-<p> 
+<p>
 The developers release should have the following: similar functionality
 to previous FOP releases, a rough API and a suitable design for
 developers to work on more functionality.
@@ -48,7 +48,7 @@ to predict any dates.
       <tr><td>xalan.jar</td><td>883 kb</td></tr>
       <tr><td>xerces.jar</td><td>1,809 kb</td></tr>
     </table>
-    
+
 <p><strong>Lines of code</strong> using "find . -iname "*.java" | xargs cat | wc -l"</p>
     <table>
       <tr><td>org.apache.fop.*</td><td>67479</td></tr>
diff --git a/src/documentation/content/xdocs/testing.xml b/src/documentation/content/xdocs/testing.xml
index 219953d5a..977170338 100644
--- a/src/documentation/content/xdocs/testing.xml
+++ b/src/documentation/content/xdocs/testing.xml
@@ -14,11 +14,11 @@
   <section>
     <title>Running and Using Tests</title>
     <p>
-Testing is an important part of getting FOP to operate correctly and conform to the 
+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  
+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>
@@ -26,7 +26,7 @@ is to have the tests run to verfiy that nothing working has been broken.
 To setup the testing the developer must place a reference fop.jar in the
 "&lt;cvs_repository>/test/reference/" directory. This jar will be dynamically
 loaded to create the reference output.
-    </p> 
+    </p>
   </section>
 
   <section>
@@ -42,9 +42,9 @@ Then you can uncomment the lines in the build.xml file in the test target and it
   <section>
     <title>Writing a Test</title>
     <p>
-A test belongs to one of a few catagories. A basic test should excercise one 
+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  
+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>
diff --git a/src/documentation/sitemap.xmap b/src/documentation/sitemap.xmap
index b7dc776a9..ab029291e 100644
--- a/src/documentation/sitemap.xmap
+++ b/src/documentation/sitemap.xmap
@@ -33,7 +33,7 @@
       <!-- transformer-factory>org.apache.xalan.xsltc.trax.TransformerFactoryImpl</transformer-factory -->
     </map:transformer>
   </map:transformers>
-      
+
   <map:readers default="resource">
    <map:reader name="resource"       src="org.apache.cocoon.reading.ResourceReader"/>
   </map:readers>
@@ -103,7 +103,7 @@
      <map:pipeline name="profile-noncaching" src="org.apache.cocoon.components.profiler.ProfilingNonCachingProcessingPipeline"/>
      -->
   </map:pipelines>
-  
+
  </map:components>
 
 <!-- =========================== Views =================================== -->
@@ -125,7 +125,7 @@
      <map:parameter name="isfaq" value="{isfaq}"/>
      <map:parameter name="nopdf" value="{nopdf}"/>
      <map:parameter name="path" value="{path}"/>
-     <!-- Can set an alternative project skinconfig here 
+     <!-- Can set an alternative project skinconfig here
      <map:parameter name="config-file" value="../../../../skinconf.xml"/>
      -->
    </map:transform>
@@ -149,7 +149,7 @@
 <!-- =========================== Pipelines ================================= -->
 
  <map:pipelines>
-  
+
   <!-- Pipeline that manages the internal URI space
        For the external URI space manager, see the next pipeline. -->
   <map:pipeline internal-only="true">
@@ -216,7 +216,7 @@
 
 <!-- ========================== FOP Additions ========================== -->
 
-   <map:match pattern="body-compliance.xml"> 
+   <map:match pattern="body-compliance.xml">
      <map:generate type="file-nolabel" src="content/xdocs/compliance.xml"/>
      <map:transform src="resources/stylesheets/compliance2document.xsl" label="content"/>
      <map:call resource="skinit">
@@ -386,15 +386,15 @@
    </map:match>
 
    <map:match pattern="**">
-   
+
     <!-- if the file is present verbatim as content, give that to the user... -->
     <map:act type="resource-exists">
      <map:parameter name="url" value="content/{1}"/>
      <map:read src="content/{../1}"/>
     </map:act>
-   
+
    <!-- ... otherwise try to generate it using these rules.  -->
-  
+
   <map:match pattern="apachestats">
     <map:generate type="html"
                   src="http://www.apache.org/~rubys/stats/xml.apache.org/">
@@ -404,7 +404,7 @@
     <map:serialize type="xml"/>
   </map:match>
 
-     
+
    <map:match pattern="*.html">
     <map:aggregate element="site">
      <map:part src="cocoon:/book-{1}.xml"/>
@@ -594,7 +594,7 @@
    </map:match>
 
    </map:match>
-   
+
   </map:pipeline>
  </map:pipelines>
 
diff --git a/src/documentation/skinconf.xml b/src/documentation/skinconf.xml
index 82d35a62f..cc1b1d99d 100644
--- a/src/documentation/skinconf.xml
+++ b/src/documentation/skinconf.xml
@@ -16,7 +16,7 @@ jefft@apache.org
   <!ELEMENT credit (name, url, image, width?, height?)>
   <!ELEMENT disable-search (#PCDATA)>
   <!ELEMENT searchsite-domain (#PCDATA)>
-  <!ELEMENT searchsite-name (#PCDATA)>  
+  <!ELEMENT searchsite-name (#PCDATA)>
   <!ELEMENT project-name (#PCDATA)>
   <!ELEMENT project-url (#PCDATA)>
   <!ELEMENT project-logo (#PCDATA)>
@@ -45,7 +45,7 @@ jefft@apache.org
   <!-- Do we want the Google search box? -->
   <disable-search>false</disable-search>
   <searchsite-domain>xml.apache.org</searchsite-domain>
-  <searchsite-name>Apache XML</searchsite-name>  
+  <searchsite-name>Apache XML</searchsite-name>
 
 
   <project-name>FOP</project-name>