forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r354312 [5/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/ plugi...
Date Tue, 06 Dec 2005 04:57:22 GMT
Modified: forrest/site/docs_0_60/compliance.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/compliance.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_60/compliance.html (original)
+++ forrest/site/docs_0_60/compliance.html Mon Dec  5 20:55:03 2005
@@ -311,11 +311,11 @@
         unless the user has turned this off.
       </p>
 <p>
-        The "<span class="codefrag">crust</span>" skin (current forrest-0.6-dev)
+        The "<span class="codefrag ">crust</span>" skin (current forrest-0.6-dev)
         validates as HTML 4.0.1
       </p>
 <p>
-        The "<span class="codefrag">tigris</span>" skin (current forrest-0.6-dev)
+        The "<span class="codefrag ">tigris</span>" skin (current forrest-0.6-dev)
         validates as HTML 4.0.1
       </p>
 </div> 

Modified: forrest/site/docs_0_60/faq.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/faq.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_60/faq.html (original)
+++ forrest/site/docs_0_60/faq.html Mon Dec  5 20:55:03 2005
@@ -568,14 +568,14 @@
          files), see the second paragraph.
         </p>
 <p>
-         The <span class="codefrag">maxmemory</span> property in the <span class="codefrag">forrest.properties</span> file controls how much
+         The <span class="codefrag ">maxmemory</span> property in the <span class="codefrag ">forrest.properties</span> file controls how much
          memory Cocoon uses. Like many other properties you can copy them from the default configuration at
-         <span class="codefrag">src/core/fresh-site/forrest.properties</span>
+         <span class="codefrag ">src/core/fresh-site/forrest.properties</span>
         
 </p>
 <p>
-         Set the <span class="codefrag">ANT_OPTS</span> environment variable before you run forrest.  The exact value you set
-         it to is dependant on your JVM, but something like <span class="codefrag">ANT_OPTS=-Xmx500M</span> will probably work.
+         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>
 </div>
 <a name="N1007E"></a><a name="technical"></a>
@@ -613,7 +613,7 @@
 <a href="#clickable-email-adress-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p>You would override <span class="codefrag">
+<p>You would override <span class="codefrag ">
        src/core/context/skins/common/xslt/html/document2html.xsl</span>
        and edit the "headers/authors" template.
        </p>
@@ -625,7 +625,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
@@ -643,13 +643,13 @@
 </div>
 <div style="margin-left: 15px">
 <p>
-          This can be done by overriding the <span class="codefrag">cli.xconf</span> config file,
+          This can be done by overriding the <span class="codefrag ">cli.xconf</span> config file,
           and defining patterns for URLs to exclude.
         </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/context/WEB-INF/cli.xconf</span> to it.  Then edit
+          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/context/WEB-INF/cli.xconf</span> to it.  Then edit
           cli.xconf, and add any exclude sections you require at the end.  The
           default cli.xconf ignores directory links and links containing
           'apidocs' or starting with 'api/':
@@ -672,7 +672,7 @@
           Wildcards may be used.  These are a powerful feature of Cocoon's
           <a href="../docs_0_60/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>
+          <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>
@@ -685,7 +685,7 @@
 </div>
 <div style="margin-left: 15px">
 <p>
-          Place them in the <span class="codefrag">src/documentation/content</span> directory
+          Place them in the <span class="codefrag ">src/documentation/content</span> directory
           and they will get copied into the output tree where you can link to
           them. You can also have sub-directories there to reflect your xdocs
           tree. See the samples documents when you 'forrest seed' a new
@@ -693,10 +693,10 @@
         </p>
 <p>
          For example, if
-         <span class="codefrag">src/documentation/content/xdocs/tools/downloads.xml</span>
-         has a <span class="codefrag">&lt;link href="tool.zip"&gt;</span> then put
-         <span class="codefrag">tool.zip</span> in the
-         <span class="codefrag">src/documentation/content/tools/</span> directory.
+         <span class="codefrag ">src/documentation/content/xdocs/tools/downloads.xml</span>
+         has a <span class="codefrag ">&lt;link href="tool.zip"&gt;</span> then put
+         <span class="codefrag ">tool.zip</span> in the
+         <span class="codefrag ">src/documentation/content/tools/</span> directory.
         </p>
 <p>
           See the explanation and demonstration of "linking" in your local
@@ -714,7 +714,7 @@
 <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,
+          <span class="codefrag ">site, changes, todo, faq, images, my-images, skinconf,
           community, howto</span>
         
 </p>
@@ -771,7 +771,7 @@
 </li>
           
 <li>Unpack the Jimi distribution and copy JimiProClasses.zip to
