forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
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 GMT
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 @@
       <a href="../docs_0_70/../dtdx/dtd-docs.html">DTD documentation</a>.
       </p>
 <p>This is a simple paragraph. Most documents contain a fair amount of
-        paragraphs. Paragraphs are called <span class="codefrag">&lt;p&gt;</span>.</p>
-<div class="pre">With the <span class="codefrag">&lt;p xml:space="preserve"&gt;</span> attribute, you can declare
+        paragraphs. Paragraphs are called <span class="codefrag ">&lt;p&gt;</span>.</p>
+<div class="pre">With the <span class="codefrag ">&lt;p xml:space="preserve"&gt;</span> attribute, you can declare
         that whitespace should    be   preserved, without implying it is in any other
         way special.</div>
 <p>A number of in-line elements are available in the DTD, we will show them
-        inside an unordered list (<span class="codefrag">&lt;ul&gt;</span>):</p>
+        inside an unordered list (<span class="codefrag ">&lt;ul&gt;</span>):</p>
 <ul> 
         
-<li>Here is a simple list item (<span class="codefrag">&lt;li&gt;</span>).</li> 
+<li>Here is a simple list item (<span class="codefrag ">&lt;li&gt;</span>).</li> 
         
-<li>Have you seen the use of the <span class="codefrag">&lt;code&gt;</span> element in the
+<li>Have you seen the use of the <span class="codefrag ">&lt;code&gt;</span> element in the
           previous item?</li> 
         
-<li>Also, we have <span class="codefrag">&lt;sub&gt;</span> and <span class="codefrag">&lt;sup&gt;</span>
+<li>Also, we have <span class="codefrag ">&lt;sub&gt;</span> and <span class="codefrag ">&lt;sup&gt;</span>
           elements to show content <sup>above</sup> or <sub>below</sub> the text
           baseline.</li> 
         
 <li>There is a facility to <em>emphasize</em> certain words using the
-          <span class="codefrag">&lt;em&gt;</span> <strong><span class="codefrag">&lt;strong&gt;</span></strong>
+          <span class="codefrag ">&lt;em&gt;</span> <strong><span class="codefrag ">&lt;strong&gt;</span></strong>
           elements.</li> 
         
 <li>We can use
           <img class="icon" alt="feather" height="22" src="images/icon.png" width="26">
-          <span class="codefrag">&lt;icon&gt;</span>s, too.</li> 
+          <span class="codefrag ">&lt;icon&gt;</span>s, too.</li> 
         
-<li>Another possibility is the <span class="codefrag">&lt;img&gt;</span> element:
+<li>Another possibility is the <span class="codefrag ">&lt;img&gt;</span> element:
           <img alt="another feather" height="22" src="images/icon.png" width="26">,
           which offers the ability to refer to an image map.</li> 
         
@@ -443,7 +443,7 @@
           <dl> 
             
 <dt>
-<span class="codefrag">&lt;link href="../index.html"&gt;</span>
+<span class="codefrag ">&lt;link href="../index.html"&gt;</span>
 </dt> 
             
 <dd>Use this to
@@ -453,7 +453,7 @@
 
             
 <dt>
-<span class="codefrag">&lt;link href="#section"&gt;</span>
+<span class="codefrag ">&lt;link href="#section"&gt;</span>
 </dt> 
             
 <dd>Use this to
@@ -463,7 +463,7 @@
 
             
 <dt>
-<span class="codefrag">&lt;link href="../index.html#History"&gt;</span>
+<span class="codefrag ">&lt;link href="../index.html#History"&gt;</span>
 </dt> 
             
 <dd>Use this to
@@ -474,7 +474,7 @@
 
             
 <dt>
-<span class="codefrag">&lt;jump href="../index.html"&gt;</span>
+<span class="codefrag ">&lt;jump href="../index.html"&gt;</span>
 </dt> 
             
 <dd>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
-              <span class="codefrag">&lt;a ... target="_top"&gt;</span>
+              <span class="codefrag ">&lt;a ... target="_top"&gt;</span>
             
 </dd>
 
             
 <dt>
-<span class="codefrag">&lt;fork href="../index.html"&gt;</span>
+<span class="codefrag ">&lt;fork href="../index.html"&gt;</span>
 </dt> 
             
 <dd>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
-              <span class="codefrag">&lt;a ... target="_blank"&gt;</span>
+              <span class="codefrag ">&lt;a ... target="_blank"&gt;</span>
             
 </dd> 
         
@@ -508,7 +508,7 @@
 </li> 
 
         
-<li>Oh, by the way, a definition list <span class="codefrag">&lt;dl&gt;</span> was used inside
+<li>Oh, by the way, a definition list <span class="codefrag ">&lt;dl&gt;</span> was used inside
           the previous list item. We could put another 
           <ul> 
             
@@ -535,23 +535,23 @@
         elements.</p>
 <div class="fixme">
 <div class="label">Fixme (SN)</div>
-<div class="content">The <span class="codefrag">&lt;fixme&gt;</span> element is used for stuff
-        which still needs work. Mind the <span class="codefrag">author</span> attribute!</div>
+<div class="content">The <span class="codefrag ">&lt;fixme&gt;</span> element is used for stuff
+        which still needs work. Mind the <span class="codefrag ">author</span> attribute!</div>
 </div>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">Use the <span class="codefrag">&lt;note&gt;</span> element to draw attention to something, e.g. ...The <span class="codefrag">&lt;code&gt;</span> element is used when the author can't
+<div class="content">Use the <span class="codefrag ">&lt;note&gt;</span> element to draw attention to something, e.g. ...The <span class="codefrag ">&lt;code&gt;</span> element is used when the author can't
         express himself clearly using normal sentences ;-)</div>
 </div>
 <div class="warning">
 <div class="label">Warning</div>
 <div class="content">Sleep deprivation can be the result of being involved in an open
-        source project. (a.k.a. the <span class="codefrag">&lt;warning&gt;</span> element).</div>
+        source project. (a.k.a. the <span class="codefrag ">&lt;warning&gt;</span> element).</div>
 </div>
 <div class="note">
 <div class="label">Important</div>
 <div class="content">If you want your own labels for notes and warnings, specify them
-        using the <span class="codefrag">label</span> attribute.</div>
+        using the <span class="codefrag ">label</span> attribute.</div>
 </div>
 <p>Apart from unordered lists, we have ordered lists too, of course.</p>
 <ol> 
@@ -567,7 +567,7 @@
 <h3 class="underlined_5">Using sections</h3>
 <p>You can use sections to put some structure in your document. For some
           strange historical reason, the section title is an attribute of the
-          <span class="codefrag">&lt;section&gt;</span> element.</p>
+          <span class="codefrag ">&lt;section&gt;</span> element.</p>
 <a name="N10148"></a><a name="Sections%2C+the+sequel"></a>
 <h3 class="underlined_5">Sections, the sequel</h3>
 <p>Just some second section.</p>
@@ -577,7 +577,7 @@
 <a name="source" id="source"></a><a name="N1015F"></a><a name="Showing+preformatted+source+code"></a>
 <h3 class="underlined_5">Showing preformatted source code</h3>
 <p>Enough about these sections. Let's have a look at more interesting
-          elements, <span class="codefrag">&lt;source&gt;</span> for instance:</p>
+          elements, <span class="codefrag ">&lt;source&gt;</span> for instance:</p>
 <pre class="code">// This example is from the book _Java in a Nutshell_ by David Flanagan.
           // Written by David Flanagan.  Copyright (c) 1996 O'Reilly &amp; Associates.
           // You may study, use, modify, and distribute this example for any purpose.
