forrest-site-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r527020 [7/20] - in /forrest/site: ./ docs_0_80/ docs_0_80/howto/ docs_0_80/howto/cvs-ssh/ docs_0_80/howto/multi/ dtdx/ plan/ pluginDocs/plugins_0_70/ pluginDocs/plugins_0_80/ procedures/ procedures/release/ skins/ tools/
Date Tue, 10 Apr 2007 04:44:05 GMT
Modified: forrest/site/docs_0_80/howto/howto-custom-html-source.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-custom-html-source.html?view=diff&rev=527020&r1=527019&r2=527020
==============================================================================
--- forrest/site/docs_0_80/howto/howto-custom-html-source.html (original)
+++ forrest/site/docs_0_80/howto/howto-custom-html-source.html Mon Apr  9 21:44:00 2007
@@ -401,25 +401,26 @@
 <h2 class="underlined_10">Intended Audience</h2>
 <div class="section">
 <p>
-      Users who want to integrate HTML-pages that require custom
-      adjustments and everybody who wants to learn more about Forrest's
-      pipelines in general.
+      Users who want to integrate HTML-pages that require custom adjustments and
+      everybody who wants to learn more about Forrest's pipelines in general.
     </p>
 </div>
 <a name="N10018"></a><a name="Purpose"></a>
 <h2 class="underlined_10">Purpose</h2>
 <div class="section">
 <p>
-      Integrating legacy HTML pages is a common task when migrating
-      existing websites to Forrest. This document explains how to implement
-      custom processing which is required when Forrest's standard pipeline
-      for html does not suffice.
+      Integrating legacy HTML pages is a common task when migrating existing
+      websites to Forrest. This document explains how to implement custom
+      processing which is required when Forrest's standard pipeline for html
+      does not suffice.
     </p>
 </div>
 <a name="N10020"></a><a name="Prerequisites"></a>
 <h2 class="underlined_10">Prerequisites</h2>
 <div class="section">
-<p>To follow these instructions you will need:</p>
+<p>
+      To follow these instructions you will need:
+    </p>
 <ol>
       
 <li>
@@ -456,125 +457,124 @@
 <h2 class="underlined_10">Understanding the HTML-Pipeline</h2>
 <div class="section">
 <p>
-      The first part of this howto explains the html pipeline, so as to
-      provide the background to enable you to add additional processing
-      for legacy html documents. If you already know how pipelines work,
-      then skip to the section about
-      <a href="#custom">Customizing the html pipeline</a>.
+      The first part of this howto explains the html pipeline, so as to provide
+      the background to enable you to add additional processing for legacy html
+      documents. If you already know how pipelines work, then skip to the
+      section about <a href="#custom">Customizing the html pipeline</a>.
     </p>
 <a name="N1004F"></a><a name="example"></a>
 <h3 class="underlined_5">Driven by Example</h3>
 <p>
-        The best way to learn about Forrest pipelines is follow
-        the processing of an imaginary request through the forrest
-        machinery.
+        The best way to learn about Forrest pipelines is follow the processing
+        of an imaginary request through the forrest machinery.
       </p>
 <p>
-        So let's see what happens, when a client asks Forrest to
-        serve the document
+        So let's see what happens, when a client asks Forrest to serve the
+        document
         <br>
         'http://my.domain.org/mytest/mybad.html'.
       </p>
 <a name="N1005E"></a><a name="sitemap"></a>
 <h3 class="underlined_5">Finding the Sitemap</h3>
 <p>
-        Like all applications based on Apache Cocoon, each request for
-        a given document is processed by searching a sitemap for a
-        matching processing pipeline. With Forrest, this core sitemap
-        is found in the file
+        Like all applications based on Apache Cocoon, each request for a given
+        document is processed by searching a sitemap for a matching processing
+        pipeline. With Forrest, this core sitemap is found in the file
         'main/webapp/sitemap.xmap' in Forrest's program directory.
       </p>
 <p class="instruction">
-        Open the file 'main/webapp/sitemap.xmap' in Forrest's
-        program directory with a text editor of your choice.
+        Open the file 'main/webapp/sitemap.xmap' in Forrest's program directory
+        with a text editor of your choice.
       </p>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-        Any simple text editor will suffice, since the XML in
-        this file is quite simple in structure and easy to read.
+        Any simple text editor will suffice, since the XML in this file is quite
+        simple in structure and easy to read.
       </div>
 </div>
 <p class="instruction">
-          Search for <span class="codefrag">map:sitemap</span> to find the 
-          start of the Sitemap.
+        Search for <span class="codefrag">
+map:sitemap
+        </span> to find the start of the Sitemap.
       </p>
 <p>
-        This sitemap is the starting point
-        for all requests. So even if there are other sitemaps
-        (which we will see later on), we always start looking for a
-        matching pattern right here.
+        This sitemap is the starting point for all requests. So even if there
+        are other sitemaps (which we will see later on), we always start looking
+        for a matching pattern right here.
       </p>
 <a name="N10079"></a><a name="pipelines"></a>
 <h3 class="underlined_5">Find the Beginning of the Pipelines Section</h3>
 <p>
-        Modular as everything else in Cocoon, Forrest's sitemap
-        starts with a long list of declarations for all the
-        components used later on. We can safely ignore these at
-        the moment.
+        Modular as everything else in Cocoon, Forrest's sitemap starts with a
+        long list of declarations for all the components used later on. We can
+        safely ignore these at the moment.
       </p>
 <p class="instruction">
-        So let's skip right to the start of the
-          Pipelines-Section. Search for <span class="codefrag">map:pipelines</span>
+        So let's skip right to the start of the Pipelines-Section. Search for
+        <span class="codefrag">
+map:pipelines
+        </span>
       
 </p>
 <p>
-        Within the pipelines-element you will find a long list
-        of pipeline-Elements (no trailing 's'), each one of them defining a
+        Within the pipelines-element you will find a long list of
+        pipeline-Elements (no trailing 's'), each one of them defining a
         processing pipeline within Forrest.
       </p>
 <p>
-        When handling a request, Forrest will check the
-        Pipelines from top to bottom until it encounters a
-        Pipeline that will take care of our request.
+        When handling a request, Forrest will check the Pipelines from top to
+        bottom until it encounters a Pipeline that will take care of our
+        request.
       </p>
 <a name="N10090"></a><a name="matches"></a>
 <h3 class="underlined_5">Looking for a Match</h3>
 <p>
-        Like all Cocoon applications, Forrest knows which
-        pipeline to use for processing a certain request by
-        looking at the entry criteria for each pipeline it comes
-        across. This can be a match against a given pattern,
-        the test if a certain files exists or one of many other
-        possible tests that Cocoon supports.
+        Like all Cocoon applications, Forrest knows which pipeline to use for
+        processing a certain request by looking at the entry criteria for each
+        pipeline it comes across. This can be a match against a given pattern,
+        the test if a certain files exists or one of many other possible tests
+        that Cocoon supports.
       </p>
 <p>
-        To better know what we are talking about, let's follow
-        Forrest down the list to the Test for the First Pipeline:
+        To better know what we are talking about, let's follow Forrest down the
+        list to the Test for the First Pipeline:
       </p>
 <p class="instruction">
-           Scroll down to the line
-           <span class="codefrag">&lt;map:match pattern="cprofile.*"&gt;</span>
+        Scroll down to the line <span class="codefrag">
+&lt;map:match pattern="cprofile.*"&gt;
+        </span>
       
 </p>
 <p>
-        Here you can see that very specialized matches need to occur
-        early in the sitemap. The
-        requested file (and pathname) is compared to a pattern
-        'cprofile.*' that would match if our request started with
-        'cprofile', endet with any kind of extension and had no pathname. Since it doesn't, we don't
-        have a match and need to keep looking.
+        Here you can see that very specialized matches need to occur early in
+        the sitemap. The requested file (and pathname) is compared to a pattern
+        'cprofile.*' that would match if our request started with 'cprofile',
+        endet with any kind of extension and had no pathname. Since it doesn't,
+        we don't have a match and need to keep looking.
       </p>
 <p class="instruction">
-        Skip forward until you find
-        <span class="codefrag">&lt;map:match pattern="**/*.html"&gt;</span>.
-          
+        Skip forward until you find <span class="codefrag">
+&lt;map:match pattern="**/*.html"&gt;
+        </span>.
       </p>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">While scrolling down you may have noticed the match-pattern  
-            <span class="codefrag">&lt;map:match pattern="*.html"&gt;</span> a couple of
-            lines earlier. This will not match our request since *.something in Cocoon matches only
-            files in the root directory.
-        </div>
+<div class="content">
+        While scrolling down you may have noticed the match-pattern <span class="codefrag">
+&lt;map:match pattern="*.html"&gt;
+        </span> a couple of lines earlier. This will not match our request since
+        *.something in Cocoon matches only files in the root directory.
+      </div>
 </div>
 <a name="N100B4"></a><a name="html-pipeline"></a>
 <h3 class="underlined_5">Processing in the '**/*.html' Pipeline</h3>
-<p>  
-        Let's take a quick look at this pipeline to understand
-        what's happening here:
+<p>
+        Let's take a quick look at this pipeline to understand what's happening
+        here:
       </p>
 <pre class="code">
+
 &lt;map:match pattern="**/*.html"&gt;
         &lt;map:aggregate element="site"&gt;
           &lt;map:part src="cocoon:/skinconf.xml"/&gt;
