Using sections

Return-Path: Delivered-To: apmail-forrest-svn-archive@www.apache.org Received: (qmail 76327 invoked from network); 6 Dec 2005 04:58:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Dec 2005 04:58:39 -0000 Received: (qmail 37965 invoked by uid 500); 6 Dec 2005 04:58:37 -0000 Delivered-To: apmail-forrest-svn-archive@forrest.apache.org Received: (qmail 37746 invoked by uid 500); 6 Dec 2005 04:58:35 -0000 Mailing-List: contact svn-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Forrest Developers List" List-Id: Delivered-To: mailing list svn@forrest.apache.org Received: (qmail 37659 invoked by uid 99); 6 Dec 2005 04:58:34 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Dec 2005 20:58:34 -0800 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 05 Dec 2005 20:58:17 -0800 Received: (qmail 75121 invoked by uid 65534); 6 Dec 2005 04:57:56 -0000 Message-ID: <20051206045756.75119.qmail@minotaur.apache.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r354312 [17/17] - 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/ plug... Date: Tue, 06 Dec 2005 04:57:22 -0000 To: svn@forrest.apache.org From: crossley@apache.org X-Mailer: svnmailer-1.0.5 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Modified: forrest/site/dtdx/document-v12.html URL: http://svn.apache.org/viewcvs/forrest/site/dtdx/document-v12.html?rev=354312&r1=354311&r2=354312&view=diff ============================================================================== --- forrest/site/dtdx/document-v12.html (original) +++ forrest/site/dtdx/document-v12.html Mon Dec 5 20:55:03 2005 @@ -410,32 +410,32 @@ DTD documentation.
This is a simple paragraph. Most documents contain a fair amount of - paragraphs. Paragraphs are called .
With the attribute, you can declare + paragraphs. Paragraphs are called .
With the attribute, you can declare that whitespace should be preserved, without implying it is in any other way special.
A number of in-line elements are available in the DTD, we will show them - inside an unordered list (<ul>):
+ inside an unordered list (<ul>):
Here is a simple list item (<li>).
Here is a simple list item (<li>).
Have you seen the use of the <code> element in the +
Have you seen the use of the <code> element in the previous item?
Also, we have and +
Also, we have and elements to show content ^above or _below the text baseline.
There is a facility to emphasize certain words using the -  +  elements.
We can use - <icon>s, too.
<icon>
Another possibility is the <img> element: +
Another possibility is the <img> element: , which offers the ability to refer to an image map.
-<link href="../index.html"> +<link href="../index.html">: Use this to @@ -453,7 +453,7 @@
-<link href="#section"> +<link href="#section">: Use this to @@ -463,7 +463,7 @@
-<link href="../index.html#History"> +<link href="../index.html#History">: Use this to @@ -474,7 +474,7 @@
-<jump href="../index.html"> +<jump href="../index.html">: Use this to @@ -486,13 +486,13 @@ The jump behaves differently, in that it will replace any frames in the current window. This is the equivalent of - <a ... target="_top"> + <a ... target="_top">
-<fork href="../index.html"> +<fork href="../index.html">: Use this to @@ -500,7 +500,7 @@ your webbrowser to another document. This will open the document in a new, unnamed browser window. This is the equivalent of - <a ... target="_blank"> + <a ... target="_blank">
Apart from unordered lists, we have ordered lists too, of course.
Using sections

You can use sections to put some structure in your document. For some strange historical reason, the section title is an attribute of the - <section> element.
Sections, the sequel

Just some second section.
Showing preformatted source code

Enough about these sections. Let's have a look at more interesting - elements, <source> for instance:
// This example is from the book _Java in a Nutshell_ by David Flanagan.
           // Written by David Flanagan.  Copyright (c) 1996 O'Reilly & Associates.
           // You may study, use, modify, and distribute this example for any purpose.
@@ -632,12 +632,12 @@
 
         
 
-Not much of attributes with <table>, if you ask me.
+Not much of attributes with <table>, if you ask me.
 
 Using figures
-And a <figure> to end all of this.
+
And a <figure> to end all of this.
           Note that this can also be implemented with an
-          <img> element.
+          <img> element.
         
 
 

Modified: forrest/site/dtdx/document-v13.html
URL: http://svn.apache.org/viewcvs/forrest/site/dtdx/document-v13.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/dtdx/document-v13.html (original)
+++ forrest/site/dtdx/document-v13.html Mon Dec  5 20:55:03 2005
@@ -378,7 +378,7 @@
 Note
 
       This is a demonstration document using all possible elements in the
-      current Apache Forrest xdocs document-v13.dtd
+      current Apache Forrest xdocs document-v13.dtd
       (See the DTD changes section at the bottom.)
     
 
@@ -394,13 +394,13 @@
 
 Block and inline elements
 This is a simple paragraph. Most documents contain a fair amount of
-        paragraphs. Paragraphs are called <p>.
-With the <p xml:space="preserve"> attribute, you can declare
+        paragraphs. Paragraphs are called <p>.
+With the <p xml:space="preserve"> attribute, you can declare
         that whitespace should    be   preserved, without implying it is in any other
         way special.
 
         This next paragraph has a class attribute of 'quote'.  CSS can
-        be used to present this <p class='quote'> in
+        be used to present this <p class='quote'> in
         a different style than the other paragraphs.  The handling of
         this quoted paragraph is defined in the <extra-css>
         element in the skinconf.xml.
@@ -414,27 +414,27 @@
         potatoes, shrimp burger, shrimp sandwich. That- that's about it.
       
 A number of in-line elements are available in the DTD, we will show them
-        inside an unordered list (<ul>):
+        inside an unordered list (<ul>):
  
         
-Here is a simple list item (<li>). 
+Here is a simple list item (<li>). 
         
-Have you seen the use of the <code> element in the
+
Have you seen the use of the <code> element in the
           previous item? 
         