@@ -632,12 +632,12 @@
 </tr>
         
 </table>
-<p>Not much of attributes with <span class="codefrag">&lt;table&gt;</span>, if you ask me.</p>
+<p>Not much of attributes with <span class="codefrag ">&lt;table&gt;</span>, if you ask me.</p>
 <a name="second-figure-anchor" id="second-figure-anchor"></a><a name="N101B7"></a><a name="figure"></a>
 <h3 class="underlined_5">Using figures</h3>
-<p>And a <span class="codefrag">&lt;figure&gt;</span> to end all of this.
+<p>And a <span class="codefrag ">&lt;figure&gt;</span> to end all of this.
           Note that this can also be implemented with an
-          <span class="codefrag">&lt;img&gt;</span> element.
+          <span class="codefrag ">&lt;img&gt;</span> element.
         </p>
 <div id="" style="text-align: center;">
 <img id="" class="figure" alt="The fine Forrest logo" src="images/project-logo.png" height="65" width="220"></div>

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 @@
 <div class="label">Note</div>
 <div class="content">
       This is a demonstration document using all possible elements in the
-      current Apache Forrest xdocs <span class="codefrag">document-v13.dtd</span>
+      current Apache Forrest xdocs <span class="codefrag ">document-v13.dtd</span>
       (See the <a href="#changes">DTD changes</a> section at the bottom.)
     </div>
 </div>
@@ -394,13 +394,13 @@
 <a name="N1002F"></a><a name="block-inline"></a>
 <h3 class="underlined_5">Block and inline elements</h3>
 <p>This is a simple paragraph. Most documents contain a fair amount of
-        paragraphs. Paragraphs are called <span class="codefrag">&lt;p&gt;</span>.</p>
-<div class="pre">With the <span class="codefrag">&lt;p xml:space="preserve"&gt;</span> attribute, you can declare
+        paragraphs. Paragraphs are called <span class="codefrag ">&lt;p&gt;</span>.</p>
+<div class="pre">With the <span class="codefrag ">&lt;p xml:space="preserve"&gt;</span> attribute, you can declare
         that whitespace should    be   preserved, without implying it is in any other
         way special.</div>
 <p>
         This next paragraph has a class attribute of 'quote'.  CSS can
-        be used to present this <span class="codefrag">&lt;p class='quote'&gt;</span> in
+        be used to present this <span class="codefrag ">&lt;p class='quote'&gt;</span> in
         a different style than the other paragraphs.  The handling of
         this quoted paragraph is defined in the &lt;extra-css&gt;
         element in the skinconf.xml.
@@ -414,27 +414,27 @@
         potatoes, shrimp burger, shrimp sandwich. That- that's about it.
       </p>
 <p>A number of in-line elements are available in the DTD, we will show them
-        inside an unordered list (<span class="codefrag">&lt;ul&gt;</span>):</p>
+        inside an unordered list (<span class="codefrag ">&lt;ul&gt;</span>):</p>
 <ul> 
         
-<li>Here is a simple list item (<span class="codefrag">&lt;li&gt;</span>).</li> 
+<li>Here is a simple list item (<span class="codefrag ">&lt;li&gt;</span>).</li> 
         
-<li>Have you seen the use of the <span class="codefrag">&lt;code&gt;</span> element in the
+<li>Have you seen the use of the <span class="codefrag ">&lt;code&gt;</span> element in the
           previous item?</li> 
         
-<li>Also, we have <span class="codefrag">&lt;sub&gt;</span> and <span class="codefrag">&lt;sup&gt;</span>
+<li>Also, we have <span class="codefrag ">&lt;sub&gt;</span> and <span class="codefrag ">&lt;sup&gt;</span>
           elements to show content <sup>above</sup> or <sub>below</sub> the text
           baseline.</li> 
         
 <li>There is a facility to <em>emphasize</em> certain words using the
-          <span class="codefrag">&lt;em&gt;</span> <strong><span class="codefrag">&lt;strong&gt;</span></strong>
+          <span class="codefrag ">&lt;em&gt;</span> <strong><span class="codefrag ">&lt;strong&gt;</span></strong>
           elements.</li> 
         
 <li>We can use
           <img class="icon" alt="feather" height="22" src="images/icon.png" width="26">
-          <span class="codefrag">&lt;icon&gt;</span>s too.</li> 
+          <span class="codefrag ">&lt;icon&gt;</span>s too.</li> 
         
-<li>Another possibility is the <span class="codefrag">&lt;img&gt;</span> element:
+<li>Another possibility is the <span class="codefrag ">&lt;img&gt;</span> element:
           <img alt="another feather" height="22" src="images/icon.png" width="26">,
           which offers the ability to refer to an image map.</li> 
         
@@ -442,7 +442,7 @@
           <dl> 
             
 <dt>
-<span class="codefrag">&lt;link href="../index.html"&gt;</span>
+<span class="codefrag ">&lt;link href="../index.html"&gt;</span>
 </dt> 
             
 <dd>Use this to
@@ -452,7 +452,7 @@
 
             
 <dt>
-<span class="codefrag">&lt;link href="#section"&gt;</span>
+<span class="codefrag ">&lt;link href="#section"&gt;</span>
 </dt> 
             
 <dd>Use this to
@@ -462,7 +462,7 @@
 
             
 <dt>
-<span class="codefrag">&lt;link href="../index.html#History"&gt;</span>
+<span class="codefrag ">&lt;link href="../index.html#History"&gt;</span>
 </dt> 
             
 <dd>Use this to
@@ -473,7 +473,7 @@
 
             
 <dt>
-<span class="codefrag">&lt;jump href="../index.html"&gt;</span>
+<span class="codefrag ">&lt;jump href="../index.html"&gt;</span>
 </dt> 
             
 <dd>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
-              <span class="codefrag">&lt;a ... target="_top"&gt;</span>
+              <span class="codefrag ">&lt;a ... target="_top"&gt;</span>
             
 </dd>
 
             
 <dt>
-<span class="codefrag">&lt;fork href="../index.html"&gt;</span>
+<span class="codefrag ">&lt;fork href="../index.html"&gt;</span>
 </dt> 
             
 <dd>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
-              <span class="codefrag">&lt;a ... target="_blank"&gt;</span>
+              <span class="codefrag ">&lt;a ... target="_blank"&gt;</span>
             
 </dd> 
         
@@ -507,7 +507,7 @@
 </li> 
 
         
-<li>Oh, by the way, a definition list <span class="codefrag">&lt;dl&gt;</span> was used inside
+<li>Oh, by the way, a definition list <span class="codefrag ">&lt;dl&gt;</span> was used inside
           the previous list item. We could put another 
           <ul> 
             
@@ -547,24 +547,24 @@
         elements.</p>
 <div class="fixme">
 <div class="label">Fixme (SN)</div>
-<div class="content">The <span class="codefrag">&lt;fixme&gt;</span> element is used for stuff
-        which still needs work. Mind the <span class="codefrag">author</span> attribute!</div>
+<div class="content">The <span class="codefrag ">&lt;fixme&gt;</span> element is used for stuff
+        which still needs work. Mind the <span class="codefrag ">author</span> attribute!</div>
 </div>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">Use the <span class="codefrag">&lt;note&gt;</span> element to draw attention to something, e.g. ...The <span class="codefrag">&lt;code&gt;</span> element is used when the author can't
