Fop WebSite: Fixed obsolete URL for public DTDs plus refer to latest version of each dtd

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

src/documentation/content/xdocs/bugs.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 
 <document>
   <header>

src/documentation/content/xdocs/dev/design/areas.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 <document>
   <header>
     <title>FOP Design: Area Tree</title>

src/documentation/content/xdocs/dev/design/breakpos.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 
 <document>
   <header>

src/documentation/content/xdocs/dev/design/configuration.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd" [
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd" [
 <!ENTITY lsquo   "&#x2018;">
 <!ENTITY rsquo   "&#x2019;">
 <!ENTITY ldquo   "&#x201C;">
@@ -52,7 +51,7 @@ well-formed.</p>
     <section id="general-available">
       <title>Making Configuration Available to FOP</title>
       <p>After creating your configuration file, you must tell FOP how
-to find it.</p> 
+to find it.</p>
 
       <section id="command-line">
         <title>From the Command Line</title>
@@ -67,7 +66,7 @@ configuration file as the option value.</p>
 <code>org.apache.avalon.framework.configuration</code>. For detailed
 information, see the documentation of the package.</p>
         <p>If you want to use a user configuration file with your
-embedded program, you need to build an Avalon configuration 
+embedded program, you need to build an Avalon configuration
 object from it, and register that with the user agent:</p>
 
         <source>FOUserAgent foUserAgent;
@@ -132,17 +131,17 @@ which are provided by this font file. See the example
 configuration file for details.</dd>
       </dl>
       <p>The example configuration file provides for details about the
-other renderers.</p> 
+other renderers.</p>
     </section>
 
     <section id="hyphenation-dir">
       <title>Hyphenation</title>
       <p>When FOP needs to load a hyphenation file for a certain