@@ -587,59 +587,60 @@
           &lt;map:parameter name="type" value="transform.site.xhtml"/&gt;
           &lt;map:parameter name="path" value="{0}"/&gt;
         &lt;/map:call&gt;
-      &lt;/map:match&gt;</pre>
+      &lt;/map:match&gt;
+      </pre>
 <p>
-        In the first part of this pipeline, the
-        aggregate-element assembles information required to build
-        a Forrest page with menu and tabs from different sources.
-        Then the call to the skinit-resource picks up the
-        aggregated info and generates a page in the
-        style of the current skin. That's easy, isn't it?
+        In the first part of this pipeline, the aggregate-element assembles
+        information required to build a Forrest page with menu and tabs from
+        different sources. Then the call to the skinit-resource picks up the
+        aggregated info and generates a page in the style of the current skin.
+        That's easy, isn't it?
       </p>
 <p>
-        Well, the complex part begins, when we take a closer look at
-        the sources of the aggregation.
+        Well, the complex part begins, when we take a closer look at the sources
+        of the aggregation.
       </p>
-<pre class="code">&lt;map:part src="cocoon:/{1}/body-{2}.html"/&gt;</pre>
+<pre class="code">
+&lt;map:part src="cocoon:/{1}/body-{2}.html"/&gt;
+      </pre>
 <p>
-        This mysterious element is most easily explained as a
-        secondary request to the Forrest system.
+        This mysterious element is most easily explained as a secondary request
+        to the Forrest system.
       </p>
 <p>
-        The 'cocoon:'-part is called a pseudo-protocol and tells the
-        processor to ask Forrest for the resource named behind
-        the colon, process that request and feed the output as input
-        back into our pipeline.
-        (The 'pseudo' goes back to the fact that unlike
-        'http' or 'ftp', which are real protocols, you can use cocoon:
-        only within the cocoon environments as only Cocoon will know what to
-        do with it.)
+        The 'cocoon:'-part is called a pseudo-protocol and tells the processor
+        to ask Forrest for the resource named behind the colon, process that
+        request and feed the output as input back into our pipeline. (The
+        'pseudo' goes back to the fact that unlike 'http' or 'ftp', which are
+        real protocols, you can use cocoon: only within the cocoon environments
+        as only Cocoon will know what to do with it.)
       </p>
 <p>
-        So even though we have already seen the end of our pipeline
-        (the skinning), we still don't know, what goes into the skinning and
-        where it comes from. To find out, we have to look at the sources
-        of the aggregation.
+        So even though we have already seen the end of our pipeline (the
+        skinning), we still don't know, what goes into the skinning and where it
+        comes from. To find out, we have to look at the sources of the
+        aggregation.
       </p>
 <a name="N100D5"></a><a name="protocols"></a>
 <h3 class="underlined_5">Following the Pseudo-Protocols</h3>
 <p>
-        To find out what goes into our aggregation, we'll need to look
-        at the pipeline that is called by
+        To find out what goes into our aggregation, we'll need to look at the
+        pipeline that is called by
+      </p>
+<pre class="code">
+&lt;map:part src="cocoon:/{1}/body-{2}.html"/&gt;
+      </pre>
+<p>
+        To do that, it's always a good idea to write down what this call
+        actually looks like when all the variables are replaced by real values.
+        A safe way to do that is to look at the matcher to start with, build a
+        list of the numbered variables and their meaning in the current context
+        and then assemble the actual expression(s) from it.
       </p>
-<pre class="code">&lt;map:part src="cocoon:/{1}/body-{2}.html"/&gt;</pre>
 <p>
-        To do that, it's always a good idea to write down what this
-        call actually looks like when all the variables are replaced by real
-        values.
-        A safe way to do that is to look at the matcher to start with,
-        build a list of the numbered variables and their meaning in the
-        current context and then assemble the actual expression(s) from it.
-      </p>
-<p>In our example the matcher pattern
-       <span class="codefrag">**/*.html</span> is applied to the request-name
-       <span class="codefrag">mytest/mybad.html</span>, so we have three variables
-       altogether:
+        In our example the matcher pattern <span class="codefrag">**/*.html</span> is applied to
+        the request-name <span class="codefrag">mytest/mybad.html</span>, so we have three
+        variables altogether:
       </p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
         
@@ -668,75 +669,86 @@
 </tr>
       
 </table>
-<p>If we insert that into </p>
-<pre class="code">&lt;map:part src="cocoon:/{1}/body-{2}.html"/&gt;</pre>
-<p>we get</p>
-<pre class="code">&lt;map:part src="cocoon:/mytest/body-mybad.html"/&gt;</pre>
 <p>
-        As you can easily tell, we are suddenly calling for a whole
-        new document. Let's see where that takes us:
+        If we insert that into
+      </p>
+<pre class="code">
+&lt;map:part src="cocoon:/{1}/body-{2}.html"/&gt;
+      </pre>
+<p>
+        we get
+      </p>
+<pre class="code">
+&lt;map:part src="cocoon:/mytest/body-mybad.html"/&gt;
+      </pre>
+<p>
+        As you can easily tell, we are suddenly calling for a whole new
+        document. Let's see where that takes us:
       </p>
 <a name="N10139"></a><a name="call"></a>
 <h3 class="underlined_5">Second Call for Content</h3>
 <p>
-        Processing of cocoon-calls is not much different from
-        normal requests by a client. When you launch a call like
+        Processing of cocoon-calls is not much different from normal requests by
+        a client. When you launch a call like
       </p>
-<pre class="code">&lt;map:part src="cocoon:/mytest/body-mybad.html"/&gt;</pre>
+<pre class="code">
+&lt;map:part src="cocoon:/mytest/body-mybad.html"/&gt;
+      </pre>
 <p>
-        Forrest will once again start searching its main sitemap
-        from the beginning and look for a pipeline to match that call.
+        Forrest will once again start searching its main sitemap from the
+        beginning and look for a pipeline to match that call.
       </p>
 <p class="instruction">
-          Search for <span class="codefrag">**body-*.html</span> from the beginning of the
-         sitemap to see where we find our next match.
+        Search for <span class="codefrag">
+**body-*.html
+        </span> from the beginning of the sitemap to see where we find our next
+        match.
       </p>
 <a name="N10151"></a><a name="match-1"></a>
 <h3 class="underlined_5">First Match for '**body-*.html'</h3>
 <p>
-         Our first match is different to the previous ones because
-         there is a second condition placed inside the matcher.
-         Doing the replacements
-       </p>
+        Our first match is different to the previous ones because there is a
+        second condition placed inside the matcher. Doing the replacements
+      </p>
 <pre class="code">
+
 &lt;map:select type="exists"&gt;
-          &lt;map:when test="{lm:project.{1}{2}.ehtml}"&gt;</pre>
+          &lt;map:when test="{lm:project.{1}{2}.ehtml}"&gt;
+      </pre>
 <p>
-         we quickly discover that there can't be a file of
-         that name in the project-directory.
-         <br>
-           (The variable '{lm:project.}' is always replaced with
-         the name of your project directory that you can change
-         in the 'forrest.properties'-file.)
-       </p>
-<p>
-         So we have a pipeline, but it doesn't do anything.
-         In this case Forrest will simply keep looking for
-         the next match further down.
-       </p>
+        we quickly discover that there can't be a file of that name in the
+        project-directory.
+        <br>
+        (The variable '{lm:project.}' is always replaced with the name of your
+        project directory that you can change in the 'forrest.properties'-file.)
+      </p>
+<p>
+        So we have a pipeline, but it doesn't do anything. In this case Forrest
+        will simply keep looking for the next match further down.
+      </p>
 <a name="N10167"></a><a name="match-2"></a>
 <h3 class="underlined_5">Second Match for '**body-*.html'</h3>
 <p class="instruction">
-         Continue searching downwards for '**body-*.html' in the
-         sitemap-file.
+        Continue searching downwards for '**body-*.html' in the sitemap-file.
       </p>
 <p>
-        Looking at the pipeline that handles the request, we see that
-        the cocoon-protocol is once again invoked
+        Looking at the pipeline that handles the request, we see that the
+        cocoon-protocol is once again invoked
       </p>
-<pre class="code">&lt;map:generate src="cocoon:/{1}{2}.xml"/&gt;</pre>
+<pre class="code">
+&lt;map:generate src="cocoon:/{1}{2}.xml"/&gt;
+      </pre>
 <p>
         this time as a direct generator of input for our pipeline.
       </p>
 <p>
-        So once again we ask Forrest to process a request for content.
-        To know what matcher to look for, let's first expand the variables:
+        So once again we ask Forrest to process a request for content. To know
+        what matcher to look for, let's first expand the variables:
       </p>
 <p>
-        In our example the matcher pattern
-        <span class="codefrag">**body-*.html</span> is applied to the request-name
-        <span class="codefrag">mytest/body-mybad.html</span>.
-        Which means that we have three variables altogether:
+        In our example the matcher pattern <span class="codefrag">**body-*.html</span> is applied
+        to the request-name <span class="codefrag">mytest/body-mybad.html</span>. Which means
+        that we have three variables altogether:
       </p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
         
@@ -768,11 +780,15 @@
 <p>
         If we insert that into
       </p>
-<pre class="code">&lt;map:generate src="cocoon:/{1}{2}.xml"/&gt;</pre>
+<pre class="code">
+&lt;map:generate src="cocoon:/{1}{2}.xml"/&gt;
+      </pre>
 <p>
         we get
       </p>