-Also, we have <sub> and <sup>
+
Also, we have <sub> and <sup>
           elements to show content ^above or _below the text
           baseline. 
         
 There is a facility to emphasize certain words using the
-          <em> <strong>
+          <em> <strong>
           elements. 
         
 We can use
           
-          <icon>s too. 
+          <icon>s too. 
         
-Another possibility is the <img> element:
+
Another possibility is the <img> element:
           ,
           which offers the ability to refer to an image map. 
         
@@ -442,7 +442,7 @@
            
             
 
-<link href="../index.html">
+<link href="../index.html">
  
             
 Use this to
@@ -452,7 +452,7 @@
 
             
 

-<link href="#section">
+<link href="#section">
  
             
 Use this to
@@ -462,7 +462,7 @@
 
             
 

-<link href="../index.html#History">
+<link href="../index.html#History">
  
             
 Use this to
@@ -473,7 +473,7 @@
 
             
 

-<jump href="../index.html">
+<jump href="../index.html">
  
             
 Use this to
@@ -485,13 +485,13 @@
               The jump behaves differently, in that it will replace any frames
               in the current window.
               This is the equivalent of
-              <a ... target="_top">
+              <a ... target="_top">
             
 
 
             
 
-<fork href="../index.html">
+<fork href="../index.html">
  
             
 Use this to
@@ -499,7 +499,7 @@
               your webbrowser to another document. This will open the document
               in a new, unnamed browser window.
               This is the equivalent of
-              <a ... target="_blank">
+              <a ... target="_blank">
             
  
         
@@ -507,7 +507,7 @@
  
 
         
-Oh, by the way, a definition list <dl> was used inside
+
Oh, by the way, a definition list <dl> was used inside
           the previous list item. We could put another 
            
             
@@ -547,24 +547,24 @@
         elements.
 
 Fixme (SN)
-The <fixme> element is used for stuff
-        which still needs work. Mind the author attribute!
+The <fixme> element is used for stuff
+        which still needs work. Mind the author attribute!
 
 
 Note
-Use the <note> element to draw attention to something, e.g. ...The <code> element is used when the author can't
+Use the <note> element to draw attention to something, e.g. ...The <code> element is used when the author can't
         express himself clearly using normal sentences ;-)
 
 
 Warning
 Sleep deprivation can be the result of being involved in an open
-        source project. (a.k.a. the <warning> element).
+        source project. (a.k.a. the <warning> element).
       
 
 
 Important
 If you want your own labels for notes and
-        warnings, specify them using the label attribute.
+        warnings, specify them using the label attribute.
       
 
 Apart from unordered lists, we have ordered lists too, of course.
@@ -665,7 +665,7 @@
 Using sections
 You can use sections to put some structure in your document. For some
           strange historical reason, the section title is an attribute of the
-          <section> element.
+          <section> element.
 
 Sections, the sequel
 Just some second section.
@@ -675,7 +675,7 @@
 
 Showing preformatted source code
 Enough about these sections. Let's have a look at more interesting
-          elements, <source> for instance:
+          elements, <source> for instance:
  // This example is from the book _Java in a Nutshell_ by David Flanagan.
 // Written by David Flanagan.  Copyright (c) 1996 O'Reilly & Associates.
@@ -693,9 +693,9 @@
     }
 }
 CDATA sections are used within 
-          <source> elements so that you can write pointy
+          <source> elements so that you can write pointy
            brackets without needing to escape them with messy
-          &lt; entities ...
+          &lt; entities ...
         
  <pointy>
@@ -766,9 +766,9 @@
 
 
 Using figures
-And a <figure> to end all of this.
+
And a <figure> to end all of this.
           Note that this can also be implemented with an
-          <img> element.
+          <img> element.
         
 
 

Modified: forrest/site/dtdx/document-v20.html
URL: http://svn.apache.org/viewcvs/forrest/site/dtdx/document-v20.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/dtdx/document-v20.html (original)
+++ forrest/site/dtdx/document-v20.html Mon Dec  5 20:55:03 2005
@@ -384,7 +384,7 @@
 Note
 
       This is a demonstration document using all possible elements in the
-      current Apache Forrest xdocs document-v20.dtd
+      current Apache Forrest xdocs document-v20.dtd
       (See the DTD changes section at the bottom.)
     
 
@@ -400,13 +400,13 @@
 
 Block and inline elements
 This is a simple paragraph. Most documents contain a fair amount of
-        paragraphs. Paragraphs are called <p>.
-With the <p xml:space="preserve"> attribute, you can declare
+        paragraphs. Paragraphs are called <p>.
+With the <p xml:space="preserve"> attribute, you can declare
         that whitespace should    be   preserved, without implying it is in any other
         way special.
 
         This next paragraph has a class attribute of 'quote'.  CSS can
-        be used to present this <p class='quote'> in
+        be used to present this <p class='quote'> in
         a different style than the other paragraphs.  The handling of
         this quoted paragraph is defined in the <extra-css>
         element in the skinconf.xml.
@@ -420,27 +420,27 @@
         potatoes, shrimp burger, shrimp sandwich. That- that's about it.
       
 A number of in-line elements are available in the DTD, we will show them
-        inside an unordered list (<ul>):
+        inside an unordered list (<ul>):
  
         
-Here is a simple list item (<li>). 
+Here is a simple list item (<li>). 
         
-Have you seen the use of the <code> element in the
+
Have you seen the use of the <code> element in the
           previous item? 
         
-Also, we have <sub> and <sup>
+
Also, we have <sub> and <sup>
           elements to show content ^above or _below the text
           baseline. 
         
 There is a facility to emphasize certain words using the
-          <em> <strong>
+          <em> <strong>
           elements. 
         
 We can use
           
-          <icon>s too. 
+          <icon>s too. 
         