+<div class="content">Use the <span class="codefrag ">&lt;note&gt;</span> element to draw attention to something, e.g. ...The <span class="codefrag ">&lt;code&gt;</span> element is used when the author can't
         express himself clearly using normal sentences ;-)</div>
 </div>
 <div class="warning">
 <div class="label">Warning</div>
 <div class="content">Sleep deprivation can be the result of being involved in an open
-        source project. (a.k.a. the <span class="codefrag">&lt;warning&gt;</span> element).
+        source project. (a.k.a. the <span class="codefrag ">&lt;warning&gt;</span> element).
       </div>
 </div>
 <div class="note">
 <div class="label">Important</div>
 <div class="content">If you want your own labels for notes and
-        warnings, specify them using the <span class="codefrag">label</span> attribute.
+        warnings, specify them using the <span class="codefrag ">label</span> attribute.
       </div>
 </div>
 <p>Apart from unordered lists, we have ordered lists too, of course.</p>
@@ -665,7 +665,7 @@
 <h3 class="underlined_5">Using sections</h3>
 <p>You can use sections to put some structure in your document. For some
           strange historical reason, the section title is an attribute of the
-          <span class="codefrag">&lt;section&gt;</span> element.</p>
+          <span class="codefrag ">&lt;section&gt;</span> element.</p>
 <a name="N101D1"></a><a name="sub-section"></a>
 <h3 class="underlined_5">Sections, the sequel</h3>
 <p>Just some second section.</p>
@@ -675,7 +675,7 @@
 <a name="N101E5"></a><a name="source"></a>
 <h3 class="underlined_5">Showing preformatted source code</h3>
 <p>Enough about these sections. Let's have a look at more interesting
-          elements, <span class="codefrag">&lt;source&gt;</span> for instance:</p>
+          elements, <span class="codefrag ">&lt;source&gt;</span> for instance:</p>
 <pre class="code">
 // This example is from the book _Java in a Nutshell_ by David Flanagan.
 // Written by David Flanagan.  Copyright (c) 1996 O'Reilly &amp; Associates.
@@ -693,9 +693,9 @@
     }
 }</pre>
 <p>CDATA sections are used within 
-          <span class="codefrag">&lt;source&gt;</span> elements so that you can write pointy
+          <span class="codefrag ">&lt;source&gt;</span> elements so that you can write pointy
            brackets without needing to escape them with messy
-          <span class="codefrag">&amp;lt;</span> entities ...
+          <span class="codefrag ">&amp;lt;</span> entities ...
         </p>
 <pre class="code">
 &lt;pointy&gt;
@@ -766,9 +766,9 @@
 </table>
 <a name="second-figure-anchor" id="second-figure-anchor"></a><a name="N1026D"></a><a name="figure"></a>
 <h3 class="underlined_5">Using figures</h3>
-<p>And a <span class="codefrag">&lt;figure&gt;</span> to end all of this.
+<p>And a <span class="codefrag ">&lt;figure&gt;</span> to end all of this.
           Note that this can also be implemented with an
-          <span class="codefrag">&lt;img&gt;</span> element.
+          <span class="codefrag ">&lt;img&gt;</span> element.
         </p>
 <div id="" style="text-align: center;">
 <img id="" class="figure" alt="The fine Forrest logo" src="images/project-logo.png" height="65" width="220"></div>

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 @@
 <div class="label">Note</div>
 <div class="content">
       This is a demonstration document using all possible elements in the
-      current Apache Forrest xdocs <span class="codefrag">document-v20.dtd</span>
+      current Apache Forrest xdocs <span class="codefrag ">document-v20.dtd</span>
       (See the <a href="#changes">DTD changes</a> section at the bottom.)
     </div>
 </div>
@@ -400,13 +400,13 @@
 <a name="N1002F"></a><a name="block-inline"></a>
 <h3 class="underlined_5">Block and inline elements</h3>
 <p>This is a simple paragraph. Most documents contain a fair amount of
-        paragraphs. Paragraphs are called <span class="codefrag">&lt;p&gt;</span>.</p>
-<div class="pre">With the <span class="codefrag">&lt;p xml:space="preserve"&gt;</span> attribute, you can declare
+        paragraphs. Paragraphs are called <span class="codefrag ">&lt;p&gt;</span>.</p>
+<div class="pre">With the <span class="codefrag ">&lt;p xml:space="preserve"&gt;</span> attribute, you can declare
         that whitespace should    be   preserved, without implying it is in any other
         way special.</div>
 <p>
         This next paragraph has a class attribute of 'quote'.  CSS can
-        be used to present this <span class="codefrag">&lt;p class='quote'&gt;</span> in
+        be used to present this <span class="codefrag ">&lt;p class='quote'&gt;</span> in
         a different style than the other paragraphs.  The handling of
         this quoted paragraph is defined in the &lt;extra-css&gt;
         element in the skinconf.xml.
@@ -420,27 +420,27 @@
         potatoes, shrimp burger, shrimp sandwich. That- that's about it.
       </p>
 <p>A number of in-line elements are available in the DTD, we will show them
-        inside an unordered list (<span class="codefrag">&lt;ul&gt;</span>):</p>
+        inside an unordered list (<span class="codefrag ">&lt;ul&gt;</span>):</p>
 <ul> 
         
-<li>Here is a simple list item (<span class="codefrag">&lt;li&gt;</span>).</li> 
+<li>Here is a simple list item (<span class="codefrag ">&lt;li&gt;</span>).</li> 
         
-<li>Have you seen the use of the <span class="codefrag">&lt;code&gt;</span> element in the
+<li>Have you seen the use of the <span class="codefrag ">&lt;code&gt;</span> element in the
           previous item?</li> 
         
-<li>Also, we have <span class="codefrag">&lt;sub&gt;</span> and <span class="codefrag">&lt;sup&gt;</span>
+<li>Also, we have <span class="codefrag ">&lt;sub&gt;</span> and <span class="codefrag ">&lt;sup&gt;</span>
           elements to show content <sup>above</sup> or <sub>below</sub> the text
           baseline.</li> 
         
 <li>There is a facility to <em>emphasize</em> certain words using the
-          <span class="codefrag">&lt;em&gt;</span> <strong><span class="codefrag">&lt;strong&gt;</span></strong>
+          <span class="codefrag ">&lt;em&gt;</span> <strong><span class="codefrag ">&lt;strong&gt;</span></strong>
           elements.</li> 
         
 <li>We can use
           <img class="icon" alt="feather" height="22" src="images/icon.png" width="26">
-          <span class="codefrag">&lt;icon&gt;</span>s too.</li> 
+          <span class="codefrag ">&lt;icon&gt;</span>s too.</li> 
         
-<li>Another possibility is the <span class="codefrag">&lt;img&gt;</span> element:
+<li>Another possibility is the <span class="codefrag ">&lt;img&gt;</span> element:
           <img alt="another feather" height="22" src="images/icon.png" width="26">,
           which offers the ability to refer to an image map.</li> 
         
@@ -448,7 +448,7 @@
           <dl> 
             
 <dt>
-<span class="codefrag">&lt;a href="../index.html"&gt;</span>
+<span class="codefrag ">&lt;a href="../index.html"&gt;</span>
 </dt> 
             
 <dd>Use this to
@@ -458,7 +458,7 @@
 
             
 <dt>