-<pre class="code">&lt;map:generate src="cocoon:/mytests/mybad.xml"/&gt;</pre>
+<pre class="code">
+&lt;map:generate src="cocoon:/mytests/mybad.xml"/&gt;
+      </pre>
 <a name="N101CF"></a><a name="match-3"></a>
 <h3 class="underlined_5">Third Call for Content</h3>
 <p class="instruction">
@@ -780,57 +796,70 @@
         '/mytests/mybad.xml'.
       </p>
 <p>
-        We find it in the pattern <span class="codefrag">&lt;map:match pattern="**.xml"&gt;</span>,
-        which is the standard handling for all xml-requests.
+        We find it in the pattern <span class="codefrag">
+&lt;map:match pattern="**.xml"&gt;
+        </span>, which is the standard handling for all xml-requests.
       </p>
 <p>
-        Since our request fulfils none of the secondary criteria in
-        this pipeline, it falls right through to the map:mount-element
-        at the end:
-        </p>
-<pre class="code">&lt;map:mount uri-prefix="" src="forrest.xmap" check-reload="yes" /&gt;</pre>
+        Since our request fulfils none of the secondary criteria in this
+        pipeline, it falls right through to the map:mount-element at the end:
+      </p>
+<pre class="code">
+&lt;map:mount uri-prefix="" src="forrest.xmap" check-reload="yes" /&gt;
+      </pre>
 <p>
-        which makes Forrest load and process a secondary sitemap,
-        the file 'forrest.xmap' in the same directory.
+        which makes Forrest load and process a secondary sitemap, the file
+        'forrest.xmap' in the same directory.
       </p>
 <p class="instruction">
-        Open the file 'forrest.xmap' and continue the search for a
-        matching pattern.
+        Open the file 'forrest.xmap' and continue the search for a matching
+        pattern.
+      </p>
+<p>
+        Our search first leads us to the matcher <span class="codefrag">
+&lt;map:match type="wildcard" pattern="**.xml"&gt;
+        </span> with a number of submatchers embedded into it.
       </p>
 <p>
-        Our search first leads us to the matcher <span class="codefrag">&lt;map:match type="wildcard" pattern="**.xml"&gt;</span> 
-          with a number of submatchers embedded into it. 
+        The first one, <span class="codefrag">
+&lt;map:match type="wildcard" pattern="**.xml"&gt;
+        </span>, would handle input coming from Forrest plugins. We won't go
+        into details here.
       </p>
-<p>The first one, <span class="codefrag">&lt;map:match type="wildcard" pattern="**.xml"&gt;</span>, would handle input coming from Forrest plugins. 
-      We won't go into details here.</p>
 <p>
-        All further matchers <span class="codefrag">&lt;map:match type="i18n" pattern="{properties:content.xdocs}{1}.*.xml"&gt; </span>.
-        implement what we call a cascade of matchers. By testing for the existence of one source file after another Forrest will use and process the 
-        first of the tested source-formats found.  
+        All further matchers <span class="codefrag">
+&lt;map:match type="i18n" pattern="{properties:content.xdocs}{1}.*.xml"&gt; 
+        </span>. implement what we call a cascade of matchers. By testing for
+        the existence of one source file after another Forrest will use and
+        process the first of the tested source-formats found.
       </p>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">Using the i18n-matcher here, Forrest will do a lot more than just finding content in one of many possible source formats. 
-          It will also make sure that the the proper language version of the conent (if there are several) is used. 
-          Read more about this matcher <a href="http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/matching/LocaleMatcher.html">http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/matching/LocaleMatcher.html</a>
+<div class="content">
+        Using the i18n-matcher here, Forrest will do a lot more than just
+        finding content in one of many possible source formats. It will also
+        make sure that the the proper language version of the conent (if there
+        are several) is used. Read more about this matcher
+        <a href="http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/matching/LocaleMatcher.html">http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/matching/LocaleMatcher.html</a>
+      
 </div>
 </div>
 <p>
-        Checking each matcher in turn you will find that a pipeline that tests for the existence of
-        the file with different extensions. '.html' is third in this
-        list and leads to the processing steps shown below:
+        Checking each matcher in turn you will find that a pipeline that tests
+        for the existence of the file with different extensions. '.html' is
+        third in this list and leads to the processing steps shown below:
       </p>
-<a name="N10209"></a><a name="process-html"></a>
+<a name="N1020A"></a><a name="process-html"></a>
 <h3 class="underlined_5">html-Default Processing</h3>
 <p>
-        The default processing of html-files consists of three
-        processing steps:
+        The default processing of html-files consists of three processing steps:
       </p>
 <ol>
         
 <li>
+<span class="codefrag">
+&lt;map:generate src="{source}" type="html" /&gt;</span>
           
-<span class="codefrag">&lt;map:generate src="{source}" type="html" /&gt;</span>
 <br>
             Using Cocoons html-generator, Forrest reads the html-document
             from file and uses JTidy to clean up and convert it to xml
@@ -842,8 +871,9 @@
         </li>
         
 <li>
-            
-<span class="codefrag">&lt;map:transform src="{lm:transform.html.document}" /&gt;</span>
+<span class="codefrag">
+&lt;map:transform src="{lm:transform.html.document}" /&gt;</span>
+          
 <br>
           Using the standard stylesheet 'html-to-document.xsl', this XHTML is 
             transformed into Forrest's <a href="../../docs_0_80/glossary.html">Standard Document Format</a>.  (refer to a detailed <a href="../../docs_0_80/locationmap.html">explanation of locationsmaps</a> 
@@ -851,8 +881,8 @@
         </li>
         
 <li>
-          
 <span class="codefrag">&lt;map:serialize type="xml-document"/&gt;</span>
+          
 <br>
           Finally the document is serialized as XML and returned to the
           calling pipeline.
@@ -860,35 +890,32 @@
       
 </ol>
 <p>
-        As a result, we now hand back the content of the html-document
-        in Forrest standard document format to the calling pipeline
+        As a result, we now hand back the content of the html-document in
+        Forrest standard document format to the calling pipeline
       </p>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-        To look at the output of this pipeline you can simply
-        point you browser to 'http://localhost:8888/mytest/mybad.xml'
-        (assuming that you are currently running Forrest on your
-        machine and there is an html-page of that name).
+        To look at the output of this pipeline you can simply point you browser
+        to 'http://localhost:8888/mytest/mybad.xml' (assuming that you are
+        currently running Forrest on your machine and there is an html-page of
+        that name).
       </div>
 </div>
-<a name="N1023D"></a><a name="body"></a>
+<a name="N1023E"></a><a name="body"></a>
 <h3 class="underlined_5">Returning to the '**body-*.html'-Pipeline</h3>
 <p>
-        On returning into the
-        '**body-*.html'-Pipeline (in sitemap.xmap),
+        On returning into the '**body-*.html'-Pipeline (in sitemap.xmap),
         processing continues with the next components in this pipeline:
       </p>
 <ul>
         
 <li>
-          
 <strong>idgen</strong> will generate unique IDs for all elements
           that need to be referenced within a page (mainly headlines).
         </li>
         
 <li>
-          
 <strong>xinclude</strong> would process any xinclude statements
           in the source.
           Since HTML does not support this mechanism, nothing happens
@@ -896,14 +923,14 @@
         </li>
         
 <li>
-          
 <strong>linkrewriter</strong> adjusts links between pages
           so that they will still work in the final Forrest output
           directory structure. It also resolves any special Forrest links.
         </li>
         
 <li>
-            The final transformation, <span class="codefrag">&lt;map:transform src="{lm:transform.html.broken-links}" /&gt;</span> as the name suggests, will take
+            The final transformation, <span class="codefrag">
+&lt;map:transform src="{lm:transform.html.broken-links}" /&gt;</span> as the name suggests, will take
           care of reporting broken site-links.
         </li>
         
@@ -916,50 +943,49 @@
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-        To look at the output of this pipeline you can simply
-        point you browser to 'http://localhost:8888/mytest/body-mybad.html'
-        (assuming that you are currently running Forrest on your machine
-        and there is an html-page of that name).
+        To look at the output of this pipeline you can simply point you browser
+        to 'http://localhost:8888/mytest/body-mybad.html' (assuming that you are
+        currently running Forrest on your machine and there is an html-page of
+        that name).
       </div>
 </div>
-<a name="N10268"></a><a name="aggregate"></a>
+<a name="N10266"></a><a name="aggregate"></a>
 <h3 class="underlined_5">Returning to the '**/*.html'-Pipeline</h3>
 <p>
-        At the end of this pipeline, processing returns the results into
-        the aggregation section of the
-        <a href="#html-pipeline">'**/*.html' Pipeline</a>,
-        merges it with other data, skins and serializes for presentation
-        in the requesting client.
+        At the end of this pipeline, processing returns the results into the
+        aggregation section of the <a href="#html-pipeline">'**/*.html'
+        Pipeline</a>, merges it with other data, skins and serializes for
+        presentation in the requesting client.
       </p>
-<a name="N10276"></a><a name="custom"></a>
+<a name="N10274"></a><a name="custom"></a>
 <h3 class="underlined_5">Customizing the html pipeline</h3>
 <p>
         In this last part of this document, we will show how to customize the
         HTML-pipeline to add your additional steps to the default processing.
       </p>
-<a name="N1027F"></a><a name="when"></a>
+<a name="N1027D"></a><a name="when"></a>
 <h4>When to customize?</h4>
 <p>
