forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r357603 [6/11] - in /forrest/site: ./ docs_0_60/ docs_0_60/howto/ docs_0_60/howto/bugzilla-patch/ docs_0_70/ docs_0_70/howto/ docs_0_70/howto/cvs-ssh/ docs_0_80/ docs_0_80/howto/ docs_0_80/howto/cvs-ssh/ dtdx/ pluginDocs/plugins_0_70/ plugi...
Date Mon, 19 Dec 2005 01:33:15 GMT
Modified: forrest/site/docs_0_70/validation.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/validation.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/validation.html (original)
+++ forrest/site/docs_0_70/validation.html Sun Dec 18 17:31:25 2005
@@ -348,7 +348,7 @@
         By default, Forrest will validate your XML before generating
         HTML or a webapp from it, and fail if any XML files are not valid.
         Validation can be performed manually by doing
-        '<span class="codefrag ">forrest validate</span>' in the project root directory.
+        '<span class="codefrag">forrest validate</span>' in the project root directory.
       </p>
 <p>
         For an XML file to be valid, it <em>must</em> have a document type
@@ -362,7 +362,7 @@
         project.  In validated sections, it is possible for projects to specify
         exactly what files they want (and don't want) validated.  Forrest
         validation is controlled through a set of properties in
-        <span class="codefrag ">forrest.properties</span>:
+        <span class="codefrag">forrest.properties</span>:
       </p>
 <pre class="code">
 ##############
@@ -389,18 +389,18 @@
       </pre>
 <p>
         For example, to avoid validating
-        <span class="codefrag ">${project.xdocs-dir}</span>/slides.xml and everything inside the
-        <span class="codefrag ">${project.xdocs-dir}/manual/</span> directory, add this to
-        <span class="codefrag ">forrest.properties</span>:
+        <span class="codefrag">${project.xdocs-dir}</span>/slides.xml and everything inside the
+        <span class="codefrag">${project.xdocs-dir}/manual/</span> directory, add this to
+        <span class="codefrag">forrest.properties</span>:
       </p>
 <pre class="code">forrest.validate.xdocs.excludes=slides.xml, manual/**</pre>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-        The <span class="codefrag ">failonerror</span> properties only work for files validated
+        The <span class="codefrag">failonerror</span> properties only work for files validated
         with Ant's &lt;xmlvalidate&gt; and not (yet) for those validated
-        with &lt;jing&gt;, where <span class="codefrag ">failonerror</span> defaults to
-        <span class="codefrag ">true</span>.
+        with &lt;jing&gt;, where <span class="codefrag">failonerror</span> defaults to
+        <span class="codefrag">true</span>.
       </div>
 </div>
 </div>
@@ -412,12 +412,12 @@
 <p>
         Forrest provides an <a href="http://www.oasis-open.org/committees/entity/spec.html">OASIS Catalog</a>
         [see <a href="http://xml.apache.org/commons/components/resolver/resolver-article.html">tutorial</a>]
-        <span class="codefrag ">forrest/main/webapp/resources/schema/catalog.xcat</span>
+        <span class="codefrag">forrest/main/webapp/resources/schema/catalog.xcat</span>
         as a means of associating public identifiers
-        (e.g. <span class="codefrag ">-//APACHE//DTD Documentation V1.1//EN</span> above) with DTDs.
+        (e.g. <span class="codefrag">-//APACHE//DTD Documentation V1.1//EN</span> above) with DTDs.
         If you <a href="../docs_0_70/your-project.html#adding_new_content_type">add a new content type</a>, you
-        should add the DTD to <span class="codefrag ">${project.schema-dir}/dtd/</span> and add
-        an entry to the <span class="codefrag ">${project.schema-dir}/catalog.xcat</span> file.  This
+        should add the DTD to <span class="codefrag">${project.schema-dir}/dtd/</span> and add
+        an entry to the <span class="codefrag">${project.schema-dir}/catalog.xcat</span> file.  This
         section describes the details of this process.
       </p>
 <a name="N1006A"></a><a name="Creating+or+extending+a+DTD"></a>
@@ -447,13 +447,13 @@
         </pre>
 <p>
           The document-v13 entities are defined in a reusable 'module':
-          <span class="codefrag ">forrest/main/webapp/resources/schema/dtd/document-v13.mod</span>
+          <span class="codefrag">forrest/main/webapp/resources/schema/dtd/document-v13.mod</span>
           The
-          <span class="codefrag ">forrest/main/webapp/resources/schema/dtd/document-v13.dtd</span>
+          <span class="codefrag">forrest/main/webapp/resources/schema/dtd/document-v13.dtd</span>
           file provides a full description and basic example of how to pull in
           modules.  In our example, our DTD reuses modules
-          <span class="codefrag ">common-charents-v10.mod</span> and
-          <span class="codefrag ">document-v13.mod</span>.  Here is the full DTD, with
+          <span class="codefrag">common-charents-v10.mod</span> and
+          <span class="codefrag">document-v13.mod</span>.  Here is the full DTD, with
           explanation to follow.
         </p>
 <pre class="code">
@@ -528,20 +528,20 @@
 &lt;!-- =============================================================== --&gt;
         </pre>
 <p>This custom DTD should be placed in your project resources
-        directory at <span class="codefrag ">src/documentation/resources/schema/dtd/</span>
+        directory at <span class="codefrag">src/documentation/resources/schema/dtd/</span>
 </p>
 <p>
           The &lt;!ENTITY % ... &gt; blocks are so-called 
           <a href="http://www.xml.com/axml/target.html#dt-PERef">parameter
             entities</a>.  They are like macros, whose content will be
           inserted when a parameter-entity reference, like
-          <span class="codefrag ">%common-charents;</span> or <span class="codefrag ">%document;</span> is
+          <span class="codefrag">%common-charents;</span> or <span class="codefrag">%document;</span> is
           inserted.
         </p>
 <p>
           In our DTD, we first pull in the 'common-charents' entity, which
           defines character symbol sets.  We then define the 'document'
-          entity.  However, before the <span class="codefrag ">%document;</span> PE reference, we
+          entity.  However, before the <span class="codefrag">%document;</span> PE reference, we
           first override the 'local.section' entity.  This is a hook into
           document-v13.mod.  By setting its value to '|release', we declare
           that our &lt;release&gt; element is to be allowed wherever "local
@@ -573,7 +573,7 @@
           "download-v10.dtd"&gt;
         </pre>
 <p>
-          We only care about the quoted section after <span class="codefrag ">PUBLIC</span>, called
+          We only care about the quoted section after <span class="codefrag">PUBLIC</span>, called
           the "public identifier", which globally identifies our document type.
           We cannot rely on the subsequent "system identifier" part
           ("download-v10.dtd"), because as a relative reference it is liable to
@@ -590,21 +590,21 @@
 </div>
 <p>
           Forrest provides a standard catalog file at
-          <span class="codefrag ">forrest/main/webapp/resources/schema/catalog.xcat</span>
+          <span class="codefrag">forrest/main/webapp/resources/schema/catalog.xcat</span>
           for the document
           types that Forrest provides.  Projects can augment this with their
           own catalog file located in
-          <span class="codefrag ">${project.schema-dir}/catalog.xcat</span> to use it you must
+          <span class="codefrag">${project.schema-dir}/catalog.xcat</span> to use it you must
 	    specify either the path (full or relative) to your 
-	    <span class="codefrag ">catalog.xcat</span> in the <span class="codefrag ">CatalogManager.properties</span>
+	    <span class="codefrag">catalog.xcat</span> in the <span class="codefrag">CatalogManager.properties</span>
 	    file. If you provide a relative path you must set the property 
-	    <span class="codefrag ">relative-catalogs</span> to "yes".
+	    <span class="codefrag">relative-catalogs</span> to "yes".
 	  </p>
 <p>
-          When Cocoon starts, it reads the <span class="codefrag ">CatalogManager.properties</span> file from your
-          <span class="codefrag ">project.classes-dir</span>. This is usually src/documentation/classes/
-          but you can change this in <span class="codefrag ">forrest.properties</span>. When you seed 
-          a new site using <span class="codefrag ">forrest seed-site</span> a sample catalog file
+          When Cocoon starts, it reads the <span class="codefrag">CatalogManager.properties</span> file from your
+          <span class="codefrag">project.classes-dir</span>. This is usually src/documentation/classes/
+          but you can change this in <span class="codefrag">forrest.properties</span>. When you seed 
+          a new site using <span class="codefrag">forrest seed-site</span> a sample catalog file
           is placed in the site structure, you can use this as a template for your
           own files.
         </p>
@@ -623,17 +623,17 @@
 <p>
           The format is described in <a href="http://www.oasis-open.org/committees/entity/spec.html">the
           spec</a>, and is fairly simple and very powerful.
-          The "<span class="codefrag ">public</span>" elements map
+          The "<span class="codefrag">public</span>" elements map
           a public identifier to a DTD (relative to the catalog file).
         </p>
 <p>
           We now have a custom DTD and a catalog mapping which lets both
           Forrest and Cocoon
-          locate the DTD.  Now if we were to run <span class="codefrag ">'forrest validate'</span>
+          locate the DTD.  Now if we were to run <span class="codefrag">'forrest validate'</span>
           our download file would validate along with all the others.  If
-          something goes wrong, try running <span class="codefrag ">'forrest -v validate'</span> to
+          something goes wrong, try running <span class="codefrag">'forrest -v validate'</span> to
           see the error in more detail. Remember to raise the "verbosity"
-          level in <span class="codefrag ">cocoon.xconf</span> if you suspect problems
+          level in <span class="codefrag">cocoon.xconf</span> if you suspect problems
           with your catalog.
         </p>
 </div>
@@ -644,8 +644,8 @@
 <div class="section">
 <p>
         Look at the source of this document
-        (<span class="codefrag ">xdocs/docs/validation.xml</span>) and see how the entity set
-        <span class="codefrag ">"Numeric and Special Graphic"</span> is declared in the
+        (<span class="codefrag">xdocs/docs/validation.xml</span>) and see how the entity set
+        <span class="codefrag">"Numeric and Special Graphic"</span> is declared in the
         document type declaration.
       </p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -687,10 +687,10 @@
       </p>
 <p>
         The RNG grammars to do this are located in the
-        <span class="codefrag ">main/webapp/resources/schema/relaxng</span> directory.
+        <span class="codefrag">main/webapp/resources/schema/relaxng</span> directory.
         If you want to
         know more about this, and perhaps extend it for your own use, then
-        see <span class="codefrag ">main/webapp/resources/schema/relaxng/README.txt</span>
+        see <span class="codefrag">main/webapp/resources/schema/relaxng/README.txt</span>
         and the Ant targets in the various build.xml files.
       </p>
 </div>

Modified: forrest/site/docs_0_70/your-project.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/your-project.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/your-project.html (original)
+++ forrest/site/docs_0_70/your-project.html Sun Dec 18 17:31:25 2005
@@ -454,7 +454,7 @@
 <h5>Permanently Setting The Environment Variables for Linux/Unix</h5>
 <p>Export only changes the variables during that terminal session for that 
            user, this is useful for testing. To permanently add the variable edit either 
-           <span class="codefrag ">/etc/bash.bashrc</span> (for all users) or <span class="codefrag ">~/.bash_profile</span>
+           <span class="codefrag">/etc/bash.bashrc</span> (for all users) or <span class="codefrag">~/.bash_profile</span>
            (for individual users). Add these lines to the end of the file you edit:</p>
 <pre class="code">
       FORREST_HOME=/full/path/to/forrest
@@ -466,9 +466,9 @@
 <a name="N1005B"></a><a name="Windows+2000"></a>
 <h4>Windows 2000</h4>
 <p class="instruction">Go to "My Computer", "Properties", "Advanced", "Environment Variables"</p>
-<p class="instruction">add a new variable <span class="codefrag ">FORREST_HOME</span> as <span class="codefrag ">C:\full\path\to\apache-forrest-0.7</span>
+<p class="instruction">add a new variable <span class="codefrag">FORREST_HOME</span> as <span class="codefrag">C:\full\path\to\apache-forrest-0.7</span>
 </p>
-<p class="instruction">edit <span class="codefrag ">PATH</span> as <span class="codefrag ">%PATH%;%FORREST_HOME%\bin</span>
+<p class="instruction">edit <span class="codefrag">PATH</span> as <span class="codefrag">%PATH%;%FORREST_HOME%\bin</span>
 </p>
 <a name="N10078"></a><a name="In+Windows+XP%3A"></a>
 <h4>In Windows XP:</h4>
@@ -676,16 +676,16 @@
       </pre>
 <p>
         To render this to HTML, type 'forrest'. You should have a HTML site rendered
-        into the <span class="codefrag ">build/site</span> directory:
+        into the <span class="codefrag">build/site</span> directory:
       </p>
 <div id="" style="text-align: center;">
 <img id="" class="figure" alt="New project" src="images/new-project.png" height="356" width="500"></div>
 <p>
         Practise with adding new content. Change to the directory
-        <span class="codefrag ">src/documentation/content/xdocs</span> and copy the file
-        <span class="codefrag ">index.xml</span> to create <span class="codefrag ">my-new-file.xml</span> as a
+        <span class="codefrag">src/documentation/content/xdocs</span> and copy the file
+        <span class="codefrag">index.xml</span> to create <span class="codefrag">my-new-file.xml</span> as a
         new document. Edit it to change some text. Add an entry to 
-        <span class="codefrag ">site.xml</span> by copying one of the other entries and
+        <span class="codefrag">site.xml</span> by copying one of the other entries and
         changing it to suit. Now do 'forrest' to see the result.
       </p>
 </div>
@@ -704,7 +704,7 @@
         If your project already has XML documentation, it may be easier to tell
         Forrest where the XML sources are, rather than rearrange your project
         directories to accommodate Forrest. This can be done by editing
-        <span class="codefrag ">forrest.properties</span> (consult
+        <span class="codefrag">forrest.properties</span> (consult
         the <a href="#Changing_the_layout">Changing the layout</a>
         section for more details).
       </p>
@@ -722,7 +722,7 @@
 <h3 class="underlined_5">Configuring the Forrest skin: skinconf.xml</h3>
 <p>
           Most Forrest skins can be customized through a single XML file,
-          <span class="codefrag ">src/documentation/skinconf.xml</span>, which looks like this:
+          <span class="codefrag">src/documentation/skinconf.xml</span>, which looks like this:
         </p>
 <pre class="code">
 &lt;!--
@@ -886,9 +886,9 @@
 &lt;/skinconfig&gt;
 </pre>
 <p>
-          Customise this file for your project. The <span class="codefrag ">images/</span> directory
+          Customise this file for your project. The <span class="codefrag">images/</span> directory
           mentioned in 'project-logo' and 'group-logo' elements corresponds to the
-          <span class="codefrag ">src/documentation/resources/images</span> directory
+          <span class="codefrag">src/documentation/resources/images</span> directory
           (this mapping is done automatically by the sitemap).
         </p>
 <p>
@@ -903,7 +903,7 @@
           major file types.
         </p>
 <p>
-          The <span class="codefrag ">forrest.properties</span> file maps from your directory
+          The <span class="codefrag">forrest.properties</span> file maps from your directory
           layout to Forrest's. If you generated your site with 'forrest seed', you
           will have one pre-written, with all the entries commented out.
         </p>
@@ -941,7 +941,7 @@
        </pre>
 <p>
          For example, if you wish to keep XML documentation in src/xdocs rather than
-         <span class="codefrag ">src/documentation/content/xdocs</span> simply change the
+         <span class="codefrag">src/documentation/content/xdocs</span> simply change the
          definition for project.xdocs-dir
        </p>
 <pre class="code">project.xdocs-dir=src/xdocs</pre>
@@ -967,7 +967,7 @@
 <div class="label">Note</div>
 <div class="content">
            Internally, Forrest rearranges the specified directory into the default
-           <span class="codefrag ">src/documentation/content/xdocs</span> structure. In the layout above, we have
+           <span class="codefrag">src/documentation/content/xdocs</span> structure. In the layout above, we have
            overlapping directories, so you will end up with duplicate files. This small
            glitch doesn't usually cause problems; just always remember that all links
            are resolved through the sitemap.
@@ -981,14 +981,14 @@
 <div class="section">
 <p>
         Now you can start adding content of your own, in
-        <span class="codefrag ">src/documentation/content/xdocs</span>
+        <span class="codefrag">src/documentation/content/xdocs</span>
       
 </p>
 <a name="N10159"></a><a name="site.xml"></a>
 <h3 class="underlined_5">site.xml</h3>
 <p>
           When adding a new xml document, you would add an entry to the project's
-          <span class="codefrag ">site.xml</span> file. This site.xml is like a site index, and is rendered as
+          <span class="codefrag">site.xml</span> file. This site.xml is like a site index, and is rendered as
           the vertical column of links in the default skin.  Look at Forrest's own
           xdocs for an example.  More detailed info about site.xml is provided in 
           the document <a href="../docs_0_70/linking.html">Menus and Linking</a>.
@@ -996,7 +996,7 @@
 <a name="N1016A"></a><a name="tabs.xml"></a>
 <h3 class="underlined_5">tabs.xml</h3>
 <p>
-          The <span class="codefrag ">tabs.xml</span> file is used to produce the 'tabs'.
+          The <span class="codefrag">tabs.xml</span> file is used to produce the 'tabs'.
           which enable users to quickly jump to sections of your site.
           See the
           <a href="../docs_0_70/linking.html#menu_generation">menu generation</a> documentation
@@ -1008,12 +1008,12 @@
 <p>You can have one or two levels of tabs. The images above show a 
         single level. However, you can create a second level that
         will only be displayed when its parent tab is selected. For example,
-        the <span class="codefrag ">tabs.xml</span> snippet below will display either one or
+        the <span class="codefrag">tabs.xml</span> snippet below will display either one or
         two rows of tabs, depending on which of the top level tabs is selected.
-        The first row will have two tabs: one labelled <span class="codefrag ">How-Tos</span>
-        and the other labelled <span class="codefrag ">Apache XML Projects</span>. When the 
-        <span class="codefrag ">How-Tos</span> tab is selected there will
-        be no second row of tabs. However, when the <span class="codefrag ">Apache XML
+        The first row will have two tabs: one labelled <span class="codefrag">How-Tos</span>
+        and the other labelled <span class="codefrag">Apache XML Projects</span>. When the 
+        <span class="codefrag">How-Tos</span> tab is selected there will
+        be no second row of tabs. However, when the <span class="codefrag">Apache XML
         Projects</span> tab is selected, a second row of tabs will be displayed
         below the first.</p>
 <pre class="code">
@@ -1026,10 +1026,10 @@
 <a name="N10195"></a><a name="images"></a>
 <h3 class="underlined_5">Images</h3>
 <p>
-          Images usually go in the <span class="codefrag ">content/xdocs/images/</span> directory.
+          Images usually go in the <span class="codefrag">content/xdocs/images/</span> directory.
           The default sitemap
-          maps this directory to <span class="codefrag ">images/</span> so image tags will typically look
-          like <span class="codefrag ">&lt;figure src="images/project-logo.png" alt="Project Logo"/&gt;</span> 
+          maps this directory to <span class="codefrag">images/</span> so image tags will typically look
+          like <span class="codefrag">&lt;figure src="images/project-logo.png" alt="Project Logo"/&gt;</span> 
         
 </p>
 </div>
@@ -1065,8 +1065,8 @@
           sources available as "virtual" files.
           (<strong>Note:</strong> Forrest makes extensive use of aggregation
           in the default sitemaps. It also defines a whole-site HTML
-          and PDF, available as the standard names <span class="codefrag ">wholesite.html</span>
-          and <span class="codefrag ">wholesite.pdf</span>.)</li>
+          and PDF, available as the standard names <span class="codefrag">wholesite.html</span>
+          and <span class="codefrag">wholesite.pdf</span>.)</li>
         
 <li>Read content from exotic sources like
         <a href="http://www.rpbourret.com/xml/XMLDBLinks.htm">XML
@@ -1080,13 +1080,13 @@
 </ul>
 <p>
         The Forrest sitemaps are at
-        <span class="codefrag ">main/webapp/*.xmap</span>
+        <span class="codefrag">main/webapp/*.xmap</span>
       
 </p>
 <p>
         You can add pre-processing sitemaps to your project
-        <span class="codefrag ">src/documentation</span> directory (or wherever
-        <span class="codefrag ">${project.sitemap-dir}</span> points to). Get a copy of a simple
+        <span class="codefrag">src/documentation</span> directory (or wherever
+        <span class="codefrag">${project.sitemap-dir}</span> points to). Get a copy of a simple
         sitemap.xmap from a 'forrest seed site'. </p>
 <p>Any match that
         is not handled, passes through to be handled by the default Forrest
@@ -1169,15 +1169,15 @@
     &lt;/section&gt;
   &lt;/body&gt;
 &lt;/document&gt;</pre>
-<p>This file called "<span class="codefrag ">download.xml</span>" would be placed in
+<p>This file called "<span class="codefrag">download.xml</span>" would be placed in
           your content directory (typically
-          <span class="codefrag ">src/documentation/content/xdocs</span>) and an entry added to
-          <span class="codefrag ">site.xml</span>
+          <span class="codefrag">src/documentation/content/xdocs</span>) and an entry added to
+          <span class="codefrag">site.xml</span>
 </p>
 <p>
           To handle these special tags, one would write a stylesheet to convert
           them to the intermediate Forrest xdocs structure. Here is such a stylesheet,
-          called "<span class="codefrag ">download2document.xsl</span>" ...
+          called "<span class="codefrag">download2document.xsl</span>" ...
         </p>
 <pre class="code">&lt;?xml version="1.0" encoding="utf-8"?&gt;
 &lt;xsl:stylesheet
@@ -1214,7 +1214,7 @@
 </pre>
 <p>
             Place this file in the default stylesheets directory,
-            <span class="codefrag ">src/documentation/resources/stylesheets</span> (or wherever
+            <span class="codefrag">src/documentation/resources/stylesheets</span> (or wherever
             ${project.stylesheets-dir} points).
           </p>
 <p>
@@ -1231,7 +1231,7 @@
 </div>
 <p>
             Add the following match to the file
-            <span class="codefrag ">src/documentation/sitemap.xmap</span> ...
+            <span class="codefrag">src/documentation/sitemap.xmap</span> ...
           </p>
 <pre class="code">&lt;?xml version="1.0"?&gt;
 &lt;map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0"&gt;
@@ -1272,7 +1272,7 @@
                    one.</li>
                  
 <li>Place the new DTD in the
-                   <span class="codefrag ">${project.schema-dir}/dtd</span> directory.</li>
+                   <span class="codefrag">${project.schema-dir}/dtd</span> directory.</li>
                  
 <li>Add an XML Catalog to enable a mapping from the
                    DOCTYPE public id to the relevant DTD file.</li>
@@ -1356,7 +1356,7 @@
 </pre>
 <p>
               This is the type of processing that happens in the main
-              <span class="codefrag ">main/webapp/forrest.xmap</span> sitemap. We have
+              <span class="codefrag">main/webapp/forrest.xmap</span> sitemap. We have
               added similar handling to our project sitemap. Basically, this
               uses the <a href="../docs_0_70/cap.html">SourceTypeAction (content aware pipelines)</a>
               to detect the doctype. The new document-v11.dtd needs to be also
@@ -1392,9 +1392,9 @@
 &lt;/map:sitemap&gt;
 </pre>
 <p>You will probably want to copy the core Forrest 
-              <span class="codefrag ">rss2document.xsl</span> to your project,
+              <span class="codefrag">rss2document.xsl</span> to your project,
               customise it to your needs, and refer to it with
-              <span class="codefrag ">src="{project:resources.stylesheets}/rss2document.xsl"</span>.
+              <span class="codefrag">src="{project:resources.stylesheets}/rss2document.xsl"</span>.
               Then of course you would add an entry to site.xml to link
               to weblog.html
             </p>
@@ -1407,10 +1407,10 @@
 <p>
           As Forrest separates content from presentation, we can plug in different
           "skins" to instantly change a site's look and feel.  Forrest provides one
-          primary skin, <span class="codefrag ">pelt</span>, and some others in various
+          primary skin, <span class="codefrag">pelt</span>, and some others in various
           states of development.
-          To change the skin, edit the <span class="codefrag ">forrest.properties</span> file
-          to set <span class="codefrag ">project.skin=leather-dev</span> or some other skin name.
+          To change the skin, edit the <span class="codefrag">forrest.properties</span> file
+          to set <span class="codefrag">project.skin=leather-dev</span> or some other skin name.
           If running in dynamic mode you need to restart Forrest in order to see
           the new skin.
         </p>
@@ -1427,7 +1427,7 @@
 <h3 class="underlined_5">Configuration of skins</h3>
 <p>
           All configuration is done via your project
-          <span class="codefrag ">src/documentation/skinconf.xml</span> file.
+          <span class="codefrag">src/documentation/skinconf.xml</span> file.
           It contains many comments to describe each capability.
           Please read those, there is no point repeating here.
           </p>
@@ -1441,14 +1441,14 @@
           </p>
 <p>
             Projects can define their own skin in the
-            <span class="codefrag ">src/documentation/skins</span> directory (or wherever
-            <span class="codefrag ">${project.skins-dir}</span> points). The default sitemap assumes a
+            <span class="codefrag">src/documentation/skins</span> directory (or wherever
+            <span class="codefrag">${project.skins-dir}</span> points). The default sitemap assumes a
             certain skin layout, so the easiest way to create a new skin is by
             copying an existing Forrest skin.  For example, copy
-            <span class="codefrag ">main/webapp/skins/pelt</span>
+            <span class="codefrag">main/webapp/skins/pelt</span>
             to your project area at
-            <span class="codefrag ">src/documentation/skins/my-fancy-skin</span> and add
-            <span class="codefrag ">project.skin=my-fancy-skin</span> to forrest.properties
+            <span class="codefrag">src/documentation/skins/my-fancy-skin</span> and add
+            <span class="codefrag">project.skin=my-fancy-skin</span> to forrest.properties
           </p>
 <p>
             The two most interesting XSLT stylesheets involved are:
@@ -1456,7 +1456,7 @@
 <dl>
             
 <dt>
-<span class="codefrag ">xslt/html/document2html.xsl</span>
+<span class="codefrag">xslt/html/document2html.xsl</span>
 </dt>
             
 <dd>
@@ -1465,7 +1465,7 @@
             </dd>
             
 <dt>
-<span class="codefrag ">xslt/html/site2xhtml.xsl</span>
+<span class="codefrag">xslt/html/site2xhtml.xsl</span>
 </dt>
             
 <dd>
@@ -1489,7 +1489,7 @@
 &lt;/xsl:stylesheet&gt;</pre>
 <p>In order to use this feature in your custom skins you must copy
           the common skin from the forrest distribution into your custom skins 
-          directory (from <span class="codefrag ">main/webapp/skins/common</span>).
+          directory (from <span class="codefrag">main/webapp/skins/common</span>).
           This will protect your skin from changes in the Forrest common skin,
           but you must remember to update this skin in order to take advantage
           of new features added over time by the Forrest team.</p>
@@ -1522,20 +1522,20 @@
 <a name="N10347"></a><a name="forrest_run"></a>
 <h3 class="underlined_5">Running as a webapp</h3>
 <p>
-          Type '<span class="codefrag ">forrest run</span>' in your project root to start Forrest's
+          Type '<span class="codefrag">forrest run</span>' in your project root to start Forrest's
           built-in Jetty web server.  Once it has started, point your browser at
           <a href="http://localhost:8888/">http://localhost:8888/</a>, which
           will show your website, rendered on demand as each link is followed.
         </p>
 <p>(Alternatively, if you wish to run Forrest from within an existing
-          servlet container, type <span class="codefrag ">forrest webapp</span> to build an open
-          webapp in <span class="codefrag ">build/webapp/</span>)
+          servlet container, type <span class="codefrag">forrest webapp</span> to build an open
+          webapp in <span class="codefrag">build/webapp/</span>)
         </p>
 <a name="N10360"></a><a name="using_webapp"></a>
 <h4>Using the webapp</h4>
 <p>
             You can now edit the XML content in
-            <span class="codefrag ">build/webapp/content/xdocs</span> and see the changes
+            <span class="codefrag">build/webapp/content/xdocs</span> and see the changes
             immediately in the browser.
           </p>
 </div>
@@ -1575,14 +1575,14 @@
 <p>Because you are using your own version
       of Ant to do Forrest's work, you will need to provide the
       supporting catalog entity resolver:
-      '<span class="codefrag ">cp forrest/lib/core/xml-commons-resolver-1.1.jar $ANT_HOME/lib</span>'
+      '<span class="codefrag">cp forrest/lib/core/xml-commons-resolver-1.1.jar $ANT_HOME/lib</span>'
       </p>
 <p>Note: The technique described above requires Ant 1.6+ otherwise
         the &lt;import&gt;
         task will not be available for you to use. Forrest
         bundles the latest version of Ant, so you can invoke your project
-        like this: '<span class="codefrag ">forrest -f myproject.xml</span>'.
-        This will not run the '<span class="codefrag ">forrest</span>' command. It will just
+        like this: '<span class="codefrag">forrest -f myproject.xml</span>'.
+        This will not run the '<span class="codefrag">forrest</span>' command. It will just
         use Forrest's Ant and resolver to execute your buildfile.
       </p>
 <p>

Modified: forrest/site/docs_0_80/build.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/build.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_80/build.html (original)
+++ forrest/site/docs_0_80/build.html Sun Dec 18 17:31:25 2005
@@ -373,16 +373,16 @@
           </li>
           
 <li>At a command prompt, enter
-           '<span class="codefrag ">svn co http://svn.apache.org/repos/asf/forrest/trunk forrest</span>'
-           (committers should replace <span class="codefrag ">http</span> with <span class="codefrag ">https</span>).</li>
+           '<span class="codefrag">svn co http://svn.apache.org/repos/asf/forrest/trunk forrest</span>'
+           (committers should replace <span class="codefrag">http</span> with <span class="codefrag">https</span>).</li>
           
-<li>This will create a directory called "<span class="codefrag ">forrest</span>" where the Forrest source will be stored.</li> 
+<li>This will create a directory called "<span class="codefrag">forrest</span>" where the Forrest source will be stored.</li> 
         
 </ol>
 <p>Whenever you want to update your Forrest source tree to the current
          version, change to the top-level
-"<span class="codefrag ">forrest</span>" directory and invoke '<span class="codefrag ">svn update</span>'.</p>
-<p>To see what changes you've made, invoke '<span class="codefrag ">svn status</span>'</p>
+"<span class="codefrag">forrest</span>" directory and invoke '<span class="codefrag">svn update</span>'.</p>
+<p>To see what changes you've made, invoke '<span class="codefrag">svn status</span>'</p>
 <p>SVN is really powerful. See
           <a href="http://svnbook.red-bean.com/">Version Control with Subversion</a> - the opensource SVN book.
         </p>
@@ -407,8 +407,8 @@
 </div>
 </div>
 <p>
-       To build Forrest, change directory to '<span class="codefrag ">forrest/main</span>', and
-       then type '<span class="codefrag ">build</span>' on Windows or '<span class="codefrag ">./build.sh</span>' on
+       To build Forrest, change directory to '<span class="codefrag">forrest/main</span>', and
+       then type '<span class="codefrag">build</span>' on Windows or '<span class="codefrag">./build.sh</span>' on
        Unix. (Requires Java 1.4)
        If everything is successful, you should see a message similar to:
      </p>
@@ -427,8 +427,8 @@
   *-----------------------------------------------------------------
      </pre>
 <p>
-       As the message says, you need to add the distribution's <span class="codefrag ">bin/</span>
-       ("binary") directory to your PATH variable, so the <span class="codefrag ">'forrest'</span>
+       As the message says, you need to add the distribution's <span class="codefrag">bin/</span>
+       ("binary") directory to your PATH variable, so the <span class="codefrag">'forrest'</span>
        command is available everywhere:
      </p>
 <pre class="code">
@@ -453,7 +453,7 @@
 <p>
       Forrest is now ready to go. To view and edit the local copy of
       Forrest core documentation, cd to site-author and do
-      '<span class="codefrag ">forrest run</span>' to see
+      '<span class="codefrag">forrest run</span>' to see
       the local webapp using the bundled Jetty server. Edit something in
       content/xdocs/*.xml see the immediate effect.
     </p>

Modified: forrest/site/docs_0_80/cap.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/cap.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_80/cap.html (original)
+++ forrest/site/docs_0_80/cap.html Sun Dec 18 17:31:25 2005
@@ -380,7 +380,7 @@
  &lt;/map:components&gt;
  &lt;...&gt;
 &lt;/map:sitemap&gt;</pre>
-<p>There are other examples in <span class="codefrag ">main/webapp/forrest.xmap</span>
+<p>There are other examples in <span class="codefrag">main/webapp/forrest.xmap</span>
 </p>
 <p>Each sourcetype-tag declares a source type. Inside the sourcetype-tag
         a number of rules can be defined, described below. The sourcetypes will be
@@ -392,31 +392,31 @@
 <dt>document-declaration</dt> 
         
 <dd>This rule checks the public ID. It takes one attribute
-          <span class="codefrag ">public-id</span>.</dd> 
+          <span class="codefrag">public-id</span>.</dd> 
         
 <dt>document-element</dt> 
         
 <dd>This rule checks the local name and/or namespace of the document
-          element. These are specified with the attributes <span class="codefrag ">local-name</span> and
-          <span class="codefrag ">namespace</span>. At least one of these two is required.</dd> 
+          element. These are specified with the attributes <span class="codefrag">local-name</span> and
+          <span class="codefrag">namespace</span>. At least one of these two is required.</dd> 
         
 <dt>processing-instruction</dt> 
         
 <dd>This rule checks a processing instruction. It can take two
-          attributes: <span class="codefrag ">target</span> and <span class="codefrag ">data</span>. The target attribute is
+          attributes: <span class="codefrag">target</span> and <span class="codefrag">data</span>. The target attribute is
           always required, the data attribute is optional.</dd> 
         
 <dt>w3c-xml-schema</dt> 
         
 <dd>This rule checks the value of the xsi:schemaLocation and
           xsi:noNamespaceSchemaLocation attributes on the document element. These are
-          specified with the attributes <span class="codefrag ">schema-location</span> and
-          <span class="codefrag ">no-namespace-schema-location</span>.</dd> 
+          specified with the attributes <span class="codefrag">schema-location</span> and
+          <span class="codefrag">no-namespace-schema-location</span>.</dd> 
       
 </dl>
 <p>
        Perhaps you need other methods. Please enhance the source at
-       <span class="codefrag ">main/java/org/apache/forrest/sourcetype</span>
+       <span class="codefrag">main/java/org/apache/forrest/sourcetype</span>
       
 </p>
 </div> 

Modified: forrest/site/docs_0_80/catalog.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/catalog.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_80/catalog.html (original)
+++ forrest/site/docs_0_80/catalog.html Sun Dec 18 17:31:25 2005
@@ -423,15 +423,15 @@
 <div class="section">
 <p>
         The Forrest DTDs and supporting resources are in the Forrest
-        distribution at <span class="codefrag ">main/webapp/resources/schema/</span>
+        distribution at <span class="codefrag">main/webapp/resources/schema/</span>
       
 </p>
 <p>
         Usually all that is required is to direct your tool to the "catalog"
         supplied by Forrest at either:
-        <span class="codefrag ">$FORREST_HOME/main/webapp/resources/schema/catalog.xcat</span>
+        <span class="codefrag">$FORREST_HOME/main/webapp/resources/schema/catalog.xcat</span>
         (for XML Catalog) or
-        <span class="codefrag ">$FORREST_HOME/main/webapp/resources/schema/catalog</span>
+        <span class="codefrag">$FORREST_HOME/main/webapp/resources/schema/catalog</span>
         (for TR 9401 Catalog).
       </p>
 </div>
@@ -445,8 +445,8 @@
 <p>
           Some operating systems already provide a system-wide catalog that
           is used by many tools. This is usually located at
-          <span class="codefrag ">/etc/xml/catalog</span> or at
-          <span class="codefrag ">/usr/share/sgml/catalog</span> files.
+          <span class="codefrag">/etc/xml/catalog</span> or at
+          <span class="codefrag">/usr/share/sgml/catalog</span> files.
         </p>
 <p>
           For an XML Catalog, add this line:
@@ -585,7 +585,7 @@
         that is provided by the
         <a href="http://xml.apache.org/commons/">Apache XML Commons</a>
         project. The resolver is packaged with the Forrest distribution at
-        <span class="codefrag ">lib/core/xml-commons-resolver-x.y.jar</span>
+        <span class="codefrag">lib/core/xml-commons-resolver-x.y.jar</span>
       
 </p>
 <p>

Modified: forrest/site/docs_0_80/changes.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/changes.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_80/changes.html (original)
+++ forrest/site/docs_0_80/changes.html Sun Dec 18 17:31:25 2005
@@ -350,10 +350,10 @@
 <a href="#version_0.7.1-dev">Version 0.7.1-dev (not yet released)</a>
 <ul class="minitoc">
 <li>
-<a href="#Changes+to+the+Code+Base-N100D3">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N100DD">Changes to the Code Base</a>
 </li>
 <li>
-<a href="#Changes+to+Documentation-N100DD">Changes to Documentation</a>
+<a href="#Changes+to+Documentation-N100E7">Changes to Documentation</a>
 </li>
 </ul>
 </li>
@@ -367,13 +367,13 @@
 <a href="#Changes+to+Build">Changes to Build</a>
 </li>
 <li>
-<a href="#Changes+to+the+Code+Base-N10106">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N10110">Changes to the Code Base</a>
 </li>
 <li>
-<a href="#Changes+to+Documentation-N10278">Changes to Documentation</a>
+<a href="#Changes+to+Documentation-N10282">Changes to Documentation</a>
 </li>
 <li>
-<a href="#Contributors-N10318">Contributors</a>
+<a href="#Contributors-N10322">Contributors</a>
 </li>
 </ul>
 </li>
@@ -381,19 +381,19 @@
 <a href="#version_0.6">Version 0.6 (2004-10-15)</a>
 <ul class="minitoc">
 <li>
-<a href="#Changes+to+Project+Administration-N10340">Changes to Project Administration</a>
+<a href="#Changes+to+Project+Administration-N1034A">Changes to Project Administration</a>
 </li>
 <li>
-<a href="#Changes+to+Build-N1034A">Changes to Build</a>
+<a href="#Changes+to+Build-N10354">Changes to Build</a>
 </li>
 <li>
-<a href="#Changes+to+the+Code+Base-N10378">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N10382">Changes to the Code Base</a>
 </li>
 <li>
-<a href="#Changes+to+Documentation-N1073D">Changes to Documentation</a>
+<a href="#Changes+to+Documentation-N10747">Changes to Documentation</a>
 </li>
 <li>
-<a href="#Contributors-N1079B">Contributors</a>
+<a href="#Contributors-N107A5">Contributors</a>
 </li>
 </ul>
 </li>
@@ -401,10 +401,10 @@
 <a href="#version_0.5.1">Version 0.5.1 (2003-10-06)</a>
 <ul class="minitoc">
 <li>
-<a href="#Changes+to+Build-N107C7">Changes to Build</a>
+<a href="#Changes+to+Build-N107D1">Changes to Build</a>
 </li>
 <li>
-<a href="#Changes+to+the+Code+Base-N107D1">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N107DB">Changes to the Code Base</a>
 </li>
 </ul>
 </li>
@@ -412,13 +412,13 @@
 <a href="#version_0.5">Version 0.5 (2003-09-13)</a>
 <ul class="minitoc">
 <li>
-<a href="#Changes+to+the+Code+Base-N10816">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N10820">Changes to the Code Base</a>
 </li>
 <li>
-<a href="#Changes+to+Documentation-N10A17">Changes to Documentation</a>
+<a href="#Changes+to+Documentation-N10A21">Changes to Documentation</a>
 </li>
 <li>
-<a href="#Contributors-N10A21">Contributors</a>
+<a href="#Contributors-N10A2B">Contributors</a>
 </li>
 </ul>
 </li>
@@ -426,13 +426,13 @@
 <a href="#version_0.4">Version 0.4 (2003-02-12)</a>
 <ul class="minitoc">
 <li>
-<a href="#Changes+to+the+Code+Base-N10A3D">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N10A47">Changes to the Code Base</a>
 </li>
 <li>
-<a href="#Changes+to+Documentation-N10AA4">Changes to Documentation</a>
+<a href="#Changes+to+Documentation-N10AAE">Changes to Documentation</a>
 </li>
 <li>
-<a href="#Contributors-N10AAE">Contributors</a>
+<a href="#Contributors-N10AB8">Contributors</a>
 </li>
 </ul>
 </li>
@@ -440,16 +440,16 @@
 <a href="#version_0.3">Version 0.3 (2003-01-30)</a>
 <ul class="minitoc">
 <li>
-<a href="#Changes+to+Build-N10AC0">Changes to Build</a>
+<a href="#Changes+to+Build-N10ACA">Changes to Build</a>
 </li>
 <li>
-<a href="#Changes+to+the+Code+Base-N10ACF">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N10AD9">Changes to the Code Base</a>
 </li>
 <li>
-<a href="#Changes+to+Documentation-N10BE5">Changes to Documentation</a>
+<a href="#Changes+to+Documentation-N10BEF">Changes to Documentation</a>
 </li>
 <li>
-<a href="#Contributors-N10BEF">Contributors</a>
+<a href="#Contributors-N10BF9">Contributors</a>
 </li>
 </ul>
 </li>
@@ -457,7 +457,7 @@
 <a href="#version_0.2">Version 0.2 (2002-11-16)</a>
 <ul class="minitoc">
 <li>
-<a href="#Changes+to+the+Code+Base-N10BFF">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N10C09">Changes to the Code Base</a>
 </li>
 </ul>
 </li>
@@ -465,22 +465,22 @@
 <a href="#version_0.2rc1">Version 0.2rc1 (2002-11-13)</a>
 <ul class="minitoc">
 <li>
-<a href="#Changes+to+Project+Administration-N10C1B">Changes to Project Administration</a>
+<a href="#Changes+to+Project+Administration-N10C25">Changes to Project Administration</a>
 </li>
 <li>
-<a href="#Changes+to+Build-N10C25">Changes to Build</a>
+<a href="#Changes+to+Build-N10C2F">Changes to Build</a>
 </li>
 <li>
-<a href="#Changes+to+the+Code+Base-N10C93">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N10C9D">Changes to the Code Base</a>
 </li>
 <li>
 <a href="#Changes+to+Design">Changes to Design</a>
 </li>
 <li>
-<a href="#Changes+to+Documentation-N10D58">Changes to Documentation</a>
+<a href="#Changes+to+Documentation-N10D62">Changes to Documentation</a>
 </li>
 <li>
-<a href="#Contributors-N10DC1">Contributors</a>
+<a href="#Contributors-N10DCB">Contributors</a>
 </li>
 </ul>
 </li>
@@ -500,6 +500,15 @@
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
+<img class="icon" alt="add" src="../images/add.jpg"> New protocol / source factory 
+        that is contacting the locationmap module to look up the source. Use it 
+        like lm://resolve.contract.html.content-main for source resolving. 
+        (TS)</li>
+<li>
+<img class="icon" alt="add" src="../images/add.jpg"> Added first implementation of 
+        the dispatcher. Including contract bean implementation and interface; 
+        dispatcher exception and dispatcher transformers. (TS)</li>
+<li>
 <img class="icon" alt="add" src="../images/add.jpg">
         The broken-links file is now copied into to the site root as
         "broken-links.xml" so that when building with Forrestbot
@@ -553,7 +562,7 @@
 <img class="icon" alt="add" src="../images/add.jpg">
         Use sets of symbols as xml entities for character replacement.
         There is a core set and each project can define a set.
-        For example, use "<span class="codefrag ">&amp;myp-t;</span>" to represent the
+        For example, use "<span class="codefrag">&amp;myp-t;</span>" to represent the
         project name together with trademark symbol
         "My Project Name&trade;".
         See <a href="../docs_0_80/faq.html#xml-entities">FAQ</a>.
@@ -578,7 +587,7 @@
 <img class="icon" alt="add" src="../images/add.jpg">
         Added support for a locationmap. This enables content to be retrieved from a location
         that is defined in a locationmap file (located at 
-        <span class="codefrag ">PROJECT_HOME/src/documentation/content/locationmap.xml</span> file. The
+        <span class="codefrag">PROJECT_HOME/src/documentation/content/locationmap.xml</span> file. The
         advantage of this is that the URL seen by the user need bear no relation to the location
         of the source document, thus Forrest can separate the client URL space from the source
         docuement URL space. Thus, using the locationmap it is possible to pull together
@@ -625,7 +634,7 @@
         Updated tools/forrestbar to be compatiable with recent versions of Firefox.
       (DC) Thanks to Addison Berry.</li>
 </ul>
-<a name="N100A4"></a><a name="Changes+to+Documentation"></a>
+<a name="N100AE"></a><a name="Changes+to+Documentation"></a>
 <h3 class="underlined_5">Changes to Documentation</h3>
 <ul>
 <li>
@@ -641,7 +650,7 @@
         committer</a>.
       () Thanks to Addison Berry. Fixes <a href="http://issues.apache.org/jira/browse/FOR-603">FOR-603</a>.</li>
 </ul>
-<a name="N100C1"></a><a name="Contributors"></a>
+<a name="N100CB"></a><a name="Contributors"></a>
 <h3 class="underlined_5">Contributors</h3>
 <p>This is a list of all people who have contributed to this release, but 
        were full developers on the project. We thank these people for their 
@@ -653,10 +662,10 @@
 </ul>
 </div>
     
-<a name="N100CF"></a><a name="version_0.7.1-dev"></a>
+<a name="N100D9"></a><a name="version_0.7.1-dev"></a>
 <h2 class="underlined_10">Version 0.7.1-dev (not yet released)</h2>
 <div class="section">
-<a name="N100D3"></a><a name="Changes+to+the+Code+Base-N100D3"></a>
+<a name="N100DD"></a><a name="Changes+to+the+Code+Base-N100DD"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -669,7 +678,7 @@
         Doing 'forrest clean' will remove both sections.
       (DC)</li>
 </ul>
-<a name="N100DD"></a><a name="Changes+to+Documentation-N100DD"></a>
+<a name="N100E7"></a><a name="Changes+to+Documentation-N100E7"></a>
 <h3 class="underlined_5">Changes to Documentation</h3>
 <ul>
 <li>
@@ -681,10 +690,10 @@
 </ul>
 </div>
     
-<a name="N100EE"></a><a name="version_0.7"></a>
+<a name="N100F8"></a><a name="version_0.7"></a>
 <h2 class="underlined_10">Version 0.7 (2005-06-23)</h2>
 <div class="section">
-<a name="N100F2"></a><a name="Changes+to+Project+Administration"></a>
+<a name="N100FC"></a><a name="Changes+to+Project+Administration"></a>
 <h3 class="underlined_5">Changes to Project Administration</h3>
 <ul>
 <li>
@@ -692,7 +701,7 @@
         Added testing facilities to plugins to facilitate integration testing. 
       (RDG)</li>
 </ul>
-<a name="N100FC"></a><a name="Changes+to+Build"></a>
+<a name="N10106"></a><a name="Changes+to+Build"></a>
 <h3 class="underlined_5">Changes to Build</h3>
 <ul>
 <li>
@@ -702,7 +711,7 @@
         Ant "import" task.
       (DC)</li>
 </ul>
-<a name="N10106"></a><a name="Changes+to+the+Code+Base-N10106"></a>
+<a name="N10110"></a><a name="Changes+to+the+Code+Base-N10110"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -955,7 +964,7 @@
         starting with Forrest-0.7-dev
       (DC)</li>
 </ul>
-<a name="N10278"></a><a name="Changes+to+Documentation-N10278"></a>
+<a name="N10282"></a><a name="Changes+to+Documentation-N10282"></a>
 <h3 class="underlined_5">Changes to Documentation</h3>
 <ul>
 <li>
@@ -1045,7 +1054,7 @@
         tab</a> to create subject-specific aggregated documents.
       (TS)</li>
 </ul>
-<a name="N10318"></a><a name="Contributors-N10318"></a>
+<a name="N10322"></a><a name="Contributors-N10322"></a>
 <h3 class="underlined_5">Contributors</h3>
 <p>This is a list of all people who have contributed to this release, but 
        were full developers on the project. We thank these people for their 
@@ -1068,10 +1077,10 @@
 </ul>
 </div>
     
-<a name="N1033C"></a><a name="version_0.6"></a>
+<a name="N10346"></a><a name="version_0.6"></a>
 <h2 class="underlined_10">Version 0.6 (2004-10-15)</h2>
 <div class="section">
-<a name="N10340"></a><a name="Changes+to+Project+Administration-N10340"></a>
+<a name="N1034A"></a><a name="Changes+to+Project+Administration-N1034A"></a>
 <h3 class="underlined_5">Changes to Project Administration</h3>
 <ul>
 <li>
@@ -1082,7 +1091,7 @@
         OpenSymphony's OSUser for flexible authentication.
       (DB)</li>
 </ul>
-<a name="N1034A"></a><a name="Changes+to+Build-N1034A"></a>
+<a name="N10354"></a><a name="Changes+to+Build-N10354"></a>
 <h3 class="underlined_5">Changes to Build</h3>
 <ul>
 <li>
@@ -1106,7 +1115,7 @@
         Add more desriptions to forrest targets.  Highlight the most common ones.
       (DB) Fixes <a href="http://issues.apache.org/jira/browse/FOR-216">FOR-216</a>.</li>
 </ul>
-<a name="N10378"></a><a name="Changes+to+the+Code+Base-N10378"></a>
+<a name="N10382"></a><a name="Changes+to+the+Code+Base-N10382"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -1436,7 +1445,7 @@
         document2html and site2xhtml XSLs. This allows matches
         defined in the imported transformation sheets to match
         (imported sheets have lower precedence).
-        * Defined a couple of <span class="codefrag ">&lt;div id="..."&gt;</span> place holder
+        * Defined a couple of <span class="codefrag">&lt;div id="..."&gt;</span> place holder
         tags used by the document2html. Those are then skinned by the
         site2xhtml sheets.
         * Note: If you have your own skins that were referencing "$config" or
@@ -1468,8 +1477,8 @@
 <img class="icon" alt="fix" src="../images/fix.jpg">
         Replace document() function to get skinconf values and use "//skinconfig".
         Fix order so it can validate skinconf.
-        Use <span class="codefrag ">&lt;search/&gt;</span> instead of
-        <span class="codefrag ">&lt;disable-search/&gt; &lt;disable-lucene/&gt;
+        Use <span class="codefrag">&lt;search/&gt;</span> instead of
+        <span class="codefrag">&lt;disable-search/&gt; &lt;disable-lucene/&gt;
         &lt;searchsite-domain/&gt; &lt;searchsite-name/&gt;</span>.
         Fix skinconf.xsl so it produces a proper skinconf
       (JJP)</li>
@@ -1851,7 +1860,7 @@
         Sort action types order to "add","remove","update","fix".
       (JJP)</li>
 </ul>
-<a name="N1073D"></a><a name="Changes+to+Documentation-N1073D"></a>
+<a name="N10747"></a><a name="Changes+to+Documentation-N10747"></a>
 <h3 class="underlined_5">Changes to Documentation</h3>
 <ul>
 <li>
@@ -1908,7 +1917,7 @@
         <a href="http://forrest.apache.org/">http://forrest.apache.org/</a>
       (DC)</li>
 </ul>
-<a name="N1079B"></a><a name="Contributors-N1079B"></a>
+<a name="N107A5"></a><a name="Contributors-N107A5"></a>
 <h3 class="underlined_5">Contributors</h3>
 <p>This is a list of all people who have contributed to this release, but 
        were full developers on the project. We thank these people for their 
@@ -1934,10 +1943,10 @@
 </div>
 
     
-<a name="N107C3"></a><a name="version_0.5.1"></a>
+<a name="N107CD"></a><a name="version_0.5.1"></a>
 <h2 class="underlined_10">Version 0.5.1 (2003-10-06)</h2>
 <div class="section">
-<a name="N107C7"></a><a name="Changes+to+Build-N107C7"></a>
+<a name="N107D1"></a><a name="Changes+to+Build-N107D1"></a>
 <h3 class="underlined_5">Changes to Build</h3>
 <ul>
 <li>
@@ -1945,7 +1954,7 @@
         forrest.antproxy.xml script now properly fails when Cocoon fails
       (JT)</li>
 </ul>
-<a name="N107D1"></a><a name="Changes+to+the+Code+Base-N107D1"></a>
+<a name="N107DB"></a><a name="Changes+to+the+Code+Base-N107DB"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -1985,10 +1994,10 @@
 </div>
 
     
-<a name="N10812"></a><a name="version_0.5"></a>
+<a name="N1081C"></a><a name="version_0.5"></a>
 <h2 class="underlined_10">Version 0.5 (2003-09-13)</h2>
 <div class="section">
-<a name="N10816"></a><a name="Changes+to+the+Code+Base-N10816"></a>
+<a name="N10820"></a><a name="Changes+to+the+Code+Base-N10820"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -2024,9 +2033,9 @@
       (JT)</li>
 <li>
 <img class="icon" alt="add" src="../images/add.jpg">
-        Added a <span class="codefrag ">forrest.maxmemory</span> property specifying the maximum
+        Added a <span class="codefrag">forrest.maxmemory</span> property specifying the maximum
         amount of memory allocated to the JVM. Useful for rendering large PDFs.
-        Added <span class="codefrag ">forrest.jvmargs</span> property for other JVM options.
+        Added <span class="codefrag">forrest.jvmargs</span> property for other JVM options.
       (JT)</li>
 <li>
 <img class="icon" alt="add" src="../images/add.jpg">
@@ -2161,7 +2170,7 @@
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
         Fixed bug where absolute paths to images were created in the
-        <span class="codefrag ">build/site</span> directory.
+        <span class="codefrag">build/site</span> directory.
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
@@ -2181,7 +2190,7 @@
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
-        In <span class="codefrag ">skins/common/xslt/html/tab2menu.xsl</span>, renamed template
+        In <span class="codefrag">skins/common/xslt/html/tab2menu.xsl</span>, renamed template
         'unselected-tab-href' to 'calculate-tab-href', potentially breaking 3rd
         party skins.
       (JT)</li>
@@ -2193,7 +2202,7 @@
 <img class="icon" alt="fix" src="../images/fix.jpg">
         Get images in PDFs working with FOP 0.20.x.  This requires the user to
         download jimi.jar from <a href="http://java.sun.com/products/jimi/">Sun</a> and place it in
-        the <span class="codefrag ">lib/core</span> (src distro) or <span class="codefrag ">WEB-INF/lib</span>
+        the <span class="codefrag">lib/core</span> (src distro) or <span class="codefrag">WEB-INF/lib</span>
         (binary distro) directory.
       (JT)</li>
 <li>
@@ -2204,13 +2213,13 @@
       (NKB)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
-        Fixed <span class="codefrag ">java.lang.NoClassDefFoundError:
+        Fixed <span class="codefrag">java.lang.NoClassDefFoundError:
           javax/servlet/ServletInputStream</span> error.
       (JT) Thanks to <a href="mailto:cheche.at.che-che.com">Juan Jose Pablos</a>.</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
         Allow users to determine which URLs Forrest should ignore, by overriding
-        <span class="codefrag ">stylesheets/filterlinks.xsl</span> (and other stylesheets in that
+        <span class="codefrag">stylesheets/filterlinks.xsl</span> (and other stylesheets in that
         directory).
       (JT)</li>
 <li>
@@ -2226,7 +2235,7 @@
 <img class="icon" alt="update" src="../images/update.jpg">
         In the forrest-site skin and derivatives, display the author and version at the
         bottom of the page, as krysalis-site does.  Also added parsing for CVS Revision
-        tags, so <span class="codefrag ">&lt;version&gt;$Revision: 1.288 $&lt;/version&gt;</span> can be used.
+        tags, so <span class="codefrag">&lt;version&gt;$Revision: 1.288 $&lt;/version&gt;</span> can be used.
       (JT)</li>
 <li>
 <img class="icon" alt="update" src="../images/update.jpg">
@@ -2282,7 +2291,7 @@
       (JT)</li>
 <li>
 <img class="icon" alt="update" src="../images/update.jpg">
-        Allow any sort of content inside <span class="codefrag ">resources/</span>, which will be
+        Allow any sort of content inside <span class="codefrag">resources/</span>, which will be
         made available to the sitemap but not automatically copied to the
         generated site output.
       (JT)</li>
@@ -2366,7 +2375,7 @@
         the xinclude,  linkrewriter, and idgen steps.
       (NKB)</li>
 </ul>
-<a name="N10A17"></a><a name="Changes+to+Documentation-N10A17"></a>
+<a name="N10A21"></a><a name="Changes+to+Documentation-N10A21"></a>
 <h3 class="underlined_5">Changes to Documentation</h3>
 <ul>
 <li>
@@ -2375,7 +2384,7 @@
         upgrading to v0.5
       (JT)</li>
 </ul>
-<a name="N10A21"></a><a name="Contributors-N10A21"></a>
+<a name="N10A2B"></a><a name="Contributors-N10A2B"></a>
 <h3 class="underlined_5">Contributors</h3>
 <p>This is a list of all people who have contributed to this release, but 
        were full developers on the project. We thank these people for their 
@@ -2392,10 +2401,10 @@
 </ul>
 </div>
     
-<a name="N10A39"></a><a name="version_0.4"></a>
+<a name="N10A43"></a><a name="version_0.4"></a>
 <h2 class="underlined_10">Version 0.4 (2003-02-12)</h2>
 <div class="section">
-<a name="N10A3D"></a><a name="Changes+to+the+Code+Base-N10A3D"></a>
+<a name="N10A47"></a><a name="Changes+to+the+Code+Base-N10A47"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -2448,7 +2457,7 @@
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
-        Fix <span class="codefrag ">site:</span> and <span class="codefrag ">ext:</span> rewriting in book.xml,
+        Fix <span class="codefrag">site:</span> and <span class="codefrag">ext:</span> rewriting in book.xml,
         ihtml, ehtml and cwiki files in subdirectories.
       (JT)</li>
 <li>
@@ -2472,7 +2481,7 @@
         Switched all loglevels to ERROR.
       (NKB)</li>
 </ul>
-<a name="N10AA4"></a><a name="Changes+to+Documentation-N10AA4"></a>
+<a name="N10AAE"></a><a name="Changes+to+Documentation-N10AAE"></a>
 <h3 class="underlined_5">Changes to Documentation</h3>
 <ul>
 <li>
@@ -2481,7 +2490,7 @@
         to the forrestbar.xpi generated by Gump every day.
       (NKB)</li>
 </ul>
-<a name="N10AAE"></a><a name="Contributors-N10AAE"></a>
+<a name="N10AB8"></a><a name="Contributors-N10AB8"></a>
 <h3 class="underlined_5">Contributors</h3>
 <p>This is a list of all people who have contributed to this release, but 
        were full developers on the project. We thank these people for their 
@@ -2494,10 +2503,10 @@
 </div>
 
     
-<a name="N10ABC"></a><a name="version_0.3"></a>
+<a name="N10AC6"></a><a name="version_0.3"></a>
 <h2 class="underlined_10">Version 0.3 (2003-01-30)</h2>
 <div class="section">
-<a name="N10AC0"></a><a name="Changes+to+Build-N10AC0"></a>
+<a name="N10ACA"></a><a name="Changes+to+Build-N10ACA"></a>
 <h3 class="underlined_5">Changes to Build</h3>
 <ul>
 <li>
@@ -2512,7 +2521,7 @@
         instead of Cocoon + Centipede logos.
       (JT)</li>
 </ul>
-<a name="N10ACF"></a><a name="Changes+to+the+Code+Base-N10ACF"></a>
+<a name="N10AD9"></a><a name="Changes+to+the+Code+Base-N10AD9"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -2522,7 +2531,7 @@
 <li>
 <img class="icon" alt="add" src="../images/add.jpg">
         Added a means to override the check for existing content: 
-        <span class="codefrag ">forrest seed -Dskip.contentcheck=yes</span>
+        <span class="codefrag">forrest seed -Dskip.contentcheck=yes</span>
         Thanks to Tom Klaasen.
       (JT)</li>
 <li>
@@ -2555,51 +2564,51 @@
       (JT)</li>
 <li>
 <img class="icon" alt="add" src="../images/add.jpg">
-        New <span class="codefrag ">site.xml</span> file in content/xdocs.  This is used to
+        New <span class="codefrag">site.xml</span> file in content/xdocs.  This is used to
         implement &lt;link href="site:internalURI"&gt; 'semantic' links,
         &lt;link href="ext:externalURI"&gt; aliases to external links, and
-        renders <span class="codefrag ">book.xml</span> files obsolete.  See <a href="../docs_0_70/linking.html">Menus and Linking</a> for more info.
+        renders <span class="codefrag">book.xml</span> files obsolete.  See <a href="../docs_0_70/linking.html">Menus and Linking</a> for more info.
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
-        If <span class="codefrag ">build/webapp/content/xdocs/*</span> is more recent than
-        <span class="codefrag ">src/*</span> equivalent, <span class="codefrag ">forrest webapp</span> won't clobber
-        it.  A new <span class="codefrag ">forrest backcopy</span> command will copy
-        <span class="codefrag ">build/webapp/content/xdocs</span> content back to
-        <span class="codefrag ">src/documentation/content/xdocs</span>.
+        If <span class="codefrag">build/webapp/content/xdocs/*</span> is more recent than
+        <span class="codefrag">src/*</span> equivalent, <span class="codefrag">forrest webapp</span> won't clobber
+        it.  A new <span class="codefrag">forrest backcopy</span> command will copy
+        <span class="codefrag">build/webapp/content/xdocs</span> content back to
+        <span class="codefrag">src/documentation/content/xdocs</span>.
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
-        <span class="codefrag ">forrest-site</span> skin is now HTML 4.0.1 compliant.  The
+        <span class="codefrag">forrest-site</span> skin is now HTML 4.0.1 compliant.  The
         compliance validator logo can be switched off with a
-        <span class="codefrag ">skinconf.xml</span> element.
+        <span class="codefrag">skinconf.xml</span> element.
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
         Indirectly referenced files in skins (e.g. images in
-        CSS<span class="codefrag ">url()</span>'s) are now copied across to the rendered site.
+        CSS<span class="codefrag">url()</span>'s) are now copied across to the rendered site.
         Previously, we relied on spidering to cover the URI space, which has
         proved insufficient.
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
         HTML fragment identifiers for sections are now meaningfully named, based
-        on the section title, rather than <span class="codefrag ">document-id()</span>-generated
+        on the section title, rather than <span class="codefrag">document-id()</span>-generated
         characters.
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
         Fixed site regeneration bugs where changing the skin in
-        <span class="codefrag ">forrest.properties</span> had no effect after the first build.
+        <span class="codefrag">forrest.properties</span> had no effect after the first build.
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
-        Now all files in <span class="codefrag ">src/documentation/content</span> (except xdocs)
-        and <span class="codefrag ">src/documentation/resources/images</span> are copied across
+        Now all files in <span class="codefrag">src/documentation/content</span> (except xdocs)
+        and <span class="codefrag">src/documentation/resources/images</span> are copied across
         when Forrest generates a static site.  This fixes the problem when an
         unparseable file links to another, and Cocoon can't crawl (and hence
         copy) the linked-to file.  An example of this are CSS
-        <span class="codefrag ">url('foo.png')</span> image refs (so krysalis-site will now work
+        <span class="codefrag">url('foo.png')</span> image refs (so krysalis-site will now work
         properly).  Also, large batches of pregenerated files like Javadocs will
         now be copied across instead of individually traversed.
       (JT)</li>
@@ -2651,13 +2660,13 @@
 <img class="icon" alt="remove" src="../images/remove.jpg">
         Removed some images (built-with-cocoon.gif, centipede-logo-small.gif)
         from the skins, and moved them to
-        <span class="codefrag ">src/documentation/resources/images</span>, as they are
+        <span class="codefrag">src/documentation/resources/images</span>, as they are
         Forrest-specific.
       (JT)</li>
 <li>
 <img class="icon" alt="update" src="../images/update.jpg">
         Lots of FAQ improvements:
-        -Improved URI space by using <span class="codefrag ">@id</span> attributes as the
+        -Improved URI space by using <span class="codefrag">@id</span> attributes as the
             #fragment-identifier for &lt;faq&gt; and &lt;part&gt; elements.
         -Number FAQ entries and categories
         -Added back-links from FAQ entries to the menu
@@ -2743,7 +2752,7 @@
         We need icons for the new buttons.
       (NKB)</li>
 </ul>
-<a name="N10BE5"></a><a name="Changes+to+Documentation-N10BE5"></a>
+<a name="N10BEF"></a><a name="Changes+to+Documentation-N10BEF"></a>
 <h3 class="underlined_5">Changes to Documentation</h3>
 <ul>
 <li>
@@ -2753,7 +2762,7 @@
         Stylesheets not yet done.
       (NKB)</li>
 </ul>
-<a name="N10BEF"></a><a name="Contributors-N10BEF"></a>
+<a name="N10BF9"></a><a name="Contributors-N10BF9"></a>
 <h3 class="underlined_5">Contributors</h3>
 <p>This is a list of all people who have contributed to this release, but 
        were full developers on the project. We thank these people for their 
@@ -2764,10 +2773,10 @@
 </ul>
 </div>
     
-<a name="N10BFB"></a><a name="version_0.2"></a>
+<a name="N10C05"></a><a name="version_0.2"></a>
 <h2 class="underlined_10">Version 0.2 (2002-11-16)</h2>
 <div class="section">
-<a name="N10BFF"></a><a name="Changes+to+the+Code+Base-N10BFF"></a>
+<a name="N10C09"></a><a name="Changes+to+the+Code+Base-N10C09"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -2779,7 +2788,7 @@
 <img class="icon" alt="fix" src="../images/fix.jpg">
         Fixed bug where changes to the breadcrumb links in skinconf.xml were
         ignored until the Forrest binary was rebuilt, or the project
-        <span class="codefrag ">build/tmp/</span> deleted.
+        <span class="codefrag">build/tmp/</span> deleted.
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
@@ -2788,10 +2797,10 @@
 </ul>
 </div>
     
-<a name="N10C17"></a><a name="version_0.2rc1"></a>
+<a name="N10C21"></a><a name="version_0.2rc1"></a>
 <h2 class="underlined_10">Version 0.2rc1 (2002-11-13)</h2>
 <div class="section">
-<a name="N10C1B"></a><a name="Changes+to+Project+Administration-N10C1B"></a>
+<a name="N10C25"></a><a name="Changes+to+Project+Administration-N10C25"></a>
 <h3 class="underlined_5">Changes to Project Administration</h3>
 <ul>
 <li>
@@ -2799,7 +2808,7 @@
         Initial Import
       (SM)</li>
 </ul>
-<a name="N10C25"></a><a name="Changes+to+Build-N10C25"></a>
+<a name="N10C2F"></a><a name="Changes+to+Build-N10C2F"></a>
 <h3 class="underlined_5">Changes to Build</h3>
 <ul>
 <li>
@@ -2881,8 +2890,8 @@
 <li>
 <img class="icon" alt="update" src="../images/update.jpg">
         Updated Cocoon to 2.1-dev to use xsltc and new CLI status messages.
-        Logs are in the <span class="codefrag ">build/work/WEB-INF/logs</span> directory and the 
-        list of broken links is in the <span class="codefrag ">build</span> directory.
+        Logs are in the <span class="codefrag">build/work/WEB-INF/logs</span> directory and the 
+        list of broken links is in the <span class="codefrag">build</span> directory.
       (NKB)</li>
 <li>
 <img class="icon" alt="update" src="../images/update.jpg">
@@ -2899,7 +2908,7 @@
         Added basic Forrest descriptor.
       (NKB)</li>
 </ul>
-<a name="N10C93"></a><a name="Changes+to+the+Code+Base-N10C93"></a>
+<a name="N10C9D"></a><a name="Changes+to+the+Code+Base-N10C9D"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -2936,12 +2945,12 @@
 <li>
 <img class="icon" alt="add" src="../images/add.jpg">
         XML validation is now fully configurable through a hierarchical set of
-        <span class="codefrag ">forrest.validation.*{includes,excludes,failonerror}</span>
+        <span class="codefrag">forrest.validation.*{includes,excludes,failonerror}</span>
         properties.
       (JT)</li>
 <li>
 <img class="icon" alt="add" src="../images/add.jpg">
-        Validate XSLTs in user skins and <span class="codefrag ">resources/stylesheets</span>
+        Validate XSLTs in user skins and <span class="codefrag">resources/stylesheets</span>
         directories.
       (JT)</li>
 <li>
@@ -3015,7 +3024,7 @@
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
-        Allow <span class="codefrag ">xml:space='preserve'</span> attribute on &lt;p&gt; element, which preserves
+        Allow <span class="codefrag">xml:space='preserve'</span> attribute on &lt;p&gt; element, which preserves
         space without the changed font and block display that &lt;code&gt; uses.
       (JT)</li>
 <li>
@@ -3047,7 +3056,7 @@
         Put the internal matches in a separate pipeline with internal-only="true".
       (NKB)</li>
 </ul>
-<a name="N10D4E"></a><a name="Changes+to+Design"></a>
+<a name="N10D58"></a><a name="Changes+to+Design"></a>
 <h3 class="underlined_5">Changes to Design</h3>
 <ul>
 <li>
@@ -3056,7 +3065,7 @@
         cross-browser issues.
       (BK)</li>
 </ul>
-<a name="N10D58"></a><a name="Changes+to+Documentation-N10D58"></a>
+<a name="N10D62"></a><a name="Changes+to+Documentation-N10D62"></a>
 <h3 class="underlined_5">Changes to Documentation</h3>
 <ul>
 <li>
@@ -3067,7 +3076,7 @@
 <li>
 <img class="icon" alt="add" src="../images/add.jpg">
         Allow user to specify what XML files to validate via
-        <span class="codefrag ">forrest.validate.{includes,excludes}</span> properties.
+        <span class="codefrag">forrest.validate.{includes,excludes}</span> properties.
       (JT)</li>
 <li>
 <img class="icon" alt="add" src="../images/add.jpg">
@@ -3144,7 +3153,7 @@
         validated using these DTDs and OASIS Catalogs.
       (DC) Thanks to <a href="mailto:stevenn.at.outerthought.org">Steven Noels</a>.</li>
 </ul>
-<a name="N10DC1"></a><a name="Contributors-N10DC1"></a>
+<a name="N10DCB"></a><a name="Contributors-N10DCB"></a>
 <h3 class="underlined_5">Contributors</h3>
 <p>This is a list of all people who have contributed to this release, but 
        were full developers on the project. We thank these people for their 
@@ -3160,7 +3169,7 @@
 </ul>
 </div>
   
-<a name="N10DD7"></a><a name="Committers"></a>
+<a name="N10DE1"></a><a name="Committers"></a>
 <h2 class="underlined_10">Committers</h2>
 <div class="section">
 <p>This is a list of all people who have been 

Modified: forrest/site/docs_0_80/changes.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/changes.pdf?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/docs_0_80/changes.rss
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/changes.rss?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_80/changes.rss (original)
+++ forrest/site/docs_0_80/changes.rss Sun Dec 18 17:31:25 2005
@@ -48,7 +48,24 @@
         Added document to facilitate
         upgrading to v0.8
       </description></item>
+      
+      <item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+         New protocol / source factory 
+        that is contacting the locationmap module to look up the source. Use it 
+        like lm://resolve.contract.html.content-main for source resolving. 
+        </description></item>
         
+      <item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+         Added first implementation of 
+        the dispatcher. Including contract bean implementation and interface; 
+        dispatcher exception and dispatcher transformers. </description></item>
+      
       <item><title>code update</title><link>changes.html</link><description>code update
         by
         DC
@@ -4267,7 +4284,20 @@
 
         Added document to facilitate
         upgrading to v0.8
-      </description></item><item><title>code update</title><link>changes.html</link><description>code update
+      </description></item><item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+         New protocol / source factory 
+        that is contacting the locationmap module to look up the source. Use it 
+        like lm://resolve.contract.html.content-main for source resolving. 
+        </description></item><item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+         Added first implementation of 
+        the dispatcher. Including contract bean implementation and interface; 
+        dispatcher exception and dispatcher transformers. </description></item><item><title>code update</title><link>changes.html</link><description>code update
         by
         DC
         :

Modified: forrest/site/docs_0_80/changes.xml
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/changes.xml?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_80/changes.xml (original)
+++ forrest/site/docs_0_80/changes.xml Sun Dec 18 17:31:25 2005
@@ -1,6 +1,11 @@
 <?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "document-v13.dtd">
 <document><header><title>History of Changes</title></header><body><p><link href="changes.rss"><img alt="RSS" src="../images/rss.png"/></link></p>
-    <section id="version_0.8-dev"><title>Version 0.8-dev (not yet released)</title><section><title>Changes to the Code Base</title><ul><li><icon alt="add" src="../images/add.jpg"/>
+    <section id="version_0.8-dev"><title>Version 0.8-dev (not yet released)</title><section><title>Changes to the Code Base</title><ul><li><icon alt="add" src="../images/add.jpg"/> New protocol / source factory 
+        that is contacting the locationmap module to look up the source. Use it 
+        like lm://resolve.contract.html.content-main for source resolving. 
+        (TS)</li><li><icon alt="add" src="../images/add.jpg"/> Added first implementation of 
+        the dispatcher. Including contract bean implementation and interface; 
+        dispatcher exception and dispatcher transformers. (TS)</li><li><icon alt="add" src="../images/add.jpg"/>
         The broken-links file is now copied into to the site root as
         "broken-links.xml" so that when building with Forrestbot
         you can easily view it.

Modified: forrest/site/docs_0_80/compliance.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/compliance.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_80/compliance.html (original)
+++ forrest/site/docs_0_80/compliance.html Sun Dec 18 17:31:25 2005
@@ -368,11 +368,11 @@
         unless the user has turned this off.
       </p>
 <p>
-        The "<span class="codefrag ">pelt</span>" skin
+        The "<span class="codefrag">pelt</span>" skin
         validates as HTML 4.0.1
       </p>
 <p>
-        The "<span class="codefrag ">tigris</span>" skin
+        The "<span class="codefrag">tigris</span>" skin
         validates as HTML 4.0.1
       </p>
 </div> 



Mime
View raw message