-            <span class="codefrag">$FORREST/lib/optional/jimi-1.0.jar</span>.</li>
+            <span class="codefrag ">$FORREST/lib/optional/jimi-1.0.jar</span>.</li>
         
 </ol>
 <p>Alternatively you can use JAI (Java Advanced Imaging API at 
@@ -797,11 +797,11 @@
 </div>
 <div style="margin-left: 15px">
 <p>
-          In <span class="codefrag">tabs.xml</span>, use @href instead of @dir, and omit the
+          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 contain:
+          <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>
@@ -823,8 +823,8 @@
 <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:
+          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>
 <pre class="code">forrest -Dforrest.jvmargs=-Djava.awt.headless=true site</pre>
 <p>
@@ -858,8 +858,8 @@
 <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>
@@ -944,7 +944,7 @@
 </div>
 <div style="margin-left: 15px">
 <p>Breadcrumbs begin with up to three URLs specified in
-      <span class="codefrag">skinconf.xml</span>.  Here is what the Forrest site uses:</p>
+      <span class="codefrag ">skinconf.xml</span>.  Here is what the Forrest site uses:</p>
 <pre class="code">
   &lt;trail&gt;
     &lt;link1 name="apache" href="http://www.apache.org/"/&gt;
@@ -956,7 +956,7 @@
       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>.
+      in <span class="codefrag ">skinconf.xml</span>.
       </p>
 </div>
 <a name="N1020E"></a><a name="old_faqs"></a>
@@ -971,7 +971,7 @@
 </div>
 <div style="margin-left: 15px">
 <p>This is a bug in 0.4. The following modification to
-          <span class="codefrag">FORREST_HOME/forrest.antproxy.xml</span> should fix it:</p>
+          <span class="codefrag ">FORREST_HOME/forrest.antproxy.xml</span> should fix it:</p>
 <pre class="code">--- forrest.antproxy.xml        7 Feb 2003 22:21:15 -0000       1.2
 +++ forrest.antproxy.xml        22 Feb 2003 09:39:42 -0000
 @@ -41,6 +41,7 @@
@@ -993,7 +993,7 @@
 </div>
 <div style="margin-left: 15px">
 <p>
-          Forrest now uses a HTML 4.0.1 <span class="codefrag">DOCTYPE</span> declaration:</p>
+          Forrest now uses a HTML 4.0.1 <span class="codefrag ">DOCTYPE</span> declaration:</p>
 <pre class="code">
 &lt;!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
   "http://www.w3.org/TR/html4/loose.dtd"&gt;</pre>
@@ -1018,14 +1018,14 @@
 <p>
           You are probably trying to build the project with an old version of
           Forrest (built before 2003-01-08) that is incorrectly trying to validate
-          the <span class="codefrag">site.xml</span> file.  If so, please update your Forrest
+          the <span class="codefrag ">site.xml</span> file.  If so, please update your Forrest
           installation.
         </p>
 <p>
           Alternatively, you may be building with an up-to-date Forrest, but have
-          overridden <span class="codefrag">forrest.validate.xdocs.excludes</span> in
-          <span class="codefrag">forrest.properties</span>.  With the introduction of
-          <span class="codefrag">site.xml</span>, the above property must have <span class="codefrag">site.xml</span>
+          overridden <span class="codefrag ">forrest.validate.xdocs.excludes</span> in
+          <span class="codefrag ">forrest.properties</span>.  With the introduction of
+          <span class="codefrag ">site.xml</span>, the above property must have <span class="codefrag ">site.xml</span>
           listed to prevent an attempt at DTD-based validation.
         </p>
 </div>
@@ -1056,13 +1056,13 @@
 </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
+          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.
+          where <span class="codefrag ">site.xml</span>-generated menus aren't appropriate.
           See <a href="../docs_0_60/linking.html">Menus and Linking</a>.
       </p>
 </div>
@@ -1134,13 +1134,13 @@
 </div>
 <div style="margin-left: 15px">
 <p>
-          Do <span class="codefrag">'forrest -projecthelp'</span> or <span class="codefrag">'./build.sh'</span>
+          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 messages.
+          Doing <span class="codefrag ">'forrest -v'</span> will provide verbose build messages.
         </p>
 </div>
 <a name="N102BF"></a><a name="logs"></a>
@@ -1152,23 +1152,23 @@
 </div>
 <div style="margin-left: 15px">
 <p>
-          The logfiles are at <span class="codefrag">build/webapp/WEB-INF/logs/</span>
+          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>
+          The log level can be raised with the <span class="codefrag ">logkit.xconf</span>
           configuration. If you are using Forrest in the interactive webapp
           mode (which is generally easiest for debugging errors) then see the
-          <span class="codefrag">build/webapp/WEB-INF/logkit.xconf</span> file.
+          <span class="codefrag ">build/webapp/WEB-INF/logkit.xconf</span> file.
           If you are generating a static site (with command-line 'forrest')
-          then copy <span class="codefrag">$FORREST_HOME/context/WEB-INF/logkit.xconf</span>
+          then copy <span class="codefrag ">$FORREST_HOME/context/WEB-INF/logkit.xconf</span>
           to your project at
-          <span class="codefrag">src/documentation/content/conf/logkit.xconf</span>
+          <span class="codefrag ">src/documentation/content/conf/logkit.xconf</span>
           and modify it. See more information and efficiency tips with
           <a href="http://wiki.apache.org/cocoon/ExploringTheLogs">Cocoon logging</a>.
         </p>
 <p>
-          Doing <span class="codefrag">'forrest -v'</span> will provide verbose build messages
+          Doing <span class="codefrag ">'forrest -v'</span> will provide verbose build messages
           to the standard output.
         </p>
 </div>

Modified: forrest/site/docs_0_60/forrest-contract.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/forrest-contract.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_60/forrest-contract.html (original)
+++ forrest/site/docs_0_60/forrest-contract.html Mon Dec  5 20:55:03 2005
@@ -303,10 +303,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> 
@@ -339,17 +339,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 ">{projecthome}/skinconf.xml</span>
         
 </li>
       
@@ -364,13 +364,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> 
             
@@ -378,7 +378,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>
@@ -386,7 +386,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_60/howto/bugzilla-patch/howto-bugzilla-patch.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/howto/bugzilla-patch/howto-bugzilla-patch.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_60/howto/bugzilla-patch/howto-bugzilla-patch.html (original)
+++ forrest/site/docs_0_60/howto/bugzilla-patch/howto-bugzilla-patch.html Mon Dec  5 20:55:03 2005
@@ -327,7 +327,7 @@
 <h4>Specify Version</h4>
 <p>
 This is the version of Cocoon that you prepared your patch against. Choose
-<span class="codefrag">Current CVS</span> if you have an up-to-date local working copy
+<span class="codefrag ">Current CVS</span> if you have an up-to-date local working copy
 of HEAD branch or a very recent nightly build. Otherwise choose the relevant
 release version. This is a very important step, as you will confuse the
 committer if your changes do not match the repository. If you are unsure, then
@@ -338,53 +338,53 @@
 <p>
 Follow the "Component" link for description of the available
 components. If you do not know which component is relevant, then just use
-<span class="codefrag">core</span>.
+<span class="codefrag ">core</span>.
 </p>
 <a name="N10072"></a><a name="Specify+Platform"></a>
 <h4>Specify Platform</h4>
 <p>
 This is really meant for bug reporting. Perhaps it could be relevant for a
-patch. You would usually specify the <span class="codefrag">All</span> option.
+patch. You would usually specify the <span class="codefrag ">All</span> option.
 </p>
 <a name="N1007F"></a><a name="Specify+Operating+System+%28OS%29"></a>
 <h4>Specify Operating System (OS)</h4>
 <p>
 Really meant for bug reporting. Perhaps it could be relevant for a patch.
-You would usually specify the <span class="codefrag">All</span> option.
+You would usually specify the <span class="codefrag ">All</span> option.
 </p>
 <a name="N1008C"></a><a name="Specify+Severity"></a>
 <h4>Specify Severity</h4>
 <p>
 The impact that would arise if your patch is not applied. For a documentation
-patch, the severity would usually be the default <span class="codefrag">Normal</span>.
+patch, the severity would usually be the default <span class="codefrag ">Normal</span>.
 However, if it addressed some serious lack or fixed a misguided configuration
-statement, then the impact could be <span class="codefrag">major</span>.
+statement, then the impact could be <span class="codefrag ">major</span>.
 </p>
 <p>
 <!--FIXME: (DS) Why include this if it isn't recommended for a patch? -->
 <!--       (DC) To try to discourage them from using it. Does it need
 better words? -->
-(The <span class="codefrag">enhancement</span> option would not be used for a patch, as it is
+(The <span class="codefrag ">enhancement</span> option would not be used for a patch, as it is
 intended for suggesting something that should be done. Use this option wisely.
 It would be better to discuss it on the mailing list first.)
 </p>
 <a name="N100A6"></a><a name="Specify+Initial+State"></a>
 <h4>Specify Initial State</h4>
 <p>
-Use the <span class="codefrag">New</span> option.
+Use the <span class="codefrag ">New</span> option.
 </p>
 <a name="N100B3"></a><a name="Specify+Assigned+To"></a>
 <h4>Specify Assigned To</h4>
 <p>
 Leave it blank. Your patch will be automatically assigned to the
-<span class="codefrag">cocoon-dev</span> mailing list. When a committer takes on your patch,
+<span class="codefrag ">cocoon-dev</span> mailing list. When a committer takes on your patch,
 that committer will assign the bug to their own email address. This pevents
 duplication of effort by other committers.
 </p>
 <p>
 The Cc field can be used if you need the bug reports, and any follow-up, to be
 copied to some other person. Remember that your report will be sent
-automatically to the <span class="codefrag">cocoon-dev</span> mailing list, so you do not need
+automatically to the <span class="codefrag ">cocoon-dev</span> mailing list, so you do not need
 to Cc anyone there.
 </p>
 <a name="N100C6"></a><a name="Specify+URL"></a>
@@ -403,7 +403,7 @@
 Use up all the characters available ... about 60 maximum.
 </p>
 <p>
-Start the Summary with the <span class="codefrag">[PATCH]</span> tag. This will ensure that it
+Start the Summary with the <span class="codefrag ">[PATCH]</span> tag. This will ensure that it
 is included in the Cocoon automated patch queue summary posted to the mailing
 lists. The patch queue summary reminds people what patches are pending. If you
 omit this tag, then your patch may easily be overlooked.
@@ -431,7 +431,7 @@
 <p>
 Review your options, then press the <strong>Commit</strong> button. This will
 add an entry to the bug database and email a report to the 
-<span class="codefrag">cocoon-dev</span> mailing list and a copy to you. Your submission will be
+<span class="codefrag ">cocoon-dev</span> mailing list and a copy to you. Your submission will be
 assigned a unique Bug Number which you can use to review its progress.
 </p>
 <p>
@@ -442,7 +442,7 @@
 <h3 class="underlined_5">4. Create an attachment of the actual patch</h3>
 <p>
 You will be presented with a status screen saying that your bug report
-was accepted and that email was sent to <span class="codefrag">cocoon-dev</span> mailing list.
+was accepted and that email was sent to <span class="codefrag ">cocoon-dev</span> mailing list.
 </p>
 <p>
 Now you have a choice ... proceed to review your bug report by selecting the
@@ -456,32 +456,32 @@
 <h4>Specify the file to be uploaded</h4>
 <p>
 Provide the local pathname to your patchfile, e.g.
-<span class="codefrag">/home/me/work/cocoon/patch/howto-bugzilla.tar.gz</span>
+<span class="codefrag ">/home/me/work/cocoon/patch/howto-bugzilla.tar.gz</span>
 
 </p>
 <a name="N10122"></a><a name="Describe+the+attachment"></a>
 <h4>Describe the attachment</h4>
 <p>
 Provide a concise one line description, e.g.
-<span class="codefrag">Gzipped TAR archive with new docs and diffs</span>
+<span class="codefrag ">Gzipped TAR archive with new docs and diffs</span>
 
 </p>
 <a name="N1012F"></a><a name="Specify+the+contentType+of+the+attachment"></a>
 <h4>Specify the contentType of the attachment</h4>
 <p>
 If it is a Gzipped TAR archive (*.tar.gz) or a .zip archive, then select
-"<span class="codefrag">Binary file (application/octet-stream)</span>".
+"<span class="codefrag ">Binary file (application/octet-stream)</span>".
 If it is just a single xml document, then select
-"<span class="codefrag">Plain text (text/plain)</span>".
+"<span class="codefrag ">Plain text (text/plain)</span>".
 If the patch is just a single diff file, then select
-"<span class="codefrag">Patch file (text/plain, diffs)</span>".
+"<span class="codefrag ">Patch file (text/plain, diffs)</span>".
 </p>
 <a name="N10143"></a><a name="5.+Submit+the+attachment"></a>
 <h3 class="underlined_5">5. Submit the attachment</h3>
 <p>
 When you are ready, press the <strong>Submit</strong> button. As for Step 3,
 you will be presented with a status screen saying that your attachment
-was accepted and that email was sent to <span class="codefrag">cocoon-dev</span> mailing list.
+was accepted and that email was sent to <span class="codefrag ">cocoon-dev</span> mailing list.
 </p>
 <a name="N10153"></a><a name="6.+Be+patient"></a>
 <h3 class="underlined_5">6. Be patient</h3>

Modified: forrest/site/docs_0_60/howto/howto-asf-mirror.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/howto/howto-asf-mirror.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_60/howto/howto-asf-mirror.html (original)
+++ forrest/site/docs_0_60/howto/howto-asf-mirror.html Mon Dec  5 20:55:03 2005
@@ -365,10 +365,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/src/documentation/content/mirrors.cgi">mirrors.cgi</a>)
       </p>
@@ -380,7 +380,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/src/documentation/content/xdocs/mirrors.ihtml">mirrors.html</a>
         as a template and edit it to suit.)
@@ -407,8 +407,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/context/WEB-INF/cli.xconf</span> to your
-        <span class="codefrag">src/documentation/conf/</span> directory (or wherever
+        <span class="codefrag ">$FORREST_HOME/context/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">
@@ -419,7 +419,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>
 <a name="N100A7"></a><a name="explain"></a>

Modified: forrest/site/docs_0_60/howto/howto-howto.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/howto/howto-howto.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_60/howto/howto-howto.html (original)
+++ forrest/site/docs_0_60/howto/howto-howto.html Mon Dec  5 20:55:03 2005
@@ -389,7 +389,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_60/howto/howto-pdf-tab.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/howto/howto-pdf-tab.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_60/howto/howto-pdf-tab.html (original)
+++ forrest/site/docs_0_60/howto/howto-pdf-tab.html Mon Dec  5 20:55:03 2005
@@ -351,16 +351,16 @@
 <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> based on the <span class="codefrag">aggregate.xmap</span>
+      <span class="codefrag ">sitemap.xmap</span> and create a new
+      <span class="codefrag ">pdf-tab.xmap</span> based on the <span class="codefrag ">aggregate.xmap</span>
     
 </p>
 <a name="N10040"></a><a name="sitemap"></a>
 <h3 class="underlined_5">Create your project's main sitemap.xmap</h3>
 <p>
       Simply copy the sitemap.xmap from the Forrest sitemaps at
-      <span class="codefrag">${FORREST_HOME}/context/sitemap.xmap</span> into your
-      <span class="codefrag">src/documentation</span> directory (or wherever
+      <span class="codefrag ">${FORREST_HOME}/context/sitemap.xmap</span> into your
+      <span class="codefrag ">src/documentation</span> directory (or wherever
       ${project.sitemap-dir} points to).
     </p>
 <a name="N10050"></a><a name="aggregator"></a>
@@ -378,7 +378,7 @@
     </div>
 </div>
 <p>
-      Edit the project <span class="codefrag">sitemap.xmap</span> to comment-out the match
+      Edit the project <span class="codefrag ">sitemap.xmap</span> to comment-out the match
       for the sitemap like this:
     </p>
 <pre class="code">
@@ -396,7 +396,7 @@
 <h3 class="underlined_5">Edit project sitemap.xmap to mount pdf-tab.xmap</h3>
 <p>
       Insert the following lines after the
-      <span class="codefrag">&lt;map:match pattern="site.xml"&gt;</span>
+      <span class="codefrag ">&lt;map:match pattern="site.xml"&gt;</span>
       pipeline in the section called "SOURCE FORMATS".
     </p>
 <pre class="code">
@@ -409,7 +409,7 @@
 <a name="N1007F"></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">
@@ -433,7 +433,7 @@
 <a name="N10092"></a><a name="edit-site"></a>
 <h3 class="underlined_5">Edit your site.xml</h3>
 <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;
@@ -453,11 +453,11 @@
     </pre>
 <p>
       This allows you to link to it via a
-      <span class="codefrag">&lt;link href="site:v0.60//whole_foosite"&gt;</span>
+      <span class="codefrag ">&lt;link href="site:v0.60//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"
@@ -467,8 +467,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="N100C2"></a><a name="explain"></a>
@@ -477,9 +477,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">
@@ -491,8 +491,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"> 
@@ -507,33 +507,33 @@
     </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 class="note">
 <div class="label">Note</div>
 <div class="content">
-      In the original <span class="codefrag">aggregate.xmap</span> there is the line
+      In the original <span class="codefrag ">aggregate.xmap</span> there is the line
       <br>
       
-<span class="codefrag">&lt;map:parameter name="ignore" value="{1}"/&gt;</span>
+<span class="codefrag ">&lt;map:parameter name="ignore" value="{1}"/&gt;</span>
       
 <br>
       just before the title definition
-      (<span class="codefrag">&lt;map:parameter name="title" value=".../&gt;</span>).
+      (<span class="codefrag ">&lt;map:parameter name="title" value=".../&gt;</span>).
       Be sure to delete it or comment it out if you like to generate a
       pdf-file for specific sites. You only need it for the generation of
       one pdf-file for the whole project (this is what
-      <span class="codefrag">aggregate.xmap</span> usually does).
+      <span class="codefrag ">aggregate.xmap</span> usually does).
     </div>
 </div>
 </div>

Modified: forrest/site/docs_0_60/linking.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/linking.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_60/linking.html (original)
+++ forrest/site/docs_0_60/linking.html Mon Dec  5 20:55:03 2005
@@ -348,7 +348,7 @@
 <div class="section">
 <p>
         This document describes Forrest's internal URI space; how it is managed
-        with the "<span class="codefrag">site.xml</span>" configuration file, how menus are generated,
+        with the "<span class="codefrag ">site.xml</span>" configuration file, how menus are generated,
         and how various link schemes (site: and ext:) operate.
         An overview of the implementation is also provided.
       </p>
@@ -359,9 +359,9 @@
 <h2 class="underlined_10">site.xml</h2>
 <div class="section">
 <p>
-        The "<span class="codefrag">site.xml</span>" configuration file is what we would call a "site map"
+        The "<span class="codefrag ">site.xml</span>" configuration file is what we would call a "site map"
         if Cocoon hadn't already claimed that term. 
-        The "<span class="codefrag">site.xml</span>" is a loosely structured XML file, acting as a map of the
+        The "<span class="codefrag ">site.xml</span>" is a loosely structured XML file, acting as a map of the
         site's contents.  It provides a unique identifier (an XPath address)
         for "nodes" of information in the website.  A "node" of site information
         can be:
@@ -374,17 +374,17 @@
 <li>A specific page, e.g. "the FAQ page"</li>
         
 <li>A specific section in a page, e.g. the "general" section of the FAQ
-          page (identified by <span class="codefrag">id="general"</span> attribute)</li>
+          page (identified by <span class="codefrag ">id="general"</span> attribute)</li>
       
 </ul>
 <p>
-        In addition to providing fine-grained addressing of site info, the <span class="codefrag">site.xml</span>
+        In addition to providing fine-grained addressing of site info, the <span class="codefrag ">site.xml</span>
         allows <em>metadata</em> to be associated with each node, using
-        attributes or child elements.  Most commonly, a <span class="codefrag">label</span>
+        attributes or child elements.  Most commonly, a <span class="codefrag ">label</span>
         attribute is used to provide a text description of the node.
       </p>
 <p>
-        There are currently two applications of <span class="codefrag">site.xml</span>
+        There are currently two applications of <span class="codefrag ">site.xml</span>
       
 </p>
 <dl>
@@ -394,21 +394,21 @@
 </dt>
         
 <dd>
-<span class="codefrag">site.xml</span> is used to generate the menus for the HTML website.</dd>
+<span class="codefrag ">site.xml</span> is used to generate the menus for the HTML website.</dd>
         
 <dt>
 <a href="#semantic_linking">Indirect linking</a>
 </dt>
         
 <dd>
-<span class="codefrag">site.xml</span> provides a basic aliasing mechanism for linking, e.g. one
+<span class="codefrag ">site.xml</span> provides a basic aliasing mechanism for linking, e.g. one
           can write &lt;link href="site:v0.60//changes"&gt; from anywhere in the site, and
           link to the "changes" information node (translated to changes.html).
           More on this below.</dd>
       
 </dl>
 <p>
-        Here is a sample <span class="codefrag">site.xml</span> ... a modified version from Forrest's
+        Here is a sample <span class="codefrag ">site.xml</span> ... a modified version from Forrest's
         own <a href="http://forrest.apache.org/">website</a>:
       </p>
 <pre class="code">
@@ -470,25 +470,25 @@
 <ul>
         
 <li>The root element must be "site", and normal content should be in the
-          namespace <span class="codefrag">http://apache.org/forrest/linkmap/1.0</span> (Feel
+          namespace <span class="codefrag ">http://apache.org/forrest/linkmap/1.0</span> (Feel
           free to mix in your own content (RDF, dublin core, etc) under new
           namespaces)</li>
         
-<li>Element names are used as identifiers.  The "<span class="codefrag">foo</span>" in
-          "<span class="codefrag">site:foo</span>" must therefore be a valid NMTOKEN.</li>
+<li>Element names are used as identifiers.  The "<span class="codefrag ">foo</span>" in
+          "<span class="codefrag ">site:foo</span>" must therefore be a valid NMTOKEN.</li>
         
-<li>Elements with <span class="codefrag">href</span> attributes can be used as identifiers
-          in "<span class="codefrag">site:</span>" URIs</li>
+<li>Elements with <span class="codefrag ">href</span> attributes can be used as identifiers
+          in "<span class="codefrag ">site:</span>" URIs</li>
         
 <li>Relative href attribute contents are "accumulated" by prepending hrefs
           from ancestor nodes</li>
         
-<li>Elements without <span class="codefrag">label</span> attributes (and their children)
+<li>Elements without <span class="codefrag ">label</span> attributes (and their children)
           are not displayed in the menu.</li>
         
-<li>Elements below <span class="codefrag">external-refs</span> are mapped to the
-          "<span class="codefrag">ext:</span>" scheme.  So "<span class="codefrag">ext:commons/resolver/</span>" becomes
-          "<span class="codefrag">http://xml.apache.org/commons/resolver/</span>"</li>
+<li>Elements below <span class="codefrag ">external-refs</span> are mapped to the
+          "<span class="codefrag ">ext:</span>" scheme.  So "<span class="codefrag ">ext:commons/resolver/</span>" becomes
+          "<span class="codefrag ">http://xml.apache.org/commons/resolver/</span>"</li>
       
 </ul>
 </div>
@@ -498,11 +498,11 @@
 <h2 class="underlined_10">Generating Menus</h2>
 <div class="section">
 <p>
-        Two files are used to define a site's tabs and menu (<span class="codefrag">site.xml</span> and
-        <span class="codefrag">tabs.xml</span>).  Both files are located in
-        <span class="codefrag">src/documentation/content/xdocs/</span>
+        Two files are used to define a site's tabs and menu (<span class="codefrag ">site.xml</span> and
+        <span class="codefrag ">tabs.xml</span>).  Both files are located in
+        <span class="codefrag ">src/documentation/content/xdocs/</span>
 </p>
-<p>Assume that our <span class="codefrag">tabs.xml</span> looks like this:</p>
+<p>Assume that our <span class="codefrag ">tabs.xml</span> looks like this:</p>
 <pre class="code">
 &lt;tabs ...&gt;
     &lt;tab id="home" label="Home" dir=""/&gt;
@@ -510,48 +510,48 @@
     &lt;tab id="howto" label="How-Tos" dir="community/howto"/&gt;
 &lt;/tabs&gt;
       </pre>
-<p>Using the "<span class="codefrag">site.xml</span>" listed above, we would get these menus:</p>
+<p>Using the "<span class="codefrag ">site.xml</span>" listed above, we would get these menus:</p>
 <p>
         
 <img alt="Menu generated from site.xml" src="images/menu.png">&nbsp;&nbsp;&nbsp;
         <img alt="Community menu generated from site.xml" src="images/menu2.png">&nbsp;&nbsp;&nbsp;
         <img alt="Howto menu generated from site.xml" src="images/menu3.png">
       </p>
-<p>When using the "<span class="codefrag">dir</span>" attribute as above the value of the
-      "<span class="codefrag">indexfile</span>" parameter is appended to the value of the 
-      "<span class="codefrag">dir</span>" attribute (together with a preceding '/'). For example,
+<p>When using the "<span class="codefrag ">dir</span>" attribute as above the value of the
+      "<span class="codefrag ">indexfile</span>" parameter is appended to the value of the 
+      "<span class="codefrag ">dir</span>" attribute (together with a preceding '/'). For example,
       the link for the community tab above is 
-      <span class="codefrag">community/mailLists.html</span>. Note that "<span class="codefrag">indexfile</span>"
-      defaults to "<span class="codefrag">index.html</span>" if no value is supplied. Therefore the
-      link for the howto tab is <span class="codefrag">community/howto/index.html</span>
+      <span class="codefrag ">community/mailLists.html</span>. Note that "<span class="codefrag ">indexfile</span>"
+      defaults to "<span class="codefrag ">index.html</span>" if no value is supplied. Therefore the
+      link for the howto tab is <span class="codefrag ">community/howto/index.html</span>
 </p>
 <a name="N100ED"></a><a name="tabs-external"></a>
 <h3 class="underlined_5">Tabs for External Resources</h3>
 <p>A tab can refer to an external resource by using the 
-        "<span class="codefrag">href</span>" attribute instead of the "<span class="codefrag">dir</span>" attribute.
-        The value of "<span class="codefrag">href</span>" should be the URI of the resource you wish 
+        "<span class="codefrag ">href</span>" attribute instead of the "<span class="codefrag ">dir</span>" attribute.
+        The value of "<span class="codefrag ">href</span>" should be the URI of the resource you wish 
         to link to. For example:</p>
 <pre class="code">
 &lt;tab id="apache" label="XML Apache" href="http://xml.apache.org/"/&gt;
         </pre>
-<p>Unlike the "<span class="codefrag">dir</span>" attribute, the value of "<span class="codefrag">href</span>"
+<p>Unlike the "<span class="codefrag ">dir</span>" attribute, the value of "<span class="codefrag ">href</span>"
         is left unmodified by Forrest unless it is root-relative and obviously 
         specifies a directory (ends in '/'). In which case /index.html will be 
         added.</p>
 <a name="N1010D"></a><a name="selecting-entries"></a>
 <h3 class="underlined_5">Selecting menu entries</h3>
 <p>Forrest decides which menu entries to display, by examining the
-          "<span class="codefrag">tab</span>" attributes in the <span class="codefrag">site.xml</span> file. The children of 
-          all <span class="codefrag">site.xml</span> entries with a
-          "<span class="codefrag">tab</span>" which is equal to that of the current page, are
+          "<span class="codefrag ">tab</span>" attributes in the <span class="codefrag ">site.xml</span> file. The children of 
+          all <span class="codefrag ">site.xml</span> entries with a
+          "<span class="codefrag ">tab</span>" which is equal to that of the current page, are
           added to the menu, whilst the element itself forms the root of that
-          part of the menu (see the "<span class="codefrag">community</span>" element in the 
+          part of the menu (see the "<span class="codefrag ">community</span>" element in the 
           example below). Child elements that have a different 
-          "<span class="codefrag">tab</span>" attribute value will appear in the menu for their
+          "<span class="codefrag ">tab</span>" attribute value will appear in the menu for their
           parents, and will also form the root of a new menu for a tab with 
-          the appropriate name (see the "<span class="codefrag">howto-samples</span>" element
+          the appropriate name (see the "<span class="codefrag ">howto-samples</span>" element
           below).</p>
-<p>Consider our <span class="codefrag">site.xml</span> example:</p>
+<p>Consider our <span class="codefrag ">site.xml</span> example:</p>
 <pre class="code">
 &lt;site label="Forrest" href="" <strong>tab="home"</strong>
   xmlns="http://apache.org/forrest/linkmap/1.0"&gt;
@@ -576,25 +576,25 @@
         &lt;step1 label="Step 1" href="step1.html"/&gt;
       ...</pre>
 <p>
-          Every <span class="codefrag">site.xml</span> node can potentially have a "<span class="codefrag">tab</span>" attribute.  If
-          unspecified, nodes inherit the "<span class="codefrag">tab</span>" of their parent.  Thus
+          Every <span class="codefrag ">site.xml</span> node can potentially have a "<span class="codefrag ">tab</span>" attribute.  If
+          unspecified, nodes inherit the "<span class="codefrag ">tab</span>" of their parent.  Thus
           everything in the <strong>&lt;about&gt;</strong> section has an implicit
-          <span class="codefrag">tab="home" </span>attribute.</p>
+          <span class="codefrag ">tab="home" </span>attribute.</p>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">You can see this by viewing your site's 
         <a href="../abs-menulinks">abs-menulinks</a> pipeline in a
           browser.</div>
 </div>
-<p>Say that the user is viewing the <span class="codefrag">linking.html</span>
+<p>Say that the user is viewing the <span class="codefrag ">linking.html</span>
           page.  The <strong>&lt;linking&gt;</strong> node has an implicit tab
-          value of "<span class="codefrag">home</span>".  Forrest will select <em>all nodes with
+          value of "<span class="codefrag ">home</span>".  Forrest will select <em>all nodes with
             tab="home"</em> and put them in the menu.
         </p>
 <a name="N10167"></a><a name="other-menu-selection"></a>
 <h3 class="underlined_5">Alternative menu selection mechanisms.</h3>
 <p>
-          The "<span class="codefrag">tab</span>" attribute-based scheme for selecting a menu's
+          The "<span class="codefrag ">tab</span>" attribute-based scheme for selecting a menu's
           entries is not the only one, although it is the most flexible.  Here
           we describe a few alternatives.
         </p>
@@ -613,11 +613,11 @@
           </p>
 <ul>
             
-<li>Edit <span class="codefrag">forrest.properties</span> and set
-              <span class="codefrag">project.menu-scheme=directories</span>
+<li>Edit <span class="codefrag ">forrest.properties</span> and set
+              <span class="codefrag ">project.menu-scheme=directories</span>
 </li>
             
-<li>Remove the "<span class="codefrag">id</span>" attributes from <span class="codefrag">tabs.xml</span>
+<li>Remove the "<span class="codefrag ">id</span>" attributes from <span class="codefrag ">tabs.xml</span>
               entries.</li>
           
 </ul>
@@ -625,21 +625,21 @@
 <h4>Specifying menus with book.xml</h4>
 <p>
             Historically, menus in Forrest have been generated from a
-            <span class="codefrag">book.xml</span> file, one per directory.  This mechanism is
-            still available, and if a <span class="codefrag">book.xml</span> is found, it will be
-            used in preference to the menu generated by the <span class="codefrag">site.xml</span> file. The <span class="codefrag">book.xml</span>
-            files can use "<span class="codefrag">site:</span>" URIs to ease the maintenance burden
+            <span class="codefrag ">book.xml</span> file, one per directory.  This mechanism is
+            still available, and if a <span class="codefrag ">book.xml</span> is found, it will be
+            used in preference to the menu generated by the <span class="codefrag ">site.xml</span> file. The <span class="codefrag ">book.xml</span>
+            files can use "<span class="codefrag ">site:</span>" URIs to ease the maintenance burden
             that led to obsolescence of book.xml files.  In general, however, we
-            recommend that users avoid <span class="codefrag">book.xml</span> files.
+            recommend that users avoid <span class="codefrag ">book.xml</span> files.
           </p>
 <a name="N101C0"></a><a name="tab-selection"></a>
 <h3 class="underlined_5">Selecting the current tab</h3>
 <p>
           The tab selection algorithm is quite simple: the tab with the
-          "<span class="codefrag">id</span>" which matches that of the current <span class="codefrag">site.xml</span>
+          "<span class="codefrag ">id</span>" which matches that of the current <span class="codefrag ">site.xml</span>
           node is "selected". If you experience any problems, try to add a 
-          <span class="codefrag">&lt;foo label="Foo" href="index.html"/&gt;</span> to the
-          <span class="codefrag">site.xml</span> configuration.
+          <span class="codefrag ">&lt;foo label="Foo" href="index.html"/&gt;</span> to the
+          <span class="codefrag ">site.xml</span> configuration.
         </p>
 </div>
 
@@ -651,35 +651,35 @@
       is created from the titles of each section in your xdoc. By default only
       sections up to two levels deep are included and the table of contents is
       displayed at the top of the page. However, you can configure this
-      behaviour in <span class="codefrag">src/documentation/skinconf.xml</span> using the 
-      "<span class="codefrag">toc</span>" element.</p>
+      behaviour in <span class="codefrag ">src/documentation/skinconf.xml</span> using the 
+      "<span class="codefrag ">toc</span>" element.</p>
 <pre class="code">
 &lt;toc level="2" location="page"/&gt;
       </pre>
 <ul>
         
 <li>
-<strong><span class="codefrag">level</span></strong> - is the depth to which you
+<strong><span class="codefrag ">level</span></strong> - is the depth to which you
         want your table of contents to go. Setting it to "3" will therefore 
         include sections nested to 3 levels. Setting this to "0" will result in
         no table of contents being generated.</li>
         
 <li>
-<strong><span class="codefrag">location</span></strong> - indicates where you
+<strong><span class="codefrag ">location</span></strong> - indicates where you
         want the table of contents to be rendered. It can be set to one of
         three values:
           <ul>
             
 <li>
-<span class="codefrag">page</span> - the table of contents will be rendered
+<span class="codefrag ">page</span> - the table of contents will be rendered
             at the top of the body of your page</li>
             
 <li>
-<span class="codefrag">menu</span> - the table of contents will be rendered
+<span class="codefrag ">menu</span> - the table of contents will be rendered
             in the menu to the left of the body of the page</li>
             
 <li>
-<span class="codefrag">menu, page</span> - table of contents will be rendered
+<span class="codefrag ">menu, page</span> - table of contents will be rendered
             in both the page and the menu positions</li>
           
 </ul>
@@ -697,8 +697,8 @@
 <h3 class="underlined_5">Direct linking</h3>
 <p>
           In earlier versions of Forrest (and in similar systems), there has
-          been only one URI space: that of the generated site.  If <span class="codefrag">index.xml</span> wants to
-          link to <span class="codefrag">todo.xml</span> then <span class="codefrag">index.xml</span> would use
+          been only one URI space: that of the generated site.  If <span class="codefrag ">index.xml</span> wants to
+          link to <span class="codefrag ">todo.xml</span> then <span class="codefrag ">index.xml</span> would use
         </p>
 <pre class="code">
           &lt;link href="todo.html"&gt;to-do list&lt;link&gt;
@@ -729,8 +729,8 @@
           
 <dt>todo</dt>
           
-<dd>identifies the content in <span class="codefrag">todo.xml</span> by reference to a
-            "node" of content declared in <span class="codefrag">site.xml</span>
+<dd>identifies the content in <span class="codefrag ">todo.xml</span> by reference to a
+            "node" of content declared in <span class="codefrag ">site.xml</span>
 </dd>
         
 </dl>
@@ -743,13 +743,13 @@
 <a name="N1025E"></a><a name="resolve-site-uris"></a>
 <h4>Resolving site: URIs</h4>
 <p>
-            So how does "<span class="codefrag">site:todo</span>" get resolved?  A full answer
+            So how does "<span class="codefrag ">site:todo</span>" get resolved?  A full answer
             is provided in the <a href="#implementation">implementation</a>
-            section.  Essentially, the "<span class="codefrag">todo</span>" part has
-            "<span class="codefrag">/site//</span>" prepended, and "<span class="codefrag">/@href</span>" appended, to
-            form the string "<span class="codefrag">/site//todo/@href</span>".  This is
-            then used as an XPath expression in <span class="codefrag">site.xml</span> to identify the string
-            replacement, in this case "<span class="codefrag">todo.html</span>"
+            section.  Essentially, the "<span class="codefrag ">todo</span>" part has
+            "<span class="codefrag ">/site//</span>" prepended, and "<span class="codefrag ">/@href</span>" appended, to
+            form the string "<span class="codefrag ">/site//todo/@href</span>".  This is
+            then used as an XPath expression in <span class="codefrag ">site.xml</span> to identify the string
+            replacement, in this case "<span class="codefrag ">todo.html</span>"
           </p>
 <p>
             Thus by modifying the XPath prefix and suffix, almost any XML
@@ -759,33 +759,33 @@
 <div class="label">Note</div>
 <div class="content">
             Actually, the XPath is applied to XML generated dynamically from
-            <span class="codefrag">site.xml</span>.  The generated XML has each "@href" fully expanded ("absolutized")
+            <span class="codefrag ">site.xml</span>.  The generated XML has each "@href" fully expanded ("absolutized")
             and dot-dots (..) added as needed ("relativized").
           </div>
 </div>
 <p>
             Notice that the "//" allows us any degree of specificity when linking.
-            In the sample <span class="codefrag">site.xml</span> above, both "<span class="codefrag">site:new_content_type</span>" and
-            "<span class="codefrag">site:about/your-project/new_content_type</span>" identify the
+            In the sample <span class="codefrag ">site.xml</span> above, both "<span class="codefrag ">site:new_content_type</span>" and
+            "<span class="codefrag ">site:about/your-project/new_content_type</span>" identify the
             same node.  It is up to you to decide how specific to make links.  One
-            nice benefit of link "ambiguity" is that <span class="codefrag">site.xml</span> can be reorganized
+            nice benefit of link "ambiguity" is that <span class="codefrag ">site.xml</span> can be reorganized
             without breaking links.  For example, "new_content_type" currently
             identifies a node in "your-project".  By leaving that fact unspecified
-            in "<span class="codefrag">site:new_content_type</span>" we are free to make
+            in "<span class="codefrag ">site:new_content_type</span>" we are free to make
             "new_content_type" its own XML file, or a node in another file, in
             another category.
           </p>
 <a name="N1029C"></a><a name="resolve-ext-uris"></a>
 <h4>ext: URIs: linking to external URLs</h4>
 <p>
-            The "<span class="codefrag">ext:</span>" scheme was created partly to demonstrate the
+            The "<span class="codefrag ">ext:</span>" scheme was created partly to demonstrate the
             ease with which new schemes can be defined, and partly for practical
-            use. The "<span class="codefrag">ext:</span>" URIs identify nodes in <span class="codefrag">site.xml</span> below the
+            use. The "<span class="codefrag ">ext:</span>" URIs identify nodes in <span class="codefrag ">site.xml</span> below the
             &lt;external-refs&gt; node.  By convention, nodes here link to URLs
             outside the website, and are not listed in the menu generated from
-            the <span class="codefrag">site.xml</span> file.
+            the <span class="codefrag ">site.xml</span> file.
           </p>
-<p>Here is a <span class="codefrag">site.xml</span> snippet illustrating "<span class="codefrag">external-refs</span>":</p>
+<p>Here is a <span class="codefrag ">site.xml</span> snippet illustrating "<span class="codefrag ">external-refs</span>":</p>
 <pre class="code">
 &lt;site&gt;
   ...
@@ -806,30 +806,30 @@
           
 </p>
 <p>
-            The general rules of <span class="codefrag">site.xml</span> and "<span class="codefrag">site:</span>" linking apply.
+            The general rules of <span class="codefrag ">site.xml</span> and "<span class="codefrag ">site:</span>" linking apply.
             Specifically, the "@href" aggregation makes defining large numbers of
             related URLs easy.
           </p>
 <a name="N102CF"></a><a name="source-uris"></a>
 <h4>Theory: source URIs</h4>
 <p>
-            The "<span class="codefrag">site:</span>" URIs like "<span class="codefrag">site:todo</span>" are examples of
+            The "<span class="codefrag ">site:</span>" URIs like "<span class="codefrag ">site:todo</span>" are examples of
             "<em>source</em>" URIs, in contrast to the more usual
-            <span class="codefrag">foo.html</span> style URIs, which we here call
+            <span class="codefrag ">foo.html</span> style URIs, which we here call
             "<em>destination</em>" URIs.  This introduces an important concept: that
             the "<em>source</em>" URI space exists and is independent of that of the
             generated site.  Furthermore, URIs (i.e. links) are first-class objects,
             on par with XML documents, in that just as XML content is transformed,
             so are the links.  Within the source URI space, we can have all sorts of
             interesting schemes (person: mail: google: java: etc). These will
-            all be translated into plain old "<span class="codefrag">http:</span>" or relative URIs
+            all be translated into plain old "<span class="codefrag ">http:</span>" or relative URIs
             in the destination URI space, just like exotic XML source formats are
             translated into plain old HTML in the output.
           </p>
 <a name="N102EE"></a><a name="future-schemes"></a>
 <h4>Future schemes</h4>
 <p>
-            So far, the "<span class="codefrag">site:</span>" and "<span class="codefrag">ext:</span>" schemes are defined.
+            So far, the "<span class="codefrag ">site:</span>" and "<span class="codefrag ">ext:</span>" schemes are defined.
             To give you some ideas on other things we'd like to implement (and
             wouldd welcome help to implement) here are a few possibilities.
           </p>
@@ -843,10 +843,10 @@
               
 <td colspan="1" rowspan="1">java</td>
               <td colspan="1" rowspan="1">java:org.apache.proj.SomeClass</td>
-              <td colspan="1" rowspan="1"><span class="codefrag">../../apidocs/org/apache/proj/SomeClass.html</span></td>
+              <td colspan="1" rowspan="1"><span class="codefrag ">../../apidocs/org/apache/proj/SomeClass.html</span></td>
               <td colspan="1" rowspan="1">
                 Links to documentation for a Java class (typically generated by
-                <span class="codefrag">javadoc</span>).
+                <span class="codefrag ">javadoc</span>).
               </td>
             
 </tr>
@@ -855,9 +855,9 @@
               
 <td colspan="1" rowspan="1">mail</td>
               <td colspan="1" rowspan="1">mail::&lt;Message-Id&gt;</td>
-              <td colspan="1" rowspan="1"><span class="codefrag">http://marc.theaimsgroup.com?t=12345678</span></td>
+              <td colspan="1" rowspan="1"><span class="codefrag ">http://marc.theaimsgroup.com?t=12345678</span></td>
               <td colspan="1" rowspan="1">
-                Links to an email, identified by its <span class="codefrag">Message-Id</span>
+                Links to an email, identified by its <span class="codefrag ">Message-Id</span>
                 header. Any mail archive website could be used.
               </td>
             
@@ -867,7 +867,7 @@
               
 <td colspan="1" rowspan="1">search</td>
               <td colspan="1" rowspan="1">search:&lt;searchterm&gt;</td>
-              <td colspan="1" rowspan="1"><span class="codefrag">http://www.google.com/search?q=searchterm</span></td>
+              <td colspan="1" rowspan="1"><span class="codefrag ">http://www.google.com/search?q=searchterm</span></td>
               <td colspan="1" rowspan="1">Link to set of results from a search engine</td>
             
 </tr>
@@ -876,10 +876,10 @@
               
 <td colspan="1" rowspan="1">person</td>
               <td colspan="1" rowspan="1">person:JT, person:JT/blog etc</td>
-              <td colspan="1" rowspan="1"><span class="codefrag">mailto:jefft&lt;at&gt;apache.org</span>,
-                <span class="codefrag">http://www.webweavertech.com/jefft/weblog/</span></td>
+              <td colspan="1" rowspan="1"><span class="codefrag ">mailto:jefft&lt;at&gt;apache.org</span>,
+                <span class="codefrag ">http://www.webweavertech.com/jefft/weblog/</span></td>
               <td colspan="1" rowspan="1">
-                A "<span class="codefrag">person:</span>" scheme could be used, say, to insert an
+                A "<span class="codefrag ">person:</span>" scheme could be used, say, to insert an
                 automatically obfuscated email address, or link to a URI in some
                 way associated with that person.
               </td>
@@ -889,10 +889,10 @@
 </table>
 <p>
             There are even more possibilities in specific environments.  In an
-            intranet, a "<span class="codefrag">project:XYZ</span>" scheme could identify company
+            intranet, a "<span class="codefrag ">project:XYZ</span>" scheme could identify company
             project pages.  In a project like <a href="http://ant.apache.org/">Apache
               Ant</a>, each Task could be identified with
-            <span class="codefrag">task:&lt;taskname&gt;</span>, e.g. <span class="codefrag">task:pathconvert</span>.
+            <span class="codefrag ">task:&lt;taskname&gt;</span>, e.g. <span class="codefrag ">task:pathconvert</span>.
           </p>
 </div>
     
@@ -900,13 +900,13 @@
 <h2 class="underlined_10">Concept</h2>
 <div class="section">
 <p>
-        The "<span class="codefrag">site:</span>" scheme and associated ideas for <span class="codefrag">site.xml</span> were
+        The "<span class="codefrag ">site:</span>" scheme and associated ideas for <span class="codefrag ">site.xml</span> were
         originally described in <a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=103444028129281&w=2">the 'linkmap' RT
           email</a> to the forrest-dev list (RT means 'random thought'; a
         Cocoon invention).   Only section 2 has been implemented, and there is
         still significant work required to implement the full system
         described.  In particular, there is much scope for automating the
-        creation of <span class="codefrag">site.xml</span> (section 4).  However, what is currently implemented
+        creation of <span class="codefrag ">site.xml</span> (section 4).  However, what is currently implemented
         gains most of the advantages of the system.
       </p>
 </div>

Modified: forrest/site/docs_0_60/project-sitemap.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/project-sitemap.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_60/project-sitemap.html (original)
+++ forrest/site/docs_0_60/project-sitemap.html Mon Dec  5 20:55:03 2005
@@ -318,7 +318,7 @@
 <a name="N10029"></a><a name="how"></a>
 <h2 class="underlined_10">How does it work?</h2>
 <div class="section">
-<p>If a project has a <span class="codefrag">sitemap.xmap</span> file in it's 
+<p>If a project has a <span class="codefrag ">sitemap.xmap</span> file in it's 
       documentation dir, that gets mounted automatically by Forrest and 
       becomes part of the processing: it is a preprocessing step, and 
       is the first one to handle the request. Because of this it can 

Modified: forrest/site/docs_0_60/searching.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/searching.html?rev=354312&r1=354311&r2=354312&view=diff
==============================================================================
--- forrest/site/docs_0_60/searching.html (original)
+++ forrest/site/docs_0_60/searching.html Mon Dec  5 20:55:03 2005
@@ -312,15 +312,15 @@
 	functionality is implemented on Google's end, you do not need
 	any additional capability on your Forrest server (which may
 	well be a simple static web server serving content generated
-	with <span class="codefrag">forrest site</span>).</p>
+	with <span class="codefrag ">forrest site</span>).</p>
 <p>To use Google SiteSearch in your Forrest application, open