-          The html-Pipeline in Forrest is designed to be able to also
-          integrate legacy html-Pages in a Forrest project. In doing so,
-          it will fix common markup errors and convert html to Forrest's
-          intermediate document format.
+          The html-Pipeline in Forrest is designed to be able to also integrate
+          legacy html-Pages in a Forrest project. In doing so, it will fix
+          common markup errors and convert html to Forrest's intermediate
+          document format.
         </p>
 <p>
           Due to the nature of html as presentational markup, there is no way
-          this automated process can identify elements in your pages that
-          are not required or even unwanted in the Forrest environment. 
+          this automated process can identify elements in your pages that are
+          not required or even unwanted in the Forrest environment.
         </p>
 <p>
           A good example are pages from sites where the navigational elements
-          (menus, tabs etc.) are embedded in the html of each page.
-          Since Forrest can't know what is an unwanted menu and what belongs
-          to the page body that you want to keep, you will need to customize
-          the process to remove elements that are not needed. If you don't,
-          then you will see the original page from your legacy website,
-          menu and all, embedded in your new Forrest site.
+          (menus, tabs etc.) are embedded in the html of each page. Since
+          Forrest can't know what is an unwanted menu and what belongs to the
+          page body that you want to keep, you will need to customize the
+          process to remove elements that are not needed. If you don't, then you
+          will see the original page from your legacy website, menu and all,
+          embedded in your new Forrest site.
         </p>
-<a name="N1028F"></a><a name="how"></a>
+<a name="N1028D"></a><a name="how"></a>
 <h4>How to customize?</h4>
 <p>
           To add your own custom processing for a group of pages, you will
@@ -968,68 +994,72 @@
         </p>
 <p>
           This project sitemap is located in the file
-          'src/documentation/sitemap.xmap' in your Forrest project directory
-          and is created automatically whenever you seed a new project.
-          At this point it already contains a  few examples for custom pipelines.
+          'src/documentation/sitemap.xmap' in your Forrest project directory and
+          is created automatically whenever you seed a new project. At this
+          point it already contains a few examples for custom pipelines.
         </p>
 <p>
           To add your own custom processing, edit the file and add a new