-<span class="codefrag">&lt;a href="#section"&gt;</span>
+<span class="codefrag ">&lt;a href="#section"&gt;</span>
 </dt> 
             
 <dd>Use this to
@@ -468,7 +468,7 @@
 
             
 <dt>
-<span class="codefrag">&lt;a href="../index.html#History"&gt;</span>
+<span class="codefrag ">&lt;a href="../index.html#History"&gt;</span>
 </dt> 
             
 <dd>Use this to
@@ -487,7 +487,7 @@
 </li> 
 
         
-<li>Oh, by the way, a definition list <span class="codefrag">&lt;dl&gt;</span> was used inside
+<li>Oh, by the way, a definition list <span class="codefrag ">&lt;dl&gt;</span> was used inside
           the previous list item. We could put another 
           <ul> 
             
@@ -527,24 +527,24 @@
         elements.</p>
 <div class="fixme">
 <div class="label">Fixme (SN)</div>
-<div class="content">The <span class="codefrag">&lt;fixme&gt;</span> element is used for stuff
-        which still needs work. Mind the <span class="codefrag">author</span> attribute!</div>
+<div class="content">The <span class="codefrag ">&lt;fixme&gt;</span> element is used for stuff
+        which still needs work. Mind the <span class="codefrag ">author</span> attribute!</div>
 </div>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">Use the <span class="codefrag">&lt;note&gt;</span> element to draw attention to something, e.g. ...The <span class="codefrag">&lt;code&gt;</span> element is used when the author can't
+<div class="content">Use the <span class="codefrag ">&lt;note&gt;</span> element to draw attention to something, e.g. ...The <span class="codefrag ">&lt;code&gt;</span> element is used when the author can't
         express himself clearly using normal sentences ;-)</div>
 </div>
 <div class="warning">
 <div class="label">Warning</div>
 <div class="content">Sleep deprivation can be the result of being involved in an open
-        source project. (a.k.a. the <span class="codefrag">&lt;warning&gt;</span> element).
+        source project. (a.k.a. the <span class="codefrag ">&lt;warning&gt;</span> element).
       </div>
 </div>
 <div class="note">
 <div class="label">Important</div>
 <div class="content">If you want your own labels for notes and
-        warnings, specify them using the <span class="codefrag">label</span> attribute.
+        warnings, specify them using the <span class="codefrag ">label</span> attribute.
       </div>
 </div>
 <p>Apart from unordered lists, we have ordered lists too, of course.</p>
@@ -643,19 +643,18 @@
 </table>
 <a name="N101AB"></a><a name="section"></a>
 <h3 class="underlined_5">Using sections</h3>
-<p>You can use sections to put some structure in your document. For some
-          strange historical reason, the section title is an attribute of the
-          <span class="codefrag">&lt;section&gt;</span> element.</p>
-<a name="N101B8"></a><a name="sub-section"></a>
+<p>You can use sections to put some structure in your document.
+        </p>
+<a name="N101B5"></a><a name="sub-section"></a>
 <h3 class="underlined_5">Sections, the sequel</h3>
 <p>Just some second section.</p>
-<a name="N101C1"></a><a name="sub-sub-section"></a>
+<a name="N101BE"></a><a name="sub-sub-section"></a>
 <h4>Section 2.1</h4>
 <p>Which contains a subsection (2.1).</p>
-<a name="N101CC"></a><a name="source"></a>
+<a name="N101C9"></a><a name="source"></a>
 <h3 class="underlined_5">Showing preformatted source code</h3>
 <p>Enough about these sections. Let's have a look at more interesting
-          elements, <span class="codefrag">&lt;source&gt;</span> for instance:</p>
+          elements, <span class="codefrag ">&lt;source&gt;</span> for instance:</p>
 <pre class="code">
 // This example is from the book _Java in a Nutshell_ by David Flanagan.
 // Written by David Flanagan.  Copyright (c) 1996 O'Reilly &amp; Associates.
@@ -673,9 +672,9 @@
     }
 }</pre>
 <p>CDATA sections are used within 
-          <span class="codefrag">&lt;source&gt;</span> elements so that you can write pointy
+          <span class="codefrag ">&lt;source&gt;</span> elements so that you can write pointy
            brackets without needing to escape them with messy
-          <span class="codefrag">&amp;lt;</span> entities ...
+          <span class="codefrag ">&amp;lt;</span> entities ...
         </p>
 <pre class="code">
 &lt;pointy&gt;
@@ -684,7 +683,7 @@
 </pre>
 <p>Please take care to still use a sensible line-length within your
           source elements.</p>
-<a name="N101ED"></a><a name="table"></a>
+<a name="N101EA"></a><a name="table"></a>
 <h3 class="underlined_5">Using tables</h3>
 <p>And now for a table:</p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -744,15 +743,15 @@
 </tr>
         
 </table>
-<a name="second-figure-anchor" id="second-figure-anchor"></a><a name="N10254"></a><a name="figure"></a>
+<a name="second-figure-anchor" id="second-figure-anchor"></a><a name="N10251"></a><a name="figure"></a>
 <h3 class="underlined_5">Using figures</h3>
-<p>And a <span class="codefrag">&lt;figure&gt;</span> to end all of this.
+<p>And a <span class="codefrag ">&lt;figure&gt;</span> to end all of this.
           Note that this can also be implemented with an
-          <span class="codefrag">&lt;img&gt;</span> element.
+          <span class="codefrag ">&lt;img&gt;</span> element.
         </p>
 <div id="" style="text-align: center;">
 <img id="" class="figure" alt="The fine Forrest logo" src="images/project-logo.png" height="65" width="220"></div>
-<a name="N1026A"></a><a name="link-class"></a>
+<a name="N10267"></a><a name="link-class"></a>
 <h3 class="underlined_5">Using class attribute on links</h3>
 <p>The document-v13 had elements &lt;fork&gt; and &lt;jump&gt;. In
         document-v20, those elements no longer exist but the functionality can
@@ -805,13 +804,13 @@
 </div>
 
     
-<a name="N102AA"></a><a name="changes"></a>
+<a name="N102A7"></a><a name="changes"></a>
 <h2 class="underlined_10">DTD changes</h2>
 <div class="section">
 <p>See the generated
         <a href="../docs_0_80/../dtdx/dtd-docs.html">DTD reference documentation</a>.
       </p>
-<a name="N102B7"></a><a name="changes-20"></a>
+<a name="N102B4"></a><a name="changes-20"></a>
 <h3 class="underlined_5">Changes between document-v13 and document-v20</h3>
 <ul>
           
@@ -827,14 +826,14 @@
           </li>
         
 </ul>
-<a name="N102DA"></a><a name="changes-13"></a>
+<a name="N102D7"></a><a name="changes-13"></a>
 <h3 class="underlined_5">Changes between document-v12 and document-v13</h3>
 <p>
           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.
         </p>
-<a name="N102E4"></a><a name="changes-12"></a>
+<a name="N102E1"></a><a name="changes-12"></a>
 <h3 class="underlined_5">Changes between document-v11 and document-v12</h3>
 <p>
           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<<section> > 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 @@
       </section>
       <section id="section"> 
         <title>Using sections</title>
-        <p>You can use sections to put some structure in your document. For some
-          strange historical reason, the section title is an attribute of the
-          <code>&lt;section&gt;</code> element.</p> 
+        <p>You can use sections to put some structure in your document.
+        </p>
       </section> 
       <section id="sub-section">
         <title>Sections, the sequel</title>

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.</p>
 <p>The actual DTDs are located in the Forrest distribution at