-Another possibility is the <img> element:
+
Another possibility is the <img> element:
           ,
           which offers the ability to refer to an image map. 
         
@@ -448,7 +448,7 @@
            
             
 
-<a href="../index.html">
+<a href="../index.html">
  
             
 Use this to
@@ -458,7 +458,7 @@
 
             
 

-<a href="#section">
+<a href="#section">
  
             
 Use this to
@@ -468,7 +468,7 @@
 
             
 

-<a href="../index.html#History">
+<a href="../index.html#History">
  
             
 Use this to
@@ -487,7 +487,7 @@
  
 
         
-Oh, by the way, a definition list <dl> was used inside
+
Oh, by the way, a definition list <dl> was used inside
           the previous list item. We could put another 
            
             
@@ -527,24 +527,24 @@
         elements.
 
 Fixme (SN)
-The <fixme> element is used for stuff
-        which still needs work. Mind the author attribute!
+The <fixme> element is used for stuff
+        which still needs work. Mind the author attribute!
 
 
 Note
-Use the <note> element to draw attention to something, e.g. ...The <code> element is used when the author can't
+Use the <note> element to draw attention to something, e.g. ...The <code> element is used when the author can't
         express himself clearly using normal sentences ;-)
 
 
 Warning
 Sleep deprivation can be the result of being involved in an open
-        source project. (a.k.a. the <warning> element).
+        source project. (a.k.a. the <warning> element).
       
 
 
 Important
 If you want your own labels for notes and
-        warnings, specify them using the label attribute.
+        warnings, specify them using the label attribute.
       
 
 Apart from unordered lists, we have ordered lists too, of course.
@@ -643,19 +643,18 @@
 
 
 Using sections
-You can use sections to put some structure in your document. For some
-          strange historical reason, the section title is an attribute of the
-          <section> element.
-
+You can use sections to put some structure in your document.
+        
+
 Sections, the sequel
 Just some second section.
-
+
 Section 2.1
 Which contains a subsection (2.1).
-
+
 Showing preformatted source code
 Enough about these sections. Let's have a look at more interesting
-          elements, <source> for instance:
+          elements, <source> for instance:
  // This example is from the book _Java in a Nutshell_ by David Flanagan.
 // Written by David Flanagan.  Copyright (c) 1996 O'Reilly & Associates.
@@ -673,9 +672,9 @@
     }
 }
 CDATA sections are used within 
-          <source> elements so that you can write pointy
+          <source> elements so that you can write pointy
            brackets without needing to escape them with messy
-          &lt; entities ...
+          &lt; entities ...
         
  <pointy>
@@ -684,7 +683,7 @@
 
 Please take care to still use a sensible line-length within your
           source elements.
-
+
 Using tables
 And now for a table:
 
@@ -744,15 +743,15 @@
 
         
 
-
+
 Using figures
-And a <figure> to end all of this.
+
And a <figure> to end all of this.
           Note that this can also be implemented with an
-          <img> element.
+          <img> element.
         
 
 
-
+
 Using class attribute on links
 The document-v13 had elements <fork> and <jump>. In
         document-v20, those elements no longer exist but the functionality can
@@ -805,13 +804,13 @@
 
 
     
-
+
 DTD changes
 
 See the generated
         DTD reference documentation.
       
-
+
 Changes between document-v13 and document-v20
 
           
@@ -827,14 +826,14 @@
           
         
 
-
+
 Changes between document-v12 and document-v13
 
           All v1.2 docs will work fine as v1.3 DTD. The main change is the
           addition of a @class attribute to every element, which enables the
           "extra-css" section in the skinconf to be put to good use.
         
-
+
 Changes between document-v11 and document-v12
 
           doc-v12 enhances doc-v11 by relaxing various restrictions that were

Modified: forrest/site/dtdx/document-v20.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/dtdx/document-v20.pdf?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/dtdx/document-v20.pod
URL: http://svn.apache.org/viewcvs/forrest/site/dtdx/document-v20.pod?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/dtdx/document-v20.pod (original)
+++ forrest/site/dtdx/document-v20.pod Mon Dec  5 20:55:03 2005
@@ -313,7 +313,7 @@
 
 =head3 Using sections
 
-You can use sections to put some structure in your document. For some strange historical reason, the section title is an attribute of the C<
 > element. 
+You can use sections to put some structure in your document. 
 
 
 

Modified: forrest/site/dtdx/document-v20.xml
URL: http://svn.apache.org/viewcvs/forrest/site/dtdx/document-v20.xml?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/dtdx/document-v20.xml (original)
+++ forrest/site/dtdx/document-v20.xml Mon Dec  5 20:55:03 2005
@@ -207,9 +207,8 @@
       
        
         Using sections
-        You can use sections to put some structure in your document. For some
-          strange historical reason, the section title is an attribute of the
-          <section> element. 
+        You can use sections to put some structure in your document.
+        
        
       
         Sections, the sequel

Modified: forrest/site/dtdx/dtd-docs.html
URL: http://svn.apache.org/viewcvs/forrest/site/dtdx/dtd-docs.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/dtdx/dtd-docs.html (original)
+++ forrest/site/dtdx/dtd-docs.html Mon Dec  5 20:55:03 2005
@@ -345,7 +345,7 @@
         do not reflect the modularity of our DTDs, they are primarily
         "user-oriented help" documentation.
 The actual DTDs are located in the Forrest distribution at
-        main/webapp/resources/schema/
+        main/webapp/resources/schema/
 
 
     

Modified: forrest/site/forrest-friday.html
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-friday.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/forrest-friday.html (original)
+++ forrest/site/forrest-friday.html Mon Dec  5 20:55:03 2005
@@ -265,7 +265,7 @@
         
         
 
-          Listen to the dev mailing list. That is where any decisions will be
+          Read the dev mailing list. That is where any decisions will be
           made and the name of the IRC channel will be announced.
         
         