-          pipeline to the project sitemap. Since the project sitemap is
-          loaded into the main sitemap right at the top (search for 'This is the user pipeline'),
-          your pipeline intercepts practically all of Forrest's standard pipelines.
+          pipeline to the project sitemap. Since the project sitemap is loaded
+          into the main sitemap right at the top (search for 'This is the user
+          pipeline'), your pipeline intercepts practically all of Forrest's
+          standard pipelines.
         </p>
-<a name="N1029F"></a><a name="what"></a>
+<a name="N1029D"></a><a name="what"></a>
 <h4>What to intercept?</h4>
 <p>
           Where to intercept standard processing is really a matter of your
-          choice. A good rule is to replace as little standard handling
-          as possible so that future changes in the Forrest architecture are
-          less likely to break your application.
+          choice. A good rule is to replace as little standard handling as
+          possible so that future changes in the Forrest architecture are less
+          likely to break your application.
         </p>
 <p>
-          In our case all we need to do is add a transformation that
-          removes all the unwanted elements. The best place to do this
-          would be right after the generator has converted our document to
-          xhtml.
+          In our case all we need to do is add a transformation that removes all
+          the unwanted elements. The best place to do this would be right after
+          the generator has converted our document to xhtml.
         </p>
 <p>
-          However, since we can only replace a complete pipeline,
-          we'll create a new pipeline that intercepts **.xml for our pages,
-          copy the steps the original processor is doing and add a
-          transformation of our own to it.
+          However, since we can only replace a complete pipeline, we'll create a
+          new pipeline that intercepts **.xml for our pages, copy the steps the
+          original processor is doing and add a transformation of our own to it.
         </p>
-<a name="N102AF"></a><a name="intercept"></a>
+<a name="N102AD"></a><a name="intercept"></a>
 <h4>Intercept pattern</h4>
 <p>
-          Take great care when intercepting very basic pipelines.
-          Instead of designing our custom pipeline to match the
-          original **.xml pattern, try to narrow your matcher down to
-          something that will only match your pages.
+          Take great care when intercepting very basic pipelines. Instead of
+          designing our custom pipeline to match the original **.xml pattern,
+          try to narrow your matcher down to something that will only match your
+          pages.
         </p>
 <p>
-          If all your pages are located in a directory called mytest,
-          then use a matcher like '/mytest/*.xml' to avoid highjacking
-          the processing for all the other requests.
+          If all your pages are located in a directory called mytest, then use a
+          matcher like '/mytest/*.xml' to avoid highjacking the processing for
+          all the other requests.
         </p>
 <p class="instruction">
-          Add a new pipeline in your project sitemap and set the matcher
-          to '/mytest/*.xml'.
+          Add a new pipeline in your project sitemap and set the matcher to
+          '/mytest/*.xml'.
         </p>
 <p>
           The new pipeline should look like this and does nothing so far.
         </p>
 <pre class="code">
+
 &lt;!--Custom Pipeline for my bad html-pages--&gt;        
 &lt;map:pipeline&gt;
     &lt;map:match pattern="mytest/*.xml"&gt;
 
     &lt;/map:match&gt;
-&lt;/map:pipeline&gt;</pre>
+&lt;/map:pipeline&gt;
+        </pre>
 <p class="instruction">
-          Open the 'forrest.xmap', search for <span class="codefrag">&lt;map:match type="i18n" pattern="{properties:content.xdocs}{1}.*.html"&gt;</span>,
-          copy the three lines for handling *.html files and paste them into your new pipeline.
+          Open the 'forrest.xmap', search for <span class="codefrag">
+&lt;map:match type="i18n" pattern="{properties:content.xdocs}{1}.*.html"&gt;
+          </span>, copy the three lines for handling *.html files and paste them
+          into your new pipeline.
         </p>
 <pre class="code">
+
 &lt;!--Custom Pipeline for my bad html-pages--&gt;        
 &lt;map:pipeline&gt;
     &lt;map:match pattern="mytest/*.xml"&gt;
@@ -1037,47 +1067,49 @@
       &lt;map:transform src="{lm:transform.html.document}" /&gt;
       &lt;map:serialize type="xml-document"/&gt;
     &lt;/map:match&gt;
-&lt;/map:pipeline&gt;</pre>
+&lt;/map:pipeline&gt;
+        </pre>
 <p>
           Your custom pipeline will now behave exactly like the standard
-          html-handler. All that is left to be done is creating the
-          custom transformation and adding it the pipeline.
+          html-handler. All that is left to be done is creating the custom
+          transformation and adding it the pipeline.
         </p>
 <p class="instruction">
-          Design and test a new XSL-Transformation that removes the
-          unwanted elements and save it in your project's stylesheet
-          directory, usually src/documentation/resources/stylesheets
-          (defined in project.stylesheets-dir of forrest.properties),
-          which is central storage for all stylesheets in a project.
+          Design and test a new XSL-Transformation that removes the unwanted
+          elements and save it in your project's stylesheet directory, usually
+          src/documentation/resources/stylesheets (defined in
+          project.stylesheets-dir of forrest.properties), which is central
+          storage for all stylesheets in a project.
         </p>
 <p class="instruction">
           Add the new transformation as a new line, straight after the
-          generator, and save the changes. 
+          generator, and save the changes.
         </p>
 <pre class="code">
+
 &lt;!--Custom Pipeline for my bad html-pages--&gt;        
 &lt;map:pipeline&gt;
     &lt;map:match pattern="mytest/*.xml"&gt;
-      &lt;map:generate src="mytest/{1}.html" type="html" /&gt;
-      <strong>
-      &lt;map:transform src="{properties:resources.stylesheets}/fixMyBadHTML.xsl"/&gt;
-      </strong>
+      &lt;map:generate src="mytest/{1}.html" type="html" /&gt;<strong>
+
+      &lt;map:transform src="{properties:resources.stylesheets}/fixMyBadHTML.xsl"/&gt;</strong>
+
       &lt;map:transform src="{lm:transform.html.document}" /&gt;
       &lt;map:serialize type="xml-document"/&gt;
     &lt;/map:match&gt;
-&lt;/map:pipeline&gt;</pre>
+&lt;/map:pipeline&gt;
+        </pre>
 <p>
-          Done! You have just added your own custom-processing.
-          Don't forget to view the pages to verify that it is working
-          properly.
+          Done! You have just added your own custom-processing. Don't forget to
+          view the pages to verify that it is working properly.
         </p>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-          Our pipeline does not exactly do what the original pipeline does.
-          To make things easier, we omitted the internationalization part
-          in our pipeline. So if you need to create multi-language sites,
-          make sure that you adjust your pipeline accordingly.
+          Our pipeline does not exactly do what the original pipeline does. To
+          make things easier, we omitted the internationalization part in our
+          pipeline. So if you need to create multi-language sites, make sure
+          that you adjust your pipeline accordingly.
         </div>
 </div>
 </div>

Modified: forrest/site/docs_0_80/howto/howto-custom-html-source.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-custom-html-source.pdf?view=diff&rev=527020&r1=527019&r2=527020
==============================================================================
Binary files - no diff available.

Modified: forrest/site/docs_0_80/howto/howto-editcss.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-editcss.html?view=diff&rev=527020&r1=527019&r2=527020
==============================================================================
--- forrest/site/docs_0_80/howto/howto-editcss.html (original)
+++ forrest/site/docs_0_80/howto/howto-editcss.html Mon Apr  9 21:44:00 2007
@@ -319,10 +319,10 @@
 </div>
 <h1>How to customize Forrest CSS 
       WYSIWYG-style</h1>
-<div class="abstract"> This How-To shows how to use Mozilla 
-      Firefox and the free EditCSS-Plugin to 
-      customize your Forrest design in a 
-      WYSIWYG-way.</div>
+<div class="abstract">
+      This How-To shows how to use Mozilla Firefox and the free EditCSS-Plugin
+      to customize your Forrest design in a WYSIWYG-way.
+    </div>
 <div id="motd-area">
         This is documentation for development version v0.8
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
@@ -362,30 +362,32 @@
 <a name="N10010"></a><a name="Intended Audience"></a>
 <h2 class="underlined_10">Intended Audience</h2>
 <div class="section">
-<p> Users who want to customize the Forrest look 
-      and feel or simply experiment with changing 
-      certain CSS-styles settings to see what 
-      happens.</p>
+<p>
+      Users who want to customize the Forrest look and feel or simply experiment
+      with changing certain CSS-styles settings to see what happens.
+    </p>
 </div>
 <a name="N10018"></a><a name="Purpose"></a>
 <h2 class="underlined_10">Purpose</h2>
 <div class="section">
-<p> A major part of Forrest's look and feel is 
-      controlled by a few CSS style sheets. Since 
-      Forrest allows you to override these settings, 
-      changing the CSS is a quick and easy 
-      alternative to creating (and maintaining) a 
-      whole new skin.</p>
-<p> You'll learn how to use free tools to change 
-      and experiment with styles in a WYSIWYG way, so 
-      that you can immediately see what effect 
-      changing a CSS property will have on the 
-      look and feel of your Forrest.</p>
+<p>
+      A major part of Forrest's look and feel is controlled by a few CSS style
+      sheets. Since Forrest allows you to override these settings, changing the
+      CSS is a quick and easy alternative to creating (and maintaining) a whole
+      new skin.
+    </p>
+<p>
+      You'll learn how to use free tools to change and experiment with styles in
+      a WYSIWYG way, so that you can immediately see what effect changing a CSS
+      property will have on the look and feel of your Forrest.
+    </p>
 </div>
 <a name="N10023"></a><a name="Prerequisites"></a>
 <h2 class="underlined_10">Prerequisites</h2>
 <div class="section">
-<p>To follow these instructions you will need:</p>
+<p>
+      To follow these instructions you will need:
+    </p>
 <ol>
       
 <li>Browser-access to the Forrest-site you want 
@@ -393,37 +395,34 @@
         good for your first attempt.
         <div class="note">
 <div class="label">Note</div>
-<div class="content">You can even 
-        experiment with Forrest's core skins CSS. Please send patches if
-        you enhance something.
+<div class="content">
+          You can even experiment with Forrest's core skins CSS. Please send
+          patches if you enhance something.
         </div>
-</div> 
+</div>
 </li>
       
 <li>The current version of the free Mozilla 
         Firefox-Browser installed on your system. 
         If you don't already use it, you can 
-        download it from <a href="http://www.mozilla.org/products/firefox/">http://www.mozilla.org/products/firefox/</a> 
-        
+        download it from <a href="http://www.mozilla.org/products/firefox/">http://www.mozilla.org/products/firefox/</a>
 </li>
-
       
 <li>The Firefox-PlugIn EditCSS. It downloads 
         and installs in just a few seconds from the 
-        Install-Link at <a href="http://editcss.mozdev.org/">http://editcss.mozdev.org/</a> 
+        Install-Link at <a href="http://editcss.mozdev.org/">http://editcss.mozdev.org/</a>
         
 <div class="note">
 <div class="label">Note</div>
-<div class="content">With standard security settings in 
-        place, Firefox will pop up a line at the top 
-        of the window because this site has by 
-        default no permission to install plugins on 
-        your computer. Click "Edit Options" and 
-        then "Allow" to change that, then click on 
-        the Install-link again. Don't forget to 
-        close and restart Firebird when the
-        installation is finished.</div>
-</div> 
+<div class="content">
+          With standard security settings in place, Firefox will pop up a line
+          at the top of the window because this site has by default no
+          permission to install plugins on your computer. Click "Edit Options"
+          and then "Allow" to change that, then click on the Install-link again.
+          Don't forget to close and restart Firebird when the installation is
+          finished.
+        </div>
+</div>
 </li>
       
 <li>A basic understanding of CSS and access to 
@@ -432,55 +431,61 @@
     
 </ol>
 </div>
-<a name="N1004C"></a><a name="Steps"></a>
+<a name="N10049"></a><a name="Steps"></a>
 <h2 class="underlined_10">Steps</h2>
 <div class="section">
-<a name="N10051"></a><a name="openForrest"></a>
+<a name="N1004E"></a><a name="openForrest"></a>
 <h3 class="underlined_5">Open your Forrest</h3>
-<p class="instruction">Start your Firefox 
-        Browser and open the Forrest you'd like to 
-        work on/play with.</p>
-<p>The page you have pointed to will show up in 
-        Firefox's main window.</p>
-<a name="N1005F"></a><a name="OpenEditCSS"></a>
+<p class="instruction">
+        Start your Firefox Browser and open the Forrest you'd like to work
+        on/play with.
+      </p>
+<p>
+        The page you have pointed to will show up in Firefox's main window.
+      </p>
+<a name="N1005C"></a><a name="OpenEditCSS"></a>
 <h3 class="underlined_5">Open the EditCSS-Sidebar</h3>
-<p class="instruction">Select 
-        View-Sidebar-EditCSS from Firefox's main 
-        menu to open the EditCSS sidebar.</p>
-<p>The EditCSS sidebar will show next to the 
-        main window and load all the styles from 
-        the main page.</p>
-<a name="N1006D"></a><a name="changeCSS"></a>
+<p class="instruction">
+        Select View-Sidebar-EditCSS from Firefox's main menu to open the EditCSS
+        sidebar.
+      </p>
+<p>
+        The EditCSS sidebar will show next to the main window and load all the
+        styles from the main page.
+      </p>
+<a name="N1006A"></a><a name="changeCSS"></a>
 <h3 class="underlined_5">Change any CSS</h3>
-<p class="instruction">Change any style you'd 
-        like to experiment with or add new settings 
-        and styles of your choice by simply 
-        editing the text of the sidebar.</p>
-<p>EditCSS pushes any change you make in the 
-        sidebar right back into the style-settings 
-        of the main window, so that effects will 
-        show right away.</p>
+<p class="instruction">
+        Change any style you'd like to experiment with or add new settings and
+        styles of your choice by simply editing the text of the sidebar.
+      </p>
+<p>
+        EditCSS pushes any change you make in the sidebar right back into the
+        style-settings of the main window, so that effects will show right away.
+      </p>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">On slow systems or when inserting big 
-        changes it might be a good idea to paste 
-        these from the clipboard to avoid a zillion 
-        updates to the main windows for every 
-        character you type.</div>
+<div class="content">
+        On slow systems or when inserting big changes it might be a good idea to
+        paste these from the clipboard to avoid a zillion updates to the main
+        windows for every character you type.
+      </div>
 </div>
-<a name="N1007E"></a><a name="saveChanges"></a>
+<a name="N1007B"></a><a name="saveChanges"></a>
 <h3 class="underlined_5">How to save changes?</h3>
-<p>Since it takes a few explanations to apply 
-        the changes to your Forrest, I've made 
-        this the topic of yet another HowTo called 
-        "Howto change and extend Forrest-CSS"</p>
+<p>
+        Since it takes a few explanations to apply the changes to your Forrest,
+        I've made this the topic of yet another HowTo called "Howto change and
+        extend Forrest-CSS"
+      </p>
 </div>
-<a name="N10088"></a><a name="Feedback and further development of this How-To"></a>
+<a name="N10085"></a><a name="Feedback and further development of this How-To"></a>
 <h2 class="underlined_10">Feedback and further development of this How-To</h2>
 <div class="section">
-<p> Please provide feedback about this document via 
-      the <a href="../../mail-lists.html">mailing 
-      lists</a>. </p>
+<p>
+      Please provide feedback about this document via the
+      <a href="../../mail-lists.html">mailing lists</a>.
+    </p>
 </div>
 </div>
 <!--+

Modified: forrest/site/docs_0_80/howto/howto-editcss.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-editcss.pdf?view=diff&rev=527020&r1=527019&r2=527020
==============================================================================
Binary files - no diff available.

Modified: forrest/site/docs_0_80/howto/howto-forrest-from-maven.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-forrest-from-maven.html?view=diff&rev=527020&r1=527019&r2=527020
==============================================================================
--- forrest/site/docs_0_80/howto/howto-forrest-from-maven.html (original)
+++ forrest/site/docs_0_80/howto/howto-forrest-from-maven.html Mon Apr  9 21:44:00 2007
@@ -317,8 +317,9 @@
 	          &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
 </div>
 <h1>How to run Forrest from within Maven</h1>
-<div class="abstract">This How-To describes how to run Forrest from within
-    Maven.</div>
+<div class="abstract">
+      This How-To describes how to run Forrest from within Maven.
+    </div>
 <div id="motd-area">
         This is documentation for development version v0.8
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
@@ -359,13 +360,17 @@
 <a name="N10010"></a><a name="Intended Audience"></a>
 <h2 class="underlined_10">Intended Audience</h2>
 <div class="section">
-<p>Users who want to run Forrest from within Maven.</p>
+<p>
+      Users who want to run Forrest from within Maven.
+    </p>
 </div>
 <a name="N10018"></a><a name="Purpose"></a>
 <h2 class="underlined_10">Purpose</h2>
 <div class="section">
-<p>One may want to generate their project's documentation and/or website
-    using Forrest in lieu of Maven's site plugin.</p>
+<p>
+      One may want to generate their project's documentation and/or website
+      using Forrest in lieu of Maven's site plugin.
+    </p>
 </div>
 <a name="N10020"></a><a name="Prerequisites"></a>
 <h2 class="underlined_10">Prerequisites</h2>
@@ -379,24 +384,31 @@
 <a name="N1002F"></a><a name="Steps"></a>
 <h2 class="underlined_10">Steps</h2>
 <div class="section">
-<p>The procedure outlined below describes how to add a goal to your
-    project's maven.xml that will invoke Forrest's <span class="codefrag">site</span>
-    target.</p>
+<p>
+      The procedure outlined below describes how to add a goal to your project's
+      maven.xml that will invoke Forrest's <span class="codefrag">site</span> target.
+    </p>
 <a name="N1003A"></a><a name="set-maven-home"></a>
 <h3 class="underlined_5">Set the FORREST_HOME environment variable</h3>
-<p>Make sure the FORREST_HOME environment variable points to your
-      Forrest home directory (i.e. the directory that contains
-      <span class="codefrag">forrest.build.xml</span>) (e.g. C:\opt\apache-forrest-0.7)</p>
+<p>
+        Make sure the FORREST_HOME environment variable points to your Forrest
+        home directory (i.e. the directory that contains
+        <span class="codefrag">forrest.build.xml</span>) (e.g. C:\opt\apache-forrest-0.7)
+      </p>
 <a name="N10047"></a><a name="define-ant-environment-prop"></a>
 <h3 class="underlined_5">Initialize an Ant environment property at the top of
       maven.xml</h3>
-<p>Paste the following line at the top of your maven.xml:</p>
+<p>
+        Paste the following line at the top of your maven.xml:
+      </p>
 <pre class="code">
 &lt;property environment="env" /&gt;
       </pre>
 <a name="N10055"></a><a name="add-forrest-goal-to-maven-xml"></a>
 <h3 class="underlined_5">Add forrest goal to maven.xml</h3>
-<p>Paste the following goal into your project's maven.xml:</p>
+<p>
+        Paste the following goal into your project's maven.xml:
+      </p>
 <pre class="code">
 &lt;goal name="forrest" description="runs Forrest"&gt;
   &lt;property name="forrest.home" location="${env.FORREST_HOME}" /&gt;
@@ -416,19 +428,27 @@
   &lt;/java&gt;
 &lt;/goal&gt;      
       </pre>
-<p>It is necessary to fork a separate java process because Maven 1.0
-      embeds Ant 1.5.2, but Forrest's forrest.build.xml requires Ant 1.6. The
-      goal makes use of the copy of Ant 1.6 that is bundled with Forrest, so
-      it's not even necessary to have Ant 1.6 installed separately.</p>
+<p>
+        It is necessary to fork a separate java process because Maven 1.0 embeds
+        Ant 1.5.2, but Forrest's forrest.build.xml requires Ant 1.6. The goal
+        makes use of the copy of Ant 1.6 that is bundled with Forrest, so it's
+        not even necessary to have Ant 1.6 installed separately.
+      </p>
 <a name="N10066"></a><a name="Alternative+file"></a>
 <h3 class="underlined_5">Alternative file</h3>
-<p>Under <span class="codefrag">$FORREST_HOME/tools/targets/maven.xml</span>
+<p>
+        Under <span class="codefrag">$FORREST_HOME/tools/targets/maven.xml</span>
+      
 </p>
 </div>
-<a name="N10072"></a><a name="Feedback"></a>
+<a name="N10073"></a><a name="Feedback"></a>
 <h2 class="underlined_10">Feedback</h2>
 <div class="section">
-<p>Please provide feedback about this document via the <a href="../../mail-lists.html">mailing lists</a>.<!-- Original author: Ian Springer (ips AT apache DOT org) --></p>
+<p>
+      Please provide feedback about this document via the
+      <a href="../../mail-lists.html">mailing lists</a>.
+<!-- Original author: Ian Springer (ips AT apache DOT org) -->
+    </p>
 </div>
 </div>
 <!--+

Modified: forrest/site/docs_0_80/howto/howto-forrest-from-maven.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-forrest-from-maven.pdf?view=diff&rev=527020&r1=527019&r2=527020
==============================================================================
Binary files - no diff available.

Modified: forrest/site/docs_0_80/howto/howto-pdf-tab.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-pdf-tab.html?view=diff&rev=527020&r1=527019&r2=527020
==============================================================================
--- forrest/site/docs_0_80/howto/howto-pdf-tab.html (original)
+++ forrest/site/docs_0_80/howto/howto-pdf-tab.html Mon Apr  9 21:44:00 2007
@@ -317,9 +317,10 @@
 	          &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
 </div>
 <h1>How to create a PDF document for each tab</h1>
-<div class="abstract">This How-To describes the generation of a PDF document for each
-    group of documents that is defined by a tab. 
-  </div>
+<div class="abstract">
+      This How-To describes the generation of a PDF document for each group of
+      documents that is defined by a tab.
+    </div>
 <div id="motd-area">
         This is documentation for development version v0.8
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
@@ -366,18 +367,17 @@
 <h2 class="underlined_10">Intended Audience</h2>
 <div class="section">
 <p>
-      Users who need to generate one printable document aggregated from a
-      group of documents.
+      Users who need to generate one printable document aggregated from a group
+      of documents.
     </p>
 </div>
 <a name="N10018"></a><a name="Purpose"></a>
 <h2 class="underlined_10">Purpose</h2>
 <div class="section">
 <p>
-      By default Forrest generates a pdf file for each separate document of
-      your project.
-      As well you can create a pdf of the whole site. But sometimes it may
-      be necessary to generate a pdf file out of selected tab, i.e. only for
+      By default Forrest generates a pdf file for each separate document of your
+      project. As well you can create a pdf of the whole site. But sometimes it
+      may be necessary to generate a pdf file out of selected tab, i.e. only for
       certain parts of the site.
     </p>
 </div>
@@ -394,28 +394,29 @@
 <a name="N1002F"></a><a name="Steps"></a>
 <h2 class="underlined_10">Steps</h2>
 <div class="section">
-<p>The procedure outlined below will define a project
-      <span class="codefrag">sitemap.xmap</span> and create a new
-      <span class="codefrag">pdf-tab.xmap</span>.
+<p>
+      The procedure outlined below will define a project
+      <span class="codefrag">sitemap.xmap</span> and create a new <span class="codefrag">pdf-tab.xmap</span>.
     </p>
 <a name="N1003D"></a><a name="sitemap"></a>
 <h3 class="underlined_5">Create your project's main sitemap.xmap</h3>
 <p>
-      If you do not have already a sitemap then create a new empty one in your
-      <span class="codefrag">src/documentation</span> directory (or wherever
-      ${project.sitemap-dir} points to).
-    </p>
+        If you do not have already a sitemap then create a new empty one in your
+        <span class="codefrag">src/documentation</span> directory (or wherever
+        ${project.sitemap-dir} points to).
+      </p>
 <a name="N1004A"></a><a name="aggregator"></a>
 <h3 class="underlined_5">Create another sitemap: pdf-tab.xmap</h3>
 <p>
-    Like before create an empty sitemap and name it pdf-tab.xmap.
-    </p>
+        Like before create an empty sitemap and name it pdf-tab.xmap.
+      </p>
 <a name="N10054"></a><a name="mount"></a>
 <h3 class="underlined_5">Edit project sitemap.xmap to mount pdf-tab.xmap</h3>
 <p>
-      Your sitemap should look something like this.
-    </p>
+        Your sitemap should look something like this.
+      </p>
 <pre class="code">
+
 &lt;map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0"&gt;
   &lt;map:pipelines&gt;
     &lt;map:pipeline internal-only="false"&gt;
@@ -430,14 +431,16 @@
     &lt;/map:pipeline&gt;
   &lt;/map:pipelines&gt;
 &lt;/map:sitemap&gt;
-    </pre>
+      </pre>
 <a name="N10062"></a><a name="edit-aggregator"></a>
 <h3 class="underlined_5">Edit the file pdf-tab.xmap</h3>
 <p>
-      The <span class="codefrag">&lt;map:match pattern="*.xml"&gt;</span> element
-      should look like the following:
-    </p>
+        The <span class="codefrag">
+&lt;map:match pattern="*.xml"&gt;
+        </span> element should look like the following:
+      </p>
 <pre class="code">
+
 &lt;map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0"&gt;
   &lt;map:pipelines&gt;
     &lt;map:pipeline internal-only="false"&gt;
@@ -460,27 +463,30 @@
    &lt;/map:pipeline&gt;
   &lt;/map:pipelines&gt;
 &lt;/map:sitemap&gt;
-    </pre>
+      </pre>
 <a name="N10075"></a><a name="edit-site"></a>
 <h3 class="underlined_5">Edit your site.xml</h3>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-        Do not use directories with "." in it. Replace them by "_"
-        e.g 1.2/ will not work in the aggregation. e.g. 1_2/ just works fine.
-    </div>
+        Do not use directories with "." in it. Replace them by "_" e.g 1.2/ will
+        not work in the aggregation. e.g. 1_2/ just works fine.
+      </div>
 </div>
 <p>
-      Add the following entry to your site.xml in the
-      <span class="codefrag">&lt;about&gt;</span> element
-    </p>
-<pre class="code">... 
+        Add the following entry to your site.xml in the <span class="codefrag">
+&lt;about&gt;
+        </span> element
+      </p>
+<pre class="code">
+... 
 &lt;whole_foosite href="pdf-tab.html" label="sub site" /&gt;
-    </pre>
+      </pre>
 <p>
-      Your site.xml should look like this ...
-    </p>
-<pre class="code">... 
+        Your site.xml should look like this ...
+      </p>
+<pre class="code">
+... 
 &lt;about label="About"&gt;
   &lt;index label="Index" href="index.html" description="Welcome to MyProj"/&gt;
   &lt;changes label="Changes" href="changes.html"
@@ -489,52 +495,61 @@
   &lt;whole_foosite href="pdf-tab.html" label="pdf-tab" /&gt;
 &lt;/about&gt;
 ...
-    </pre>
+      </pre>
 <p>
-      This allows you to link to it via a
-      <span class="codefrag">&lt;link href="site:whole_foosite"&gt;</span>
-      reference. 
-    </p>
-<p>Add to every element that should be included in the pdf-tab.pdf
-      the attribute <span class="codefrag">wholesite="true"</span>
+        This allows you to link to it via a <span class="codefrag">
+&lt;link href="site:whole_foosite"&gt;
+        </span> reference.
+      </p>
+<p>
+        Add to every element that should be included in the pdf-tab.pdf the
+        attribute <span class="codefrag">wholesite="true"</span>
+      
 </p>
 <pre class="code">
+
 &lt;sample-wiki label="Wiki page" href="wiki-sample.html"
   description="wiki-sample" wholesite="true"/&gt;
-	  </pre>
+      </pre>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">This attribute will be inherited by all children of the element. 
-	 Do not use it in the parent element that contains the 
-	 <span class="codefrag">&lt;whole_foosite href="pdf-tab.html" label="pdf-tab" /&gt;</span> 
-	 as the child (will cause a <span class="codefrag">stack overflow</span> if you do)!!!
-	</div>
+<div class="content">
+        This attribute will be inherited by all children of the element. Do not
+        use it in the parent element that contains the <span class="codefrag">
+&lt;whole_foosite href="pdf-tab.html" label="pdf-tab" /&gt;
+        </span> as the child (will cause a <span class="codefrag">stack overflow</span> if you
+        do)!!!
+      </div>
 </div>
-<a name="N100A8"></a><a name="explain"></a>
+<a name="N100A9"></a><a name="explain"></a>
 <h3 class="underlined_5">Explanation of the operation</h3>
 <p>
-      Line 4 of our example
-      <br>
-      
-<span class="codefrag">&lt;map:parameter name="include" value="//*[@wholesite='true']"/&gt;</span>
-      looks at your site.xml and will match every element containing the
-      <span class="codefrag">wholesite="true"</span> attribute. For example, to use the "samples"
-      tab ...
-    </p>
+        Line 4 of our example
+        <br>
+        
+<span class="codefrag">
+&lt;map:parameter name="include" value="//*[@wholesite='true']"/&gt;
+        </span> looks at your site.xml and will match every element containing
+        the <span class="codefrag">wholesite="true"</span> attribute. For example, to use the
+        "samples" tab ...
+      </p>
 <pre class="code">
+
 ...
 &lt;samples label="Samples" href="samples/" tab="samples" wholesite="true"&gt;
 ...
 &lt;/samples&gt;
 ...
-    </pre>
+      </pre>
 <p>
-      It matches <strong>all</strong> of the elements that contain
-      <span class="codefrag">wholesite="true"</span>
-      (in our example <span class="codefrag">&lt;samples&gt;</span>
-      and its "children") for the content of the pdf file to be generated.
-    </p>
-<pre class="code"> 
+        It matches <strong>all</strong> of the elements that contain
+        <span class="codefrag">wholesite="true"</span> (in our example <span class="codefrag">
+&lt;samples&gt;
+        </span> and its "children") for the content of the pdf file to be
+        generated.
+      </p>
+<pre class="code">
+ 
 &lt;samples label="Samples" href="samples/" tab="samples" wholesite="true"&gt;
  &lt;sample2 label="Static content" href="sample2.html"      
    description="More Samples" wholesite='false'/&gt;
@@ -542,24 +557,26 @@
    description="wiki-sample" /&gt;
  &lt;sample-ihtml label="ihtml page" href="ihtml-sample.html"      
    description="Test iHTML page" /&gt;
-&lt;/samples&gt;     	
-    </pre>
+&lt;/samples&gt; 
+      </pre>
 <p>
-      This example shows that you can as well exclude site(s) from the aggregation 
-      by using the <span class="codefrag">wholesite="false"</span> attribute. This attribute will be as well inherited 
-      by all children of the element.
-    </p>
-<p>
-      Line 8 defines the title of the pdf file by taking the content
-      of the project-name variable in
-      <span class="codefrag">skinconf.xml</span> and adding some funny text:
-      <br>
+        This example shows that you can as well exclude site(s) from the
+        aggregation by using the <span class="codefrag">wholesite="false"</span> attribute. This
+        attribute will be as well inherited by all children of the element.
+      </p>
+<p>
+        Line 8 defines the title of the pdf file by taking the content of the
+        project-name variable in <span class="codefrag">skinconf.xml</span> and adding some funny
+        text:
+        <br>
+        
+<span class="codefrag">
+&lt;map:parameter name="title" value="{conf:project-name}: Still My Foo Site"/&gt;
+        </span>
       
-<span class="codefrag">&lt;map:parameter name="title" value="{conf:project-name}: Still My Foo Site"/&gt;</span>
-    
 </p>
 </div>
-<a name="N100DF"></a><a name="Feedback and further development of this How-To"></a>
+<a name="N100E0"></a><a name="Feedback and further development of this How-To"></a>
 <h2 class="underlined_10">Feedback and further development of this How-To</h2>
 <div class="section">
 <p>
@@ -567,8 +584,8 @@
       <a href="../../mail-lists.html">mailing lists</a>.
     </p>
 <p>
-      In the future, this ability will probably be incorporated into the
-      main Forrest process.
+      In the future, this ability will probably be incorporated into the main
+      Forrest process.
     </p>
 </div>
 </div>

Modified: forrest/site/docs_0_80/howto/howto-pdf-tab.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-pdf-tab.pdf?view=diff&rev=527020&r1=527019&r2=527020
==============================================================================
Binary files - no diff available.

Modified: forrest/site/docs_0_80/howto/index.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/index.html?view=diff&rev=527020&r1=527019&r2=527020
==============================================================================
--- forrest/site/docs_0_80/howto/index.html (original)
+++ forrest/site/docs_0_80/howto/index.html Mon Apr  9 21:44:00 2007
@@ -357,13 +357,12 @@
 </ul>
 </div>
     
-    
 <a name="N10023"></a><a name="Using+and+developing+with+Forrest"></a>
 <h2 class="underlined_10">Using and developing with Forrest</h2>
 <div class="section">
 <p>
-        You will soon see that there is not much distinction between
-        users and developers.
+        You will soon see that there is not much distinction between users and
+        developers.
       </p>
 <ul>
         
@@ -400,7 +399,6 @@
       
 </ul>
 </div>
-    
     
 <a name="N1004E"></a><a name="Extending+Forrest"></a>
 <h2 class="underlined_10">Extending Forrest</h2>

Modified: forrest/site/docs_0_80/howto/multi/howto-multi.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/multi/howto-multi.html?view=diff&rev=527020&r1=527019&r2=527020
==============================================================================
--- forrest/site/docs_0_80/howto/multi/howto-multi.html (original)
+++ forrest/site/docs_0_80/howto/multi/howto-multi.html Mon Apr  9 21:44:00 2007
@@ -317,7 +317,8 @@
 	          &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
 </div>
 <h1>Example of a multi-page how-to</h1>
-<div class="abstract">This is the shell of a multi-page how-to. Add your own content.
+<div class="abstract">
+      This is the shell of a multi-page how-to. Add your own content.
     </div>
 <div id="motd-area">
         This is documentation for development version v0.8
@@ -353,26 +354,34 @@
 <a name="N10010"></a><a name="Intended audience"></a>
 <h2 class="underlined_10">Intended audience</h2>
 <div class="section">
-<p>Describe the audience here.</p>
+<p>
+      Describe the audience here.
+    </p>
 </div>
 <a name="N10018"></a><a name="Purpose"></a>
 <h2 class="underlined_10">Purpose</h2>
 <div class="section">
-<p>Explain the purpose of the howto here.</p>
+<p>
+      Explain the purpose of the howto here.
+    </p>
 </div>
 <a name="N10020"></a><a name="Prerequisites"></a>
 <h2 class="underlined_10">Prerequisites</h2>
 <div class="section">
-<p>Configuration requirements:</p>
-<ul> 
+<p>
+      Configuration requirements:
+    </p>
+<ul>
       
 <li>This.</li>
       
 <li>That.</li>
     
 </ul>
-<p>Requisite skills:</p>
-<ul> 
+<p>
+      Requisite skills:
+    </p>
+<ul>
       
 <li>These.</li>
       
@@ -383,8 +392,10 @@
 <a name="N1003D"></a><a name="Various Steps"></a>
 <h2 class="underlined_10">Various Steps</h2>
 <div class="section">
-<p>After this brief introductory paragraph, the steps are described in
-     separate documents:</p>
+<p>
+      After this brief introductory paragraph, the steps are described in
+      separate documents:
+    </p>
 <ul>
       
 <li>
@@ -404,25 +415,31 @@
 <a name="N10057"></a><a name="Real World Extension"></a>
 <h2 class="underlined_10">Real World Extension</h2>
 <div class="section">
-<p>Briefly describe some relevant extensions that go beyond these basics.</p>
+<p>
+      Briefly describe some relevant extensions that go beyond these basics.
+    </p>
 </div>
 <a name="N1005F"></a><a name="Tips"></a>
 <h2 class="underlined_10">Tips</h2>
 <div class="section">
-<p>If you have a problem running the example, then you can try the
-    following tips:</p>
+<p>
+      If you have a problem running the example, then you can try the following
+      tips:
+    </p>
 <ul>
-     
+      
 <li>Tip #1</li>
-     
+      
 <li>Tip #2</li>
-   
+    
 </ul>
 </div>
 <a name="N10070"></a><a name="Related Resources"></a>
 <h2 class="underlined_10">Related Resources</h2>
 <div class="section">
-<p>Cocoon resources:</p>
+<p>
+      Cocoon resources:
+    </p>
 <ul>
       
 <li>For all Cocoon basics see the
@@ -434,9 +451,10 @@
 <a name="N10082"></a><a name="Feedback"></a>
 <h2 class="underlined_10">Feedback</h2>
 <div class="section">
-<p>If you find any faults in this How-to or can see any improvements,
-      please contact the
-      <a href="../../../mail-lists.html">project mail lists</a> with them.
+<p>
+      If you find any faults in this How-to or can see any improvements, please
+      contact the <a href="../../../mail-lists.html">project mail lists</a> with
+      them.
     </p>
 </div>
 </div>

Modified: forrest/site/docs_0_80/howto/multi/step1.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/multi/step1.html?view=diff&rev=527020&r1=527019&r2=527020
==============================================================================
--- forrest/site/docs_0_80/howto/multi/step1.html (original)
+++ forrest/site/docs_0_80/howto/multi/step1.html Mon Apr  9 21:44:00 2007
@@ -340,18 +340,27 @@
 <div class="section">
 <a name="N10012"></a><a name="First+section+of+this+step"></a>
 <h3 class="underlined_5">First section of this step</h3>
-<p>Description here.</p>
+<p>
+        Description here.
+      </p>
 <a name="N1001C"></a><a name="Second+section+of+this+step"></a>
 <h3 class="underlined_5">Second section of this step</h3>
-<p>Description here.</p>
-<p>Source code follows ...</p>
+<p>
+        Description here.
+      </p>
+<p>
+        Source code follows ...
+      </p>
 <pre class="code">
+
 &lt;pointy-brackets&gt;
   &lt;are-allowed-in-source-CDATA-sections/&gt;
 &lt;/pointy-brackets&gt;
 
       </pre>
-<p>Now we move on to <a href="step2.html">Step 2: Do foobar</a>
+<p>
+        Now we move on to <a href="step2.html">Step 2: Do foobar</a>
+      
 </p>
 </div>
 </div>

Modified: forrest/site/docs_0_80/howto/multi/step1.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/multi/step1.pdf?view=diff&rev=527020&r1=527019&r2=527020
==============================================================================
Binary files - no diff available.

Modified: forrest/site/docs_0_80/howto/multi/step2.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/multi/step2.html?view=diff&rev=527020&r1=527019&r2=527020
==============================================================================
--- forrest/site/docs_0_80/howto/multi/step2.html (original)
+++ forrest/site/docs_0_80/howto/multi/step2.html Mon Apr  9 21:44:00 2007
@@ -340,11 +340,17 @@
 <div class="section">
 <a name="N10012"></a><a name="First+section+of+this+step"></a>
 <h3 class="underlined_5">First section of this step</h3>
-<p>Description here.</p>
+<p>
+        Description here.
+      </p>
 <a name="N1001C"></a><a name="Second+section+of+this+step"></a>
 <h3 class="underlined_5">Second section of this step</h3>
-<p>Description here.</p>
-<p>Now we move on to <a href="step3.html">Step 3: Finish up</a>
+<p>
+        Description here.
+      </p>
+<p>
+        Now we move on to <a href="step3.html">Step 3: Finish up</a>
+      
 </p>
 </div>
 </div>

Modified: forrest/site/docs_0_80/howto/multi/step3.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/multi/step3.html?view=diff&rev=527020&r1=527019&r2=527020
==============================================================================
--- forrest/site/docs_0_80/howto/multi/step3.html (original)
+++ forrest/site/docs_0_80/howto/multi/step3.html Mon Apr  9 21:44:00 2007
@@ -340,12 +340,18 @@
 <div class="section">
 <a name="N10012"></a><a name="First+section+of+this+step"></a>
 <h3 class="underlined_5">First section of this step</h3>
-<p>Description here.</p>
+<p>
+        Description here.
+      </p>
 <a name="N1001C"></a><a name="Second+section+of+this+step"></a>
 <h3 class="underlined_5">Second section of this step</h3>
-<p>Description here.</p>
-<p>Congratulations, you have finished. Now return to the
-      <a href="howto-multi.html">start</a>.</p>
+<p>
+        Description here.
+      </p>
+<p>
+        Congratulations, you have finished. Now return to the
+        <a href="howto-multi.html">start</a>.
+      </p>
 </div>
 </div>
 <!--+

Modified: forrest/site/docs_0_80/index.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/index.html?view=diff&rev=527020&r1=527019&r2=527020
==============================================================================
--- forrest/site/docs_0_80/index.html (original)
+++ forrest/site/docs_0_80/index.html Mon Apr  9 21:44:00 2007
@@ -320,30 +320,33 @@
 <div id="motd-area">
         This is documentation for development version v0.8
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
-      
+    
 <p>
-        A good place to get started in our docs is the <a href="your-project.html">Using Forrest</a>
-        guide.
-      </p>
-      
-<p>In the <a href="howto/index.html">How-To</a> section you will find various 
-      practical guides on how to achieve common objectives in Forrest.</p>
-      
-<p>We also have a <a href="faq.html">FAQ</a> list that you should consult before posting questions to
-      our user list.</p>
-      
+      A good place to get started in our docs is the
+      <a href="your-project.html">Using Forrest</a> guide.
+    </p>
+    
 <p>
-        The documentation <a href="../linkmap.html">Table of Contents</a> provides a
-        useful overview of the main documentation. <a href="../docs_0_80/faq.html#docs">This FAQ</a>
-        explains that there is other documentation at the example forrest seed
-        site and that each plugin has its own documentation.
-      </p>
-      
+      In the <a href="howto/index.html">How-To</a> section you will find various
+      practical guides on how to achieve common objectives in Forrest.
+    </p>
+    
 <p>
-        There are docs for 
-        <a href="../versions/index.html">other versions</a>
-        too.
-      </p>
+      We also have a <a href="faq.html">FAQ</a> list that you should consult
+      before posting questions to our user list.
+    </p>
+    
+<p>
+      The documentation <a href="../linkmap.html">Table of Contents</a> provides a
+      useful overview of the main documentation. <a href="../docs_0_80/faq.html#docs">This
+      FAQ</a> explains that there is other documentation at the example forrest
+      seed site and that each plugin has its own documentation.
+    </p>
+    
+<p>
+      There are docs for <a href="../versions/index.html">other versions</a>
+      too.
+    </p>
   
 </div>
 <!--+

Modified: forrest/site/docs_0_80/index.xml
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/index.xml?view=diff&rev=527020&r1=527019&r2=527020
==============================================================================
--- forrest/site/docs_0_80/index.xml (original)
+++ forrest/site/docs_0_80/index.xml Mon Apr  9 21:44:00 2007
@@ -14,29 +14,32 @@
   See the License for the specific language governing permissions and
   limitations under the License.
 --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "document-v13.dtd">
-<document> 
-  <header> 
-    <title>Apache Forrest documentation</title> 
-  </header> 
+<document>
+  <header>
+    <title>Apache Forrest documentation</title>
+  </header>
   <body>
-      <p>
-        A good place to get started in our docs is the <link href="your-project.html">Using Forrest</link>
-        guide.
-      </p>
-      <p>In the <link href="howto/index.html">How-To</link> section you will find various 
-      practical guides on how to achieve common objectives in Forrest.</p>
-      <p>We also have a <link href="faq.html">FAQ</link> list that you should consult before posting questions to
-      our user list.</p>
-      <p>
-        The documentation <link href="site:linkmap">Table of Contents</link> provides a
-        useful overview of the main documentation. <link href="site:faq/docs">This FAQ</link>
-        explains that there is other documentation at the example forrest seed
-        site and that each plugin has its own documentation.
-      </p>
-      <p>
-        There are docs for 
-        <link href="site:versions/overview">other versions</link>
-        too.
-      </p>
+    <p>
+      A good place to get started in our docs is the
+      <link href="your-project.html">Using Forrest</link> guide.
+    </p>
+    <p>
+      In the <link href="howto/index.html">How-To</link> section you will find various
+      practical guides on how to achieve common objectives in Forrest.
+    </p>
+    <p>
+      We also have a <link href="faq.html">FAQ</link> list that you should consult
+      before posting questions to our user list.
+    </p>
+    <p>
+      The documentation <link href="site:linkmap">Table of Contents</link> provides a
+      useful overview of the main documentation. <link href="site:faq/docs">This
+      FAQ</link> explains that there is other documentation at the example forrest
+      seed site and that each plugin has its own documentation.
+    </p>
+    <p>
+      There are docs for <link href="site:versions/overview">other versions</link>
+      too.
+    </p>
   </body>
 </document>



Mime
View raw message