-        <span class="codefrag">main/webapp/resources/schema/</span>
+        <span class="codefrag ">main/webapp/resources/schema/</span>
 </p>
 </div>
     

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 @@
         </li>
         
 <li>
-          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.
         </li>
         
@@ -317,12 +317,12 @@
         </li>
         
 <li>
-          Set the channel mode: <span class="codefrag">/mode +n</span>
+          Set the channel mode: <span class="codefrag ">/mode +n</span>
         
 </li>
         
 <li>
-          Declare today's topic: <span class="codefrag">/topic ForrestFriday: XHTML2 core and Jira cleanup</span>
+          Declare today's topic: <span class="codefrag ">/topic ForrestFriday: XHTML2 core and Jira cleanup</span>
         
 </li>
         

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 @@
 <a href="#%5BFOR-711%5D+Cache+results+from+the+Locationmap">[FOR-711] Cache results from the Locationmap</a>
 </li>
 <li>
-<a href="#%5BFOR-735%5D+PDF+cannot+be+generated+when+running+Forrest+as+a+webapp">[FOR-735] PDF cannot be generated when running Forrest as a webapp</a>
-</li>
-<li>
 <a href="#%5BFOR-388%5D+Use+plugins+in-place+if+src+available">[FOR-388] Use plugins in-place if src available</a>
 </li>
 <li>
 <a href="#%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo">[FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo</a>
 </li>
 <li>
+<a href="#%5BFOR-735%5D+PDF+cannot+be+generated+when+running+Forrest+as+a+webapp">[FOR-735] PDF cannot be generated when running Forrest as a webapp</a>
+</li>
+<li>
 <a href="#%5BFOR-490%5D+serve+multiple+sites+on+a+single+Forrest+instance">[FOR-490] serve multiple sites on a single Forrest instance</a>
 </li>
 <li>
@@ -576,23 +576,7 @@
 &lt;br&gt;
 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)</p>
 </div>
