forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r354312 [14/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/docs_0_80/changes.xml
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/changes.xml?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_80/changes.xml (original)
+++ forrest/site/docs_0_80/changes.xml Mon Dec  5 20:55:03 2005
@@ -92,7 +92,9 @@
         Added document to explain the process for
         <link href="site:getting-involved/committed">Becoming an Apache Forrest
         committer</link>.
-      () Thanks to Addison Berry. Fixes <link href="http://issues.apache.org/jira/browse/FOR-603">FOR-603</link>.</li></ul></section></section>
+      () Thanks to Addison Berry. Fixes <link href="http://issues.apache.org/jira/browse/FOR-603">FOR-603</link>.</li></ul></section><section><title>Contributors</title><p>This is a list of all people who have contributed to this release, but 
+       were full developers on the project. We thank these people for their 
+       contributions.</p><ul><li>Addison Berry</li><li>Pier Fumagalli</li><li>Sjur N. Moshagen</li></ul></section></section>
     <section id="version_0.7.1-dev"><title>Version 0.7.1-dev (not yet released)</title><section><title>Changes to the Code Base</title><ul><li><icon alt="update" src="../images/update.jpg"/>
         Added new "clean" targets. Doing 'forrest clean-site' will remove
         the contents of the project's generated documents directory.
@@ -314,7 +316,9 @@
         Updated How-To:
         <link href="site:v0.70//pdf-tab">How to create a PDF document for each
         tab</link> to create subject-specific aggregated documents.
-      (TS)</li></ul></section></section>
+      (TS)</li></ul></section><section><title>Contributors</title><p>This is a list of all people who have contributed to this release, but 
+       were full developers on the project. We thank these people for their 
+       contributions.</p><ul><li>Cyriaque Dupoirieux</li><li>Ferdinand Soethe</li><li>Florian G. Haas</li><li>Gary Feldman</li><li>Ian P. Springer</li><li>Joao Ferreira</li><li>Johannes Schaefer</li><li>Jörg Werner</li><li>Kevin</li><li>Mark Eggers</li><li>Ron Blaschke</li><li>Stephan E. Schlierf</li><li>Tamara Harpster</li><li>Upayavira</li></ul></section></section>
     <section id="version_0.6"><title>Version 0.6 (2004-10-15)</title><section><title>Changes to Project Administration</title><ul><li><icon alt="update" src="../images/update.jpg"/>
         Moved forrestbot2 from scratchpad into main.  Uses ant 1.6's 
         'import' task instead of XSLT/ant.  Webapp completely
@@ -828,7 +832,9 @@
       (JJP)</li><li><icon alt="update" src="../images/update.jpg"/>
         Forrest is now a top-level Apache project. The new website is at
         <link href="http://forrest.apache.org/">http://forrest.apache.org/</link>
-      (DC)</li></ul></section></section>
+      (DC)</li></ul></section><section><title>Contributors</title><p>This is a list of all people who have contributed to this release, but 
+       were full developers on the project. We thank these people for their 
+       contributions.</p><ul><li>Apache Infrastructure</li><li>Arturo Vazquez</li><li>Eric Burghard</li><li>Eric BURGHARD</li><li>Fabio Rinaldi</li><li>Jan Materne</li><li>Juan Jose Pablos</li><li>Nick Chalko</li><li>Pierrick Brihaye</li><li>Ramón Prades</li><li>Rick Tessner</li><li>Rob Exley</li><li>Ross Gardler</li><li>Sean Wheller</li><li>Sebastian Bergmann</li><li>Unico Hommes</li></ul></section></section>
 
     <section id="version_0.5.1"><title>Version 0.5.1 (2003-10-06)</title><section><title>Changes to Build</title><ul><li><icon alt="fix" src="../images/fix.jpg"/>
         forrest.antproxy.xml script now properly fails when Cocoon fails
@@ -1082,7 +1088,9 @@
       (NKB)</li></ul></section><section><title>Changes to Documentation</title><ul><li><icon alt="add" src="../images/add.jpg"/>
         Added new document to facilitate
         upgrading to v0.5
-      (JT)</li></ul></section></section>
+      (JT)</li></ul></section><section><title>Contributors</title><p>This is a list of all people who have contributed to this release, but 
+       were full developers on the project. We thank these people for their 
+       contributions.</p><ul><li>Dave Brondsema</li><li>Eirik Bjørsnøs</li><li>Frederic Robesyn</li><li>J.Pietschmann</li><li>Joerg Heinicke</li><li>Ralf Hauser</li><li>Ringo de Smet</li><li>Stefan Bodewig</li></ul></section></section>
     <section id="version_0.4"><title>Version 0.4 (2003-02-12)</title><section><title>Changes to the Code Base</title><ul><li><icon alt="add" src="../images/add.jpg"/>
         Added a minimal template skin.
       (JT)</li><li><icon alt="fix" src="../images/fix.jpg"/>
@@ -1127,7 +1135,9 @@
       (NKB)</li></ul></section><section><title>Changes to Documentation</title><ul><li><icon alt="update" src="../images/update.jpg"/>
         Added page for ForrestBar on the site with a simple link and an autoinstall link
         to the forrestbar.xpi generated by Gump every day.
-      (NKB)</li></ul></section></section>
+      (NKB)</li></ul></section><section><title>Contributors</title><p>This is a list of all people who have contributed to this release, but 
+       were full developers on the project. We thank these people for their 
+       contributions.</p><ul><li>Berin Loritsch</li><li>Bernhard Brandmair</li><li>Cathy Zura</li></ul></section></section>
 
     <section id="version_0.3"><title>Version 0.3 (2003-01-30)</title><section><title>Changes to Build</title><ul><li><icon alt="add" src="../images/add.jpg"/>
         Allow configuration of a project local-catalog and the entity resolver
@@ -1287,7 +1297,9 @@
         Added enhancements to status.xml to comply with the needs for a complete status file,
         like other "STATUS" text files at Apache.
         Stylesheets not yet done.
-      (NKB)</li></ul></section></section>
+      (NKB)</li></ul></section><section><title>Contributors</title><p>This is a list of all people who have contributed to this release, but 
+       were full developers on the project. We thank these people for their 
+       contributions.</p><ul><li>Omar Belhaj</li><li>Stefan Michels</li></ul></section></section>
     <section id="version_0.2"><title>Version 0.2 (2002-11-16)</title><section><title>Changes to the Code Base</title><ul><li><icon alt="fix" src="../images/fix.jpg"/>
         Fixed bug where validation of xdocs was not descending into
         sub-directories.
@@ -1497,5 +1509,8 @@
       (JT)</li><li><icon alt="update" src="../images/update.jpg"/>
         Ensure that initial DTDs are valid and that the initial XML instances can be
         validated using these DTDs and OASIS Catalogs.
-      (DC) Thanks to <link href="mailto:stevenn@outerthought.org">Steven Noels</link>.</li></ul></section></section>
-  </body></document>
\ No newline at end of file
+      (DC) Thanks to <link href="mailto:stevenn@outerthought.org">Steven Noels</link>.</li></ul></section><section><title>Contributors</title><p>This is a list of all people who have contributed to this release, but 
+       were full developers on the project. We thank these people for their 
+       contributions.</p><ul><li>Bert Van Kets</li><li>Bruno Dumon</li><li>Kevin Ross</li><li>Leo Simons</li><li>Marc Portier</li><li>Peter Donald</li><li>Steven Noels</li></ul></section></section>
+  <section><title>Committers</title><p>This is a list of all people who have been 
+         voted in as committers on this project.</p><ul><li>Stefano Mazzocchi (SM)</li><li>Sam Ruby (SR)</li><li>John Morrison (JM)</li><li>David Crossley (DC)</li><li>Steven Noels (SN)</li><li>Nicola Ken Barozzi (NKB)</li><li>Konstantin Piroumian (KP)</li><li>Bert Van Kets (BK)</li><li>Marc Portier (MP)</li><li>Jeff Turner (JT)</li><li>Juan Jose Pablos (JJP)</li><li>Dave Brondsema (DB)</li><li>Antonio Gallardo (AG)</li><li>Reinhard Pötz (RP)</li><li>Ross Gardler (RDG)</li><li>Thorsten Scherler (TS)</li><li>Rick Tessner (RFT)</li><li>Ferdinand Soethe (FSO)</li><li>Volunteer needed (open)</li></ul></section></body></document>
\ No newline at end of file

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

Modified: forrest/site/docs_0_80/faq.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/faq.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_80/faq.html (original)
+++ forrest/site/docs_0_80/faq.html Mon Dec  5 20:55:03 2005
@@ -603,14 +603,14 @@
 <p> There are two ways to control this. If you get an OutOfMemoryError when Cocoon is
           generating pages, see the first paragraph. If you get an OutOfMemoryError when outside of
           Cocoon (e.g., copying raw files), see the second paragraph. </p>
-<p> The <span class="codefrag">maxmemory</span> property in the <span class="codefrag">forrest.properties</span> file controls
+<p> The <span class="codefrag ">maxmemory</span> property in the <span class="codefrag ">forrest.properties</span> file controls
           how much memory Cocoon uses. Like many other properties you can copy them from the default
-          configuration at <span class="codefrag">main/fresh-site/forrest.properties</span>
+          configuration at <span class="codefrag ">main/fresh-site/forrest.properties</span>
         
 </p>
-<p> Set the <span class="codefrag">ANT_OPTS</span> environment variable before you run forrest. The exact
+<p> Set the <span class="codefrag ">ANT_OPTS</span> environment variable before you run forrest. The exact
           value you set it to is dependant on your JVM, but something like
-          <span class="codefrag">ANT_OPTS=-Xmx500M</span> will probably work. </p>
+          <span class="codefrag ">ANT_OPTS=-Xmx500M</span> will probably work. </p>
 </div>
 <a name="N10080"></a><a name="debug"></a>
 <h4 class="faq">1.8.  How can I start forrest in debug mode? </h4>
@@ -618,9 +618,9 @@
 <a href="#debug-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p> The <span class="codefrag">forrest.jvmargs</span> property in the <span class="codefrag">forrest.properties</span> file 
+<p> The <span class="codefrag ">forrest.jvmargs</span> property in the <span class="codefrag ">forrest.properties</span> file 
           can be used to start forrest in debug mode on a specific port.
-          <span class="codefrag">forrest.jvmargs=-Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n</span>
+          <span class="codefrag ">forrest.jvmargs=-Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n</span>
         
 </p>
 </div>
@@ -651,7 +651,7 @@
 </div>
 <div style="margin-left: 15px">
 <p>
-          The <span class="codefrag">site.xml</span> configuration file is used for two different purposes:
+          The <span class="codefrag ">site.xml</span> configuration file is used for two different purposes:
           defining the navigation menus, and as a method for defining references
           to be used when linking between documents.
           This file is fully explained in
@@ -694,7 +694,7 @@
 <div style="margin-left: 15px">
 <p>
           There are examples in the 'forrest seed site' and also the Forrest website documents
-          are included with the distribution (<span class="codefrag">cd forrest/site-author;
+          are included with the distribution (<span class="codefrag ">cd forrest/site-author;
             forrest run</span>).
         </p>
 </div>
@@ -732,8 +732,8 @@
             page break on. All the common block grouping elements support this class, for example, 
             note, warning, p and so on.</p>
 <p>If you want these classes to be processed in your HTML documents as well you should add
-          the following to the <span class="codefrag">extra-css</span> element in your projects
-          <span class="codefrag">skinconf.xml</span>
+          the following to the <span class="codefrag ">extra-css</span> element in your projects
+          <span class="codefrag ">skinconf.xml</span>
         
 </p>
 <pre class="code"> 
@@ -753,7 +753,7 @@
 <a href="#clickable-email-address-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p>You would override <span class="codefrag">
+<p>You would override <span class="codefrag ">
             $FORREST_HOME/main/webapp/skins/common/xslt/html/document2html.xsl</span> and edit the
           "headers/authors" template. </p>
 </div>
@@ -787,11 +787,11 @@
 </li>
           
 <li>Unpack the Jimi distribution and copy JimiProClasses.zip to
-              <span class="codefrag">$FORREST/lib/optional/jimi-1.0.jar</span>.</li>
+              <span class="codefrag ">$FORREST/lib/optional/jimi-1.0.jar</span>.</li>
         
 </ol>
 <p>Alternatively you can use JAI (Java Advanced Imaging API at
-          <span class="codefrag">http://java.sun.com/products/java-media/jai</span>). For more info, see <a href="http://xml.apache.org/fop/graphics.html#packages">FOP Graphics Packages</a>
+          <span class="codefrag ">http://java.sun.com/products/java-media/jai</span>). For more info, see <a href="http://xml.apache.org/fop/graphics.html#packages">FOP Graphics Packages</a>
         
 </p>
 <div class="note">
@@ -806,9 +806,9 @@
 <a href="#tab-index-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p> In <span class="codefrag">tabs.xml</span>, use @href instead of @dir, and omit the trailing '/'. Which
+<p> In <span class="codefrag ">tabs.xml</span>, use @href instead of @dir, and omit the trailing '/'. Which
           file to serve is then a concern of the sitemap. For example, if the "User Manual" tab
-          should link to <span class="codefrag">manual/Introduction.html</span> then <span class="codefrag">tabs.xml</span> should
+          should link to <span class="codefrag ">manual/Introduction.html</span> then <span class="codefrag ">tabs.xml</span> should
           contain: </p>
 <pre class="code">
   &lt;tab label="User Manual" href="manual"/&gt;</pre>
@@ -896,7 +896,7 @@
 </div>
 <div style="margin-left: 15px">
 <p> Use the numeric values for character entities. For example, rather than using
-            <span class="codefrag">&amp;ouml;</span> use <span class="codefrag">&amp;#246;</span>
+            <span class="codefrag ">&amp;ouml;</span> use <span class="codefrag ">&amp;#246;</span>
         
 </p>
 <p> See the <a href="http://www.w3.org/TR/xhtml-modularization/dtd_module_defs.html#a_xhtml_character_entities">XHTML Character Entities</a> and see more discussion at <a href="http://issues.apache.org/jira/browse/FOR-244">Issue FOR-244</a>. </p>
@@ -924,7 +924,7 @@
 <p>but the file content is actually using ISO-8859-1 then you will receive validation
           errors, especially if you include some non-ASCII characters.</p>
 <p> This situation is commonly encountered when you edit the templates created by
-            <span class="codefrag">forrest seed</span> with your favorite (probably localized) editor without paying
+            <span class="codefrag ">forrest seed</span> with your favorite (probably localized) editor without paying
           attention to the encoding, or when you create a new file and simply copy the headers from
           another file. </p>
 <p>Although UTF-8 is an encoding well-suited for most languages, it is not usually the
@@ -932,16 +932,16 @@
           handle different encodings to write the file in disk. With some editors the encoding of
           the file is preserved, while with others the default is used regardless of the original
           encoding. In most cases the encoding used to write files can be controlled by setting the
-          environment variable <span class="codefrag">LANG</span> to an appropriate value, for instance: </p>
+          environment variable <span class="codefrag ">LANG</span> to an appropriate value, for instance: </p>
 <pre class="code">[localhost]$ export LANG=en_US.UTF-8</pre>
 <p>Of course the <em>appropriate</em> way to set the encoding depends on the editor/OS, but
           ultimately relys on the user preferences. So you can use the encoding you prefer, as long
-          as the <span class="codefrag">encoding</span> attribute of the XML declaration matches the actual encoding
+          as the <span class="codefrag ">encoding</span> attribute of the XML declaration matches the actual encoding
           of the file. This means that if you are not willing to abandon ISO-8859-1 you can always
           use the following declaration instead:</p>
 <pre class="code">&lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;</pre>
-<p>Another option is to use "character entities" such as <span class="codefrag">&amp;ouml;</span>
-          (&ouml;) or the numeric form <span class="codefrag">&amp;#246;</span> (&ouml;). </p>
+<p>Another option is to use "character entities" such as <span class="codefrag ">&amp;ouml;</span>
+          (&ouml;) or the numeric form <span class="codefrag ">&amp;#246;</span> (&ouml;). </p>
 <p>Another related issue is that your webserver needs to send http headers with the matching
           charset definitions to the html page. </p>
 <p>Here are some references which explain further: <a href="http://orixo.com/events/gt2004/bios.html#torsten">GT2004 presentation by Torsten
@@ -958,7 +958,7 @@
 <p>
           A set of symbols is available. See the demonstration
           in a fresh 'forrest seed' site (at samples/xml-entities.html).
-          For example, use "<span class="codefrag">&amp;myp-t;</span>" to represent the
+          For example, use "<span class="codefrag ">&amp;myp-t;</span>" to represent the
           project name together with trademark symbol
           "My Project Name&trade;".
           Avoid lengthy typing and potential spelling errors.
@@ -1005,7 +1005,7 @@
 <div style="margin-left: 15px">
 <p>To serve, for example a legacy HTML site, add something like the following 
         to your project's sitemap and place the source content at the
-        <span class="codefrag">src/documentation/content/xdocs/old_site/</span> directory.</p>
+        <span class="codefrag ">src/documentation/content/xdocs/old_site/</span> directory.</p>
 <pre class="code">
 &lt;map:match pattern="old_site/**.html"&gt;
  &lt;map:select type="exists"&gt;
@@ -1071,8 +1071,8 @@
 <a href="#proxy_config-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p>You can configure the proxy in the <span class="codefrag">forrest.properties</span> file. Set the
-            <span class="codefrag">proxy.host</span> and <span class="codefrag">proxy.port</span> accordingly (the port will default
+<p>You can configure the proxy in the <span class="codefrag ">forrest.properties</span> file. Set the
+            <span class="codefrag ">proxy.host</span> and <span class="codefrag ">proxy.port</span> accordingly (the port will default
           to port 80).</p>
 </div>
 <a name="N102B8"></a><a name="CVS_revison_tags"></a>
@@ -1081,7 +1081,7 @@
 <a href="#CVS_revison_tags-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p>If you have:<span class="codefrag">&lt;version&gt;$Revision: 1.30
+<p>If you have:<span class="codefrag ">&lt;version&gt;$Revision: 1.30
           $&lt;/version&gt;</span>The '1.30' will be extracted and
           displayed at the bottom of the page as "version 1.30". See for example the
           bottom of the <a href="../docs_0_80/your-project.html"> Using Forrest</a> document.</p>
@@ -1097,13 +1097,13 @@
 <div style="margin-left: 15px">
 <p> Forrest uses a configuration file to control the processing done by the Apache Cocoon
           command-line called cli.xconf </p>
-<p> Your project can supply its own <span class="codefrag">cli.xconf</span> and define patterns for URIs to
+<p> Your project can supply its own <span class="codefrag ">cli.xconf</span> and define patterns for URIs to
           exclude. There are also other powerful configuration features. </p>
-<p> This means creating a directory <span class="codefrag">src/documentation/conf</span> (or wherever
-            <span class="codefrag">${forrest.conf-dir}</span> points) and copying
-            <span class="codefrag">$FORREST_HOME/main/webapp/WEB-INF/cli.xconf</span> to it. Declare the location of
+<p> This means creating a directory <span class="codefrag ">src/documentation/conf</span> (or wherever
+            <span class="codefrag ">${forrest.conf-dir}</span> points) and copying
+            <span class="codefrag ">$FORREST_HOME/main/webapp/WEB-INF/cli.xconf</span> to it. Declare the location of
           this file in the forrest.properties configuration, e.g.
-            <span class="codefrag">project.configfile=${project.home}/src/documentation/conf/cli.xconf</span>
+            <span class="codefrag ">project.configfile=${project.home}/src/documentation/conf/cli.xconf</span>
         
 </p>
 <p> Then edit cli.xconf, and add any exclude sections that you require. The default
@@ -1122,7 +1122,7 @@
 <div class="note">
 <div class="label">Note</div>
 <div class="content"> Wildcards may be used. These are a powerful feature of Cocoon's <a href="../docs_0_80/sitemap-ref.html">sitemap</a>. For example, <strong>foo/*</strong> would match
-            <span class="codefrag">foo/bar</span>, but not <span class="codefrag">foo/bar/baz</span> &mdash; use
+            <span class="codefrag ">foo/bar</span>, but not <span class="codefrag ">foo/bar/baz</span> &mdash; use
           <strong>foo/**</strong> to match that. </div>
 </div>
 </div>
@@ -1134,7 +1134,7 @@
 </div>
 <div style="margin-left: 15px">
 <p> This can be done by overriding the <a href="#cli-xconf">
-            <span class="codefrag">cli.xconf</span>
+            <span class="codefrag ">cli.xconf</span>
           </a> Cocoon config file, and defining patterns for URLs to exclude. </p>
 </div>
 <a name="N10316"></a><a name="claimed_patterns"></a>
@@ -1144,7 +1144,7 @@
 </div>
 <div style="margin-left: 15px">
 <p> Certain patterns are claimed by the default sitemaps for special processing. These
-          include: <span class="codefrag">site, changes, todo, faq, images, my-images, skinconf, community,
+          include: <span class="codefrag ">site, changes, todo, faq, images, my-images, skinconf, community,
           howto</span>
         
 </p>
@@ -1194,8 +1194,8 @@
 </div>
 <div style="margin-left: 15px">
 <p> If you are using JDK 1.4.0 or newer, you can enable <em>headless</em> operation by
-          running Forrest with the <span class="codefrag">forrest.jvmarg</span> parameter set to
-            <span class="codefrag">-Djava.awt.headless=true</span>, like this: </p>
+          running Forrest with the <span class="codefrag ">forrest.jvmarg</span> parameter set to
+            <span class="codefrag ">-Djava.awt.headless=true</span>, like this: </p>
 <pre class="code">forrest -Dforrest.jvmargs=-Djava.awt.headless=true site</pre>
 <p> See also <a href="http://cocoon.apache.org/2.1/faq/faq-configure-environment.html">Cocoon FAQ</a>. </p>
 </div>
@@ -1210,11 +1210,11 @@
 <p>
           In a 'forrest seed site' the project and the group logo are generated from a
           Scalable Vector Graphics (SVG) file, using the text from the
-          <span class="codefrag">&lt;project-name&gt;</span> and
-          <span class="codefrag">&lt;group-name&gt;</span> elements of the <span class="codefrag">skinconf.xml</span> file.
+          <span class="codefrag ">&lt;project-name&gt;</span> and
+          <span class="codefrag ">&lt;group-name&gt;</span> elements of the <span class="codefrag ">skinconf.xml</span> file.
           If you have a long project-name then you may need to adjust the width of the image.
           Perhaps you want to change the colours too. Edit the file at
-          <span class="codefrag">src/documentation/content/xdocs/images/project.svg</span> and adjust the "width"
+          <span class="codefrag ">src/documentation/content/xdocs/images/project.svg</span> and adjust the "width"
           attribute of the &lt;svg&gt; element. For further details see
           <a href="http://www.w3.org/Graphics/SVG/">SVG</a> resources.
         </p>
@@ -1295,7 +1295,7 @@
 <a href="#breadcrumbs-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p>Breadcrumbs begin with up to three URLs specified in <span class="codefrag">skinconf.xml</span>. Here is
+<p>Breadcrumbs begin with up to three URLs specified in <span class="codefrag ">skinconf.xml</span>. Here is
           what the Forrest site uses:</p>
 <pre class="code">
   &lt;trail&gt;
@@ -1306,7 +1306,7 @@
 <p>If any links are blank, they are not used. After these first links, JavaScript looks at
           the URL for the current page and makes a link for each directory after the domain. If you
           are viewing the site locally, there is no domain and so there will be no extra
-          breadcrumbs, only the ones that are specified in <span class="codefrag">skinconf.xml</span>. </p>
+          breadcrumbs, only the ones that are specified in <span class="codefrag ">skinconf.xml</span>. </p>
 </div>
 <a name="N103EB"></a><a name="run_port"></a>
 <h4 class="faq">3.13. How do I make forrest run listen on a different port?</h4>
@@ -1316,11 +1316,11 @@
 <div style="margin-left: 15px">
 <p>
           
-<span class="codefrag">forrest run -Dforrest.jvmargs="-Djetty.port=80"</span>
+<span class="codefrag ">forrest run -Dforrest.jvmargs="-Djetty.port=80"</span>
         
 </p>
 <p>Or copy Forrest's main/webapp/jettyconf.xml file to your project's src/documentation
-          directory and set the port number in that file. Then do <span class="codefrag">forrest run</span>
+          directory and set the port number in that file. Then do <span class="codefrag ">forrest run</span>
         
 </p>
 </div>
@@ -1332,8 +1332,8 @@
 <div style="margin-left: 15px">
 <p>If you use an IDE like Eclipse and want to debug java code in Forrest
         you need to start Forrest with debugging mode turned on. To do this you need
-        to add <span class="codefrag">-Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,susp end=n</span>
-        to the <span class="codefrag">forrest.jvmargs</span> property in the <span class="codefrag">forrest.properties</span>
+        to add <span class="codefrag ">-Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,susp end=n</span>
+        to the <span class="codefrag ">forrest.jvmargs</span> property in the <span class="codefrag ">forrest.properties</span>
         file. Don't forget to ensure the property is uncommented in that file.</p>
 </div>
 <a name="N10410"></a><a name="old_faqs"></a>
@@ -1345,7 +1345,7 @@
 </div>
 <div style="margin-left: 15px">
 <p> Certain patterns are claimed by the default sitemaps for special processing. These
-          include: <span class="codefrag">site, changes, todo, faq, images, my-images, skinconf, community,
+          include: <span class="codefrag ">site, changes, todo, faq, images, my-images, skinconf, community,
           howto</span>
         
 </p>
@@ -1362,12 +1362,12 @@
 <a href="#generating_menus-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p> One <span class="codefrag">site.xml</span> file in your project root can replace all the book.xml files (one per
-          directory) in your site. Internally, Forrest uses <span class="codefrag">site.xml</span> to dynamically generate book.xml
+<p> One <span class="codefrag ">site.xml</span> file in your project root can replace all the book.xml files (one per
+          directory) in your site. Internally, Forrest uses <span class="codefrag ">site.xml</span> to dynamically generate book.xml
           files. However, Forrest first checks for the existence of a book.xml file, so
           backwards-compatibility is preserved. If a directory has a book.xml file, the book.xml
           will be used to generate the menu. This supplement is useful in situations where
-          <span class="codefrag">site.xml</span>-generated menus aren't appropriate. See <a href="../docs_0_80/linking.html">Menus and
+          <span class="codefrag ">site.xml</span>-generated menus aren't appropriate. See <a href="../docs_0_80/linking.html">Menus and
             Linking</a>. </p>
 </div>
 <a name="N10445"></a><a name="docbook"></a>
@@ -1376,7 +1376,7 @@
 <a href="#docbook-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p> There are two ways. Forrest has a <span class="codefrag">simplifiedDocbook</span> plugin which can
+<p> There are two ways. Forrest has a <span class="codefrag ">simplifiedDocbook</span> plugin which can
           transform the DocBook format into the Forrest "xdocs" format on-the-fly and then render
           that as normal Forrest documents. Be aware that the stylesheet that does this
           transformation is deliberately very limited and does not attempt to deal with all DocBook
@@ -1407,7 +1407,7 @@
         in the components section of the sitemap. See the 
         <a href="http://cocoon.apache.org/2.1/userdocs/serializers/xhtml-serializer.html">Cocoon
         docs</a> for the elements you need to add to define this component. You can see examples 
-        of other components being added in the <span class="codefrag">FORREST_HOME/main/webapp/sitemap.xmap</span> file.</p>
+        of other components being added in the <span class="codefrag ">FORREST_HOME/main/webapp/sitemap.xmap</span> file.</p>
 <p> You can also use a mixture of the two methods, some handled automatically by Forrest and
           some directly using DocBook stylesheets. You can also have a mixture of source files as
           "document-v*" DTD and DocBook. </p>
@@ -1423,10 +1423,10 @@
 <a href="#version-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p> Do <span class="codefrag">'forrest -projecthelp'</span> or <span class="codefrag">'./build.sh'</span> to find the version
+<p> Do <span class="codefrag ">'forrest -projecthelp'</span> or <span class="codefrag ">'./build.sh'</span> to find the version
           number. </p>
 <p> To list the properties, add "forrest.echo=true" to your forrest.properties file and
-          watch the build messages. Doing <span class="codefrag">'forrest -v'</span> will provide verbose build
+          watch the build messages. Doing <span class="codefrag ">'forrest -v'</span> will provide verbose build
           messages. </p>
 </div>
 <a name="N10487"></a><a name="logs"></a>
@@ -1435,17 +1435,17 @@
 <a href="#logs-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p> The logfiles are at <span class="codefrag">build/webapp/WEB-INF/logs/</span>
+<p> The logfiles are at <span class="codefrag ">build/webapp/WEB-INF/logs/</span>
         
 </p>
-<p> The log level can be raised with the <span class="codefrag">logkit.xconf</span> configuration. If you are
+<p> The log level can be raised with the <span class="codefrag ">logkit.xconf</span> configuration. If you are
           using Forrest in the interactive webapp mode (which is generally easiest for debugging
-          errors) then see the <span class="codefrag">main/webapp/WEB-INF/logkit.xconf</span> file. If you are
+          errors) then see the <span class="codefrag ">main/webapp/WEB-INF/logkit.xconf</span> file. If you are
           generating a static site (with command-line 'forrest') then copy
-            <span class="codefrag">$FORREST_HOME/main/webapp/WEB-INF/logkit.xconf</span> to your project at
-            <span class="codefrag">src/documentation/conf/logkit.xconf</span> and modify it. See more
+            <span class="codefrag ">$FORREST_HOME/main/webapp/WEB-INF/logkit.xconf</span> to your project at
+            <span class="codefrag ">src/documentation/conf/logkit.xconf</span> and modify it. See more
           information and efficiency tips with <a href="http://wiki.apache.org/cocoon/ExploringTheLogs">Cocoon logging</a>. </p>
-<p> Doing <span class="codefrag">'forrest -v'</span> will provide verbose build messages to the standard
+<p> Doing <span class="codefrag ">'forrest -v'</span> will provide verbose build messages to the standard
           output. </p>
 </div>
 <a name="N104AB"></a><a name="how_can_I_help"></a>

Modified: forrest/site/docs_0_80/forrest-contract.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/forrest-contract.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_80/forrest-contract.html (original)
+++ forrest/site/docs_0_80/forrest-contract.html Mon Dec  5 20:55:03 2005
@@ -360,10 +360,10 @@
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-      Some terminology will assist: <span class="codefrag">{docroot}</span> is the location
+      Some terminology will assist: <span class="codefrag ">{docroot}</span> is the location
       inside TheProject's file hierarchy where all documentation related
-      resources are stored. Usually <span class="codefrag">{docroot}</span> equals to
-      <span class="codefrag">{projecthome}/src/documentation</span>
+      resources are stored. Usually <span class="codefrag ">{docroot}</span> equals to
+      <span class="codefrag ">{projecthome}/src/documentation</span>
     
 </div>
 </div> 
@@ -396,17 +396,17 @@
 <p>Provide content and configuration ...</p>
 <ul> 
         
-<li>Provide XML content in <span class="codefrag">{docroot}/content/xdocs</span>
+<li>Provide XML content in <span class="codefrag ">{docroot}/content/xdocs</span>
           according to the Forrest DTDs or one of the other input formats.
         </li> 
         
 <li>Provide navigation metadata using the configuration files
-          <span class="codefrag">site.xml</span> and <span class="codefrag">tabs.xml</span>
+          <span class="codefrag ">site.xml</span> and <span class="codefrag ">tabs.xml</span>
         
 </li>
         
 <li>Provide the skin configuation file in
-          <span class="codefrag">{projecthome}/skinconf.xml</span>
+          <span class="codefrag ">{docroot}/skinconf.xml</span>
         
 </li>
       
@@ -421,13 +421,13 @@
 <ul> 
         
 <li>Provide its own skin in
-          <span class="codefrag">{docroot}/skins/{your-skin-name}</span> (Check the current
+          <span class="codefrag ">{docroot}/skins/{your-skin-name}</span> (Check the current
           Forrest skins and the related pipelines to see what they are doing.
           Bear in mind that the provided skins are able to be configured and
           may already meet your needs.)</li> 
         
 <li>Provide own DTDs to handle other specialised document types in
-          <span class="codefrag">{docroot}/resources/schema/dtd</span> 
+          <span class="codefrag ">{docroot}/resources/schema/dtd</span> 
           
 <ul> 
             
@@ -435,7 +435,7 @@
               intermediate 'document' structure.</li> 
             
 <li>and declare those extra DTDs in
-              <span class="codefrag">{docroot}/resources/schema/catalog.xcat</span>
+              <span class="codefrag ">{docroot}/resources/schema/catalog.xcat</span>
 </li> 
           
 </ul>
@@ -443,7 +443,7 @@
 </li> 
         
 <li>Provide its own overwriting versions of sitemaps
-          (<span class="codefrag">{docroot}/sitemap.xmap</span> and other *.xmap files)
+          (<span class="codefrag ">{docroot}/sitemap.xmap</span> and other *.xmap files)
           ... (be sure you know what you are doing since you are then leaving
           the area where other Forresters can help you out.
         </li> 

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

Modified: forrest/site/docs_0_80/howto/cvs-ssh/howto-cvs-ssh.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/cvs-ssh/howto-cvs-ssh.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/cvs-ssh/howto-cvs-ssh.html (original)
+++ forrest/site/docs_0_80/howto/cvs-ssh/howto-cvs-ssh.html Mon Dec  5 20:55:03 2005
@@ -257,7 +257,7 @@
 <div class="label">Note</div>
 <div class="content">This step is necessary only for Windows users. Linux users can happily skip this section and pass to <a href="#ssh_access">Setting up SSH access</a> section</div>
 </div>
-<p>If you are a domain user then you should be added to Cygwin users list (See <span class="codefrag">[cygwin-dir]/etc/passwd</span>). 
+<p>If you are a domain user then you should be added to Cygwin users list (See <span class="codefrag ">[cygwin-dir]/etc/passwd</span>). 
             </p>
 <ul>
               
@@ -305,7 +305,7 @@
     </p>
 <div class="warning">
 <div class="label">Warning</div>
-<div class="content">Having an empty passphrase isn't recommended for security reasons. See <span class="codefrag">ssh-agent</span> documentation on how to configure automatic passphrase retaining.</div>
+<div class="content">Having an empty passphrase isn't recommended for security reasons. See <span class="codefrag ">ssh-agent</span> documentation on how to configure automatic passphrase retaining.</div>
 </div>
 <a name="N100B2"></a><a name="Setting+up+passphrase+access"></a>
 <h3 class="underlined_5">Setting up passphrase access</h3>
@@ -332,7 +332,7 @@
             </pre>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">If this command doesn't work then it can mean that you have an old version of SSH. In this case try <span class="codefrag">ssh -l userxxx cvs.apache.org</span>. Run <span class="codefrag">ssh --help</span> to get all available options.</div>
+<div class="content">If this command doesn't work then it can mean that you have an old version of SSH. In this case try <span class="codefrag ">ssh -l userxxx cvs.apache.org</span>. Run <span class="codefrag ">ssh --help</span> to get all available options.</div>
 </div>
 <p>
             If now you are logged in to the to the CVS machine without entering the password then everything's Ok.
@@ -351,10 +351,10 @@
                 
 <li>Add ssh.exe directory to your system PATH environment variable. Say: <br>
                 
-<span class="codefrag">C:\&gt;set PATH=%PATH%;C:\cygwin\bin</span>
+<span class="codefrag ">C:\&gt;set PATH=%PATH%;C:\cygwin\bin</span>
 </li>
                 
-<li>Add <span class="codefrag">CVS_RSH=ssh</span> environment variable</li>
+<li>Add <span class="codefrag ">CVS_RSH=ssh</span> environment variable</li>
             
 </ul>
 <p>
@@ -369,7 +369,7 @@
 </li>
                 
 <li>In the dialog that comes up: <br>
-                Set the CVSROOT to <span class="codefrag">userxxx@cvs.apache.org:/home/cvs</span>
+                Set the CVSROOT to <span class="codefrag ">userxxx@cvs.apache.org:/home/cvs</span>
 </li>
                 
 <li>Set the Authentication to SSH Server</li>                

Modified: forrest/site/docs_0_80/howto/forrest.xmap.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/forrest.xmap.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/forrest.xmap.html (original)
+++ forrest/site/docs_0_80/howto/forrest.xmap.html Mon Dec  5 20:55:03 2005
@@ -253,7 +253,7 @@
 <div id="minitoc-area">
 <ul class="minitoc">
 <li>
-<a href="#sitemap.xmap">sitemap.xmap</a>
+<a href="#forrest.xmap">forrest.xmap</a>
 <ul class="minitoc">
 <li>
 <a href="#Definition+of+File-Resolver-Resource">Definition of File-Resolver-Resource</a>
@@ -265,8 +265,8 @@
 </li>
 </ul>
 </div>
-<a name="N10010"></a><a name="sitemap.xmap"></a>
-<h2 class="underlined_10">sitemap.xmap</h2>
+<a name="N10010"></a><a name="forrest.xmap"></a>
+<h2 class="underlined_10">forrest.xmap</h2>
 <div class="section">
 <pre>
 &lt;?xml version="1.0"?&gt;

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

Modified: forrest/site/docs_0_80/howto/howto-asf-mirror.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-asf-mirror.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-asf-mirror.html (original)
+++ forrest/site/docs_0_80/howto/howto-asf-mirror.html Mon Dec  5 20:55:03 2005
@@ -419,10 +419,10 @@
 <h3 class="underlined_5">Add the mirrors.cgi as a raw file</h3>
 <p>As explained in the mirrors document, there will be a two-line CGI
       wrapper script at the top-level of your website called
-      <span class="codefrag">mirrors.cgi</span>
+      <span class="codefrag ">mirrors.cgi</span>
 </p>
 <p>Utilising the Forrest concept of raw un-processed content,
-       add the file as <span class="codefrag">src/documentation/mirrors.cgi</span>
+       add the file as <span class="codefrag ">src/documentation/mirrors.cgi</span>
        (copy the Forrest project's
         <a href="http://svn.apache.org/repos/asf/forrest/trunk/site-author/content/mirrors.cgi">mirrors.cgi</a>)
       </p>
@@ -434,7 +434,7 @@
         script to add the list of mirrors and select the closest.
       </p>
 <p>
-        Add the file as <span class="codefrag">src/documentation/xdocs/mirrors.html</span>
+        Add the file as <span class="codefrag ">src/documentation/xdocs/mirrors.html</span>
         (Use the Forrest project's
         <a href="http://svn.apache.org/repos/asf/forrest/trunk/site-author/content/xdocs/mirrors.html">mirrors.html</a>
         as a template and edit it to suit.)
@@ -465,8 +465,8 @@
         (<a href="http://cocoon.apache.org/2.1/userdocs/offline/">CLI</a>)
         to the rescue. Add an entry to your project's cli.xconf by copying the
         default one from
-        <span class="codefrag">$FORREST_HOME/main/webapp/WEB-INF/cli.xconf</span> to your
-        <span class="codefrag">src/documentation/conf/</span> directory (or wherever
+        <span class="codefrag ">$FORREST_HOME/main/webapp/WEB-INF/cli.xconf</span> to your
+        <span class="codefrag ">src/documentation/conf/</span> directory (or wherever
         ${forrest.conf-dir} points). Add the following entry ...
       </p>
 <pre class="code">
@@ -477,7 +477,7 @@
 <h3 class="underlined_5">Run 'forrest' to build your site</h3>
 <p>
         That is all that you need to do, Forrest will take care of it from
-        there. Run the '<span class="codefrag">forrest</span>' command. The mirrors.html page
+        there. Run the '<span class="codefrag ">forrest</span>' command. The mirrors.html page
         will be generated with the skin applied.
       </p>
 <div class="note">

Modified: forrest/site/docs_0_80/howto/howto-buildPlugin.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-buildPlugin.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-buildPlugin.html (original)
+++ forrest/site/docs_0_80/howto/howto-buildPlugin.html Mon Dec  5 20:55:03 2005
@@ -502,7 +502,7 @@
         to automate some steps in the process. Since ant
         is distributed as part of Forrest, all you need to do
         is add the ant executable directory to your system path. The
-        name of this directory is <span class="codefrag">tools/ant/bin</span>
+        name of this directory is <span class="codefrag ">tools/ant/bin</span>
         in your Forrest program directory.
         (Alternatively you can prefix all calls to ant in
         the following instructions with the full path of the ant binary directory.)
@@ -521,7 +521,7 @@
       structure is almost identical, as are most of the required
       configuration files. In this How-To we will assume that you are creating a 
       plugin in the Forrest source tree. All plugins are developed in the
-      <span class="codefrag">forrest/plugins</span> directory.</p>
+      <span class="codefrag ">forrest/plugins</span> directory.</p>
 <p class="instruction">Run the following set of commands:</p>
 <pre class="code">
       cd [path_to_forrest]/plugins
@@ -541,7 +541,7 @@
 <div class="note">
 <div class="label">Note</div>
 <div class="content">If you plan on building your plugin elsewhere you can copy the
-      <span class="codefrag">build.xml</span> build file to your own plugin work directory and 
+      <span class="codefrag ">build.xml</span> build file to your own plugin work directory and 
       use it there.</div>
 </div>
 <p>See 
@@ -558,7 +558,7 @@
 <h5>status.xml</h5>
 <p>This file is used to track changes to the plugin
           project and to manage lists of things that still need to be done.
-          At this stage you should correct the <span class="codefrag">person</span> entry
+          At this stage you should correct the <span class="codefrag ">person</span> entry
           near the top of the file. It is also a good idea to add a few key
           milestones in the task list towards the bottom of the file.</p>
 <p>As you work on the plugin you should record all major changes in
@@ -583,9 +583,9 @@
 <a name="N100D6"></a><a name="componentConfig"></a>
 <h5>Component Configuration</h5>
 <p>If your plugin needs to provide additional Cocoon configuration
-          in the form of an <span class="codefrag">xconf</span>, or if some of the components
+          in the form of an <span class="codefrag ">xconf</span>, or if some of the components
           you are using need a configuration file (such as a JTidy config)
-          you should place them in a <span class="codefrag">conf</span> directory in the root
+          you should place them in a <span class="codefrag ">conf</span> directory in the root
           of your plugin.</p>
 <a name="N100E6"></a><a name="hosted"></a>
 <h5>Style notes for plugins hosted at forrest.apache.org</h5>
@@ -597,18 +597,18 @@
           </p>
 <a name="N100F2"></a><a name="edit-sitemap"></a>
 <h3 class="underlined_5">Edit the Plugin sitemap file(s)</h3>
-<p>The plugin <span class="codefrag">xmap</span> file is a Cocoon sitemap that is mounted
+<p>The plugin <span class="codefrag ">xmap</span> file is a Cocoon sitemap that is mounted
       at a strategic place in the Forrest pipeline. It is in this file
       that you will instruct Forrest how to operate. An input plugin
-      must provide a <span class="codefrag">input.xmap</span> file, an output plugin
-      must provide a <span class="codefrag">output.xmap</span> file, whilst an internal
-      plugin provides a <span class="codefrag">internal.xmap</span> file. In addition, an
-      input plugin may provide a <span class="codefrag">resources.xmap</span> file to
+      must provide a <span class="codefrag ">input.xmap</span> file, an output plugin
+      must provide a <span class="codefrag ">output.xmap</span> file, whilst an internal
+      plugin provides a <span class="codefrag ">internal.xmap</span> file. In addition, an
+      input plugin may provide a <span class="codefrag ">resources.xmap</span> file to
       allow the plugin to handle items such as JavaScript files.</p>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">All input plugins should allow the original source to be retrieved
-      by requesting the document with a <span class="codefrag">*.source.xml</span> extension. So
+      by requesting the document with a <span class="codefrag ">*.source.xml</span> extension. So
       you should ensure that you provide such a match.</div>
 </div>
 <p>It is beyond the scope of this How-To to give details about how to 
@@ -625,14 +625,14 @@
 <p>If your plugin uses any components (i.e. generators, transformers or
         serializers), actions or resources they must
         be defined in either the xmap for this plugin or one of its parents. The parents
-        of an <span class="codefrag">input.xmap</span> are <span class="codefrag">sitemap.xmap</span> and
-        <span class="codefrag">forrest.xmap</span>, whilst the parent of both 
-        <span class="codefrag">output.xmap</span> and <span class="codefrag">internal.xmap</span> are 
-        <span class="codefrag">sitemap.xmap</span>
+        of an <span class="codefrag ">input.xmap</span> are <span class="codefrag ">sitemap.xmap</span> and
+        <span class="codefrag ">forrest.xmap</span>, whilst the parent of both 
+        <span class="codefrag ">output.xmap</span> and <span class="codefrag ">internal.xmap</span> are 
+        <span class="codefrag ">sitemap.xmap</span>
 </p>
 <p>If you want to use the realpath where the sitemap.xmap of your plugin 
         resides then you need to use 
-        <span class="codefrag">{forrest:plugins}/PLUGIN_NAME</span> instead of <span class="codefrag">{realpath:/}</span>.
+        <span class="codefrag ">{forrest:plugins}/PLUGIN_NAME</span> instead of <span class="codefrag ">{realpath:/}</span>.
         </p>
 <p>See the examples below for more details.</p>
 <a name="N10147"></a><a name="resources"></a>
@@ -646,9 +646,9 @@
 <p>Plugin documentation should provide (as a minimum) an
       index page that provides an overview and a set of samples that demonstrate
       the functionality of the plugin. Typically these samples will be
-      provided in a <span class="codefrag">samples</span> subdirectory in the plugin 
-      documentation and will be referenced from both <span class="codefrag">site.xml</span>
-      and <span class="codefrag">tabs.xml</span> configuration files.</p>
+      provided in a <span class="codefrag ">samples</span> subdirectory in the plugin 
+      documentation and will be referenced from both <span class="codefrag ">site.xml</span>
+      and <span class="codefrag ">tabs.xml</span> configuration files.</p>
 <p>Try to provide a sample for all the major functions of your plugin
       and document any configuration that is available.</p>
 <a name="N10168"></a><a name="test"></a>
@@ -656,21 +656,21 @@
 <p>Since your documentation for the plugin illustrates all of its 
       functionality, you can use that site for testing the plugin. However, you
       must first deploy in your local install of Forrest. Each plugin contains
-      a buildfile that includes a <span class="codefrag">test</span> target. This target, by
+      a buildfile that includes a <span class="codefrag ">test</span> target. This target, by
       default, builds the documentation for your plugin.</p>
-<p class="instruction">Run the command <span class="codefrag">ant test</span> in
+<p class="instruction">Run the command <span class="codefrag ">ant test</span> in
       the plugins directory.</p>
 <p>Of course, the build should complete without errors.</p>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">You can also use <span class="codefrag">forrest run</span> to interactively examine
+<div class="content">You can also use <span class="codefrag ">forrest run</span> to interactively examine
       your documentation (point your browser at 
       <a href="http://localhost:8888">http://localhost:8888</a>).</div>
 </div>
 <p>It is also a really good idea to build proper tests for your 
       plugins using a suitable testing framework, for example, 
       <a href="http://webtest.canoo.com/">WebTest</a>. We recommend that you
-      extend the <span class="codefrag">test</span> target in your plugins build file because
+      extend the <span class="codefrag ">test</span> target in your plugins build file because
       this target is also used when performing integration tests on Forrest.
       In addition, we recommend that you use the samples in your documentation 
       for your tests, this way you are documenting your plugin at the same time 
@@ -681,7 +681,7 @@
 <h4>Testing During Development</h4>
 <p>In the current plugin system plugins are not used from their
         src directories, they must first be deployed locally. To do this
-        run the command <span class="codefrag">ant local-deploy</span>.</p>
+        run the command <span class="codefrag ">ant local-deploy</span>.</p>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">The test target will do this deployment automatically for you.
@@ -690,7 +690,7 @@
 </div>
 <p>In most cases you can locally deploy a plugin without having to 
         restart Forrest. However, if your plugin changes any configuration
-        files in the <span class="codefrag">conf</span> directory you will, most likely, have 
+        files in the <span class="codefrag ">conf</span> directory you will, most likely, have 
         to restart Forrest to see these changes.</p>
 <a name="N101AC"></a><a name="release"></a>
 <h3 class="underlined_5">Releasing a Plugin</h3>
@@ -705,28 +705,28 @@
 <h4>Deploying the Plugin</h4>
 <p>To deploy the plugin so that others can use it, it must be made 
         available as a zip from the URL indicated in the 
-        <span class="codefrag">plugins.xml</span> file. The plugins build file provides targets 
+        <span class="codefrag ">plugins.xml</span> file. The plugins build file provides targets 
         to assist with this task.</p>
 <p class="instruction">To deploy a plugin simply run the command
-        <span class="codefrag">ant deploy</span> from within the plugin directory.</p>
+        <span class="codefrag ">ant deploy</span> from within the plugin directory.</p>
 <p>This command will, by default, deploy to the Apache Forrest web site.
         In order to do this you need commit access to Forrest. If you want to
         deploy your plugin to a different location you 
-        can build the zip of your plugin with <span class="codefrag">ant dist</span>
-        and then copy the zip file from <span class="codefrag">build/dist</span> to wherever
+        can build the zip of your plugin with <span class="codefrag ">ant dist</span>
+        and then copy the zip file from <span class="codefrag ">build/dist</span> to wherever
         you intend to host the plugin.</p>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">Running this command on any plugin will also deploy any
-        changes to the <span class="codefrag">plugins.xml</span> file. If you are deploying to
+        changes to the <span class="codefrag ">plugins.xml</span> file. If you are deploying to
         your own website you will have to request changes to the 
-        <span class="codefrag">plugins.xml</span> and ask the Forrest committers to publish the new
+        <span class="codefrag ">plugins.xml</span> and ask the Forrest committers to publish the new
         document.</div>
 </div>
 <div class="warning">
 <div class="label">Warning</div>
-<div class="content">Running the <span class="codefrag">deploy</span> or <span class="codefrag">dist</span> targets
-        will always run the <span class="codefrag">test</span> target first. This is to ensure
+<div class="content">Running the <span class="codefrag ">deploy</span> or <span class="codefrag ">dist</span> targets
+        will always run the <span class="codefrag ">test</span> target first. This is to ensure
         that you only deploy working plugins. This adds a little time to
         the deploy cycle, but we feel the peace of mind is worth it.</div>
 </div>
@@ -796,13 +796,13 @@
 <div class="note">
 <div class="label">Note</div>
 <div class="content">For an example of each of these features in use see the 
-      <span class="codefrag">org.apache.forrest.internal.NoteTaking</span> plugin.</div>
+      <span class="codefrag ">org.apache.forrest.internal.NoteTaking</span> plugin.</div>
 </div>
 <a name="N10236"></a><a name="Locationmap"></a>
 <h4>Locationmap</h4>
 <p>Plugins can use the Forrest locationmap to expose resources to your
         project and other plgins. To use this functionality add your 
-        <span class="codefrag">locationmap.xml</span> file to the root of the plugin directory.</p>
+        <span class="codefrag ">locationmap.xml</span> file to the root of the plugin directory.</p>
 <p>We have an <a href="http://issues.apache.org/jira/browse/FOR-200">issue</a>
         for the status of locationmap development.</p>
 <a name="N1024A"></a><a name="Dispatcher"></a>
@@ -812,9 +812,9 @@
         configurable system of defining the contents and look and feel of a site.</p>
 <p>Plugins can expose contracts for use in structurer files used within
         Dispatcher-based sites. In order to do this you should develop your contracts
-        as normal and place them in <span class="codefrag">PLUGIN_HOME/resources/themes</span>. However,
+        as normal and place them in <span class="codefrag ">PLUGIN_HOME/resources/themes</span>. However,
         this, by itself, is not sufficient to export your contracts. You will also need to
-        add the following match to your plugin's <span class="codefrag">locationmap.xml</span> file:</p>
+        add the following match to your plugin's <span class="codefrag ">locationmap.xml</span> file:</p>
 <pre class="code">
     &lt;match pattern="resolvePluginContract.*.**"&gt;
       &lt;select type="exists"&gt;
@@ -822,7 +822,7 @@
       &lt;/select&gt;
     &lt;/match&gt;
         </pre>
-<p>Of course, you should replace <span class="codefrag">PLUGIN_NAME</span> with the name of 
+<p>Of course, you should replace <span class="codefrag ">PLUGIN_NAME</span> with the name of 
         your plugin.</p>
 <p>Once Dispatcher becomes stable we will add this match to the default locationmap
         which is generated when you seed a new plugin, but for now it must be done manually.</p>

Modified: forrest/site/docs_0_80/howto/howto-corner-images.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-corner-images.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-corner-images.html (original)
+++ forrest/site/docs_0_80/howto/howto-corner-images.html Mon Dec  5 20:55:03 2005
@@ -407,7 +407,7 @@
       The procedure outlined below provides an understanding of how corner
       images are named (the contract) and then shows how to define new
       colors for these images by modifying the
-      <span class="codefrag">src/documentation/skinconf.xml</span> of a project.
+      <span class="codefrag ">src/documentation/skinconf.xml</span> of a project.
     </p>
 <a name="N10048"></a><a name="css-files"></a>
 <h3 class="underlined_5">Understand how corner images are named (the contract)</h3>
@@ -437,13 +437,13 @@
       </pre>
 <p>
         The first part
-        (<span class="codefrag">images/{$name}-{$v-orientation}-{$h-orientation}-{$size}</span>)
+        (<span class="codefrag ">images/{$name}-{$v-orientation}-{$h-orientation}-{$size}</span>)
         identifies which images is used and how big (width x height) it should
         be. The second part\
-        (<span class="codefrag">-1{$backgroundColor}-2{$strokeColor}-3{$foregroundColor}</span>)
+        (<span class="codefrag ">-1{$backgroundColor}-2{$strokeColor}-3{$foregroundColor}</span>)
         identifies the coloring of each portion of the image. The input
         parameter for the second part comes from the color profile of
-        <span class="codefrag">src/documentation/skinconf.xml</span>. The second part is
+        <span class="codefrag ">src/documentation/skinconf.xml</span>. The second part is
         easily identifiable through the numbering 1-2-3.
       </p>
 <p>
@@ -452,19 +452,19 @@
 <dl>
         
 <dt>
-<span class="codefrag">images</span>
+<span class="codefrag ">images</span>
 </dt>
         
 <dd>
           Path to the xslt that creates the corner.
           <br>
           
-<span class="codefrag">images/ = {$FORREST_HOME}/main/webapp/skins/common/images/</span>
+<span class="codefrag ">images/ = {$FORREST_HOME}/main/webapp/skins/common/images/</span>
         
 </dd>
         
 <dt>
-<span class="codefrag">{$name}</span>
+<span class="codefrag ">{$name}</span>
 </dt>
         
 <dd>
@@ -473,108 +473,108 @@
             
 <li>
               
-<span class="codefrag">rc.svg.xslt</span>: handles rounded corners
+<span class="codefrag ">rc.svg.xslt</span>: handles rounded corners
             </li>
             
 <li>
               
-<span class="codefrag">dc.svg.xslt</span>: handles diagonal 45-degree corners
+<span class="codefrag ">dc.svg.xslt</span>: handles diagonal 45-degree corners
             </li>
           
 </ul>
           
-<span class="codefrag">name = [rc|dc]</span>
+<span class="codefrag ">name = [rc|dc]</span>
           
 <br>
           
-<em>e.g.</em> <span class="codefrag">rc</span>
+<em>e.g.</em> <span class="codefrag ">rc</span>
         
 </dd>
         
 <dt>
-<span class="codefrag">{$v-orientation}</span>
+<span class="codefrag ">{$v-orientation}</span>
 </dt>
         
 <dd>
           Vertical orientation of the corner images (top or bottom).
           <br>
           
-<span class="codefrag">v-orientation = [t|b]</span>
+<span class="codefrag ">v-orientation = [t|b]</span>
           
 <br>
           
-<em>e.g.</em> <span class="codefrag">t</span>
+<em>e.g.</em> <span class="codefrag ">t</span>
         
 </dd>
         
 <dt>
-<span class="codefrag">{$h-orientation}</span>
+<span class="codefrag ">{$h-orientation}</span>
 </dt>
         
 <dd>
           Horizontal orientation of the corner images (left or right).
           <br>
           
-<span class="codefrag">h-orientation = [l|r]</span>
+<span class="codefrag ">h-orientation = [l|r]</span>
           
 <br>
           
-<em>e.g.</em> <span class="codefrag">r</span>
+<em>e.g.</em> <span class="codefrag ">r</span>
         
 </dd>
         
 <dt>
-<span class="codefrag">{$size}</span>
+<span class="codefrag ">{$size}</span>
 </dt>
         
 <dd>
           Pixels size of the width <strong>and</strong> height of the corner image.
           <br>
           
-<span class="codefrag">size=x</span>
+<span class="codefrag ">size=x</span>
           
 <br>
           
-<em>e.g.</em> <span class="codefrag">5</span>
+<em>e.g.</em> <span class="codefrag ">5</span>
         
 </dd>
         
 <dt>
-<span class="codefrag">{$backgroundColor}</span>
+<span class="codefrag ">{$backgroundColor}</span>
 </dt>
         
 <dd>
-          Any <span class="codefrag">&lt;color name=""/&gt;</span> element in the <span class="codefrag">skinconf.xml</span> (the <span class="codefrag">value="{$color}"</span>
+          Any <span class="codefrag ">&lt;color name=""/&gt;</span> element in the <span class="codefrag ">skinconf.xml</span> (the <span class="codefrag ">value="{$color}"</span>
           attribute will be applied).
           <br>
           
-<em>e.g.</em> <span class="codefrag">header</span>
+<em>e.g.</em> <span class="codefrag ">header</span>
         
 </dd>
         
 <dt>
-<span class="codefrag">{$strokeColor}</span>
+<span class="codefrag ">{$strokeColor}</span>
 </dt>
         
 <dd>
-          Any <span class="codefrag">&lt;color name=""/&gt;</span> element in the <span class="codefrag">skinconf.xml</span> (the <span class="codefrag">value="{$color}"</span>
+          Any <span class="codefrag ">&lt;color name=""/&gt;</span> element in the <span class="codefrag ">skinconf.xml</span> (the <span class="codefrag ">value="{$color}"</span>
           attribute will be applied).
           <br>
           
-<em>e.g.</em> <span class="codefrag">searchbox</span>
+<em>e.g.</em> <span class="codefrag ">searchbox</span>
         
 </dd>
         
 <dt>
-<span class="codefrag">{$foregroundColor}</span>
+<span class="codefrag ">{$foregroundColor}</span>
 </dt>
         
 <dd>
-          Any <span class="codefrag">&lt;color name=""/&gt;</span> element in the <span class="codefrag">skinconf.xml</span> (the <span class="codefrag">value="{$color}"</span>
+          Any <span class="codefrag ">&lt;color name=""/&gt;</span> element in the <span class="codefrag ">skinconf.xml</span> (the <span class="codefrag ">value="{$color}"</span>
           attribute will be applied).
           <br>
           
-<em>e.g.</em> <span class="codefrag">searchbox</span>
+<em>e.g.</em> <span class="codefrag ">searchbox</span>
         
 </dd>
       
@@ -582,12 +582,12 @@
 <a name="N10123"></a><a name="skinconfig"></a>
 <h3 class="underlined_5">Modifying the skinconf.xml of your project</h3>
 <p>
-        modifying the <span class="codefrag">skinconf.xml</span> of your project (by
-        default you find it at <span class="codefrag">[project-dir]/src/documentation/</span>).
+        modifying the <span class="codefrag ">skinconf.xml</span> of your project (by
+        default you find it at <span class="codefrag ">[project-dir]/src/documentation/</span>).
       </p>
 <p>
-        Starting about line 155 you find a <span class="codefrag">&lt;colors&gt;</span>
-        ... <span class="codefrag">&lt;/colors&gt;</span> element with content commented-out:
+        Starting about line 155 you find a <span class="codefrag ">&lt;colors&gt;</span>
+        ... <span class="codefrag ">&lt;/colors&gt;</span> element with content commented-out:
       </p>
 <pre class="code">
 &lt;colors&gt;
@@ -610,8 +610,8 @@
       </pre>
 <p>
         To modify the colors of the corner images, you can either define
-        your own <span class="codefrag">&lt;color name=.../&gt;</span> elements or uncomment
-        one of the existing <span class="codefrag">&lt;color name=.../&gt;</span> elements
+        your own <span class="codefrag ">&lt;color name=.../&gt;</span> elements or uncomment
+        one of the existing <span class="codefrag ">&lt;color name=.../&gt;</span> elements
         and adjust the color value to your needs.
       </p>
 <p>
@@ -623,10 +623,10 @@
 &lt;color name="tab-selected" value="#FF0000"/&gt;
       </pre>
 <p>
-        This affects all corner images whose <span class="codefrag">{$backgroundColor}</span>, <span class="codefrag">{$strokeColor}</span> or
-        <span class="codefrag">{$foregroundColor}</span> is set to <span class="codefrag">tab-selected</span>.
+        This affects all corner images whose <span class="codefrag ">{$backgroundColor}</span>, <span class="codefrag ">{$strokeColor}</span> or
+        <span class="codefrag ">{$foregroundColor}</span> is set to <span class="codefrag ">tab-selected</span>.
         <br>
-        For example, in <span class="codefrag">screen.css</span> (of the "pelt" skin) you find:
+        For example, in <span class="codefrag ">screen.css</span> (of the "pelt" skin) you find:
       </p>
 <pre class="code">
 #roundbottomsmall {
@@ -636,15 +636,15 @@
 }
       </pre>
 <p>
-        Now the stroke color (<span class="codefrag">-2tab-selected</span>) and the foreground
-        color (<span class="codefrag">-3tab-selected</span>) are set to red (remember: we
-        defined <span class="codefrag">#FF0000</span> as the "color" value of
-        <span class="codefrag">tab-selected</span>).
+        Now the stroke color (<span class="codefrag ">-2tab-selected</span>) and the foreground
+        color (<span class="codefrag ">-3tab-selected</span>) are set to red (remember: we
+        defined <span class="codefrag ">#FF0000</span> as the "color" value of
+        <span class="codefrag ">tab-selected</span>).
       </p>
 <a name="N1017A"></a><a name="css_modify"></a>
 <h3 class="underlined_5">Modifying .css files</h3>
 <p>
-        In addition to the modification of <span class="codefrag">skinconf.xml</span>
+        In addition to the modification of <span class="codefrag ">skinconf.xml</span>
         you can also modify the respective .css file of your skin.
       </p>
 <p>
@@ -671,7 +671,7 @@
       </pre>
 <p>
         Here we have created our own color tags (in the .css file) and
-        defined the respective values for them (in <span class="codefrag">skinconf.xml</span>). 
+        defined the respective values for them (in <span class="codefrag ">skinconf.xml</span>). 
         Now you have color images with a red background and a green
         foreground. Horrible, isn't it?
       </p>

Modified: forrest/site/docs_0_80/howto/howto-custom-html-source.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-custom-html-source.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-custom-html-source.html (original)
+++ forrest/site/docs_0_80/howto/howto-custom-html-source.html Mon Dec  5 20:55:03 2005
@@ -653,8 +653,8 @@
         current context and then assemble the actual expression(s) from it.
       </p>
 <p>In our example the matcher pattern
-       <span class="codefrag">**/*.html</span> is applied to the request-name
-       <span class="codefrag">mytest/mybad.html</span>, so we have three variables
+       <span class="codefrag ">**/*.html</span> is applied to the request-name
+       <span class="codefrag ">mytest/mybad.html</span>, so we have three variables
        altogether:
       </p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -753,8 +753,8 @@
       </p>
 <p>
         In our example the matcher pattern
-        <span class="codefrag">**body-*.html</span> is applied to the request-name
-        <span class="codefrag">mytest/body-mybad.html</span>.
+        <span class="codefrag ">**body-*.html</span> is applied to the request-name
+        <span class="codefrag ">mytest/body-mybad.html</span>.
         Which means that we have three variables altogether:
       </p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -856,7 +856,7 @@
         
 <li>
           
-<span class="codefrag">&lt;map:generate src="{project:content.xdocs}{uri}.html" type="html"/&gt;</span>
+<span class="codefrag ">&lt;map:generate src="{project:content.xdocs}{uri}.html" type="html"/&gt;</span>
 <br>
             Using the html-generator, Forrest reads the html-document
             from file and uses JTidy to clean up and convert it to xml
@@ -869,7 +869,7 @@
         
 <li>
             
-<span class="codefrag">&lt;map:transform src="{forrest:stylesheets}/html2document.xsl"/&gt;</span>
+<span class="codefrag ">&lt;map:transform src="{forrest:stylesheets}/html2document.xsl"/&gt;</span>
 <br>
           Using the standard stylesheet 'html2document.xsl', this XHTML is 
           transformed into Forrest standard document format.
@@ -877,14 +877,14 @@
         
 <li>
           
-<span class="codefrag">&lt;map:transform type="idgen"/&gt;</span>
+<span class="codefrag ">&lt;map:transform type="idgen"/&gt;</span>
 <br>
           This step generates IDs required for navigation within the page.
         </li>
         
 <li>
           
-<span class="codefrag">&lt;map:serialize type="xml-document"/&gt;</span>
+<span class="codefrag ">&lt;map:serialize type="xml-document"/&gt;</span>
 <br>
           Finally the document is serialized as XML and returned to the
           calling pipeline.
@@ -1097,7 +1097,9 @@
 &lt;map:pipeline&gt;
     &lt;map:match pattern="mytest/*.xml"&gt;
       &lt;map:generate src="{project:content.xdocs}{uri}.html" type="html" /&gt;
-      &lt;strong&gt;&lt;map:transform src="{forrest:stylesheets}/fixMyBadHTML.xsl"/&gt;&lt;/strong&gt;
+  <strong>
+      &lt;map:transform src="{project:resources.stylesheets}/fixMyBadHTML.xsl"/&gt;
+  </strong>
       &lt;map:transform src="{forrest:stylesheets}/html2document.xsl" /&gt;
       &lt;map:transform type="idgen" /&gt;
       &lt;map:serialize type="xml-document"/&gt;

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

Modified: forrest/site/docs_0_80/howto/howto-dev.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-dev.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-dev.html (original)
+++ forrest/site/docs_0_80/howto/howto-dev.html Mon Dec  5 20:55:03 2005
@@ -697,7 +697,7 @@
         </p>
 <p>
           Note that the profiler is not used by default. To switch
-         it on, edit <span class="codefrag">main/webapp/sitemap.xmap</span> and search
+         it on, edit <span class="codefrag ">main/webapp/sitemap.xmap</span> and search
          for "profiler". Follow the instructions there to replace the
           standard "map:pipe" components with the profiling pipes.
         </p>
@@ -715,7 +715,7 @@
         </p>
 <p>
           NOTE: Do not forget to turn off the profiler in 
-          <span class="codefrag">main/webapp/sitemap.xmap</span> when finished.
+          <span class="codefrag ">main/webapp/sitemap.xmap</span> when finished.
         </p>
 <a name="N10126"></a><a name="debug-logtransformer"></a>
 <h4>Using the Cocoon LogTransformer</h4>

Modified: forrest/site/docs_0_80/howto/howto-forrest-from-maven.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-forrest-from-maven.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-forrest-from-maven.html (original)
+++ forrest/site/docs_0_80/howto/howto-forrest-from-maven.html Mon Dec  5 20:55:03 2005
@@ -390,13 +390,13 @@
 <h2 class="underlined_10">Steps</h2>
 <div class="section">
 <p>The procedure outlined below describes how to add a goal to your
-    project's maven.xml that will invoke Forrest's <span class="codefrag">site</span>
+    project's maven.xml that will invoke Forrest's <span class="codefrag ">site</span>
     target.</p>
 <a name="N1003A"></a><a name="set-maven-home"></a>
 <h3 class="underlined_5">Set the FORREST_HOME environment variable</h3>
 <p>Make sure the FORREST_HOME environment variable points to your
       Forrest home directory (i.e. the directory that contains
-      <span class="codefrag">forrest.build.xml</span>) (e.g. C:\opt\apache-forrest-0.7)</p>
+      <span class="codefrag ">forrest.build.xml</span>) (e.g. C:\opt\apache-forrest-0.7)</p>
 <a name="N10047"></a><a name="define-ant-environment-prop"></a>
 <h3 class="underlined_5">Initialize an Ant environment property at the top of
       maven.xml</h3>
@@ -432,7 +432,7 @@
       it's not even necessary to have Ant 1.6 installed separately.</p>
 <a name="N10066"></a><a name="Alternative+file"></a>
 <h3 class="underlined_5">Alternative file</h3>
-<p>Under <span class="codefrag">$FORREST_HOME/tools/targets/maven.xml</span>
+<p>Under <span class="codefrag ">$FORREST_HOME/tools/targets/maven.xml</span>
 </p>
 </div>
 <a name="N10072"></a><a name="Feedback"></a>

Modified: forrest/site/docs_0_80/howto/howto-howto.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-howto.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-howto.html (original)
+++ forrest/site/docs_0_80/howto/howto-howto.html Mon Dec  5 20:55:03 2005
@@ -456,7 +456,7 @@
       
 <li>An understanding of the How-To document structure. Just use this
       template document and you will be safe.
-      Make sure you run '<span class="codefrag">forrest validate-xdocs</span>' before
+      Make sure you run '<span class="codefrag ">forrest validate-xdocs</span>' before
       contributing your document.</li>
     
 </ul>

Modified: forrest/site/docs_0_80/howto/howto-pdf-tab.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-pdf-tab.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-pdf-tab.html (original)
+++ forrest/site/docs_0_80/howto/howto-pdf-tab.html Mon Dec  5 20:55:03 2005
@@ -405,14 +405,14 @@
 <h2 class="underlined_10">Steps</h2>
 <div class="section">
 <p>The procedure outlined below will define a project
-      <span class="codefrag">sitemap.xmap</span> and create a new
-      <span class="codefrag">pdf-tab.xmap</span>.
+      <span class="codefrag ">sitemap.xmap</span> and create a new
+      <span class="codefrag ">pdf-tab.xmap</span>.
     </p>
 <a name="N1003D"></a><a name="sitemap"></a>
 <h3 class="underlined_5">Create your project's main sitemap.xmap</h3>
 <p>
       If you do not have already a sitemap then create a new empty one in your
-      <span class="codefrag">src/documentation</span> directory (or wherever
+      <span class="codefrag ">src/documentation</span> directory (or wherever
       ${project.sitemap-dir} points to).
     </p>
 <a name="N1004A"></a><a name="aggregator"></a>
@@ -444,7 +444,7 @@
 <a name="N10062"></a><a name="edit-aggregator"></a>
 <h3 class="underlined_5">Edit the file pdf-tab.xmap</h3>
 <p>
-      The <span class="codefrag">&lt;map:match pattern="*.xml"&gt;</span> element
+      The <span class="codefrag ">&lt;map:match pattern="*.xml"&gt;</span> element
       should look like the following:
     </p>
 <pre class="code">
@@ -482,7 +482,7 @@
 </div>
 <p>
       Add the following entry to your site.xml in the
-      <span class="codefrag">&lt;about&gt;</span> element
+      <span class="codefrag ">&lt;about&gt;</span> element
     </p>
 <pre class="code">... 
 &lt;whole_foosite href="pdf-tab.html" label="sub site" /&gt;
@@ -502,11 +502,11 @@
     </pre>
 <p>
       This allows you to link to it via a
-      <span class="codefrag">&lt;link href="site:whole_foosite"&gt;</span>
+      <span class="codefrag ">&lt;link href="site:whole_foosite"&gt;</span>
       reference. 
     </p>
 <p>Add to every element that should be included in the pdf-tab.pdf
-      the attribute <span class="codefrag">wholesite="true"</span>
+      the attribute <span class="codefrag ">wholesite="true"</span>
 </p>
 <pre class="code">
 &lt;sample-wiki label="Wiki page" href="wiki-sample.html"
@@ -516,8 +516,8 @@
 <div class="label">Note</div>
 <div class="content">This attribute will be inherited by all children of the element. 
 	 Do not use it in the parent element that contains the 
-	 <span class="codefrag">&lt;whole_foosite href="pdf-tab.html" label="pdf-tab" /&gt;</span> 
-	 as the child (will cause a <span class="codefrag">stack overflow</span> if you do)!!!
+	 <span class="codefrag ">&lt;whole_foosite href="pdf-tab.html" label="pdf-tab" /&gt;</span> 
+	 as the child (will cause a <span class="codefrag ">stack overflow</span> if you do)!!!
 	</div>
 </div>
 <a name="N100A8"></a><a name="explain"></a>
@@ -526,9 +526,9 @@
       Line 4 of our example
       <br>
       
-<span class="codefrag">&lt;map:parameter name="include" value="//*[@wholesite='true']"/&gt;</span>
+<span class="codefrag ">&lt;map:parameter name="include" value="//*[@wholesite='true']"/&gt;</span>
       looks at your site.xml and will match every element containing the
-      <span class="codefrag">wholesite="true"</span> attribute. For example, to use the "samples"
+      <span class="codefrag ">wholesite="true"</span> attribute. For example, to use the "samples"
       tab ...
     </p>
 <pre class="code">
@@ -540,8 +540,8 @@
     </pre>
 <p>
       It matches <strong>all</strong> of the elements that contain
-      <span class="codefrag">wholesite="true"</span>
-      (in our example <span class="codefrag">&lt;samples&gt;</span>
+      <span class="codefrag ">wholesite="true"</span>
+      (in our example <span class="codefrag ">&lt;samples&gt;</span>
       and its "children") for the content of the pdf file to be generated.
     </p>
 <pre class="code"> 
@@ -556,16 +556,16 @@
     </pre>
 <p>
       This example shows that you can as well exclude site(s) from the aggregation 
-      by using the <span class="codefrag">wholesite="false"</span> attribute. This attribute will be as well inherited 
+      by using the <span class="codefrag ">wholesite="false"</span> attribute. This attribute will be as well inherited 
       by all children of the element.
     </p>
 <p>
       Line 8 defines the title of the pdf file by taking the content
       of the project-name variable in
-      <span class="codefrag">skinconf.xml</span> and adding some funny text:
+      <span class="codefrag ">skinconf.xml</span> and adding some funny text:
       <br>
       
-<span class="codefrag">&lt;map:parameter name="title" value="{conf:project-name}: Still My Foo Site"/&gt;</span>
+<span class="codefrag ">&lt;map:parameter name="title" value="{conf:project-name}: Still My Foo Site"/&gt;</span>
     
 </p>
 </div>

Modified: forrest/site/docs_0_80/howto/howto-structurer-contracts.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-structurer-contracts.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-structurer-contracts.html (original)
+++ forrest/site/docs_0_80/howto/howto-structurer-contracts.html Mon Dec  5 20:55:03 2005
@@ -439,7 +439,7 @@
 <p>
       By working on the i18n integration for "pelt" we again encountered the reasons for using the dispatcher. ;-)
       The maintenance problem was to change the captions of the skin features (contracts) to enable
-      support for i18n. The case is that the <span class="codefrag">site2xhtml.xsl</span> has a lot of repeating code. 
+      support for i18n. The case is that the <span class="codefrag ">site2xhtml.xsl</span> has a lot of repeating code. 
     </p>
 <p>
       For example the "last-publish"-contract could be found 2 times in the code.  
@@ -491,7 +491,7 @@
 <h3 class="underlined_5">Explaining the blank forrest:contract</h3>
 <p>
         To start a new forrest:contract you can copy the 'blank.ft' from
-        <span class="codefrag">org.apache.forrest.plugin.output.themer/resources/themes/common/html/blank.ft</span>. 
+        <span class="codefrag ">org.apache.forrest.plugin.output.themer/resources/themes/common/html/blank.ft</span>. 
       </p>
 <p>
         The 'blank.ft' is a simple xml file with the following code which you can use to base new contracts 
@@ -529,8 +529,8 @@
 &lt;/forrest:contract&gt;
       </pre>
 <p>
-        The most important is the name of the contract <span class="codefrag">&lt;forrest:contract name="blank"/&gt;</span>. 
-        This name is the same as the file name of the contract (without file extension) <span class="codefrag">blank.ft</span>. 
+        The most important is the name of the contract <span class="codefrag ">&lt;forrest:contract name="blank"/&gt;</span>. 
+        This name is the same as the file name of the contract (without file extension) <span class="codefrag ">blank.ft</span>. 
       </p>
 <div class="note">
 <div class="label">Note</div>
@@ -539,7 +539,7 @@
       </div>
 </div>
 <p>
-        The <span class="codefrag">&lt;description/&gt;</span> tag needs to be filled in with some information
+        The <span class="codefrag ">&lt;description/&gt;</span> tag needs to be filled in with some information
         that is explaining the contract to the webdesigner. The better explained the more efficient
         for the webdesigner to pick the right contract.
       </p>
@@ -548,19 +548,19 @@
 &lt;/description&gt;
       </pre>
 <p>
-        In the <span class="codefrag">&lt;usage/&gt;</span> tag we have to explain how the designer can use 
+        In the <span class="codefrag ">&lt;usage/&gt;</span> tag we have to explain how the designer can use 
         the contract in his structurer.
       </p>
 <pre class="code">&lt;usage&gt;&lt;![CDATA[&lt;forrest:contract name="siteinfo-last-published-howto"/&gt;]]&gt;&lt;/usage&gt;
       </pre>
 <p>
         
-<span class="codefrag">&lt;forrest:template name="blank" body="false" head="false"&gt; </span> 
+<span class="codefrag ">&lt;forrest:template name="blank" body="false" head="false"&gt; </span> 
         That leads to the template attribute @body="true" and
         @head="false". In html a contract can add content to the &lt;body/&gt; or/and
         &lt;head/&gt; part of &lt;html/&gt;. These values need to be changed when adding an actual template.
         Besides this, a xsl-template needs to indicate this in the naming. A template that adds content to the 
-        html body needs to end with "<span class="codefrag">-body</span>"!!!
+        html body needs to end with "<span class="codefrag ">-body</span>"!!!
       </p>
 <div class="warning">
 <div class="label">Warning</div>
@@ -599,7 +599,7 @@
 </div>
 <p> 
         Now let us pick up the example we started with and create a "siteinfo-last-published-howto" contract.
-        Save the blank.ft to <span class="codefrag">{project.home}/src/documentation/resources/themes/common/html/siteinfo-last-published-howto.ft</span>.
+        Save the blank.ft to <span class="codefrag ">{project.home}/src/documentation/resources/themes/common/html/siteinfo-last-published-howto.ft</span>.
       </p>
 <p>
         Now the maintenance-optimized code (xpath="/html/body/*") was:
@@ -670,7 +670,7 @@
 <h3 class="underlined_5">Activating the contract</h3>
 <p>
         To see whether the new contract works we need to add it to our structurer.
-        The contract usage contains the contract-tag <span class="codefrag">&lt;forrest:contract name="siteinfo-last-published-howto"/&gt;</span>
+        The contract usage contains the contract-tag <span class="codefrag ">&lt;forrest:contract name="siteinfo-last-published-howto"/&gt;</span>
         Please see <a href="../../docs_0_80/howto/howto-structurer-dsl.html">Getting started with the "structurer"</a> for more details.
       </p>
 <div class="note">



Mime
View raw message