-	your <span class="codefrag">skinconf.xml</span> file. By default this file is
-	in the <span class="codefrag">src/documentation</span> subdirectory of your
-	Forrest repository root. Find the <span class="codefrag">&lt;search&gt;</span>
+	your <span class="codefrag ">skinconf.xml</span> file. By default this file is
+	in the <span class="codefrag ">src/documentation</span> subdirectory of your
+	Forrest repository root. Find the <span class="codefrag ">&lt;search&gt;</span>
 	element; it should be near the top of the file. If the element
 	does not exist, create it below the
-	<span class="codefrag">&lt;skinconfig&gt;</span> opening tag. If there is any
-	attribute named <span class="codefrag">provider</span>, remove it. The element
+	<span class="codefrag ">&lt;skinconfig&gt;</span> opening tag. If there is any
+	attribute named <span class="codefrag ">provider</span>, remove it. The element
 	should look similar to this:</p>
 <pre class="code">&lt;search name="MyProject"
 	domain="myproject.com"/&gt;</pre>
@@ -345,26 +345,26 @@
 	entirely in Java. To use Lucene-based search with your Forrest
 	documentation, you will need to run Forrest in a Java servlet
 	environment (such as Tomcat or Jetty). Lucene-based searching
-	will not work in a static site generated with the '<span class="codefrag">forrest
+	will not work in a static site generated with the '<span class="codefrag ">forrest
 	  site</span>' command.</p>
 <p>In order to enable Lucene-based full-text search in your
 	Forrest application, you must first edit your