-<a name="N100AB"></a><a name="%5BFOR-735%5D+PDF+cannot+be+generated+when+running+Forrest+as+a+webapp"></a>
-<h2 class="underlined_10">[FOR-735] PDF cannot be generated when running Forrest as a webapp</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-735">http://issues.apache.org/jira/browse/FOR-735</a>
-</p>
-<p>(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)
-&lt;br&gt;
-
-&lt;br&gt;
-- run forrest webapp to create an empty webapp
-&lt;br&gt;
-- configure Tomcat to run the webapp (we did it by creating a context descriptor and put it onder Tomcat's config directory)
-&lt;br&gt;
-- the pdf links give an error &amp;quot;Resource Not Found&amp;quot;</p>
-</div>
-<a name="N100B9"></a><a name="%5BFOR-388%5D+Use+plugins+in-place+if+src+available"></a>
+<a name="N100AB"></a><a name="%5BFOR-388%5D+Use+plugins+in-place+if+src+available"></a>
 <h2 class="underlined_10">[FOR-388] Use plugins in-place if src available</h2>
 <div class="section">
 <p>
@@ -608,7 +592,7 @@
 &lt;br&gt;
 </p>
 </div>
-<a name="N100C7"></a><a name="%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo"></a>
+<a name="N100B9"></a><a name="%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo"></a>
 <h2 class="underlined_10">[FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo</h2>
 <div class="section">
 <p>
@@ -621,6 +605,22 @@
 The solution is discussed here:
 &lt;br&gt;
 &lt;a href="http://marc.theaimsgroup.com/?t=113176328300002"&gt;http://marc.theaimsgroup.com/?t=113176328300002&lt;/a&gt;</p>
+</div>
+<a name="N100C7"></a><a name="%5BFOR-735%5D+PDF+cannot+be+generated+when+running+Forrest+as+a+webapp"></a>
+<h2 class="underlined_10">[FOR-735] PDF cannot be generated when running Forrest as a webapp</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-735">http://issues.apache.org/jira/browse/FOR-735</a>
+</p>
+<p>(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)
+&lt;br&gt;
+
+&lt;br&gt;
+- run forrest webapp to create an empty webapp
+&lt;br&gt;
+- configure Tomcat to run the webapp (we did it by creating a context descriptor and put it onder Tomcat's config directory)
+&lt;br&gt;
+- the pdf links give an error &amp;quot;Resource Not Found&amp;quot;</p>
 </div>
 <a name="N100D5"></a><a name="%5BFOR-490%5D+serve+multiple+sites+on+a+single+Forrest+instance"></a>
 <h2 class="underlined_10">[FOR-490] serve multiple sites on a single Forrest instance</h2>

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 @@
 <ul>
         
 <li>
-<strong>Step 1</strong>: Do <span class="codefrag">'forrest seed'</span> to populate
+<strong>Step 1</strong>: Do <span class="codefrag ">'forrest seed'</span> to populate
           the directory with template site structure and contents.</li>
         
 <li>
@@ -247,9 +247,9 @@
           task-specific, presentation-neutral XML.</li>
         
 <li>
-<strong>Step 3</strong>: Do <span class="codefrag">'forrest run'</span> then use
+<strong>Step 3</strong>: Do <span class="codefrag ">'forrest run'</span> then use
           the web browser to immediately review
-          changes at <span class="codefrag">http://localhost:8888/</span>
+          changes at <span class="codefrag ">http://localhost:8888/</span>
           
 <ul>
 <li>
@@ -267,7 +267,7 @@
 </li>
         
 <li>
-<strong>Step 4</strong>: Do <span class="codefrag">'forrest'</span> to generate the
+<strong>Step 4</strong>: Do <span class="codefrag ">'forrest'</span> to generate the
           complete website from the XML sources.
           Various styles (known as skins) are available. Custom skins
           can be developed.</li>

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 @@
 <div class="section">
 <p class="note">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 <a href="index.html#status">status</a>.</p>
 <p>Use the links below to download a distribution of Apache Forrest from one of our mirrors. It is good practice to <a href="[location]#verify">verify the integrity</a> of the distribution files.</p>
-<p>Apache Forrest is distributed as a <span class="codefrag">zip</span> archive (for Windows) and as a <span class="codefrag">tar.gz</span> archive (for UNIX). The contents are the same, the only difference is the line-endings of all text files.</p>
+<p>Apache Forrest is distributed as a <span class="codefrag ">zip</span> archive (for Windows) and as a <span class="codefrag ">tar.gz</span> archive (for UNIX). The contents are the same, the only difference is the line-endings of all text files.</p>
 <p>The distribution contains all of the source code, documentation, and resources, together with the pre-built ready-to-run forrest binary.</p>
 </div>
 <a name="N1002C"></a><a name="closest"></a>
@@ -235,7 +235,7 @@
 <h2 class="underlined_10">Verify releases</h2>
 <div class="section">
 <p>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.</p>
-<p>The PGP signatures can be verified using <a href="http://www.pgpi.org/">PGP</a> or <a href="http://www.gnupg.org/">GPG</a>. First download the Apache Forrest <a href="http://svn.apache.org/repos/asf/forrest/trunk/KEYS">KEYS</a> as well as the <span class="codefrag">asc</span> 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 ...</p>
+<p>The PGP signatures can be verified using <a href="http://www.pgpi.org/">PGP</a> or <a href="http://www.gnupg.org/">GPG</a>. First download the Apache Forrest <a href="http://svn.apache.org/repos/asf/forrest/trunk/KEYS">KEYS</a> as well as the <span class="codefrag ">asc</span> 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 ...</p>
 <pre>% 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
 </pre>
-<p>To verify the MD5 signature on the files, you need to use a program called <span class="codefrag">md5</span> or <span class="codefrag">md5sum</span>, which is included in many unix distributions. It is also available as part of <a href="http://www.gnu.org/software/textutils/textutils.html">GNU Textutils</a>. Windows users can get binary md5 programs from <a href="http://www.fourmilab.ch/md5/">here</a>, <a href="http://www.pc-tools.net/win32/freeware/console/">here</a>, or <a href="http://www.slavasoft.com/fsum/">here</a>.</p>
+<p>To verify the MD5 signature on the files, you need to use a program called <span class="codefrag ">md5</span> or <span class="codefrag ">md5sum</span>, which is included in many unix distributions. It is also available as part of <a href="http://www.gnu.org/software/textutils/textutils.html">GNU Textutils</a>. Windows users can get binary md5 programs from <a href="http://www.fourmilab.ch/md5/">here</a>, <a href="http://www.pc-tools.net/win32/freeware/console/">here</a>, or <a href="http://www.slavasoft.com/fsum/">here</a>.</p>
 <p>We strongly recommend you verify your downloads with both PGP and MD5.</p>
 </div>
 </div>

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 <span class="codefrag">project.required.plugins</span> property 
-            in the projects <span class="codefrag">forrest.properties</span> file. When Forrest 
+            have named them in the <span class="codefrag ">project.required.plugins</span> property 
+            in the projects <span class="codefrag ">forrest.properties</span> file. When Forrest 
             builds the site it will automatically discover the plugin and install 
             it.For more information on how to use plugins see
             <a href="http://forrest.apache.org/pluginDocs/plugins_0_70/usingPlugins.html">

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.</p>
 <a name="N10023"></a><a name="pluginTypes"></a>
 <h3 class="underlined_5">Types of Plugin</h3>
-<p>There are three types of plugin, <span class="codefrag">input</span>,
-        <span class="codefrag">output</span> and <span class="codefrag">internal</span>. Each plugin has a 
+<p>There are three types of plugin, <span class="codefrag ">input</span>,
+        <span class="codefrag ">output</span> and <span class="codefrag ">internal</span>. Each plugin has a 
         specific role to play and extends a different part of Forrest:</p>
 <pre class="code">
                             internal plugins
@@ -242,22 +242,22 @@
                      (**.xml)         (**.html, **.pdf etc.) 
 </pre>
 <p>The name of the sitemap will reflect the type of plugin in use.
-        That is, an internal plugin will have a sitemap called <span class="codefrag">internal.xmap</span>,
-        an output plugin has <span class="codefrag">output.xmap</span> and an input plugin has
-        <span class="codefrag">input.xmap</span>. In addition, an input plugin can optionally provide a
-        <span class="codefrag">resources.xmap</span>.</p>
+        That is, an internal plugin will have a sitemap called <span class="codefrag ">internal.xmap</span>,
+        an output plugin has <span class="codefrag ">output.xmap</span> and an input plugin has
+        <span class="codefrag ">input.xmap</span>. In addition, an input plugin can optionally provide a
+        <span class="codefrag ">resources.xmap</span>.</p>
 <a name="N10048"></a><a name="inputPlugins"></a>
 <h4>Input Plugins</h4>
 <p>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.</p>
-<p>An input plugin provides an <span class="codefrag">input.xmap</span> file. 
+<p>An input plugin provides an <span class="codefrag ">input.xmap</span> 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.</p>
-<p>An input plugin may also provide a <span class="codefrag">resources.xmap</span>
+<p>An input plugin may also provide a <span class="codefrag ">resources.xmap</span>
           file. This can be used to match additional resources that are not 
           stored in XML files, for example, javascript files.</p>
 <a name="N1005E"></a><a name="outputPlugins"></a>
@@ -265,7 +265,7 @@
 <p>Output plugins provide a new output format. For example, the
           s5 plugin extends Forrest to produce HTML slides from Forrest
           documents.</p>
-<p>An output plugin provides an <span class="codefrag">output.xmap</span> file.
+<p>An output plugin provides an <span class="codefrag ">output.xmap</span> 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.</p>
@@ -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.</p>
-<p>Internal plugins provide an <span class="codefrag">internal.xmap</span> file. 
+<p>Internal plugins provide an <span class="codefrag ">internal.xmap</span> 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:</p>
 <pre class="code">org.apache.forrest.plugin.PLUGIN_TYPE.PLUGIN_NAME</pre>
 <pre class="code">net.sf.forrestPlugins.PLUGIN_TYPE.PLUGIN_NAME</pre>
-<p>Where <span class="codefrag">PLUGIN_TYPE</span> is either "internal", "input" or
-        "output" and <span class="codefrag">PLUGIN_NAME"</span> is a suitable name chosen by
+<p>Where <span class="codefrag ">PLUGIN_TYPE</span> is either "internal", "input" or
+        "output" and <span class="codefrag ">PLUGIN_NAME"</span> is a suitable name chosen by
         yourself.</p>
 <div class="warning">
 <div class="label">Warning</div>
@@ -403,8 +403,8 @@
 <h2 class="underlined_10">How does Installation work?</h2>
 <div class="section">
 <p>When Forrest installs a plugin it downloads a zip of the plugin code and 
-    extracts it into the <span class="codefrag">plugins</span> directory of Forrest and an entry is made 
-    in <span class="codefrag">src/plugins/[input|internal|output].xmap</span> (recall the actual sitemap
+    extracts it into the <span class="codefrag ">plugins</span> directory of Forrest and an entry is made 
+    in <span class="codefrag ">src/plugins/[input|internal|output].xmap</span> (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:</p>

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.</p>
 <a name="N10016"></a><a name="What+plugins+are+available%3F"></a>
 <h3 class="underlined_5">What plugins are available?</h3>
-<p>You can run the command <span class="codefrag">forrest available-plugins</span> to get
+<p>You can run the command <span class="codefrag ">forrest available-plugins</span> to get
         a list of the known plugins for Forrest.</p>
 <p>If you would like to have your own plugin added to this list then
         contact the <a href="../../mail-lists.html">developer mailing list</a>.</p>
@@ -203,11 +203,11 @@
 <h2 class="underlined_10">How is a Plugin Installed?</h2>
 <div class="section">
 <p>If a site requires one or more plugins then the site designer will 
-      have named them in the <span class="codefrag">project.required.plugins</span> property 
-      in the projects <span class="codefrag">forrest.properties</span> file. When Forrest 
+      have named them in the <span class="codefrag ">project.required.plugins</span> property 
+      in the projects <span class="codefrag ">forrest.properties</span> file. When Forrest 
       builds the site it will automatically discover the plugin and install 
       it. In otherwords, the user need do nothing. For example, 
-      <span class="codefrag">project.required.plugins=org.apache.forrest.plugin.input.OpenOffice.org,org.apache.forrest.plugin.input.simplifiedDocbook</span>
+      <span class="codefrag ">project.required.plugins=org.apache.forrest.plugin.input.OpenOffice.org,org.apache.forrest.plugin.input.simplifiedDocbook</span>
       will cause Forrest to load the plugins called "org.apache.forrest.plugin.input.OpenOffice.org" and
       "org.apache.forrest.plugin.input.simplifiedDocbook".</p>
 <p>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
-      <span class="codefrag">org.apache.forrest.plugin.input.OpenOffice.org-1.0</span> If you define a version of the
+      <span class="codefrag ">org.apache.forrest.plugin.input.OpenOffice.org-1.0</span> 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
-        <span class="codefrag">project.required.plugins</span> property in the projects 
-        <span class="codefrag">forrest.properties</span> file all plugins that contain 
+        <span class="codefrag ">project.required.plugins</span> property in the projects 
+        <span class="codefrag ">forrest.properties</span> 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.</p>
 <p>If you do require additional plugin functionality, be sure to
         include all required plugins in the 
-        <span class="codefrag">project.required.plugins</span> property in the project's
-        <span class="codefrag">forrest.properties</span>. You can view
-        <span class="codefrag">main/webapp/default-forrest.properties</span>
+        <span class="codefrag ">project.required.plugins</span> property in the project's
+        <span class="codefrag ">forrest.properties</span>. You can view
+        <span class="codefrag ">main/webapp/default-forrest.properties</span>
         to see the names of plugins that provide previously core 
         functionality.</p>
 <p>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 
-        <span class="codefrag">project.required.plugins</span> property of 
-        <span class="codefrag">main/webapp/default-forrest.properties</span>
+        <span class="codefrag ">project.required.plugins</span> property of 
+        <span class="codefrag ">main/webapp/default-forrest.properties</span>
         it is recomended that you override this value in your project's
-        <span class="codefrag">forrest.properties</span> file.</p>
+        <span class="codefrag ">forrest.properties</span> file.</p>
 </div>
     
     
@@ -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 
-      <span class="codefrag">project.required.plugins</span> property, therefore the mounting 
+      <span class="codefrag ">project.required.plugins</span> property, therefore the mounting 
       order and therefore processing precedence is under user control.</p>
 </div>
     

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 <span class="codefrag">project.required.plugins</span> property 
-            in the projects <span class="codefrag">forrest.properties</span> file. When Forrest 
+            have named them in the <span class="codefrag ">project.required.plugins</span> property 
+            in the projects <span class="codefrag ">forrest.properties</span> file. When Forrest 
             builds the site it will automatically discover the plugin and install 
             it.For more information on how to use plugins see
             <a href="http://forrest.apache.org/pluginDocs/plugins_0_70/usingPlugins.html">

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.</p>
 <a name="N10023"></a><a name="pluginTypes"></a>
 <h3 class="underlined_5">Types of Plugin</h3>
-<p>There are three types of plugin, <span class="codefrag">input</span>,
-        <span class="codefrag">output</span> and <span class="codefrag">internal</span>. Each plugin has a 
+<p>There are three types of plugin, <span class="codefrag ">input</span>,
+        <span class="codefrag ">output</span> and <span class="codefrag ">internal</span>. Each plugin has a 
         specific role to play and extends a different part of Forrest:</p>
 <pre class="code">
                             internal plugins
@@ -246,13 +246,13 @@
 <p>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.</p>
-<p>An input plugin provides an <span class="codefrag">input.xmap</span> file. 
+<p>An input plugin provides an <span class="codefrag ">input.xmap</span> 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.</p>
-<p>An input plugin may also provide a <span class="codefrag">resources.xmap</span>
+<p>An input plugin may also provide a <span class="codefrag ">resources.xmap</span>
           file. This can be used to match additional resources that are not 
           stored in XML files, for example, javascript files.</p>
 <a name="N1004F"></a><a name="outputPlugins"></a>
@@ -260,7 +260,7 @@
 <p>Output plugins provide a new output format. For example, the
           s5 plugin extends Forrest to produce HTML slides from Forrest
           documents.</p>
-<p>An output plugin provides an <span class="codefrag">output.xmap</span> file.
+<p>An output plugin provides an <span class="codefrag ">output.xmap</span> 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.</p>
@@ -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.</p>
-<p>Internal plugins provide an <span class="codefrag">internal.xmap</span> file. 
+<p>Internal plugins provide an <span class="codefrag ">internal.xmap</span> 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:</p>
 <pre class="code">org.apache.forrest.plugin.PLUGIN_TYPE.PLUGIN_NAME</pre>
 <pre class="code">net.sf.forrestPlugins.PLUGIN_TYPE.PLUGIN_NAME</pre>
-<p>Where <span class="codefrag">PLUGIN_TYPE</span> is either "internal", "input" or
-        "output" and <span class="codefrag">PLUGIN_NAME"</span> is a suitable name chosen by
+<p>Where <span class="codefrag ">PLUGIN_TYPE</span> is either "internal", "input" or
+        "output" and <span class="codefrag ">PLUGIN_NAME"</span> is a suitable name chosen by
         yourself.</p>
 <div class="warning">
 <div class="label">Warning</div>
@@ -402,8 +402,8 @@
 <h2 class="underlined_10">How does Installation work?</h2>
 <div class="section">
 <p>When Forrest installs a plugin it downloads a zip of the plugin code and 
-    extracts it into the <span class="codefrag">plugins</span> directory of Forrest and an entry is made 
-    in <span class="codefrag">src/plugins/sitemap.xmap</span>. For example, installing the 
+    extracts it into the <span class="codefrag ">plugins</span> directory of Forrest and an entry is made 
+    in <span class="codefrag ">src/plugins/sitemap.xmap</span>. For example, installing the 
     IMSManifest plugin described above will result in the following entry 
     being added to the plugin sitemap:</p>
 <pre class="code">

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.</p>
 <a name="N10016"></a><a name="What+plugins+are+available%3F"></a>
 <h3 class="underlined_5">What plugins are available?</h3>
-<p>You can run the command <span class="codefrag">forrest available-plugins</span> to get
+<p>You can run the command <span class="codefrag ">forrest available-plugins</span> to get
         a list of the known plugins for Forrest.</p>
 <p>If you would like to have your own plugin added to this list then
         contact the <a href="../../mail-lists.html">developer mailing list</a>.</p>
@@ -203,11 +203,11 @@
 <h2 class="underlined_10">How is a Plugin Installed?</h2>
 <div class="section">
 <p>If a site requires one or more plugins then the site designer will 
-      have named them in the <span class="codefrag">project.required.plugins</span> property 
-      in the projects <span class="codefrag">forrest.properties</span> file. When Forrest 
+      have named them in the <span class="codefrag ">project.required.plugins</span> property 
+      in the projects <span class="codefrag ">forrest.properties</span> file. When Forrest 
       builds the site it will automatically discover the plugin and install 
       it. In otherwords, the user need do nothing. For example, 
-      <span class="codefrag">project.required.plugins=org.apache.forrest.plugin.input.OpenOffice.org,org.apache.forrest.plugin.input.simplifiedDocbook</span>
+      <span class="codefrag ">project.required.plugins=org.apache.forrest.plugin.input.OpenOffice.org,org.apache.forrest.plugin.input.simplifiedDocbook</span>
       will cause Forrest to load the plugins called "org.apache.forrest.plugin.input.OpenOffice.org" and
       "org.apache.forrest.plugin.input.simplifiedDocbook".</p>
 <p>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
-      <span class="codefrag">org.apache.forrest.plugin.input.OpenOffice.org-1.0</span> If you define a version of the
+      <span class="codefrag ">org.apache.forrest.plugin.input.OpenOffice.org-1.0</span> 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
-        <span class="codefrag">project.required.plugins</span> property in the projects 
-        <span class="codefrag">forrest.properties</span> file all plugins that contain 
+        <span class="codefrag ">project.required.plugins</span> property in the projects 
+        <span class="codefrag ">forrest.properties</span> 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.</p>
 <p>If you do require additional plugin functionality, be sure to
         include all required plugins in the 
-        <span class="codefrag">project.required.plugins</span> property in the project's
-        <span class="codefrag">forrest.properties</span>. You can view
-        <span class="codefrag">main/webapp/default-forrest.properties</span>
+        <span class="codefrag ">project.required.plugins</span> property in the project's
+        <span class="codefrag ">forrest.properties</span>. You can view
+        <span class="codefrag ">main/webapp/default-forrest.properties</span>
         to see the names of plugins that provide previously core 
         functionality.</p>
 <p>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 
-        <span class="codefrag">project.required.plugins</span> property of 
-        <span class="codefrag">main/webapp/default-forrest.properties</span>
+        <span class="codefrag ">project.required.plugins</span> property of 
+        <span class="codefrag ">main/webapp/default-forrest.properties</span>
         it is recomended that you override this value in your project's
-        <span class="codefrag">forrest.properties</span> file.</p>
+        <span class="codefrag ">forrest.properties</span> file.</p>
 </div>
     
     
@@ -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 
-      <span class="codefrag">project.required.plugins</span> property, therefore the mounting 
+      <span class="codefrag ">project.required.plugins</span> property, therefore the mounting 
       order and therefore processing precedence is under user control.</p>
 </div>
     

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 @@
           </h3>
 <p>
             First, you need to activate the Site.xml view. This can be done by:
-            <span class="codefrag">
+            <span class="codefrag ">
               Window -&gt; Show View -&gt; Other... -&gt; Forrest -&gt; SiteXML -&gt; OK
             </span>
             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 @@
         </h3>
 <p>
           First, you need to activate the Tab.xml view. This can be done by:
-          <span class="codefrag">
+          <span class="codefrag ">
             Window -&gt; Show View -&gt; Other... -&gt; Forrest -&gt; TabXML -&gt; OK
           </span>
           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.</p>
 <p>To build ForrestBar locally rather than downloading, go to
         FORREST_HOME/tools/forrestbar and run the following command:
-        <span class="codefrag">forrest -f build.xml</span> and the .xpi file will be built for you
+        <span class="codefrag ">forrest -f build.xml</span> 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.</p>
 </div>

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 @@
 <h2 class="underlined_10">Build</h2>
 <div class="section">
 <p>To build the webapp from source, you need <a href="http://maven.apache.org/">Apache Maven</a> installed. From a
-      command prompt, go to the <span class="codefrag">forrest/tools/forrestbot/webapp</span>
-      directory and execute "<span class="codefrag">maven war</span>".</p>
+      command prompt, go to the <span class="codefrag ">forrest/tools/forrestbot/webapp</span>
+      directory and execute "<span class="codefrag ">maven war</span>".</p>
 </div>
 
     

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 @@
       
 </table>
 <p>If you want to do more advanced processing for your project, you can
-      override the 'main' target, which by default is <span class="codefrag">&lt;target
+      override the 'main' target, which by default is <span class="codefrag ">&lt;target
       name="main" depends="getsrc, build, deploy, notify"/&gt;</span>, create
       your own implementation of a workstage, or use any other ant tasks to do
       additional work.</p>
@@ -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 <span class="codefrag">&lt;import
+      CVS/SVN). Then in your project buildfile, have <span class="codefrag ">&lt;import
       file="my-settings.xml"/&gt;</span>.</p>
 <a name="N100E9"></a><a name="Misc+Properties"></a>
 <h4>Misc Properties</h4>
@@ -476,7 +476,7 @@
 <a name="N10120"></a><a name="getsrc.clean-workdir"></a>
 <h4>getsrc.clean-workdir</h4>
 <p>This should be executed before a getsrc implementation is executed.
-          For example, <span class="codefrag">&lt;target name="getsrc"
+          For example, <span class="codefrag ">&lt;target name="getsrc"
           depends="getsrc.clean-workdir, getsrc.svn"/&gt;</span>
 </p>
 <a name="N1012C"></a><a name="getsrc.local"></a>
@@ -674,7 +674,7 @@
 
               <td colspan="1" rowspan="1">Directory to temporarily hold working files</td>
 
-              <td colspan="1" rowspan="1">work</td>
+              <td colspan="1" rowspan="1">work/${ant.project.name}</td>
 
               <td colspan="1" rowspan="1">No</td>
             
@@ -717,7 +717,7 @@
 
               <td colspan="1" rowspan="1">Path to deploy site to - the dir that would be the equivalant 
               of build/site dir.  Relative paths will be relative to
-              ${bot.home}</td>
+              project forrestbot descriptor file.</td>
 
               <td colspan="1" rowspan="1">sites/${ant.project.name}</td>
 

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 @@
 <div class="section">
 <ol>
         
-<li>Delete the <span class="codefrag">forrest</span> directory from the XXE application
-        config directory. (e.g. <span class="codefrag">D:\Program
+<li>Delete the <span class="codefrag ">forrest</span> directory from the XXE application
+        config directory. (e.g. <span class="codefrag ">D:\Program
         Files\XMLmind_XML_Editor\config</span>)
         <ul>
           
@@ -227,13 +227,13 @@
 <ol>
         
 <li>Extract into the XXE application config directory (e.g.
-        <span class="codefrag">D:\Program Files\XMLmind_XML_Editor\config</span>)<br>
+        <span class="codefrag ">D:\Program Files\XMLmind_XML_Editor\config</span>)<br>
         
 <strong>OR</strong>
 </li>
         
 <li>Extract into your XXE user directory (e.g.
-        <span class="codefrag">~/.xxe/addon/config</span>) (only in version 1.3+ of this config).
+        <span class="codefrag ">~/.xxe/addon/config</span>) (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</li>
       
@@ -250,16 +250,16 @@
 <li>Make sure the FORREST_HOME environment variable is set</li>
 
         
-<li>Change directory to <span class="codefrag">forrest/tools/xxe</span>
+<li>Change directory to <span class="codefrag ">forrest/tools/xxe</span>
 </li>
 
         
-<li>Run <span class="codefrag">ant</span> in this directory</li>
+<li>Run <span class="codefrag ">ant</span> in this directory</li>
       
 </ol>
 <p>To work directly with the SVN version, check out
       http://svn.apache.org/repos/asf/forrest/trunk/tools/xxe/ into the
-      <span class="codefrag">forrest</span> folder in the XXE <span class="codefrag">config</span> folder. Run the
+      <span class="codefrag ">forrest</span> folder in the XXE <span class="codefrag ">config</span> folder. Run the
       build there to copy the DTDs</p>
 <p>
 <a href="http://www.xmlmind.com/xmleditor/_distrib/docs/configure/index.html">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 @@
 <div class="section">
 <p>
         Configuration files and directory structures are stored in SVN at
-        <span class="codefrag">https://svn.apache.org/repos/asf/forrest/zone</span>
+        <span class="codefrag ">https://svn.apache.org/repos/asf/forrest/zone</span>
       
 </p>
 <p>
@@ -287,7 +287,7 @@
         </p>
 <p>
           Various local software is installed in
-          <span class="codefrag">/export/opt/</span> (not managed with SVN) ...
+          <span class="codefrag ">/export/opt/</span> (not managed with SVN) ...
         </p>
 <a name="N10065"></a><a name="s-forrest"></a>
 <h3 class="underlined_5">Forrest</h3>



Mime
View raw message