-language and country combination, it follows these steps.</p> 
+language and country combination, it follows these steps.</p>
       <ol>
         <li>FOP searches for the compiled hyphenation file (extension
 <code>hyp</code> in the directory <code>hyph</code> in the
-class path.</li> 
+class path.</li>
         <li>FOP searches for the compiled or the XML hyphenation file
 in a user directory. At the time of this writing FOP does not
 read the configuration file for the user directory. It always
@@ -195,7 +194,7 @@ org.apache.commons.logging.simplelog.log.org.apache.fop.pdf=trace
 </source>
       <p>FOP uses several named loggers. When you set the logging level
 for all loggers to &ldquo;info&rdquo;, you get a decent small amount
-of information 
+of information
 about application progress. The debugging and especially the trace
 levels produce a lot of output. If you need these logging levels,
 it is wise to switch them on for one or several specific loggers. The

src/documentation/content/xdocs/dev/design/embedding.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 
 <document>
   <header>

src/documentation/content/xdocs/dev/design/extending.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 
 <document>
   <header>

src/documentation/content/xdocs/dev/design/fotree.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 <document>
   <header>
     <title>FOP Design: FO Tree</title>

src/documentation/content/xdocs/dev/design/images.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 
 <document>
   <header>

src/documentation/content/xdocs/dev/design/index.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 <document>
   <header>
     <title>FOP Design: Introduction</title>

src/documentation/content/xdocs/dev/design/layout.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 <document>
   <header>
     <title>FOP Design: Layout</title>
@@ -73,7 +72,7 @@ Other cases are tables and lists, these objects will also have layout managers t
       <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. 
+      <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>
       <p>The objects in the area tree that are organised by the manager will mostly contain the information about there layout such as spacing and keeps, this information will be thrown away once the layout for a page is finalised.</p>
@@ -164,7 +163,7 @@ The body region should be in the order before float, main then footnote.</p>
       <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>Each word (group of adjacent character inline areas) will have keeps based on hyphenation. 
+      <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>
     </section>
@@ -280,7 +279,7 @@ Then the next equally low keep is found to determine if the spacing will be clos
         <title>Before Floats/Footnotes</title>
         <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. 
+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  onsidered.</p>
       </section>
@@ -382,12 +381,12 @@ that requires further analysis.</td>
           <tr>
             <td>Border collapsing on tables</td>
             <td>Low</td>
-            <td>RenderX hasnt implemented this (17/03/04)</td> 
+            <td>RenderX hasnt 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? 
+            <td>Not sure what Joerg means by this, border collapse priorties?
 Dashed and dotted borders have been implemented in PDF</td>
           </tr>
           <tr>

src/documentation/content/xdocs/dev/design/optimise.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 
 <document>
   <header>

src/documentation/content/xdocs/dev/design/parsing.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 <document>
   <header>
     <title>FOP Design: Input Parsing</title>

src/documentation/content/xdocs/dev/design/pdf-library.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 
 <document>
   <header>

src/documentation/content/xdocs/dev/design/properties.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 <document>
   <header>
     <title>FOP Design: Properties</title>

src/documentation/content/xdocs/dev/design/renderers.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 <document>
   <header>
     <title>FOP Design: Renderers</title>

src/documentation/content/xdocs/dev/design/startup.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 <document>
   <header>
     <title>FOP Design: Startup, Environment, Control</title>

src/documentation/content/xdocs/dev/design/svg.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 
 <document>
   <header>

src/documentation/content/xdocs/dev/design/useragent.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 
 <document>
   <header>

src/documentation/content/xdocs/dev/extensions.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 
 <document>
   <header>
@@ -58,7 +57,7 @@ The examples for SVG and pdfoutline.fo show how this can be done.
 The pdf documents on the FOP site use this extension.
 See also <link href="../examples.html">Examples</link> for more examples.</li>
           <li>Put your jar file in the classpath</li>
-          <li>Run FOP using your XSL-FO file as input.</li> 
+          <li>Run FOP using your XSL-FO file as input.</li>
         </ol>
     </section>
   </body>

src/documentation/content/xdocs/dev/faq.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE faqs PUBLIC "-//APACHE//DTD FAQ V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/faq-v12.dtd">
+<!DOCTYPE faqs PUBLIC "-//APACHE//DTD FAQ V1.3//EN" "http://forrest.apache.org/dtd/faq-v13.dtd">
 
 <faqs title="FOP Development: FAQ">
   <part id="part_general">

src/documentation/content/xdocs/dev/fonts.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 
 <document>
   <header>

src/documentation/content/xdocs/dev/implement.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 <document>
   <header>
     <title>FOP Development: Implementation Overview</title>

src/documentation/content/xdocs/dev/release.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 <document>
   <header>
     <title>FOP Development: Release Mechanics</title>

src/documentation/content/xdocs/dev/rtflib.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 <document>
   <header>
     <title>FOP Development: RTFLib (jfor)</title>

src/documentation/content/xdocs/dev/svg.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 
 <document>
   <header>

src/documentation/content/xdocs/examples.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 
 <document>
   <header>

src/documentation/content/xdocs/faq.xml

@@ -16,7 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE faqs PUBLIC "-//APACHE//DTD FAQ V1.1//EN" "http://forrest.apache.org/dtd/faq-v12.dtd">
+<!DOCTYPE faqs PUBLIC "-//APACHE//DTD FAQ V1.3//EN" "http://forrest.apache.org/dtd/faq-v13.dtd">
 
 <faqs title="FOP FAQ">
   <part id="part-general">
@@ -136,7 +136,7 @@
       <question>When is the next released planned?</question>
       <answer>
         <p>
-          When it's ready and the committers have enough time to go through 
+          When it's ready and the committers have enough time to go through
           the time-consuming process of creating a release. We
           released version 0.95 on August 6th, 2008, and intend to
           release version 1.0 once we consider it "feature complete", major
@@ -410,7 +410,7 @@ import javax.xml.transform.ErrorListener;
 import javax.xml.transform.TransformerException;
 
 public class DefaultErrorListener implements ErrorListener {
-    
+
     public void warning(TransformerException exc) {
         System.err.println(exc.toString());
     }
@@ -436,8 +436,8 @@ public class DefaultErrorListener implements ErrorListener {
         Discarding font cache file."</question>
       <answer>
         <p>
-          This message is a warning that FOP failed to read from the Font cache. 
-          Which means any Font auto detection or Font directories will be re-scanned. 
+          This message is a warning that FOP failed to read from the Font cache.
+          Which means any Font auto detection or Font directories will be re-scanned.
           So this failure doesn't break anything.
         </p>
         <p>
@@ -651,34 +651,34 @@ Check the following:</p>
     <faq id="table-cell-wrap">
       <question>The contents of table cells don’t wrap</question>
       <answer>
-        <p>You probably have <code>keep-together="always"</code> set on the table cell. See <link 
+        <p>You probably have <code>keep-together="always"</code> set on the table cell. See <link
             href="#keep-together">next question</link>.</p>
       </answer>
     </faq>
     <faq id="keep-together">
-      <question>FOP 0.95 and FOP 0.94 behave differently when <code>keep-together="always"</code> 
+      <question>FOP 0.95 and FOP 0.94 behave differently when <code>keep-together="always"</code>
         is set on table cells</question>
       <answer>
-        <p>Support for inline-level keeps has been added in FOP 0.95, and setting 
-          <code>keep-together="always"</code> also implicitly sets 
+        <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 
+          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>
       </answer>
     </faq>
     <faq id="row-height-constraint">
-      <question>FOP tells me: "The contents of row 1 are taller than they should be". 
+      <question>FOP tells me: "The contents of row 1 are taller than they should be".
         What does that mean?</question>
       <answer>
         <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 
+          the content is higher than the specified height. By setting "height" (a so-called
+          corresponding property) you
           <link href="http://www.w3.org/TR/xsl11/#d0e4413">implicitely set</link>
-          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: 
+          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[min=opt=max=14000]".
         </p>
         <p>
@@ -722,16 +722,16 @@ Check the following:</p>
       <answer>
         <p>
           (Applies to version 0.90 and later)
-          No, although you might easily think so. The problem has to do 
-          with property inheritance of the start-indent and end-indent 
-          properties to which the margin properties are mapped. Apache 
-          FOP strictly adheres to the XSL-FO specification here which many 
-          other commercial FO implementations don't do to better meet end-user 
-          expectations. You can make FOP behave like these if you set 
-          <code>setBreakIndentInheritanceOnReferenceAreaBoundary(true)</code> 
+          No, although you might easily think so. The problem has to do
+          with property inheritance of the start-indent and end-indent
+          properties to which the margin properties are mapped. Apache
+          FOP strictly adheres to the XSL-FO specification here which many
+          other commercial FO implementations don't do to better meet end-user
+          expectations. You can make FOP behave like these if you set
+          <code>setBreakIndentInheritanceOnReferenceAreaBoundary(true)</code>
           on the FOUserAgent. The better way is to reset <code>start-indent</code>
-          and <code>end-indent</code> to "0pt" on table-body or block-container. 
-          For further details, please consult the 
+          and <code>end-indent</code> to "0pt" on table-body or block-container.
+          For further details, please consult the
           <link href="http://wiki.apache.org/xmlgraphics-fop/IndentInheritance">Wiki page on Indent Inheritance</link>.
         </p>
       </answer>
@@ -906,19 +906,19 @@ Can I control this?</question>
       <answer>
         <p>
           This phenomenon occurs since FOP 0.92 beta. It surfaced due to a change in the handling of non-FO namespaces. It's not a
-          bug in FOP, but rather in the dependent packages: Apache Batik, Apache Xalan-J and SAXON. The bug in Apache Batik will be 
+          bug in FOP, but rather in the dependent packages: Apache Batik, Apache Xalan-J and SAXON. The bug in Apache Batik will be
           fixed in the next release. In the latest release of Apache Xalan-J, the bug is already fixed. It only occurs in the Xalan
           version bundled with Sun's JVM, because Sun uses a rather old version.
         </p>
         <p>
-          Bug description: In a namespace-enabled Level 3 DOM, an attribute in the default namespace must be set with 
-          <code>"null"</code> as the value for the namespace URI. SAX, on the other side, uses an empty string ("") to designate 
-          the default namespace. Many packages appear to not properly handle this difference in which case they still use the empty 
+          Bug description: In a namespace-enabled Level 3 DOM, an attribute in the default namespace must be set with
+          <code>"null"</code> as the value for the namespace URI. SAX, on the other side, uses an empty string ("") to designate
+          the default namespace. Many packages appear to not properly handle this difference in which case they still use the empty
           string as the namespace URI parameter for <code>org.w3c.dom.Element.setAttributeNS()</code>.
         </p>
         <p>
-          Work-around: Use the latest version of Apache Xalan-J. Note that starting with JDK 1.4 it's not enough to replace Xalan-J 
-          on the normal application classpath and you need to override the Xalan-J version bundled with the Sun JVM using the 
+          Work-around: Use the latest version of Apache Xalan-J. Note that starting with JDK 1.4 it's not enough to replace Xalan-J
+          on the normal application classpath and you need to override the Xalan-J version bundled with the Sun JVM using the
           <link href="http://java.sun.com/j2se/1.4.2/docs/guide/standards/">Endorsed Standards Override Mechanism</link>, i.e.
           you must place Xalan-J in the <code>"lib/endorsed"</code> directory of your JRE.
         </p>
@@ -1020,8 +1020,8 @@ Can I control this?</question>
         <p>
           FOP versions 0.93 and later support the starting-state property of the XSL 1.1
           <link href="http://www.w3.org/TR/xsl11/#fo_bookmark">fo:bookmark</link>
-          element which can be used for this. The color, font-style and 
-          font-weight properties on 
+          element which can be used for this. The color, font-style and
+          font-weight properties on
           <link href="http://www.w3.org/TR/xsl11/#fo_bookmark-title">fo:bookmark-title</link>
           are not yet supported, though.
         </p>

src/documentation/content/xdocs/fo.xml

@@ -16,8 +16,8 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
+
 <document>
   <header>
     <title>XSL-FO Input</title>
@@ -30,7 +30,7 @@
       <p>
         FOP uses XSL-FO as input.
 It is the responsibility of the user to make sure that the XSL-FO submitted to FOP is correct.
-The tutorial items presented here are not comprehensive, but are of the FAQ variety. Another 
+The tutorial items presented here are not comprehensive, but are of the FAQ variety. Another
 good FAQ is <fork href="http://www.dpawson.co.uk/xsl/">Dave Pawson's XSL FAQ</fork>.
       </p>
     </section>
@@ -192,8 +192,8 @@ Here is a small, self-contained document centering an image on a page:
       <section id="fo-right-align-table-horizon">
         <title>Right-Aligning (Tables)</title>
         <p>
-          To right-align a table, you can use the same approach as above for centering tables. 
-          Just remove the last table-column element which causes all the left-over space not 
+          To right-align a table, you can use the same approach as above for centering tables.
+          Just remove the last table-column element which causes all the left-over space not
           used by the columns with a fixed column-width to be assigned to the first column which
           effectively right-aligns the table.
         </p>

src/documentation/content/xdocs/index.xml

@@ -16,7 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "http://forrest.apache.org/dtd/document-v11.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 
 <document>
   <header>

src/documentation/content/xdocs/license.xml

@@ -16,8 +16,7 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
-    "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
 
 <document>
   <header>
@@ -28,7 +27,7 @@
 <section>
   <title>License</title>
   <p>
-    All new Apache FOP releases will be licensed under the <strong>Apache License, version 2.0</strong>. 
+    All new Apache FOP releases will be licensed under the <strong>Apache License, version 2.0</strong>.
     Releases until version 0.20.5 are released unter the Apache License, version 1.1.
   </p>
   <p>

src/documentation/content/xdocs/tabs.xml

@@ -16,9 +16,9 @@
   limitations under the License.
 -->
 <!-- $Id$ -->
-<!DOCTYPE tabs PUBLIC "-//APACHE//DTD Cocoon Documentation Tab V1.0//EN"
-    "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/tab-cocoon-v10.dtd?view=co">
-    
+<!DOCTYPE tabs PUBLIC "-//APACHE//DTD Cocoon Documentation Tab V1.1//EN"
+    "http://forrest.apache.org/dtd/tab-cocoon-v11.dtd">
+
 <tabs software="FOP" title="FOP" copyright="@year@ The Apache Software Foundation" xmlns:xlink="http://www.w3.org/1999/xlink">
   <tab label="Home" dir=""/>
   <tab label="Version 0.94" dir="0.94/"/>