forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r357603 [3/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_60/your-project.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/your-project.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_60/your-project.html (original)
+++ forrest/site/docs_0_60/your-project.html Sun Dec 18 17:31:25 2005
@@ -394,8 +394,8 @@
 <pre class="code">
 Go to "My Computer", "Properties", "Advanced", "Environment Variables"
 and add:
-<span class="codefrag ">FORREST_HOME</span> as <span class="codefrag ">C:\full\path\to\apache-forrest-0.6\src\core</span>
-<span class="codefrag ">PATH</span> as <span class="codefrag ">%PATH%;%FORREST_HOME%\bin</span>
+<span class="codefrag">FORREST_HOME</span> as <span class="codefrag">C:\full\path\to\apache-forrest-0.6\src\core</span>
+<span class="codefrag">PATH</span> as <span class="codefrag">%PATH%;%FORREST_HOME%\bin</span>
      
 </pre>
 <p>
@@ -589,16 +589,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>
@@ -617,7 +617,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>
@@ -635,7 +635,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;!--
@@ -799,9 +799,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>
@@ -816,7 +816,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>
@@ -854,7 +854,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>
@@ -880,7 +880,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.
@@ -894,14 +894,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="N1010E"></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_60/linking.html">Menus and Linking</a>.
@@ -909,7 +909,7 @@
 <a name="N1011F"></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_60/linking.html#menu_generation">menu generation</a> documentation
@@ -921,12 +921,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">
@@ -939,9 +939,9 @@
 <a name="N1014A"></a><a name="images"></a>
 <h3 class="underlined_5">Images</h3>
 <p>
-          Images usually go in <span class="codefrag ">src/documentation/resources/images/</span>
+          Images usually go in <span class="codefrag">src/documentation/resources/images/</span>
           The default sitemap
-          maps this directory to <span class="codefrag ">images/</span>, so image tags will typically look
+          maps this directory to <span class="codefrag">images/</span>, so image tags will typically look
           like &lt;figure src="images/project-logo.png" alt="Project Logo"/&gt; 
         </p>
 </div>
@@ -977,8 +977,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
@@ -992,13 +992,13 @@
 </ul>
 <p>
         The Forrest sitemaps are at
-        <span class="codefrag ">forrest/src/core/context/*.xmap</span>
+        <span class="codefrag">forrest/src/core/context/*.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). Any match that
+        <span class="codefrag">src/documentation</span> directory (or wherever
+        <span class="codefrag">${project.sitemap-dir}</span> points to). Any match that
         is not handled, passes through to be handled by the default Forrest
         sitemaps - obviously extremely powerful. The capability is described
         in 
@@ -1072,15 +1072,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
@@ -1117,7 +1117,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>
@@ -1134,7 +1134,7 @@
 </div>
 <p>
             Add the following as 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;
@@ -1172,7 +1172,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>
@@ -1244,7 +1244,7 @@
 </pre>
 <p>
               This is the type of processing that happens in the main
-              <span class="codefrag ">src/core/context/forrest.xmap</span> sitemap. We have
+              <span class="codefrag">src/core/context/forrest.xmap</span> sitemap. We have
               added similar handling to our project sitemap. Basically, this
               uses the <a href="../docs_0_60/cap.html">SourceTypeAction (content aware pipelines)</a>
               to detect the doctype. The new document-v11.dtd needs to be also
@@ -1279,9 +1279,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>
@@ -1294,10 +1294,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.
         </p>
 <div class="note">
 <div class="label">Note</div>
@@ -1312,7 +1312,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>
@@ -1326,14 +1326,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 ">forrest/src/core/context/skins/pelt</span>
+            <span class="codefrag">forrest/src/core/context/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:
@@ -1341,7 +1341,7 @@
 <dl>
             
 <dt>
-<span class="codefrag ">xslt/html/document2html.xsl</span>
+<span class="codefrag">xslt/html/document2html.xsl</span>
 </dt>
             
 <dd>
@@ -1350,7 +1350,7 @@
             </dd>
             
 <dt>
-<span class="codefrag ">xslt/html/site2xhtml.xsl</span>
+<span class="codefrag">xslt/html/site2xhtml.xsl</span>
 </dt>
             
 <dd>
@@ -1374,7 +1374,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 ">forrest/src/core/context/skins/common</span>).
+          directory (from <span class="codefrag">forrest/src/core/context/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>
@@ -1401,20 +1401,20 @@
 <a name="N102DB"></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="N102F4"></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>
@@ -1444,12 +1444,12 @@
 <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>.
+        like this: <span class="codefrag">forrest -f myproject.xml</span>.
         This will not run forrest; it will just use Forrest's Ant to execute
         your buildfile.)
       </p>

Modified: forrest/site/docs_0_70/build.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/build.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/build.html (original)
+++ forrest/site/docs_0_70/build.html Sun Dec 18 17:31:25 2005
@@ -355,16 +355,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>
@@ -389,8 +389,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>
@@ -409,8 +409,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">
@@ -435,7 +435,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_70/cap.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/cap.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/cap.html (original)
+++ forrest/site/docs_0_70/cap.html Sun Dec 18 17:31:25 2005
@@ -362,7 +362,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
@@ -374,31 +374,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_70/catalog.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/catalog.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/catalog.html (original)
+++ forrest/site/docs_0_70/catalog.html Sun Dec 18 17:31:25 2005
@@ -405,15 +405,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>
@@ -427,8 +427,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:
@@ -563,7 +563,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_70/changes.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/changes.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/changes.html (original)
+++ forrest/site/docs_0_70/changes.html Sun Dec 18 17:31:25 2005
@@ -332,10 +332,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>
@@ -349,13 +349,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>
@@ -363,19 +363,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>
@@ -383,10 +383,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>
@@ -394,13 +394,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>
@@ -408,13 +408,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>
@@ -422,16 +422,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>
@@ -439,7 +439,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>
@@ -447,22 +447,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>
@@ -482,6 +482,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
@@ -535,7 +544,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>.
@@ -560,7 +569,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
@@ -607,7 +616,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>
@@ -623,7 +632,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 
@@ -635,10 +644,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>
@@ -651,7 +660,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>
@@ -663,10 +672,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>
@@ -674,7 +683,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>
@@ -684,7 +693,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>
@@ -937,7 +946,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>
@@ -1027,7 +1036,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 
@@ -1050,10 +1059,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>
@@ -1064,7 +1073,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>
@@ -1088,7 +1097,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>
@@ -1418,7 +1427,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
@@ -1450,8 +1459,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>
@@ -1833,7 +1842,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>
@@ -1890,7 +1899,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 
@@ -1916,10 +1925,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>
@@ -1927,7 +1936,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>
@@ -1967,10 +1976,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>
@@ -2006,9 +2015,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">
@@ -2143,7 +2152,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">
@@ -2163,7 +2172,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>
@@ -2175,7 +2184,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>
@@ -2186,13 +2195,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>
@@ -2208,7 +2217,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">
@@ -2264,7 +2273,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>
@@ -2348,7 +2357,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>
@@ -2357,7 +2366,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 
@@ -2374,10 +2383,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>
@@ -2430,7 +2439,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>
@@ -2454,7 +2463,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>
@@ -2463,7 +2472,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 
@@ -2476,10 +2485,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>
@@ -2494,7 +2503,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>
@@ -2504,7 +2513,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>
@@ -2537,51 +2546,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>
@@ -2633,13 +2642,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
@@ -2725,7 +2734,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>
@@ -2735,7 +2744,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 
@@ -2746,10 +2755,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>
@@ -2761,7 +2770,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">
@@ -2770,10 +2779,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>
@@ -2781,7 +2790,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>
@@ -2863,8 +2872,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">
@@ -2881,7 +2890,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>
@@ -2918,12 +2927,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>
@@ -2997,7 +3006,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>
@@ -3029,7 +3038,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>
@@ -3038,7 +3047,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>
@@ -3049,7 +3058,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">
@@ -3126,7 +3135,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 
@@ -3142,7 +3151,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_70/changes.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/changes.pdf?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/docs_0_70/changes.rss
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/changes.rss?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/changes.rss (original)
+++ forrest/site/docs_0_70/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_70/changes.xml
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/changes.xml?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/changes.xml (original)
+++ forrest/site/docs_0_70/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_70/compliance.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/compliance.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/compliance.html (original)
+++ forrest/site/docs_0_70/compliance.html Sun Dec 18 17:31:25 2005
@@ -350,11 +350,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> 

Modified: forrest/site/docs_0_70/faq.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/faq.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/faq.html (original)
+++ forrest/site/docs_0_70/faq.html Sun Dec 18 17:31:25 2005
@@ -572,14 +572,14 @@
 <p> There are two ways to control this. If you get an OutOfMemoryError when Cocoon is
           generating pages, see the first paragraph. If you get an OutOfMemoryError when outside of
           Cocoon (e.g., copying raw files), see the second paragraph. </p>
-<p> The <span class="codefrag ">maxmemory</span> property in the <span class="codefrag ">forrest.properties</span> file controls
+<p> The <span class="codefrag">maxmemory</span> property in the <span class="codefrag">forrest.properties</span> file controls
           how much memory Cocoon uses. Like many other properties you can copy them from the default
-          configuration at <span class="codefrag ">src/core/fresh-site/forrest.properties</span>
+          configuration at <span class="codefrag">src/core/fresh-site/forrest.properties</span>
         
 </p>
-<p> Set the <span class="codefrag ">ANT_OPTS</span> environment variable before you run forrest. The exact
+<p> Set the <span class="codefrag">ANT_OPTS</span> environment variable before you run forrest. The exact
           value you set it to is dependant on your JVM, but something like
-          <span class="codefrag ">ANT_OPTS=-Xmx500M</span> will probably work. </p>
+          <span class="codefrag">ANT_OPTS=-Xmx500M</span> will probably work. </p>
 </div>
 <a name="N10080"></a><a name="content_faqs"></a>
 <h3 class="underlined_5">2. Content Creation</h3>
@@ -608,7 +608,7 @@
 </div>
 <div style="margin-left: 15px">
 <p>
-          The <span class="codefrag ">site.xml</span> configuration file is used for two different purposes:
+          The <span class="codefrag">site.xml</span> configuration file is used for two different purposes:
           defining the left-hand navigation menus, and as a method for defining references
           to be used when linking between documents.
           This file is fully explained in
@@ -688,8 +688,8 @@
             page break on. All the common block grouping elements support this class, for example, 
             note, warning, p and so on.</p>
 <p>If you want these classes to be processed in your HTML documents as well you should add
-          the following to the <span class="codefrag ">extra-css</span> element in your projects
-          <span class="codefrag ">skinconf.xml</span>
+          the following to the <span class="codefrag">extra-css</span> element in your projects
+          <span class="codefrag">skinconf.xml</span>
         
 </p>
 <pre class="code"> .pageBreakBefore { margin-bottom: 0; page-break-before: always; } .pageBreakAfter {
@@ -702,7 +702,7 @@
 <a href="#clickable-email-address-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p>You would override <span class="codefrag ">
+<p>You would override <span class="codefrag">
             $FORREST_HOME/main/webapp/skins/common/xslt/html/document2html.xsl</span> and edit the
           "headers/authors" template. </p>
 </div>
@@ -736,7 +736,7 @@
 </li>
           
 <li>Unpack the Jimi distribution and copy JimiProClasses.zip to
-              <span class="codefrag ">$FORREST/lib/optional/jimi-1.0.jar</span>.</li>
+              <span class="codefrag">$FORREST/lib/optional/jimi-1.0.jar</span>.</li>
         
 </ol>
 <p>Alternatively you can use JAI (Java Advanced Imaging API at
@@ -755,9 +755,9 @@
 <a href="#tab-index-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p> In <span class="codefrag ">tabs.xml</span>, use @href instead of @dir, and omit the trailing '/'. Which
+<p> In <span class="codefrag">tabs.xml</span>, use @href instead of @dir, and omit the trailing '/'. Which
           file to serve is then a concern of the sitemap. For example, if the "User Manual" tab
-          should link to <span class="codefrag ">manual/Introduction.html</span> then <span class="codefrag ">tabs.xml</span> should
+          should link to <span class="codefrag">manual/Introduction.html</span> then <span class="codefrag">tabs.xml</span> should
           contain: </p>
 <pre class="code">
   &lt;tab label="User Manual" href="manual"/&gt;</pre>
@@ -845,7 +845,7 @@
 </div>
 <div style="margin-left: 15px">
 <p> Use the numeric values for character entities. For example, rather than using
-            <span class="codefrag ">&amp;ouml;</span> use <span class="codefrag ">&amp;#246;</span>
+            <span class="codefrag">&amp;ouml;</span> use <span class="codefrag">&amp;#246;</span>
         
 </p>
 <p> See the <a href="http://www.w3.org/TR/xhtml-modularization/dtd_module_defs.html#a_xhtml_character_entities">XHTML Character Entities</a> and see more discussion at <a href="http://issues.apache.org/jira/browse/FOR-244">Issue FOR-244</a>. </p>
@@ -873,7 +873,7 @@
 <p>but the file content is actually using ISO-8859-1 then you will receive validation
           errors, especially if you include some non-ASCII characters.</p>
 <p> This situation is commonly encountered when you edit the templates created by
-            <span class="codefrag ">forrest seed</span> with your favorite (probably localized) editor without paying
+            <span class="codefrag">forrest seed</span> with your favorite (probably localized) editor without paying
           attention to the encoding, or when you create a new file and simply copy the headers from
           another file. </p>
 <p>Although UTF-8 is an encoding well-suited for most languages, it is not usually the
@@ -881,16 +881,16 @@
           handle different encodings to write the file in disk. With some editors the encoding of
           the file is preserved, while with others the default is used regardless of the original
           encoding. In most cases the encoding used to write files can be controlled by setting the
-          environment variable <span class="codefrag ">LANG</span> to an appropriate value, for instance: </p>
+          environment variable <span class="codefrag">LANG</span> to an appropriate value, for instance: </p>
 <pre class="code">[localhost]$ export LANG=en_US.UTF-8</pre>
 <p>Of course the <em>appropriate</em> way to set the encoding depends on the editor/OS, but
           ultimately relys on the user preferences. So you can use the encoding you prefer, as long
-          as the <span class="codefrag ">encoding</span> attribute of the xml declaration matches the actual encoding
+          as the <span class="codefrag">encoding</span> attribute of the xml declaration matches the actual encoding
           of the file. This means that if you are not willing to abandon ISO-8859-1 you can always
           use the following declaration instead:</p>
 <pre class="code">&lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;</pre>
-<p>Another option is to use "character entities" such as <span class="codefrag ">&amp;ouml;</span>
-          (&ouml;) or the numeric form <span class="codefrag ">&amp;#246;</span> (&ouml;). </p>
+<p>Another option is to use "character entities" such as <span class="codefrag">&amp;ouml;</span>
+          (&ouml;) or the numeric form <span class="codefrag">&amp;#246;</span> (&ouml;). </p>
 <p>Another related issue is that your webserver needs to send http headers with the matching
           charset definitions to the html page. </p>
 <p>Here are some references which explain further: <a href="http://orixo.com/events/gt2004/bios.html#torsten">GT2004 presentation by Torsten
@@ -978,8 +978,8 @@
 <a href="#proxy_config-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p>You can configure the proxy in the <span class="codefrag ">forrest.properties</span> file. Set the
-            <span class="codefrag ">proxy.host</span> and <span class="codefrag ">proxy.port</span> accordingly (the port will default
+<p>You can configure the proxy in the <span class="codefrag">forrest.properties</span> file. Set the
+            <span class="codefrag">proxy.host</span> and <span class="codefrag">proxy.port</span> accordingly (the port will default
           to port 80).</p>
 </div>
 <a name="N10285"></a><a name="CVS_revison_tags"></a>
@@ -988,7 +988,7 @@
 <a href="#CVS_revison_tags-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p>If you have:<span class="codefrag ">&lt;version&gt;$Revision: 1.30
+<p>If you have:<span class="codefrag">&lt;version&gt;$Revision: 1.30
           $&lt;/version&gt;</span>The '1.30' will be extracted and
           displayed at the bottom of the page as "version 1.30". See for example the
           bottom of the <a href="../docs_0_70/your-project.html"> Using Forrest</a> document.</p>
@@ -1004,13 +1004,13 @@
 <div style="margin-left: 15px">
 <p> Forrest uses a configuration file to control the processing done by the Apache Cocoon
           command-line called cli.xconf </p>
-<p> Your project can supply its own <span class="codefrag ">cli.xconf</span> and define patterns for URIs to
+<p> Your project can supply its own <span class="codefrag">cli.xconf</span> and define patterns for URIs to
           exclude. There are also other powerful configuration features. </p>
-<p> This means creating a directory <span class="codefrag ">src/documentation/conf</span> (or wherever
-            <span class="codefrag ">${forrest.conf-dir}</span> points) and copying
-            <span class="codefrag ">$FORREST_HOME/main/webapp/WEB-INF/cli.xconf</span> to it. Declare the location of
+<p> This means creating a directory <span class="codefrag">src/documentation/conf</span> (or wherever
+            <span class="codefrag">${forrest.conf-dir}</span> points) and copying
+            <span class="codefrag">$FORREST_HOME/main/webapp/WEB-INF/cli.xconf</span> to it. Declare the location of
           this file in the forrest.properties configuration, e.g.
-            <span class="codefrag ">project.configfile=${project.home}/src/documentation/conf/cli.xconf</span>
+            <span class="codefrag">project.configfile=${project.home}/src/documentation/conf/cli.xconf</span>
         
 </p>
 <p> Then edit cli.xconf, and add any exclude sections that you require. The default
@@ -1029,7 +1029,7 @@
 <div class="note">
 <div class="label">Note</div>
 <div class="content"> Wildcards may be used. These are a powerful feature of Cocoon's <a href="../docs_0_70/sitemap-ref.html">sitemap</a>. For example, <strong>foo/*</strong> would match
-            <span class="codefrag ">foo/bar</span>, but not <span class="codefrag ">foo/bar/baz</span> &mdash; use
+            <span class="codefrag">foo/bar</span>, but not <span class="codefrag">foo/bar/baz</span> &mdash; use
           <strong>foo/**</strong> to match that. </div>
 </div>
 </div>
@@ -1041,7 +1041,7 @@
 </div>
 <div style="margin-left: 15px">
 <p> This can be done by overriding the <a href="#cli-xconf">
-            <span class="codefrag ">cli.xconf</span>
+            <span class="codefrag">cli.xconf</span>
           </a> Cocoon config file, and defining patterns for URLs to exclude. </p>
 </div>
 <a name="N102E3"></a><a name="claimed_patterns"></a>
@@ -1051,7 +1051,7 @@
 </div>
 <div style="margin-left: 15px">
 <p> Certain patterns are claimed by the default sitemaps for special processing. These
-          include: <span class="codefrag ">site, changes, todo, faq, images, my-images, skinconf, community,
+          include: <span class="codefrag">site, changes, todo, faq, images, my-images, skinconf, community,
           howto</span>
         
 </p>
@@ -1101,8 +1101,8 @@
 </div>
 <div style="margin-left: 15px">
 <p> If you are using JDK 1.4.0 or newer, you can enable <em>headless</em> operation by
-          running Forrest with the <span class="codefrag ">forrest.jvmarg</span> parameter set to
-            <span class="codefrag ">-Djava.awt.headless=true</span>, like this: </p>
+          running Forrest with the <span class="codefrag">forrest.jvmarg</span> parameter set to
+            <span class="codefrag">-Djava.awt.headless=true</span>, like this: </p>
 <pre class="code">forrest -Dforrest.jvmargs=-Djava.awt.headless=true site</pre>
 <p> See also <a href="http://cocoon.apache.org/2.1/faq/faq-configure-environment.html">Cocoon FAQ</a>. </p>
 </div>
@@ -1117,11 +1117,11 @@
 <p>
           In a 'forrest seed site' the project and the group logo are generated from a
           Scalable Vector Graphics (SVG) file, using the text from the
-          <span class="codefrag ">&lt;project-name&gt;</span> and
-          <span class="codefrag ">&lt;group-name&gt;</span> elements of the <span class="codefrag ">skinconf.xml</span> file.
+          <span class="codefrag">&lt;project-name&gt;</span> and
+          <span class="codefrag">&lt;group-name&gt;</span> elements of the <span class="codefrag">skinconf.xml</span> file.
           If you have a long project-name then you may need to adjust the width of the image.
           Perhaps you want to change the colours too. Edit the file at
-          <span class="codefrag ">src/documentation/content/xdocs/images/project.svg</span> and adjust the "width"
+          <span class="codefrag">src/documentation/content/xdocs/images/project.svg</span> and adjust the "width"
           attribute of the &lt;svg&gt; element. For further details see
           <a href="http://www.w3.org/Graphics/SVG/">SVG</a> resources.
         </p>
@@ -1202,7 +1202,7 @@
 <a href="#breadcrumbs-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p>Breadcrumbs begin with up to three URLs specified in <span class="codefrag ">skinconf.xml</span>. Here is
+<p>Breadcrumbs begin with up to three URLs specified in <span class="codefrag">skinconf.xml</span>. Here is
           what the Forrest site uses:</p>
 <pre class="code">
   &lt;trail&gt;
@@ -1213,7 +1213,7 @@
 <p>If any links are blank, they are not used. After these first links, JavaScript looks at
           the URL for the current page and makes a link for each directory after the domain. If you
           are viewing the site locally, there is no domain and so there will be no extra
-          breadcrumbs, only the ones that are specified in <span class="codefrag ">skinconf.xml</span>. </p>
+          breadcrumbs, only the ones that are specified in <span class="codefrag">skinconf.xml</span>. </p>
 </div>
 <a name="N103B8"></a><a name="run_port"></a>
 <h4 class="faq">3.13. How do I make forrest run listen on a different port?</h4>
@@ -1223,11 +1223,11 @@
 <div style="margin-left: 15px">
 <p>
           
-<span class="codefrag ">forrest run -Dforrest.jvmargs="-Djetty.port=80"</span>
+<span class="codefrag">forrest run -Dforrest.jvmargs="-Djetty.port=80"</span>
         
 </p>
 <p>Or copy Forrest's main/webapp/jettyconf.xml file to your project's src/documentation
-          directory and set the port number in that file. Then do <span class="codefrag ">forrest run</span>
+          directory and set the port number in that file. Then do <span class="codefrag">forrest run</span>
         
 </p>
 </div>
@@ -1240,7 +1240,7 @@
 </div>
 <div style="margin-left: 15px">
 <p> Certain patterns are claimed by the default sitemaps for special processing. These
-          include: <span class="codefrag ">site, changes, todo, faq, images, my-images, skinconf, community,
+          include: <span class="codefrag">site, changes, todo, faq, images, my-images, skinconf, community,
           howto</span>
         
 </p>
@@ -1257,12 +1257,12 @@
 <a href="#generating_menus-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p> One <span class="codefrag ">site.xml</span> file in your project root can replace all the book.xml files (one per
-          directory) in your site. Internally, Forrest uses <span class="codefrag ">site.xml</span> to dynamically generate book.xml
+<p> One <span class="codefrag">site.xml</span> file in your project root can replace all the book.xml files (one per
+          directory) in your site. Internally, Forrest uses <span class="codefrag">site.xml</span> to dynamically generate book.xml
           files. However, Forrest first checks for the existence of a book.xml file, so
           backwards-compatibility is preserved. If a directory has a book.xml file, the book.xml
           will be used to generate the menu. This supplement is useful in situations where
-          <span class="codefrag ">site.xml</span>-generated menus aren't appropriate. See <a href="../docs_0_70/linking.html">Menus and
+          <span class="codefrag">site.xml</span>-generated menus aren't appropriate. See <a href="../docs_0_70/linking.html">Menus and
             Linking</a>. </p>
 </div>
 <a name="N10401"></a><a name="docbook"></a>
@@ -1271,7 +1271,7 @@
 <a href="#docbook-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p> There are two ways. Forrest has a <span class="codefrag ">simplifiedDocbook</span> plugin which can
+<p> There are two ways. Forrest has a <span class="codefrag">simplifiedDocbook</span> plugin which can
           transform the DocBook format into the Forrest "xdocs" format on-the-fly and then render
           that as normal Forrest documents. Be aware that the stylesheet that does this
           transformation is deliberately very limited and does not attempt to deal with all DocBook
@@ -1302,7 +1302,7 @@
         in the components section of the sitemap. See the 
         <a href="http://cocoon.apache.org/2.1/userdocs/serializers/xhtml-serializer.html">Cocoon
         docs</a> for the elements you need to add to define this component. You can see examples 
-        of other components being added in the <span class="codefrag ">FORREST_HOME/main/webapp/sitemap.xmap</span> file.</p>
+        of other components being added in the <span class="codefrag">FORREST_HOME/main/webapp/sitemap.xmap</span> file.</p>
 <p> You can also use a mixture of the two methods, some handled automatically by Forrest and
           some directly using DocBook stylesheets. You can also have a mixture of source files as
           "document-v*" DTD and DocBook. </p>
@@ -1318,10 +1318,10 @@
 <a href="#version-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p> Do <span class="codefrag ">'forrest -projecthelp'</span> or <span class="codefrag ">'./build.sh'</span> to find the version
+<p> Do <span class="codefrag">'forrest -projecthelp'</span> or <span class="codefrag">'./build.sh'</span> to find the version
           number. </p>
 <p> To list the properties, add "forrest.echo=true" to your forrest.properties file and
-          watch the build messages. Doing <span class="codefrag ">'forrest -v'</span> will provide verbose build
+          watch the build messages. Doing <span class="codefrag">'forrest -v'</span> will provide verbose build
           messages. </p>
 </div>
 <a name="N10443"></a><a name="logs"></a>
@@ -1330,17 +1330,17 @@
 <a href="#logs-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p> The logfiles are at <span class="codefrag ">build/webapp/WEB-INF/logs/</span>
+<p> The logfiles are at <span class="codefrag">build/webapp/WEB-INF/logs/</span>
         
 </p>
-<p> The log level can be raised with the <span class="codefrag ">logkit.xconf</span> configuration. If you are
+<p> The log level can be raised with the <span class="codefrag">logkit.xconf</span> configuration. If you are
           using Forrest in the interactive webapp mode (which is generally easiest for debugging
-          errors) then see the <span class="codefrag ">build/webapp/WEB-INF/logkit.xconf</span> file. If you are
+          errors) then see the <span class="codefrag">build/webapp/WEB-INF/logkit.xconf</span> file. If you are
           generating a static site (with command-line 'forrest') then copy
-            <span class="codefrag ">$FORREST_HOME/main/webapp/WEB-INF/logkit.xconf</span> to your project at
-            <span class="codefrag ">src/documentation/content/conf/logkit.xconf</span> and modify it. See more
+            <span class="codefrag">$FORREST_HOME/main/webapp/WEB-INF/logkit.xconf</span> to your project at
+            <span class="codefrag">src/documentation/content/conf/logkit.xconf</span> and modify it. See more
           information and efficiency tips with <a href="http://wiki.apache.org/cocoon/ExploringTheLogs">Cocoon logging</a>. </p>
-<p> Doing <span class="codefrag ">'forrest -v'</span> will provide verbose build messages to the standard
+<p> Doing <span class="codefrag">'forrest -v'</span> will provide verbose build messages to the standard
           output. </p>
 </div>
 <a name="N10467"></a><a name="how_can_I_help"></a>



Mime
View raw message