@@ -317,12 +317,12 @@
         
         
 
-          Set the channel mode: /mode +n
+          Set the channel mode: /mode +n
         
 
         
 
-          Declare today's topic: /topic ForrestFriday: XHTML2 core and Jira cleanup
+          Declare today's topic: /topic ForrestFriday: XHTML2 core and Jira cleanup
         
 
         

Modified: forrest/site/forrest-friday.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-friday.pdf?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/forrest-issues.html
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-issues.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Mon Dec  5 20:55:03 2005
@@ -219,15 +219,15 @@
 [FOR-711] Cache results from the Locationmap
 
 
-[FOR-735] PDF cannot be generated when running Forrest as a webapp
-
-
 [FOR-388] Use plugins in-place if src available
 
 
 [FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo
 
 
+[FOR-735] PDF cannot be generated when running Forrest as a webapp
+
+
 [FOR-490] serve multiple sites on a single Forrest instance
 
 
@@ -576,23 +576,7 @@
 <br>
 If we test all locationmaps and find no result we should record that tere is no result in this hashmap. This will also be a good place to throw an exception so that Cocoon can better report such errors (see FOR-701)
 
-
-[FOR-735] PDF cannot be generated when running Forrest as a webapp
-
-
-http://issues.apache.org/jira/browse/FOR-735
-
-(At this point I didn't try this scenario step by step any more; basically it is what we did to setup the site, except that we copied our project data from forrest 0.6 before trying the pdf links)
-<br>
-
-<br>
-- run forrest webapp to create an empty webapp
-<br>
-- configure Tomcat to run the webapp (we did it by creating a context descriptor and put it onder Tomcat's config directory)
-<br>
-- the pdf links give an error &quot;Resource Not Found&quot;
-
-
+
 [FOR-388] Use plugins in-place if src available
 
 
@@ -608,7 +592,7 @@
 <br>
 
 
-
+
 [FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo
 
 
@@ -621,6 +605,22 @@
 The solution is discussed here:
 <br>
 <a href="http://marc.theaimsgroup.com/?t=113176328300002">http://marc.theaimsgroup.com/?t=113176328300002</a>
+
+
+[FOR-735] PDF cannot be generated when running Forrest as a webapp
+
+
+http://issues.apache.org/jira/browse/FOR-735
+
+(At this point I didn't try this scenario step by step any more; basically it is what we did to setup the site, except that we copied our project data from forrest 0.6 before trying the pdf links)
+<br>
+
+<br>
+- run forrest webapp to create an empty webapp
+<br>
+- configure Tomcat to run the webapp (we did it by creating a context descriptor and put it onder Tomcat's config directory)
+<br>
+- the pdf links give an error &quot;Resource Not Found&quot;
 
 
 [FOR-490] serve multiple sites on a single Forrest instance

Modified: forrest/site/forrest-issues.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-issues.pdf?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/index.html
URL: http://svn.apache.org/viewcvs/forrest/site/index.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/index.html (original)
+++ forrest/site/index.html Mon Dec  5 20:55:03 2005
@@ -239,7 +239,7 @@
 
         
 
-Step 1: Do 'forrest seed' to populate
+Step 1: Do 'forrest seed' to populate
           the directory with template site structure and contents.
         
 
@@ -247,9 +247,9 @@
           task-specific, presentation-neutral XML.
         
 
-Step 3: Do 'forrest run' then use
+Step 3: Do 'forrest run' then use
           the web browser to immediately review
-          changes at http://localhost:8888/
+          changes at http://localhost:8888/
           
 
 
@@ -267,7 +267,7 @@
 
         
 
-Step 4: Do 'forrest' to generate the
+Step 4: Do 'forrest' to generate the
           complete website from the XML sources.
           Various styles (known as skins) are available. Custom skins
           can be developed.

Modified: forrest/site/mirrors.html
URL: http://svn.apache.org/viewcvs/forrest/site/mirrors.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/mirrors.html (original)
+++ forrest/site/mirrors.html Mon Dec  5 20:55:03 2005
@@ -199,7 +199,7 @@
 
 Please realise that Forrest is still pre-1.0 release version. It is certainly usable for those who are prepared to move with it. See more notes about status.
 Use the links below to download a distribution of Apache Forrest from one of our mirrors. It is good practice to verify the integrity of the distribution files.
-Apache Forrest is distributed as a zip archive (for Windows) and as a tar.gz archive (for UNIX). The contents are the same, the only difference is the line-endings of all text files.
+Apache Forrest is distributed as a zip archive (for Windows) and as a tar.gz archive (for UNIX). The contents are the same, the only difference is the line-endings of all text files.
 The distribution contains all of the source code, documentation, and resources, together with the pre-built ready-to-run forrest binary.
 
 
@@ -235,7 +235,7 @@
 Verify releases
 
 It is essential that you verify the integrity of the downloaded files using the PGP and MD5 signatures. MD5 verification ensures the file was not corrupted during the download process. PGP verification ensures that the file came from a certain person.
-The PGP signatures can be verified using PGP or GPG. First download the Apache Forrest KEYS as well as the asc signature file for the particular distribution. It is important that you get these files from the ultimate trusted source - the main ASF distribution site, rather than from a mirror. Then verify the signatures using ...
+The PGP signatures can be verified using PGP or GPG. First download the Apache Forrest KEYS as well as the asc signature file for the particular distribution. It is important that you get these files from the ultimate trusted source - the main ASF distribution site, rather than from a mirror. Then verify the signatures using ...
 % pgpk -a KEYS
 % pgpv apache-forrest-X.Y.tar.gz.asc
 
@@ -249,7 +249,7 @@
 % gpg --import KEYS
 % gpg --verify apache-forrest-X.Y.tar.gz.asc
 
-To verify the MD5 signature on the files, you need to use a program called md5 or md5sum, which is included in many unix distributions. It is also available as part of GNU Textutils. Windows users can get binary md5 programs from here, here, or here.
+To verify the MD5 signature on the files, you need to use a program called md5 or md5sum, which is included in many unix distributions. It is also available as part of GNU Textutils. Windows users can get binary md5 programs from here, here, or here.
 We strongly recommend you verify your downloads with both PGP and MD5.
 
 

Modified: forrest/site/pluginDocs/plugins_0_70/index.html
URL: http://svn.apache.org/viewcvs/forrest/site/pluginDocs/plugins_0_70/index.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/pluginDocs/plugins_0_70/index.html (original)
+++ forrest/site/pluginDocs/plugins_0_70/index.html Mon Dec  5 20:55:03 2005
@@ -199,8 +199,8 @@
             Plugins are a way of extending Forrest to
             satisfy site-specific needs. If a site requires one or 
             more plugins then the site designer will 
-            have named them in the project.required.plugins property 
-            in the projects forrest.properties file. When Forrest 
+            have named them in the project.required.plugins property 
+            in the projects forrest.properties file. When Forrest 
             builds the site it will automatically discover the plugin and install 
             it.For more information on how to use plugins see
             

Modified: forrest/site/pluginDocs/plugins_0_70/pluginInfrastructure.html
URL: http://svn.apache.org/viewcvs/forrest/site/pluginDocs/plugins_0_70/pluginInfrastructure.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/pluginDocs/plugins_0_70/pluginInfrastructure.html (original)
+++ forrest/site/pluginDocs/plugins_0_70/pluginInfrastructure.html Mon Dec  5 20:55:03 2005
@@ -225,8 +225,8 @@
       to suit individual projects needs.
 
 Types of Plugin
-There are three types of plugin, input,
-        output and internal. Each plugin has a 
+
There are three types of plugin, input,
+        output and internal. Each plugin has a 
         specific role to play and extends a different part of Forrest:
                              internal plugins
@@ -242,22 +242,22 @@
                      (**.xml)         (**.html, **.pdf etc.) 
 
 The name of the sitemap will reflect the type of plugin in use.
-        That is, an internal plugin will have a sitemap called internal.xmap,
-        an output plugin has output.xmap and an input plugin has
-        input.xmap. In addition, an input plugin can optionally provide a
-        resources.xmap.
+        That is, an internal plugin will have a sitemap called internal.xmap,
+        an output plugin has output.xmap and an input plugin has
+        input.xmap. In addition, an input plugin can optionally provide a
+        resources.xmap.
 
 Input Plugins
 Input plugins provide a new source format. For example, the
           OpenOffice.org plugin extends Forrest to allow the use of
           OpenOffice.org Application file formats.
-An input plugin provides an input.xmap file. 
+
An input plugin provides an input.xmap file. 
           This provides the source matchers (i.e. **.xml), it is 
           mounted in forrest.xmap before the default forrest **.xml behaviour 
           and therefore can override that default behaviour but it will not 
           interfere with any internal Forrest infrastructure matches, or any 
           other plugins infrastructure matches.
-An input plugin may also provide a resources.xmap
+
An input plugin may also provide a resources.xmap
           file. This can be used to match additional resources that are not 
           stored in XML files, for example, javascript files.
 
@@ -265,7 +265,7 @@
 Output plugins provide a new output format. For example, the
           s5 plugin extends Forrest to produce HTML slides from Forrest
           documents.
-An output plugin provides an output.xmap file.
+
An output plugin provides an output.xmap file.
           This provides the relevant output matchers (i.e. 
           **.html, **.pdf, **.slides), it is mounted before any of the default 
           matchers for Forrest and so can override this default behaviour.
@@ -276,7 +276,7 @@
           internal operations. For example, the IMSManifest plugin
           allows Forrest projects to use an IMS Manifest file instead of 
           a site.xml and tabs.xml configuration files.
-Internal plugins provide an internal.xmap file. 
+
Internal plugins provide an internal.xmap file. 
           This provides the infrastructure matchers (i.e. 
           site.xml, faq.xml, issues.xml), and will be mounted before 
           *any* of the Forrest matches. This sitemap can override any behaviour 
@@ -296,8 +296,8 @@
         include a relevant reverse domain name. For example:
 org.apache.forrest.plugin.PLUGIN_TYPE.PLUGIN_NAME
 net.sf.forrestPlugins.PLUGIN_TYPE.PLUGIN_NAME
-Where PLUGIN_TYPE is either "internal", "input" or
-        "output" and PLUGIN_NAME" is a suitable name chosen by
+
Where PLUGIN_TYPE is either "internal", "input" or
+        "output" and PLUGIN_NAME" is a suitable name chosen by
         yourself.
 
 Warning
@@ -403,8 +403,8 @@
 How does Installation work?
 
 When Forrest installs a plugin it downloads a zip of the plugin code and 
-    extracts it into the plugins directory of Forrest and an entry is made 
-    in src/plugins/[input|internal|output].xmap (recall the actual sitemap
+    extracts it into the plugins directory of Forrest and an entry is made 
+    in src/plugins/[input|internal|output].xmap (recall the actual sitemap
     name is dependant on the type of plugin it belongs to. For example, installing the 
     IMSManifest plugin described above will result in the following entry 
     being added to the plugin sitemap:

Modified: forrest/site/pluginDocs/plugins_0_70/usingPlugins.html
URL: http://svn.apache.org/viewcvs/forrest/site/pluginDocs/plugins_0_70/usingPlugins.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/pluginDocs/plugins_0_70/usingPlugins.html (original)
+++ forrest/site/pluginDocs/plugins_0_70/usingPlugins.html Mon Dec  5 20:55:03 2005
@@ -192,7 +192,7 @@
       plugin mechanism.
 
 What plugins are available?
-You can run the command forrest available-plugins to get
+
You can run the command forrest available-plugins to get
         a list of the known plugins for Forrest.
 If you would like to have your own plugin added to this list then
         contact the developer mailing list.
@@ -203,11 +203,11 @@
 How is a Plugin Installed?
 
 If a site requires one or more plugins then the site designer will 
-      have named them in the project.required.plugins property 
-      in the projects forrest.properties file. When Forrest 
+      have named them in the project.required.plugins property 
+      in the projects forrest.properties file. When Forrest 
       builds the site it will automatically discover the plugin and install 
       it. In otherwords, the user need do nothing. For example, 
-      project.required.plugins=org.apache.forrest.plugin.input.OpenOffice.org,org.apache.forrest.plugin.input.simplifiedDocbook
+      project.required.plugins=org.apache.forrest.plugin.input.OpenOffice.org,org.apache.forrest.plugin.input.simplifiedDocbook
       will cause Forrest to load the plugins called "org.apache.forrest.plugin.input.OpenOffice.org" and
       "org.apache.forrest.plugin.input.simplifiedDocbook".
 In the absence of a version number for the plugin (as is the case in the examples above)
@@ -216,7 +216,7 @@
       is incompatible with your current site. To force Forrest into using a specific version of 
       a plugin you shuld add "-VERSION_NUMBER" to the end of the plugin name. For example,
       to force forrest to use the 1.0 version of the OpenOffice.org plugin you would use
-      org.apache.forrest.plugin.input.OpenOffice.org-1.0 If you define a version of the
+      org.apache.forrest.plugin.input.OpenOffice.org-1.0 If you define a version of the
       plugin that does not exist then it will fall back to using the most recent version avialable.
       This feature is useful when 
       developing a new site as you can quickly force a plugin upgrade by deleting all installed 
@@ -231,25 +231,25 @@
         At this time some of the functionality previously in Forrest was
         extracted into a plugin. However, we have not broken backward 
         compatability with earlier versions. In the absence of a
-        project.required.plugins property in the projects 
-        forrest.properties file all plugins that contain 
+        project.required.plugins property in the projects 
+        forrest.properties file all plugins that contain 
         functionality previously part of Forrest itself will be loaded
         automatically. Unless you intend to use new functionality provided
         by a plugin you will not need to make any changes top your project.
 If you do require additional plugin functionality, be sure to
         include all required plugins in the 
-        project.required.plugins property in the project's
-        forrest.properties. You can view
-        main/webapp/default-forrest.properties
+        project.required.plugins property in the project's
+        forrest.properties. You can view
+        main/webapp/default-forrest.properties
         to see the names of plugins that provide previously core 
         functionality.
 It is also worth noting that there is a small performance 
         improvement if you remove plugins that are not in use. Therefore,
         if you do not use one or more of the plugins named in the 
-        project.required.plugins property of 
-        main/webapp/default-forrest.properties
+        project.required.plugins property of 
+        main/webapp/default-forrest.properties
         it is recomended that you override this value in your project's
-        forrest.properties file.
+        forrest.properties file.
 
     
     
@@ -260,7 +260,7 @@
       and full docbook plugins may try and process the same files. In this 
       instance the one that is mounted first will take precedence. Plugins 
       are mounted in the order they appear in the 
-      project.required.plugins property, therefore the mounting 
+      project.required.plugins property, therefore the mounting 
       order and therefore processing precedence is under user control.
 
     

Modified: forrest/site/pluginDocs/plugins_0_80/index.html
URL: http://svn.apache.org/viewcvs/forrest/site/pluginDocs/plugins_0_80/index.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/index.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/index.html Mon Dec  5 20:55:03 2005
@@ -199,8 +199,8 @@
             Plugins are a way of extending Forrest to
             satisfy site-specific needs. If a site requires one or 
             more plugins then the site designer will 
-            have named them in the project.required.plugins property 
-            in the projects forrest.properties file. When Forrest 
+            have named them in the project.required.plugins property 
+            in the projects forrest.properties file. When Forrest 
             builds the site it will automatically discover the plugin and install 
             it.For more information on how to use plugins see
             

Modified: forrest/site/pluginDocs/plugins_0_80/pluginInfrastructure.html
URL: http://svn.apache.org/viewcvs/forrest/site/pluginDocs/plugins_0_80/pluginInfrastructure.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/pluginInfrastructure.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/pluginInfrastructure.html Mon Dec  5 20:55:03 2005
@@ -225,8 +225,8 @@
       to suit individual projects needs.
 
 Types of Plugin
-There are three types of plugin, input,
-        output and internal. Each plugin has a 
+
There are three types of plugin, input,
+        output and internal. Each plugin has a 
         specific role to play and extends a different part of Forrest:
                              internal plugins
@@ -246,13 +246,13 @@
 Input plugins provide a new source format. For example, the
           OpenOffice.org plugin extends Forrest to allow the use of
           OpenOffice.org Application file formats.
-An input plugin provides an input.xmap file. 
+
An input plugin provides an input.xmap file. 
           This provides the source matchers (i.e. **.xml), it is 
           mounted in forrest.xmap before the default forrest **.xml behaviour 
           and therefore can override that default behaviour but it will not 
           interfere with any internal Forrest infrastructure matches, or any 
           other plugins infrastructure matches.
-An input plugin may also provide a resources.xmap
+
An input plugin may also provide a resources.xmap
           file. This can be used to match additional resources that are not 
           stored in XML files, for example, javascript files.
 
@@ -260,7 +260,7 @@
 Output plugins provide a new output format. For example, the
           s5 plugin extends Forrest to produce HTML slides from Forrest
           documents.
-An output plugin provides an output.xmap file.
+
An output plugin provides an output.xmap file.
           This provides the relevant output matchers (i.e. 
           **.html, **.pdf, **.slides), it is mounted before any of the default 
           matchers for Forrest and so can override this default behaviour.
@@ -271,7 +271,7 @@
           internal operations. For example, the IMSManifest plugin
           allows Forrest projects to use an IMS Manifest file instead of 
           a site.xml and tabs.xml configuration files.
-Internal plugins provide an internal.xmap file. 
+
Internal plugins provide an internal.xmap file. 
           This provides the infrastructure matchers (i.e. 
           site.xml, faq.xml, issues.xml), and will be mounted before 
           *any* of the Forrest matches. This sitemap can override any behaviour 
@@ -291,8 +291,8 @@
         include a relevant reverse domain name. For example:
 org.apache.forrest.plugin.PLUGIN_TYPE.PLUGIN_NAME
 net.sf.forrestPlugins.PLUGIN_TYPE.PLUGIN_NAME
-Where PLUGIN_TYPE is either "internal", "input" or
-        "output" and PLUGIN_NAME" is a suitable name chosen by
+
Where PLUGIN_TYPE is either "internal", "input" or
+        "output" and PLUGIN_NAME" is a suitable name chosen by
         yourself.
 
 Warning
@@ -402,8 +402,8 @@
 How does Installation work?
 
 When Forrest installs a plugin it downloads a zip of the plugin code and 
-    extracts it into the plugins directory of Forrest and an entry is made 
-    in src/plugins/sitemap.xmap. For example, installing the 
+    extracts it into the plugins directory of Forrest and an entry is made 
+    in src/plugins/sitemap.xmap. For example, installing the 
     IMSManifest plugin described above will result in the following entry 
     being added to the plugin sitemap:
 
Modified: forrest/site/pluginDocs/plugins_0_80/usingPlugins.html
URL: http://svn.apache.org/viewcvs/forrest/site/pluginDocs/plugins_0_80/usingPlugins.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/usingPlugins.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/usingPlugins.html Mon Dec  5 20:55:03 2005
@@ -192,7 +192,7 @@
       plugin mechanism.
 
 What plugins are available?
-You can run the command forrest available-plugins to get
+
You can run the command forrest available-plugins to get
         a list of the known plugins for Forrest.
 If you would like to have your own plugin added to this list then
         contact the developer mailing list.
@@ -203,11 +203,11 @@
 How is a Plugin Installed?
 
 If a site requires one or more plugins then the site designer will 
-      have named them in the project.required.plugins property 
-      in the projects forrest.properties file. When Forrest 
+      have named them in the project.required.plugins property 
+      in the projects forrest.properties file. When Forrest 
       builds the site it will automatically discover the plugin and install 
       it. In otherwords, the user need do nothing. For example, 
-      project.required.plugins=org.apache.forrest.plugin.input.OpenOffice.org,org.apache.forrest.plugin.input.simplifiedDocbook
+      project.required.plugins=org.apache.forrest.plugin.input.OpenOffice.org,org.apache.forrest.plugin.input.simplifiedDocbook
       will cause Forrest to load the plugins called "org.apache.forrest.plugin.input.OpenOffice.org" and
       "org.apache.forrest.plugin.input.simplifiedDocbook".
 In the absence of a version number for the plugin (as is the case in the examples above)
@@ -216,7 +216,7 @@
       is incompatible with your current site. To force Forrest into using a specific version of 
       a plugin you shuld add "-VERSION_NUMBER" to the end of the plugin name. For example,
       to force forrest to use the 1.0 version of the OpenOffice.org plugin you would use
-      org.apache.forrest.plugin.input.OpenOffice.org-1.0 If you define a version of the
+      org.apache.forrest.plugin.input.OpenOffice.org-1.0 If you define a version of the
       plugin that does not exist then it will fall back to using the most recent version avialable.
       This feature is useful when 
       developing a new site as you can quickly force a plugin upgrade by deleting all installed 
@@ -231,25 +231,25 @@
         At this time some of the functionality previously in Forrest was
         extracted into a plugin. However, we have not broken backward 
         compatability with earlier versions. In the absence of a
-        project.required.plugins property in the projects 
-        forrest.properties file all plugins that contain 
+        project.required.plugins property in the projects 
+        forrest.properties file all plugins that contain 
         functionality previously part of Forrest itself will be loaded
         automatically. Unless you intend to use new functionality provided
         by a plugin you will not need to make any changes top your project.
 If you do require additional plugin functionality, be sure to
         include all required plugins in the 
-        project.required.plugins property in the project's
-        forrest.properties. You can view
-        main/webapp/default-forrest.properties
+        project.required.plugins property in the project's
+        forrest.properties. You can view
+        main/webapp/default-forrest.properties
         to see the names of plugins that provide previously core 
         functionality.
 It is also worth noting that there is a small performance 
         improvement if you remove plugins that are not in use. Therefore,
         if you do not use one or more of the plugins named in the 
-        project.required.plugins property of 
-        main/webapp/default-forrest.properties
+        project.required.plugins property of 
+        main/webapp/default-forrest.properties
         it is recomended that you override this value in your project's
-        forrest.properties file.
+        forrest.properties file.
 
     
     
@@ -260,7 +260,7 @@
       and full docbook plugins may try and process the same files. In this 
       instance the one that is mounted first will take precedence. Plugins 
       are mounted in the order they appear in the 
-      project.required.plugins property, therefore the mounting 
+      project.required.plugins property, therefore the mounting 
       order and therefore processing precedence is under user control.
 
     

Modified: forrest/site/tools/eclipse.html
URL: http://svn.apache.org/viewcvs/forrest/site/tools/eclipse.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/tools/eclipse.html (original)
+++ forrest/site/tools/eclipse.html Mon Dec  5 20:55:03 2005
@@ -332,7 +332,7 @@
           
 
             First, you need to activate the Site.xml view. This can be done by:
-            
+            
               Window -> Show View -> Other... -> Forrest -> SiteXML -> OK
             
             Now you will see the the view open up in Eclipse. To view a tree, click on the project you are working and you should see the structure of the site.xml as a tree in the view.
@@ -374,7 +374,7 @@
         
 

           First, you need to activate the Tab.xml view. This can be done by:
-          
+          
             Window -> Show View -> Other... -> Forrest -> TabXML -> OK
           
           Now you will see the the view open up in Eclipse. To view a tree, click on the project you are working and you should see the structure of the tabs.xml as a tree in the view.

Modified: forrest/site/tools/forrestbar.html
URL: http://svn.apache.org/viewcvs/forrest/site/tools/forrestbar.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/tools/forrestbar.html (original)
+++ forrest/site/tools/forrestbar.html Mon Dec  5 20:55:03 2005
@@ -192,7 +192,7 @@
         downloaded .xpi file into your browser's window and drop it.
 To build ForrestBar locally rather than downloading, go to
         FORREST_HOME/tools/forrestbar and run the following command:
-        forrest -f build.xml and the .xpi file will be built for you
+        forrest -f build.xml and the .xpi file will be built for you
         in FORREST_HOME/tools/forrestbar/build. You can then install it by
         dragging and dropping as indicated above.
 

Modified: forrest/site/tools/forrestbot-web-interface.html
URL: http://svn.apache.org/viewcvs/forrest/site/tools/forrestbot-web-interface.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/tools/forrestbot-web-interface.html (original)
+++ forrest/site/tools/forrestbot-web-interface.html Mon Dec  5 20:55:03 2005
@@ -195,8 +195,8 @@
 Build
 
 To build the webapp from source, you need Apache Maven installed. From a
-      command prompt, go to the forrest/tools/forrestbot/webapp
-      directory and execute "maven war".
+      command prompt, go to the forrest/tools/forrestbot/webapp
+      directory and execute "maven war".
 
 
     

Modified: forrest/site/tools/forrestbot.html
URL: http://svn.apache.org/viewcvs/forrest/site/tools/forrestbot.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/tools/forrestbot.html (original)
+++ forrest/site/tools/forrestbot.html Mon Dec  5 20:55:03 2005
@@ -419,7 +419,7 @@
       
 
 If you want to do more advanced processing for your project, you can
-      override the 'main' target, which by default is <target
+      override the 'main' target, which by default is <target
       name="main" depends="getsrc, build, deploy, notify"/>, create
       your own implementation of a workstage, or use any other ant tasks to do
       additional work.
@@ -440,7 +440,7 @@
       that file in CVS
       or SVN). A nice way to do this is make a simple buildfile (e.g.
       my-settings.xml) that just sets those properties (don't include it in
-      CVS/SVN). Then in your project buildfile, have <import
+      CVS/SVN). Then in your project buildfile, have <import
       file="my-settings.xml"/>.
 
 Misc Properties
@@ -476,7 +476,7 @@
 
 getsrc.clean-workdir
 This should be executed before a getsrc implementation is executed.
-          For example, <target name="getsrc"
+          For example, <target name="getsrc"
           depends="getsrc.clean-workdir, getsrc.svn"/>
 
 
@@ -674,7 +674,7 @@
 
               Directory to temporarily hold working files
 
-              work
+              work/${ant.project.name}
 
               No
             
@@ -717,7 +717,7 @@
 
               Path to deploy site to - the dir that would be the equivalant 
               of build/site dir.  Relative paths will be relative to
-              ${bot.home}
+              project forrestbot descriptor file.
 
               sites/${ant.project.name}
 

Modified: forrest/site/tools/forrestbot.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/tools/forrestbot.pdf?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/tools/xxe.html
URL: http://svn.apache.org/viewcvs/forrest/site/tools/xxe.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/tools/xxe.html (original)
+++ forrest/site/tools/xxe.html Mon Dec  5 20:55:03 2005
@@ -202,8 +202,8 @@
 
 
         
-Delete the forrest directory from the XXE application
-        config directory. (e.g. D:\Program
+
Delete the forrest directory from the XXE application
+        config directory. (e.g. D:\Program
         Files\XMLmind_XML_Editor\config)
         
           
@@ -227,13 +227,13 @@
 
         
 Extract into the XXE application config directory (e.g.
-        D:\Program Files\XMLmind_XML_Editor\config)

+        D:\Program Files\XMLmind_XML_Editor\config)

         
 OR
 
         
 Extract into your XXE user directory (e.g.
-        ~/.xxe/addon/config) (only in version 1.3+ of this config).
+        ~/.xxe/addon/config) (only in version 1.3+ of this config).
         From version 1.3, this is the recommended installation location, as it
         permits upgrading XXE without having to reinstall this config
       
@@ -250,16 +250,16 @@
 Make sure the FORREST_HOME environment variable is set
 
         
-Change directory to forrest/tools/xxe
+
Change directory to forrest/tools/xxe
 
 
         
-Run ant in this directory
+Run ant in this directory
       
 
 To work directly with the SVN version, check out
       http://svn.apache.org/repos/asf/forrest/trunk/tools/xxe/ into the
-      forrest folder in the XXE config folder. Run the
+      forrest folder in the XXE config folder. Run the
       build there to copy the DTDs
 
 XXE

Modified: forrest/site/zone.html
URL: http://svn.apache.org/viewcvs/forrest/site/zone.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/zone.html (original)
+++ forrest/site/zone.html Mon Dec  5 20:55:03 2005
@@ -230,7 +230,7 @@
 

 
         Configuration files and directory structures are stored in SVN at
-        https://svn.apache.org/repos/asf/forrest/zone
+        https://svn.apache.org/repos/asf/forrest/zone
       
 
 
@@ -287,7 +287,7 @@
         
 
           Various local software is installed in
-          /export/opt/ (not managed with SVN) ...
+          /export/opt/ (not managed with SVN) ...
         
 
 Forrest