-	<span class="codefrag">skinconf.xml</span> file. Locate the
-	<span class="codefrag">&lt;search&gt;</span> element. If the element does not
+	<span class="codefrag ">skinconf.xml</span> file. Locate the
+	<span class="codefrag ">&lt;search&gt;</span> element. If the element does not
 	exist, insert it right underneath the
-	<span class="codefrag">&lt;skinconfig&gt;</span> opening tag. Add an attribute
-	named <span class="codefrag">provider</span> with a value of
-	<span class="codefrag">lucene</span>, so that the element looks similar to
+	<span class="codefrag ">&lt;skinconfig&gt;</span> opening tag. Add an attribute
+	named <span class="codefrag ">provider</span> with a value of
+	<span class="codefrag ">lucene</span>, so that the element looks similar to
 	this:</p>
 <pre class="code">&lt;search name="MyProject" domain="myproject.com"
 	provider="lucene"/&gt;</pre>
 <p>Next, create and run your Forrest webapp. This may mean
-	simply invoking <span class="codefrag">forrest run</span>, or building and
-	bundling a servlet webapp (with <span class="codefrag">forrest webapp</span>),
+	simply invoking <span class="codefrag ">forrest run</span>, or building and
+	bundling a servlet webapp (with <span class="codefrag ">forrest webapp</span>),
 	and then deploying it to your servlet container.</p>
 <p>You can now build a Lucene search index by pointing your web
 	browser at
-	<span class="codefrag">http://localhost:8888/lucene-update.html</span>. This
+	<span class="codefrag ">http://localhost:8888/lucene-update.html</span>. This
 	generates the search index and provides some information about
 	the index generation process.</p>
 <div class="note">
@@ -372,7 +372,7 @@
 <div class="content">You may have to substitute a different hostname, port, or
 	path, depending on your configuration. The path mentioned here
 	reflects Forrest's default settings when invoked as
-	<span class="codefrag">forrest run</span>.</div>
+	<span class="codefrag ">forrest run</span>.</div>
 </div>
 <p>Now you can utilize the full-text search box, located in the
 	top-right corner of the rendered Forrest pages. Search results
@@ -399,8 +399,8 @@
 	usable servlet-capable web server at your disposal (meaning
 	you can't use Lucene, either).</p>
 <p>To disable full-text search completely, open the
-	<span class="codefrag">skinconf.xml</span> file and remove (or comment out) the
-	entire <span class="codefrag">&lt;search&gt;</span> element.</p>
+	<span class="codefrag ">skinconf.xml</span> file and remove (or comment out) the
+	entire <span class="codefrag ">&lt;search&gt;</span> element.</p>
 </div>
   
 </div>



Mime
View raw message