forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r168512 [3/5] - /forrest/site/0.6 /forrest/site/0.7 /forrest/site/0.7/docs /forrest/site/0.7/docs/howto /forrest/site/0.7/docs/plugins /forrest/site/0.7/skin /forrest/site/0.7/skin/images
Date Fri, 06 May 2005 03:54:35 GMT
Modified: forrest/site/0.7/docs/faq.xml
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/faq.xml?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
--- forrest/site/0.7/docs/faq.xml (original)
+++ forrest/site/0.7/docs/faq.xml Thu May  5 20:54:30 2005
@@ -13,94 +13,50 @@
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.
---><document><header><title>Frequently Asked Questions</title></header><body><section id="Questions"><title>Questions</title><section id="getting_started"><title>1. Getting Started and Building Forrest</title><section id="overview"><title>1.1. 
-        Where can I read an overview about how to work with Forrest?
-      </title>
-        <p>
-          See the <link href="site:your-project">Using Forrest</link> guide.
-        </p>
-      </section><section id="requirements"><title>1.2. 
-        What are the system requirements for Forrest?
-      </title>
-        <p>
-          Forrest includes everything necessary to build and run, except
-          of course for Java. In addition to all the Cocoon JARs, Forrest
-          includes and uses its own version of Ant. Java 1.4+ is required.
-        </p>
-      </section><section id="cvs"><title>1.3. 
-        The old xml-forrest CVS code repository seems to be stale. What happened?
-      </title>
-        <p>
-          Forrest switched from a CVS code repository to SVN (subversion)
-          code repository. The old CVS repository is not kept current.
-        </p>
-      </section><section id="svn"><title>1.4. 
-        How can I use SVN to keep up to date with the latest codebase?
-      </title>
-        <p>
-          Follow these <link href="site:build">Building Forrest</link> notes.
-        </p>
-        <p>
-          The <link href="site:your-project">Using Forrest</link> guide provides
-          further step-by-step assistance in getting started with Forrest for your project.
-        </p>
-      </section><section id="single-document"><title>1.5. 
-        What is the best way to generate "standalone documents" using Forrest?
-      </title>
-        <p>
-          forrest site -Dproject.start-uri=myfile.pdf 
-        </p>
-        <p>
-          The <link href="site:your-project">Using Forrest</link> guide provides
-          further step-by-step assistance in getting started with Forrest for your project.
-        </p>
-      </section><section id="cygwin_mutex_error"><title>1.6. 
-        When running <code>./build.sh</code> in cygwin, I get an error:
-        <code>cygpath.exe: *** can't create title mutex, Win32 error 6</code>. 
-      </title>
-        <p>
-          This 
-          <link href="http://issues.cocoondev.org/secure/ViewIssue.jspa?key=FOR-10">appears
-            to be a bug in cygwin</link>. Please use the .bat script instead.
-        </p>
-      </section><section id="maxmemory"><title>1.7. 
-        How can I specify the amount of memory to be used by Java?
-      </title>
-        <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 <code>maxmemory</code> property in the <code>forrest.properties</code> file controls how much
-         memory Cocoon uses. Like many other properties you can copy them from the default configuration at
-         <code>src/core/fresh-site/forrest.properties</code>
-        </p>
-        <p>
-         Set the <code>ANT_OPTS</code> environment variable before you run forrest.  The exact value you set
-         it to is dependant on your JVM, but something like <code>ANT_OPTS=-Xmx500M</code> will probably work.
-        </p>
+--><document><header><title>Frequently Asked Questions</title></header><body><section id="Questions"><title>Questions</title><section id="getting_started"><title>1. Getting Started and Building Forrest</title><section id="overview"><title>1.1.  Where can I read an overview about how to work with Forrest? </title>
+        <p> See the <link href="site:your-project">Using Forrest</link> guide. </p>
+      </section><section id="requirements"><title>1.2.  What are the system requirements for Forrest? </title>
+        <p> Forrest includes everything necessary to build and run, except of course for Java. In
+          addition to all the Cocoon JARs, Forrest includes and uses its own version of Ant. Java
+          1.4+ is required. </p>
+      </section><section id="cvs"><title>1.3.  The old xml-forrest CVS code repository seems to be stale. What happened? </title>
+        <p> Forrest switched from a CVS code repository to SVN (subversion) code repository. The old
+          CVS repository is not kept current. </p>
+      </section><section id="svn"><title>1.4.  How can I use SVN to keep up to date with the latest codebase? </title>
+        <p> Follow these <link href="site:build">Building Forrest</link> notes. </p>
+        <p> The <link href="site:your-project">Using Forrest</link> guide provides further
+          step-by-step assistance in getting started with Forrest for your project. </p>
+      </section><section id="single-document"><title>1.5.  What is the best way to generate "standalone documents" using Forrest? </title>
+        <p> forrest site -Dproject.start-uri=myfile.pdf </p>
+        <p> The <link href="site:your-project">Using Forrest</link> guide provides further
+          step-by-step assistance in getting started with Forrest for your project. </p>
+      </section><section id="cygwin_mutex_error"><title>1.6.  When running <code>./build.sh</code> in cygwin, I get an error: <code>cygpath.exe:
+          *** can't create title mutex, Win32 error 6</code>. </title>
+        <p> This <link href="http://issues.cocoondev.org/secure/ViewIssue.jspa?key=FOR-10">appears
+            to be a bug in cygwin</link>. Please use the .bat script instead. </p>
+      </section><section id="maxmemory"><title>1.7.  How can I specify the amount of memory to be used by Java? </title>
+        <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 <code>maxmemory</code> property in the <code>forrest.properties</code> file controls
+          how much memory Cocoon uses. Like many other properties you can copy them from the default
+          configuration at <code>src/core/fresh-site/forrest.properties</code>
+        </p>
+        <p> Set the <code>ANT_OPTS</code> environment variable before you run forrest. The exact
+          value you set it to is dependant on your JVM, but something like
+          <code>ANT_OPTS=-Xmx500M</code> will probably work. </p>
       </section></section><section id="content_faqs"><title>2. Content Creation</title><section id="edit-content"><title>2.1. What tools can be used to edit the content?</title>
-        <p>If you are using the Apache Forrest xml
-          <link href="site:dtd-docs">document format</link> or DocBook
-          or other xml document types, then you can use any text editor
-          or even a dedicated xml editor. You must ensure valid xml. See our
-          <link href="site:catalog">configuration notes</link>
-          for various editors.
-        </p>
-        <p>There are content management systems like
-         <link href="ext:lenya">Apache Lenya</link>.
-        </p>
-        <p>Remember that Forrest can also use other source formats, such as
-          OpenOffice.org docs or JSPWiki. Use the appropriate editor for those
-          document types and ensure that the document stucture is consistent.
-          Forrest can also use "html" as the source format, in which case you
-          can use text editors or "html editors" such as the one provided
-          with the Mozilla web browser.
-        </p>
-      </section><section id="PDF-output"><title>2.2. How can I generate one pdf-file out of
-      the whole site or selected pages of the site?</title>
-      <p>Add the following entries to your site.xml file:</p>
+        <p>If you are using the Apache Forrest xml <link href="site:dtd-docs">document format</link>
+          or DocBook or other xml document types, then you can use any text editor or even a
+          dedicated xml editor. You must ensure valid xml. See our <link href="site:catalog">configuration notes</link> for various editors. </p>
+        <p>There are content management systems like <link href="ext:lenya">Apache Lenya</link>. </p>
+        <p>Remember that Forrest can also use other source formats, such as OpenOffice.org docs or
+          JSPWiki. Use the appropriate editor for those document types and ensure that the document
+          stucture is consistent. Forrest can also use "html" as the source format, in which case
+          you can use text editors or "html editors" such as the one provided with the Mozilla web
+          browser. </p>
+      </section><section id="PDF-output"><title>2.2. How can I generate one pdf-file out of the whole site or selected pages of the site?</title>
+        <p>Add the following entries to your site.xml file:</p>
         <source xml:space="preserve">
   &lt;about tab="home" label="About" href=""&gt;
  &#9;  ...
@@ -108,211 +64,182 @@
     &lt;all_sitePDF label="Full PDF" href="wholesite.pdf"/&gt;  
      ...
   &lt;/about&gt;</source>
-       <p>
-       In this case the menu labeled "About" will have 2 new items: 
-       "Full PDF" and "Full HTML". (See also
-       <link href="site:howto/pdf-tab">How to create a PDF document for each tab</link>.)
-       </p>
-       <p>
-         This assumes that you use the
-         <link href="site:linking">site.xml</link> method for your site
-         structure and navigation, rather than the old book.xml method.
-       </p>
-       </section><section id="pageBreaks"><title>2.3. How do I insert page breaks into documents?</title>
-        <p>Page breaks do not make a great deal of sense in HTML documents
-        intended for display on a screen. However, PDF documents are intended
-        for printing and therefore page breaks can be important.</p>
-        <p>To insert a page break in a PDF document simply add 
-        <em>pageBreakBefore</em> or <em>pageBreakAfter</em> to the class
-        attribute of a section.</p>
-        <p>If you want these classes to be processed in your HTML documents
-        as well you should add the following to the <code>extra-css</code>
-        element in your projects <code>skinconf.xml</code></p>
-        <source xml:space="preserve">
-        .pageBreakBefore {
-          margin-bottom: 0;
-          page-break-before: always;
-        } 
-        
-        .pageBreakAfter {
-          margin-bottom: 0;
-          page-break-after: always;
-        }
-        </source>
-      </section><section id="clickable-email-address"><title>2.4. How can I generate html-pages to show a 
-      'clickable' email-address (of the author-element)?</title>
-       <p>You would override <code>
-       $FORREST_HOME/main/webapp/skins/common/xslt/html/document2html.xsl</code>
-       and edit the "headers/authors" template.
-       </p>
-       </section><section id="link_raw"><title>2.5. How do I link to raw files such as config.txt and brochure.pdf?
-      </title>
-        <p>
-          Place them in the <code>src/documentation/content</code> 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
-          project for a demonstration of this ability.
-        </p>
-        <p>
-         For example, if
-         <code>src/documentation/content/xdocs/tools/downloads.xml</code>
-         has a <code>&lt;link href="tool.zip"&gt;</code> then put
-         <code>tool.zip</code> in the
-         <code>src/documentation/content/tools/</code> directory.
-        </p>
-        <p>
-          See the explanation and demonstration of "linking" in your local
-          'forrest seed' site.
+        <p> In this case the menu labeled "About" will have 2 new items: "Full PDF" and "Full HTML".
+          (See also <link href="site:howto/pdf-tab">How to create a PDF document for each
+          tab</link>.) </p>
+        <p> This assumes that you use the <link href="site:linking">site.xml</link> method for your
+          site structure and navigation, rather than the old book.xml method. </p>
+      </section><section id="pageBreaks"><title>2.3. How do I insert page breaks into documents?</title>
+        <p>Page breaks do not make a great deal of sense in HTML documents intended for display on a
+          screen. However, PDF documents are intended for printing and therefore page breaks can be
+          important.</p>
+        <p>To insert a page break in a PDF document simply add <em>pageBreakBefore</em> or
+            <em>pageBreakAfter</em> to the class attribute of a section.</p>
+        <p>If you want these classes to be processed in your HTML documents as well you should add
+          the following to the <code>extra-css</code> element in your projects
+          <code>skinconf.xml</code>
+        </p>
+        <source xml:space="preserve"> .pageBreakBefore { margin-bottom: 0; page-break-before: always; } .pageBreakAfter {
+          margin-bottom: 0; page-break-after: always; } </source>
+      </section><section id="clickable-email-address"><title>2.4. How can I generate html-pages to show a 'clickable' email-address (of the
+        author-element)?</title>
+        <p>You would override <code>
+            $FORREST_HOME/main/webapp/skins/common/xslt/html/document2html.xsl</code> and edit the
+          "headers/authors" template. </p>
+      </section><section id="link_raw"><title>2.5. How do I link to raw files such as config.txt and brochure.pdf? </title>
+        <p> Place them in the <code>src/documentation/content</code> 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
+          project for a demonstration of this ability. </p>
+        <p> For example, if <code>src/documentation/content/xdocs/tools/downloads.xml</code> has a
+            <code>&lt;link href="tool.zip"&gt;</code> then put <code>tool.zip</code> in the
+            <code>src/documentation/content/tools/</code> directory. </p>
+        <p> See the explanation and demonstration of "linking" in your local 'forrest seed' site.
         </p>
       </section><section id="pdf_images"><title>2.6. Images don't display in PDFs. How do I fix this?</title>
-        <p>
-&#9;  Forrest uses <link href="http://xml.apache.org/fop/">Apache FOP</link>
-          for rendering PDFs.  FOP cannot handle all image types natively, and
-          requires third-party jars to be added. FOP natively handles BMP, GIF,
-&#9;  JPG, TIFF and EPS (with a few limitations). FOP can also handle SVG
-&#9;  (via Batik!and PNG (see below). For details, see 
-&#9;  <link href="http://xml.apache.org/fop/graphics.html">FOP Graphics
-          formats</link>
+        <p> Forrest uses <link href="http://xml.apache.org/fop/">Apache FOP</link> for rendering
+          PDFs. FOP cannot handle all image types natively, and requires third-party jars to be
+          added. FOP natively handles BMP, GIF, JPG, TIFF and EPS (with a few limitations). FOP can
+          also handle SVG (via Batik!and PNG (see below). For details, see <link href="http://xml.apache.org/fop/graphics.html">FOP Graphics formats</link>
         </p>
         <p>To get PNGs working in PDFs with Jimi:</p>
         <ol>
-          <li>Download Jimi from
-           <link href="http://java.sun.com/products/jimi/">http://java.sun.com/products/jimi/</link></li>
+          <li>Download Jimi from <link href="http://java.sun.com/products/jimi/">http://java.sun.com/products/jimi/</link>
+          </li>
           <li>Unpack the Jimi distribution and copy JimiProClasses.zip to
-            <code>$FORREST/lib/optional/jimi-1.0.jar</code>.</li>
+              <code>$FORREST/lib/optional/jimi-1.0.jar</code>.</li>
         </ol>
-        <p>Alternatively you can use JAI (Java Advanced Imaging API at 
-&#9;  http://java.sun.com/products/java-media/jai). For more
-          info, see
-          <link href="http://xml.apache.org/fop/graphics.html#packages">FOP Graphics 
-          Packages</link>
-        </p>
-        <note>Due to Sun's licensing, we cannot redistribute Jimi or JAI with
-          Forrest.</note>
-      </section><section id="index.html"><title>2.7. 
-        The tab link in my site incorrectly assumes that 'index.html' is present in
-        the linked-to directory. How do I fix this?
-      </title>
-        <p>
-          In <code>tabs.xml</code>, 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
-          <code>manual/Introduction.html</code> then
-          <code>tabs.xml</code> should contain:
+        <p>Alternatively you can use JAI (Java Advanced Imaging API at
+          http://java.sun.com/products/java-media/jai). For more info, see <link href="http://xml.apache.org/fop/graphics.html#packages">FOP Graphics Packages</link>
         </p>
+        <note>Due to Sun's licensing, we cannot redistribute Jimi or JAI with Forrest.</note>
+      </section><section id="index.html"><title>2.7.  The tab link in my site incorrectly assumes that 'index.html' is present in the
+        linked-to directory. How do I fix this? </title>
+        <p> In <code>tabs.xml</code>, 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 <code>manual/Introduction.html</code> then <code>tabs.xml</code> should
+          contain: </p>
         <source xml:space="preserve">
   &lt;tab label="User Manual" href="manual"/&gt;</source>
-        <p>
-          and add this rule to the sitemap:
-        </p>
+        <p> and add this rule to the sitemap: </p>
         <source xml:space="preserve">
   &lt;map:match pattern="manual"&gt;
     &lt;map:redirect-to uri="manual/Introduction.html"/&gt;
   &lt;/map:match&gt;</source>
-     </section><section id="label-entity"><title>2.8. 
-        How to use special characters in the labels of the site.xml file?
-      </title>
-        <p>
-        Use the numeric values for character entities.
-        For example, rather than using
-        <code>&amp;ouml;</code> use
-        <code>&amp;#246;</code>
-        </p>
-        <p>
-        See the
-        <link href="http://www.w3.org/TR/xhtml-modularization/dtd_module_defs.html#a_xhtml_character_entities">XHTML Character Entities</link>
-        and see more discussion at
-        <link href="http://issues.cocoondev.org/browse/FOR-244">Issue FOR-244</link>.
+      </section><section id="defaultFileName"><title>2.8.  How can I change the default file name that Forrest will look for when I request a
+        URL like <code>http://myserver</code> or <code>http://myserver/mydir/</code>? </title>
+        <p>To change the default file name from 'index.html' (default) to 'overview.htm' you need to
+          make the following changes:</p>
+        <ol>
+          <li> Find and open the file 'cli.xconf' in your forrest program directory tree </li>
+          <li> Replace 'index.html' in &lt;default-filename&gt;index.html&lt;/default-filename&gt;
+            with 'overview.html'. </li>
+          <li> Save the changes. </li>
+          <li> Open the file 'sitemap.xmap' in your project's 'src'-directory. </li>
+          <li> Add the following code just before the end of the pipelines-element:
+        &lt;map:pipeline&gt;
+          &lt;map:match type="regexp" pattern="^.+/$"&gt;
+&gt;&gt;           &lt;map:redirect-to uri="overview.html"/&gt;
+&gt;&gt;       &lt;/map:match&gt;
+        &lt;/map:pipeline&gt;
+          </li>
+          <li> Save the changes. </li>
+        </ol>
+        <note>Please note that parts of these changes are global and will effect all your Forrests
+          run from this program directory. </note>
+      </section><section id="defaultStartPage"><title>2.9.  How can I use a start-up-page other than index.html? </title>
+        <p>Forrest by default assumes that the first page (home page) of your site is named
+          index.html. Which is good because most web servers are configured to look for index.html
+          when you call a url like http://myserver.</p>
+        <p>Like most settings in Forrest however this can be changed, for example when you want your
+          start-up-page for a CD-based documentation project to be named 'start.html'. </p>
+        <p>To change the start page of a site:</p>
+        <ol>
+          <li>Open the file 'sitemap.xmap' in your project's src-directory.</li>
+          <li>Add the following code just before the end of the pipelines-element:
+        &lt;map:pipeline&gt;
+          &lt;map:match pattern=""&gt;
+            &lt;map:redirect-to uri="start.html" /&gt;
+           &lt;/map:match&gt;
+        &lt;/map:pipeline&gt;
+          </li>
+          <li>Name the uri-attribute whatever you'd like your start page to be.</li>
+          <li>Don't forget to create that page and refer to it in your site.xml!</li>
+        </ol>
+      </section><section id="label-entity"><title>2.10.  How to use special characters in the labels of the site.xml file? </title>
+        <p> Use the numeric values for character entities. For example, rather than using
+            <code>&amp;ouml;</code> use <code>&amp;#246;</code>
         </p>
-      </section><section id="encoding"><title>2.9. Does Forrest handle accents for non-English languages?</title>
+        <p> See the <link href="http://www.w3.org/TR/xhtml-modularization/dtd_module_defs.html#a_xhtml_character_entities">XHTML Character Entities</link> and see more discussion at <link href="http://issues.cocoondev.org/browse/FOR-244">Issue FOR-244</link>. </p>
+      </section><section id="encoding"><title>2.11. Does Forrest handle accents for non-English languages?</title>
         <p>Yes, Forrest can process text in any language, so you can include:</p>
         <ul>
           <li>accents: á é í ó ú</li>
           <li>diereses: ä ë ï ö ü</li>
           <li>tildes: ã ñ &#297; õ &#361;</li>
         </ul>
-        <p>This is because sources for Forrest docs are xml documents, which can include any of these,
-          provided the encoding declared by the xml doc matches the actual encoding used in the file.
-          For example if you declare the default encoding:</p>
+        <p>This is because sources for Forrest docs are xml documents, which can include any of
+          these, provided the encoding declared by the xml doc matches the actual encoding used in
+          the file. For example if you declare the default encoding:</p>
         <source xml:space="preserve">&lt;?xml version="1.0" encoding="UTF-8"?&gt;</source>
-        <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 <code>forrest seed</code> 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 default in popular editors or systems.
-          In UNIX-like systems, most popular editors can 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 <code>LANG</code>
-          to an appropriate value, for instance:
-        </p>
+        <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
+            <code>forrest seed</code> 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
+          default in popular editors or systems. In UNIX-like systems, most popular editors can
+          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 <code>LANG</code> to an appropriate value, for instance: </p>
         <source xml:space="preserve">[localhost]$ export LANG=en_US.UTF-8</source>
-        <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 <code>encoding</code> 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>
+        <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 <code>encoding</code> 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>
         <source xml:space="preserve">&lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;</source>
-        <p>Another option is to use "character entities" such as
-        <code>&amp;ouml;</code> (ö) or the numeric form
-        <code>&amp;#246;</code> (ö).
-        </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:
-          <link href="http://orixo.com/events/gt2004/bios.html#torsten">GT2004 presentation by Torsten Schlabach</link> and 
-          <link href="http://www.alanwood.net/unicode/">Alan Wood's Unicode resources</link>.
-        </p>
-      </section></section><section id="technical"><title>3. Technical</title><section id="proxy_config"><title>3.1. I'm behind a proxy and it's preventing Plugins from 
-      being downloaded, what should I do?</title>
-        <p>You can configure the proxy in the <code>forrest.properties</code>
-        file. Set the <code>proxy.host</code> and <code>proxy.port</code>
-        accordingly (the port will default to port 80).</p>
-      </section><section id="CVS_revison_tags"><title>3.2. How can I generate html-pages to show the
-      revision tag of cvs?</title>
-      <p>If you have:<code>&lt;version&gt;$Revision: 1.30
-      $&lt;/version&gt;</code>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
-      <link href="site:your-project"> Using Forrest</link> document.</p>
-      <p>This technique could also be used for a modification date with
-      $Date: 2004/01/15 08:52:47 $</p>
-      </section><section id="cli-xconf"><title>3.3. 
-        How to control the processing of URIs by Cocoon, e.g. exclude
-        certain URIs, include other additional ones.
-      </title>
-        <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 <code>cli.xconf</code>
-          and define patterns for URIs to exclude. There are also
-          other powerful configuration features.
-        </p>
-        <p>
-          This means creating a directory <code>src/documentation/conf</code>
-          (or wherever <code>${forrest.conf-dir}</code> points) and copying
-          <code>$FORREST_HOME/main/webapp/WEB-INF/cli.xconf</code> to it.
-          Declare the location of this file in the forrest.properties
-          configuration, e.g.
-          <code>project.configfile=${project.home}/src/documentation/conf/cli.xconf</code>
-        </p>
-        <p>
-          Then edit
-          cli.xconf, and add any exclude sections that you require. The
-          default cli.xconf ignores directory links and links containing
-          'apidocs' or starting with 'api/':
+        <p>Another option is to use "character entities" such as <code>&amp;ouml;</code>
+          (ö) or the numeric form <code>&amp;#246;</code> (ö). </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: <link href="http://orixo.com/events/gt2004/bios.html#torsten">GT2004 presentation by Torsten
+            Schlabach</link> and <link href="http://www.alanwood.net/unicode/">Alan Wood's Unicode
+            resources</link>. </p>
+      </section><section id="cleanSite"><title>2.12.  How can I make Forrest properly clean up the build/site-directory? </title>
+        <p>Forrest for performance reasons doesn't clean out the build/site-directory each time you
+          compile your project. This usually doesn't matter during development but might become a
+          problem in a production environment.</p>
+        <p>To ensure a clean build call 'forrest clean site' instead of just 'forrest' so Forrest
+          will delete all build directories before creating new content. </p>
+      </section></section><section id="technical"><title>3. Technical</title><section id="proxy_config"><title>3.1. I'm behind a proxy and it's preventing Plugins from being downloaded, what should I
+        do?</title>
+        <p>You can configure the proxy in the <code>forrest.properties</code> file. Set the
+            <code>proxy.host</code> and <code>proxy.port</code> accordingly (the port will default
+          to port 80).</p>
+      </section><section id="CVS_revison_tags"><title>3.2. How can I generate html-pages to show the revision tag of cvs?</title>
+        <p>If you have:<code>&lt;version&gt;$Revision: 1.30
+          $&lt;/version&gt;</code>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 <link href="site:your-project"> Using Forrest</link> document.</p>
+        <p>This technique could also be used for a modification date with $Date: 2004/01/15 08:52:47
+          $</p>
+      </section><section id="cli-xconf"><title>3.3.  How to control the processing of URIs by Cocoon, e.g. exclude certain URIs, include
+        other additional ones. </title>
+        <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 <code>cli.xconf</code> and define patterns for URIs to
+          exclude. There are also other powerful configuration features. </p>
+        <p> This means creating a directory <code>src/documentation/conf</code> (or wherever
+            <code>${forrest.conf-dir}</code> points) and copying
+            <code>$FORREST_HOME/main/webapp/WEB-INF/cli.xconf</code> to it. Declare the location of
+          this file in the forrest.properties configuration, e.g.
+            <code>project.configfile=${project.home}/src/documentation/conf/cli.xconf</code>
         </p>
+        <p> Then edit cli.xconf, and add any exclude sections that you require. The default
+          cli.xconf ignores directory links and links containing 'apidocs' or starting with 'api/': </p>
         <source xml:space="preserve">
    ....
    &lt;!-- Includes and excludes can be used to limit which URLs are rendered --&gt;
@@ -323,42 +250,26 @@
    </strong>
    &lt;uri src="favicon.ico"/&gt;
 &lt;/cocoon&gt;</source>
-        <p>This is just an example, and you should modify it appropriately for
-          your site.</p>
-        <note>
-          Wildcards may be used.  These are a powerful feature of Cocoon's
-          <link href="site:sitemap-ref">sitemap</link>.
-          For example, <strong>foo/*</strong> would match
-          <code>foo/bar</code>, but not <code>foo/bar/baz</code>
-           &#8212; use <strong>foo/**</strong> to match that.
-        </note>
-      </section><section id="ignoring_javadocs"><title>3.4. 
-        How do I stop Forrest breaking on links to external files that may not
-        exist, like javadocs?
-      </title>
-        <p>
-          This can be done by overriding the 
-          <link href="#cli-xconf"><code>cli.xconf</code></link>
-          Cocoon config file, and defining patterns for URLs to exclude.
-        </p>
-      </section><section id="claimed_patterns"><title>3.5. Some of my files are not being processed because they use
-      common filenames.
-      </title>
-        <p>
-          Certain patterns are claimed by the default sitemaps for
-          special processing. These include:
-          <code>site, changes, todo, faq, images, my-images, skinconf,
-          community, howto</code>
+        <p>This is just an example, and you should modify it appropriately for your site.</p>
+        <note> Wildcards may be used. These are a powerful feature of Cocoon's <link href="site:sitemap-ref">sitemap</link>. For example, <strong>foo/*</strong> would match
+            <code>foo/bar</code>, but not <code>foo/bar/baz</code> &#8212; use
+          <strong>foo/**</strong> to match that. </note>
+      </section><section id="ignoring_javadocs"><title>3.4.  How do I stop Forrest breaking on links to external files that may not exist, like
+        javadocs? </title>
+        <p> This can be done by overriding the <link href="#cli-xconf">
+            <code>cli.xconf</code>
+          </link> Cocoon config file, and defining patterns for URLs to exclude. </p>
+      </section><section id="claimed_patterns"><title>3.5. Some of my files are not being processed because they use common filenames. </title>
+        <p> Certain patterns are claimed by the default sitemaps for special processing. These
+          include: <code>site, changes, todo, faq, images, my-images, skinconf, community,
+          howto</code>
+        </p>
+        <p> Sometimes there are workarounds, e.g. faq.html or faq-interview.html would fail, but
+          interview-faq.html would be fine. In future versions of Forrest we will attempt to deal
+          with this issue (<link href="http://issues.cocoondev.org/browse/FOR-217">FOR-217</link>).
         </p>
-        <p>
-          Sometimes there are workarounds, e.g. faq.html or faq-interview.html
-          would fail, but interview-faq.html would be fine.
-          In future versions of Forrest we will attempt to deal with this issue
-          (<link href="http://issues.cocoondev.org/browse/FOR-217">FOR-217</link>).
-        </p>
-      </section><section id="build_msg_a"><title>3.6. What do the symbols and numbers mean when Forrest lists each
-        document that it has built?
-      </title>
+      </section><section id="build_msg_a"><title>3.6. What do the symbols and numbers mean when Forrest lists each document that it has
+        built? </title>
         <source xml:space="preserve">
 * [56/0]     6.281s 23.0Kb  index.html
 * [0/0]      0.0060s 4.0Kb   images/project-logo.gif
@@ -368,156 +279,108 @@
 * [50/0]     1.222s 20.2Kb  dreams.html
 * [0/0]      0.535s 11.1Kb  dreams.pdf
 ...</source>
-        <p>
-         Column 1 is the page build status (*=okay X=brokenLink ^=pageSkipped).
-         Column 2 is the number of links that were gathered from that page.
-         Column 3 is the time taken.
-         Column 4 is the page size.
-        </p>
-      </section><section id="headless_operation"><title>3.7. 
-        When generating PNG images from SVG, I get an error: Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.
-      </title>
-        <p>
-          If you are using JDK 1.4.0 or newer, you can enable <em>headless</em>
-          operation by running Forrest with the <code>forrest.jvmarg</code>
-          parameter set to <code>-Djava.awt.headless=true</code>, like this:
-        </p>
+        <p> Column 1 is the page build status (*=okay X=brokenLink ^=pageSkipped). Column 2 is the
+          number of links that were gathered from that page. Column 3 is the time taken. Column 4 is
+          the page size. </p>
+      </section><section id="headless_operation"><title>3.7.  When generating PNG images from SVG, I get an error: Can't connect to X11 window
+        server using ':0.0' as the value of the DISPLAY variable. </title>
+        <p> If you are using JDK 1.4.0 or newer, you can enable <em>headless</em> operation by
+          running Forrest with the <code>forrest.jvmarg</code> parameter set to
+            <code>-Djava.awt.headless=true</code>, like this: </p>
         <source xml:space="preserve">forrest -Dforrest.jvmargs=-Djava.awt.headless=true site</source>
-        <p>
-          See also
-          <link href="http://cocoon.apache.org/2.1/faq/faq-configure-environment.html">Cocoon FAQ</link>.
-        </p>
-      </section><section id="catalog"><title>3.8. 
-        How do i configure my favourite XML editor or parser to find the
-        local Forrest DTDs?
-      </title>
-        <p>
-          Notes are provided for various tools at
-          <link href="site:catalog">Using Catalog Entity Resolver for
-          local DTDs</link>.
-        </p>
-      </section><section id="skin"><title>3.9. 
-        How to make the site look better and change its skin?
-      </title>
-        <p>
-        There are <link href="site:skins">default skins</link> provided,
-        which are configurable and so should meet the needs of most projects.
-        The aim is to provide many capabilities so that extra skins are not
-        needed.
-        </p>
-        <p>
-        See notes about
-        <link href="site:your-project/skins">configuration</link> of the skins.
-        Some projects may have special needs and can define their
-        <link href="site:your-project/new-skin">own skin</link>.
-        </p>
+        <p> See also <link href="http://cocoon.apache.org/2.1/faq/faq-configure-environment.html">Cocoon FAQ</link>. </p>
+      </section><section id="catalog"><title>3.8.  How do i configure my favourite XML editor or parser to find the local Forrest
+        DTDs? </title>
+        <p> Notes are provided for various tools at <link href="site:catalog">Using Catalog Entity
+            Resolver for local DTDs</link>. </p>
+      </section><section id="skin"><title>3.9.  How to make the site look better and change its skin? </title>
+        <p> There are <link href="site:skins">default skins</link> provided, which are configurable
+          and so should meet the needs of most projects. The aim is to provide many capabilities so
+          that extra skins are not needed. </p>
+        <p> See notes about <link href="site:your-project/skins">configuration</link> of the skins.
+          Some projects may have special needs and can define their <link href="site:your-project/new-skin">own skin</link>. </p>
       </section><section id="xsp"><title>3.10. How do I enable <acronym title="eXtensible Server Pages">XSP</acronym> processing?</title>
-        <p>First consider whether your needs would be better met by Cocoon itself, rather than Forrest.
-        </p>
-        <p>That said, there are valid reasons for wanting programmatically generated content, so here is how to enable
-          XSP:</p>
+        <p>First consider whether your needs would be better met by Cocoon itself, rather than
+          Forrest. </p>
+        <p>That said, there are valid reasons for wanting programmatically generated content, so
+          here is how to enable XSP:</p>
         <ol>
-          <li>Download 
-          <link href="http://cvs.apache.org/viewcvs.cgi/*checkout*/cocoon-2.1/lib/optional/jdtcore-2.1.0.jar?rev=1.1&amp;content-type=application/java">jdtcore-2.1.0.jar</link>,
-            and copy it to the $FORREST_HOME/main/webapp/WEB-INF/lib directory
-            (or lib/core/ directory in the source
-            distribution).</li>
-          <li><p>
-              Add the following generator definition in the map:generators section
-              of your <link href="site:project-sitemap">project sitemap</link></p>
+          <li>Download <link href="http://cvs.apache.org/viewcvs.cgi/*checkout*/cocoon-2.1/lib/optional/jdtcore-2.1.0.jar?rev=1.1&amp;content-type=application/java">jdtcore-2.1.0.jar</link>, and copy it to the $FORREST_HOME/main/webapp/WEB-INF/lib
+            directory (or lib/core/ directory in the source distribution).</li>
+          <li>
+            <p> Add the following generator definition in the map:generators section of your <link href="site:project-sitemap">project sitemap</link>
+            </p>
             <source xml:space="preserve">
   &lt;map:generator name="serverpages"
      pool-grow="2" pool-max="32" pool-min="4"
      src="org.apache.cocoon.generation.ServerPagesGenerator"/&gt;</source>
           </li>
-          <li><p>Decide how you want to use XSP.  For single files, you could just define a *.xml matcher:</p>
+          <li>
+            <p>Decide how you want to use XSP. For single files, you could just define a *.xml
+              matcher:</p>
             <source xml:space="preserve">
 &lt;map:match pattern="dynamic.xml"&gt;
   &lt;map:generate src="content/xdocs/dynamic.xsp" type="serverpages"/&gt;
   ...
   &lt;map:serialize type="xml"/&gt;
 &lt;/map:match&gt;</source>
-            <p>You may instead wish to override forrest.xmap to define a general mapping for XSPs.</p>
+            <p>You may instead wish to override forrest.xmap to define a general mapping for
+            XSPs.</p>
           </li>
         </ol>
-        <p>See also the 
-        <link href="http://wiki.apache.org/cocoon/AddingXSPToForrest">AddingXSPToForrest</link> Wiki page.</p>
-      </section><section id="breadcrumbs"><title>3.11. How do breadcrumbs work?  Why don't they work locally?</title>
-      <p>Breadcrumbs begin with up to three URLs specified in
-      <code>skinconf.xml</code>.  Here is what the Forrest site uses:</p>
-      <source xml:space="preserve">
+        <p>See also the <link href="http://wiki.apache.org/cocoon/AddingXSPToForrest">AddingXSPToForrest</link> Wiki page.</p>
+      </section><section id="breadcrumbs"><title>3.11. How do breadcrumbs work? Why don't they work locally?</title>
+        <p>Breadcrumbs begin with up to three URLs specified in <code>skinconf.xml</code>. Here is
+          what the Forrest site uses:</p>
+        <source xml:space="preserve">
   &lt;trail&gt;
     &lt;link1 name="apache" href="http://www.apache.org/"/&gt;
     &lt;link2 name="xml.apache" href="http://xml.apache.org/"/&gt;
     &lt;link3 name="" href=""/&gt;
   &lt;/trail&gt;</source>
-      <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 <code>skinconf.xml</code>.
-      </p>
+        <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 <code>skinconf.xml</code>. </p>
       </section><section id="run_port"><title>3.12. How do I make <code>forrest run</code> listen on a different port?</title>
-      <p><code>forrest run -Dforrest.jvmargs="-Djetty.port=80"</code></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 <code>forrest run</code>
-      </p>
-      </section></section><section id="old_faqs"><title>4. Older version: 0.6</title><section id="old_claimed_patterns"><title>4.1. Some of my files are not being processed because they use
-      common filenames.
-      </title>
-        <p>
-          Certain patterns are claimed by the default sitemaps for
-          special processing. These include:
-          <code>site, changes, todo, faq, images, my-images, skinconf,
-          community, howto</code>
-        </p>
-        <p>
-          Sometimes there are workarounds, e.g. faq.html or faq-interview.html
-          would fail, but interview-faq.html would be fine.
-          In future versions of Forrest we will attempt to deal with this issue
-          (<link href="http://issues.cocoondev.org/browse/FOR-217">FOR-217</link>).
-        </p>
-      </section></section><section id="general"><title>5. General</title><section id="generating_menus"><title>5.1. What is the relationship between <code>site.xml</code> and
-        <code>book.xml</code>?
-      </title>
-        <p>
-          One <code>site.xml</code> file in your project root can replace all the book.xml files
-          (one per directory) in your site.  Internally, Forrest uses <code>site.xml</code> 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 <code>site.xml</code>-generated menus aren't appropriate.
-          See <link href="site:linking">Menus and Linking</link>.
-      </p>
-      </section><section id="docbook"><title>5.2. 
-        How do I use DocBook as the xml documentation format?
-      </title>
         <p>
-         There are two ways. Forrest has a <code>simplified-docbook</code> 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 elements.
+          <code>forrest run -Dforrest.jvmargs="-Djetty.port=80"</code>
         </p>
-        <p>
-         The other way is to use the full DocBook stylesheets directly. The DocBook
-         DTDs are shipped with Forrest and automatically handled. However, you
-         will need to have the DocBook stylesheets on your system (they are
-         too massive to ship with Forrest) and configure Forrest accordingly.
-         You will need to create a
-         <link href="site:project-sitemap">project sitemap</link>
-          as explained in
-         <link href="site:your-project">Using Forrest</link>
-         and add matches to handle your DocBook documents.
-         Here is an example. Note that you need to change it to suit your
-         situation. The match must be very specific so that only the
-         DocBook documents are matched. The rest of the documents will be
-         handled by Forrest core. Powerful regex capabilities are available.
+        <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 <code>forrest run</code>
         </p>
+      </section></section><section id="old_faqs"><title>4. Older version: 0.6</title><section id="old_claimed_patterns"><title>4.1. Some of my files are not being processed because they use common filenames. </title>
+        <p> Certain patterns are claimed by the default sitemaps for special processing. These
+          include: <code>site, changes, todo, faq, images, my-images, skinconf, community,
+          howto</code>
+        </p>
+        <p> Sometimes there are workarounds, e.g. faq.html or faq-interview.html would fail, but
+          interview-faq.html would be fine. In future versions of Forrest we will attempt to deal
+          with this issue (<link href="http://issues.cocoondev.org/browse/FOR-217">FOR-217</link>).
+        </p>
+      </section></section><section id="general"><title>5. General</title><section id="generating_menus"><title>5.1. What is the relationship between <code>site.xml</code> and <code>book.xml</code>? </title>
+        <p> One <code>site.xml</code> file in your project root can replace all the book.xml files (one per
+          directory) in your site. Internally, Forrest uses <code>site.xml</code> 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
+          <code>site.xml</code>-generated menus aren't appropriate. See <link href="site:linking">Menus and
+            Linking</link>. </p>
+      </section><section id="docbook"><title>5.2.  How do I use DocBook as the xml documentation format? </title>
+        <p> There are two ways. Forrest has a <code>simplified-docbook</code> 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
+          elements. </p>
+        <p> The other way is to use the full DocBook stylesheets directly. The DocBook DTDs are
+          shipped with Forrest and automatically handled. However, you will need to have the DocBook
+          stylesheets on your system (they are too massive to ship with Forrest) and configure
+          Forrest accordingly. You will need to create a <link href="site:project-sitemap">project
+            sitemap</link> as explained in <link href="site:your-project">Using Forrest</link> and
+          add matches to handle your DocBook documents. Here is an example. Note that you need to
+          change it to suit your situation. The match must be very specific so that only the DocBook
+          documents are matched. The rest of the documents will be handled by Forrest core. Powerful
+          regex capabilities are available. </p>
         <source xml:space="preserve">&lt;?xml version="1.0"?&gt;
 &lt;map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0"&gt;
  &lt;map:pipelines&gt;
@@ -530,78 +393,41 @@
    &lt;/map:match&gt;
   &lt;/map:pipeline&gt;
  &lt;/map:pipelines&gt;
-&lt;/map:sitemap&gt;
-        </source>
-        <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>
-        <p>
-         Ensure that the document type declaration in your xml instance is
-         well specified. Use a public identifier. The DTD will then be properly
-         resolved by Forrest. If you need to use different DTDs, then see
-         <link href="site:your-project/new_dtd">Using Forrest</link>
-         for configuration guidance.
-        </p>
-      </section><section id="version"><title>5.3. 
-        How to report which version of Forrest is being used and the
-        properties that are set?
-      </title>
-        <p>
-          Do <code>'forrest -projecthelp'</code> or <code>'./build.sh'</code>
-          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 <code>'forrest -v'</code> will provide verbose build messages.
-        </p>
-      </section><section id="logs"><title>5.4. 
-        Where are the log files to find more infomation about errors?
-      </title>
-        <p>
-          The logfiles are at <code>build/webapp/WEB-INF/logs/</code>
-        </p>
-        <p>
-          The log level can be raised with the <code>logkit.xconf</code>
-          configuration. If you are using Forrest in the interactive webapp
-          mode (which is generally easiest for debugging errors) then see the
-          <code>build/webapp/WEB-INF/logkit.xconf</code> file.
-          If you are generating a static site (with command-line 'forrest')
-          then copy <code>$FORREST_HOME/main/webapp/WEB-INF/logkit.xconf</code>
-          to your project at
-          <code>src/documentation/content/conf/logkit.xconf</code>
-          and modify it. See more information and efficiency tips with
-          <link href="http://wiki.apache.org/cocoon/ExploringTheLogs">Cocoon logging</link>.
-        </p>
-        <p>
-          Doing <code>'forrest -v'</code> will provide verbose build messages
-          to the standard output.
-        </p>
-      </section><section id="how_can_I_help"><title>5.5. 
-        How to help?
-      </title>
-        <p>
-          Join one of the Forrest project
-          <link href="site:mail-lists">mailing lists</link>
-          and tell us what you would like to see improved.  We regard all feedback
-          as valuable, particularly from newcomers&#8212;often, close proximity
-          blinds software developers to faults that are obvious to everyone
-          else. Don't be shy!
-        </p>
-      </section><section id="patch"><title>5.6. 
-        How to contribute a patch?
-      </title>
-        <p>Please send all contributions via our
-          <link href="site:bugs">issue tracker</link>.
-          Here are notes about
-          <link href="site:contrib/patch">making patches</link>.
-        </p>
-        <p>More info about contributing can be found at the 
-          <link href="site:contrib">Contributing to Forrest</link> page.
-          It is always a good idea to check the Forrest
-          <link href="site:bugs">issue tracker</link>
-          before diving in.
-        </p>
+&lt;/map:sitemap&gt;</source>
+        <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>
+        <p> Ensure that the document type declaration in your xml instance is well specified. Use a
+          public identifier. The DTD will then be properly resolved by Forrest. If you need to use
+          different DTDs, then see <link href="site:your-project/new_dtd">Using Forrest</link> for
+          configuration guidance. </p>
+      </section><section id="version"><title>5.3.  How to report which version of Forrest is being used and the properties that are
+        set? </title>
+        <p> Do <code>'forrest -projecthelp'</code> or <code>'./build.sh'</code> 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 <code>'forrest -v'</code> will provide verbose build
+          messages. </p>
+      </section><section id="logs"><title>5.4.  Where are the log files to find more infomation about errors? </title>
+        <p> The logfiles are at <code>build/webapp/WEB-INF/logs/</code>
+        </p>
+        <p> The log level can be raised with the <code>logkit.xconf</code> configuration. If you are
+          using Forrest in the interactive webapp mode (which is generally easiest for debugging
+          errors) then see the <code>build/webapp/WEB-INF/logkit.xconf</code> file. If you are
+          generating a static site (with command-line 'forrest') then copy
+            <code>$FORREST_HOME/main/webapp/WEB-INF/logkit.xconf</code> to your project at
+            <code>src/documentation/content/conf/logkit.xconf</code> and modify it. See more
+          information and efficiency tips with <link href="http://wiki.apache.org/cocoon/ExploringTheLogs">Cocoon logging</link>. </p>
+        <p> Doing <code>'forrest -v'</code> will provide verbose build messages to the standard
+          output. </p>
+      </section><section id="how_can_I_help"><title>5.5.  How to help? </title>
+        <p> Join one of the Forrest project <link href="site:mail-lists">mailing lists</link> and
+          tell us what you would like to see improved. We regard all feedback as valuable,
+          particularly from newcomers&#8212;often, close proximity blinds software developers to
+          faults that are obvious to everyone else. Don't be shy! </p>
+      </section><section id="patch"><title>5.6.  How to contribute a patch? </title>
+        <p>Please send all contributions via our <link href="site:bugs">issue tracker</link>. Here
+          are notes about <link href="site:contrib/patch">making patches</link>. </p>
+        <p>More info about contributing can be found at the <link href="site:contrib">Contributing
+            to Forrest</link> page. It is always a good idea to check the Forrest <link href="site:bugs">issue tracker</link> before diving in. </p>
       </section></section></section></body></document>

Modified: forrest/site/0.7/docs/forrest-contract.html
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/forrest-contract.html?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
--- forrest/site/0.7/docs/forrest-contract.html (original)
+++ forrest/site/0.7/docs/forrest-contract.html Thu May  5 20:54:30 2005
@@ -422,7 +422,9 @@
 //  --></script>
 </div>
 <div class="copyright">
- Copyright &copy; 2002-2005 The Apache Software Foundation.</div>
+        Copyright &copy;
+         2002-2005 <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
+</div>
 <!--+
     |end bottomstrip
     +-->

Modified: forrest/site/0.7/docs/forrest-contract.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/forrest-contract.pdf?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/0.7/docs/forrestbar.html
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/forrestbar.html?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
--- forrest/site/0.7/docs/forrestbar.html (original)
+++ forrest/site/0.7/docs/forrestbar.html Thu May  5 20:54:30 2005
@@ -337,7 +337,9 @@
 //  --></script>
 </div>
 <div class="copyright">
- Copyright &copy; 2002-2005 The Apache Software Foundation.</div>
+        Copyright &copy;
+         2002-2005 <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
+</div>
 <!--+
     |end bottomstrip
     +-->

Modified: forrest/site/0.7/docs/forrestbar.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/forrestbar.pdf?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/0.7/docs/forrestbot-web-interface.html
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/forrestbot-web-interface.html?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
--- forrest/site/0.7/docs/forrestbot-web-interface.html (original)
+++ forrest/site/0.7/docs/forrestbot-web-interface.html Thu May  5 20:54:30 2005
@@ -509,7 +509,9 @@
 //  --></script>
 </div>
 <div class="copyright">
- Copyright &copy; 2002-2005 The Apache Software Foundation.</div>
+        Copyright &copy;
+         2002-2005 <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
+</div>
 <!--+
     |end bottomstrip
     +-->

Modified: forrest/site/0.7/docs/forrestbot-web-interface.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/forrestbot-web-interface.pdf?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/0.7/docs/forrestbot.html
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/forrestbot.html?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
--- forrest/site/0.7/docs/forrestbot.html (original)
+++ forrest/site/0.7/docs/forrestbot.html Thu May  5 20:54:30 2005
@@ -1227,7 +1227,9 @@
 //  --></script>
 </div>
 <div class="copyright">
- Copyright &copy; 2002-2005 The Apache Software Foundation.</div>
+        Copyright &copy;
+         2002-2005 <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
+</div>
 <!--+
     |end bottomstrip
     +-->

Modified: forrest/site/0.7/docs/forrestbot.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/forrestbot.pdf?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/0.7/docs/howto-v13.dtdx.html
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/howto-v13.dtdx.html?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
--- forrest/site/0.7/docs/howto-v13.dtdx.html (original)
+++ forrest/site/0.7/docs/howto-v13.dtdx.html Thu May  5 20:54:30 2005
@@ -3811,7 +3811,9 @@
 //  --></script>
 </div>
 <div class="copyright">
- Copyright &copy; 2002-2005 The Apache Software Foundation.</div>
+        Copyright &copy;
+         2002-2005 <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
+</div>
 <!--+
     |end bottomstrip
     +-->

Modified: forrest/site/0.7/docs/howto-v13.dtdx.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/howto-v13.dtdx.pdf?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/0.7/docs/howto-v20.dtdx.html
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/howto-v20.dtdx.html?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
--- forrest/site/0.7/docs/howto-v20.dtdx.html (original)
+++ forrest/site/0.7/docs/howto-v20.dtdx.html Thu May  5 20:54:30 2005
@@ -3892,7 +3892,9 @@
 //  --></script>
 </div>
 <div class="copyright">
- Copyright &copy; 2002-2005 The Apache Software Foundation.</div>
+        Copyright &copy;
+         2002-2005 <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
+</div>
 <!--+
     |end bottomstrip
     +-->

Modified: forrest/site/0.7/docs/howto-v20.dtdx.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/howto-v20.dtdx.pdf?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/0.7/docs/howto/forrest.xmap.html
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/howto/forrest.xmap.html?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
--- forrest/site/0.7/docs/howto/forrest.xmap.html (original)
+++ forrest/site/0.7/docs/howto/forrest.xmap.html Thu May  5 20:54:30 2005
@@ -742,7 +742,9 @@
 //  --></script>
 </div>
 <div class="copyright">
- Copyright &copy; 2002-2005 The Apache Software Foundation.</div>
+        Copyright &copy;
+         2002-2005 <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
+</div>
 <!--+
     |end bottomstrip
     +-->

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

Modified: forrest/site/0.7/docs/howto/howto-asf-mirror.html
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/howto/howto-asf-mirror.html?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
--- forrest/site/0.7/docs/howto/howto-asf-mirror.html (original)
+++ forrest/site/0.7/docs/howto/howto-asf-mirror.html Thu May  5 20:54:30 2005
@@ -206,28 +206,7 @@
 </li>
 </ul>
 </div>
-  
-<header>
-    
-<title>Generate an ASF mirrors page using interactive web form</title>
-
-    
-<a name="N10016"></a><a name="Overview"></a>
-<h2 class="underlined_10">Overview</h2>
-<div class="section">
-<p>Include html form elements
-    into a forrest-generated html page. For example, this enables building
-    automated download mirror pages for ASF project websites.
-    </p>
-</div>
-
-    
-<last-modified-content-date date="2005-04-20"></last-modified-content-date>
-  
-</header>
-
-  
-<a name="N10021"></a><a name="Intended Audience"></a>
+<a name="N10010"></a><a name="Intended Audience"></a>
 <h2 class="underlined_10">Intended Audience</h2>
 <div class="section">
 <ul>
@@ -240,9 +219,7 @@
     
 </ul>
 </div>
-
-  
-<a name="N10030"></a><a name="Purpose"></a>
+<a name="N1001E"></a><a name="Purpose"></a>
 <h2 class="underlined_10">Purpose</h2>
 <div class="section">
 <p>All Apache projects use dynamically generated download pages
@@ -256,9 +233,7 @@
     how to process additional files.
     </p>
 </div>
-
-  
-<a name="N1003C"></a><a name="Prerequisites"></a>
+<a name="N10029"></a><a name="Prerequisites"></a>
 <h2 class="underlined_10">Prerequisites</h2>
 <div class="section">
 <ul>
@@ -276,12 +251,10 @@
     
 </ul>
 </div>
-
-  
-<a name="N10056"></a><a name="Steps"></a>
+<a name="N10042"></a><a name="Steps"></a>
 <h2 class="underlined_10">Steps</h2>
 <div class="section">
-<a name="N1005B"></a><a name="cgi"></a>
+<a name="N10047"></a><a name="cgi"></a>
 <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
@@ -292,7 +265,7 @@
        (copy the Forrest project's
         <a href="http://svn.apache.org/repos/asf/forrest/trunk/site-author/content/mirrors.cgi">mirrors.cgi</a>)
       </p>
-<a name="N10071"></a><a name="html"></a>
+<a name="N1005D"></a><a name="html"></a>
 <h3 class="underlined_5">Add the mirrors.html to xdocs directory</h3>
 <p>This file contains the html content of your mirror page, including
         the html form elements which drive the mirror selection. It also
@@ -305,7 +278,7 @@
         <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.)
       </p>
-<a name="N10085"></a><a name="menu"></a>
+<a name="N10071"></a><a name="menu"></a>
 <h3 class="underlined_5">Add a menu entry for Download</h3>
 <p>Add an entry to your site.xml navigation. For example ...
       </p>
@@ -316,7 +289,7 @@
   &lt;download label="Download" href="http://forrest.apache.org/mirrors.cgi"/&gt;
   &lt;download_html href="mirrors.html"/&gt;&lt;!-- so the page is part of a tab --&gt;
   ...</pre>
-<a name="N10093"></a><a name="link"></a>
+<a name="N1007F"></a><a name="link"></a>
 <h3 class="underlined_5">Cause the mirrors.html to be processed as an extra file</h3>
 <p>Forrest gathers the links that are to be crawled, by reading site.xml
         and by finding any other internal links in the actual documents.
@@ -335,7 +308,7 @@
 &lt;uris name="mirrors" follow-links="false"&gt;
   &lt;uri type="append" src="mirrors.html"/&gt;
 &lt;/uris&gt;</pre>
-<a name="N100AE"></a><a name="forrest"></a>
+<a name="N1009A"></a><a name="forrest"></a>
 <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
@@ -352,7 +325,6 @@
 </div>
 </div>
 </div>
-
 </div>
 <!--+
     |end content
@@ -369,7 +341,9 @@
 //  --></script>
 </div>
 <div class="copyright">
- Copyright &copy; 2002-2005 The Apache Software Foundation.</div>
+        Copyright &copy;
+         2002-2005 <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
+</div>
 <!--+
     |end bottomstrip
     +-->

Modified: forrest/site/0.7/docs/howto/howto-asf-mirror.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/howto/howto-asf-mirror.pdf?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/0.7/docs/howto/howto-buildPlugin.html
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/howto/howto-buildPlugin.html?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
--- forrest/site/0.7/docs/howto/howto-buildPlugin.html (original)
+++ forrest/site/0.7/docs/howto/howto-buildPlugin.html Thu May  5 20:54:30 2005
@@ -256,33 +256,7 @@
 </li>
 </ul>
 </div>
-  
-<header>
-    
-<title>How to Build a Plugin</title>
-
-    
-<span class="version">0.1</span>
-
-    <a name="N1001C"></a><a name="Overview"></a>
-<h2 class="underlined_10">Overview</h2>
-<div class="section">
-<p>This How-To describes the steps necessary to build a plugin for 
-    Forrest. Forrest uses plugins to add new input formats, output formats
-    and to change its default behaviour. Since plugins are downloaded when
-    needed and can be hosted at any location, plugin code can be developed 
-    independently of Apache Forrest. This how-to describes each of the major
-    steps in creating a plugin and then works through some examples of 
-    plugin creation in order to illustrate the materials.</p>
-</div>
-
-    
-<last-modified-content-date date="2005-04-12"></last-modified-content-date>
-  
-</header>
-
-  
-<a name="N10027"></a><a name="Intended Audience"></a>
+<a name="N10013"></a><a name="Intended Audience"></a>
 <h2 class="underlined_10">Intended Audience</h2>
 <div class="section">
 <p>Users needing to add additional input formats or output formats or
@@ -301,17 +275,13 @@
     plugins. Forrest 0.6 will not work!!!</div>
 </div>
 </div>
-
-  
-<a name="N10039"></a><a name="Purpose"></a>
+<a name="N10024"></a><a name="Purpose"></a>
 <h2 class="underlined_10">Purpose</h2>
 <div class="section">
 <p>This How-To will illustrate how to build a plugin, publish a plugin
     and configure a Forrest project to use their plugin.</p>
 </div>
-
-  
-<a name="N10042"></a><a name="Prerequisites"></a>
+<a name="N1002C"></a><a name="Prerequisites"></a>
 <h2 class="underlined_10">Prerequisites</h2>
 <div class="section">
 <p>Plugin developers should have:</p>
@@ -331,19 +301,17 @@
     
 </ul>
 </div>
-
-  
-<a name="N1005E"></a><a name="Steps"></a>
+<a name="N10047"></a><a name="Steps"></a>
 <h2 class="underlined_10">Steps</h2>
 <div class="section">
 <p>Here is how to proceed.</p>
-<a name="N10066"></a><a name="typeOfPlugin"></a>
+<a name="N1004F"></a><a name="typeOfPlugin"></a>
 <h3 class="underlined_5">Type of Plugin</h3>
 <p>There are three types of plugin, each with a clear purpose, you
       must first decide which 
       <a href="../../docs/plugins/pluginInfrastructure.html">type of plugin</a>
       you need to build.</p>
-<a name="N10074"></a><a name="ant"></a>
+<a name="N1005D"></a><a name="ant"></a>
 <h3 class="underlined_5">Make ant available on the command-line</h3>
 <p>
         The following instructions rely heavily on
@@ -364,7 +332,7 @@
         to $ANT_HOME/lib directory, otherwise your plugins will go across
         the network to get the DTDs on every parse.
       </p>
-<a name="N10088"></a><a name="seed"></a>
+<a name="N10071"></a><a name="seed"></a>
 <h3 class="underlined_5">Seed a New Plugin</h3>
 <p>Regardless of the type of plugin you are building, the directory
       structure is almost identical, as are most of the requried
@@ -396,7 +364,7 @@
       <a href="../../docs/plugins/pluginInfrastructure.html">Plugin
       Infrastructure</a> for more information about the plugin
       directory structure and configuration files.</p>
-<a name="N100B3"></a><a name="edit-template"></a>
+<a name="N1009C"></a><a name="edit-template"></a>
 <h4>Edit the Plugin Template</h4>
 <p>You now have a skeleton plugin project. However, it doesn't do 
         anything useful yet. Now is a good time to edit some of the files
@@ -410,7 +378,7 @@
         </div>
 </div>
 <p>Here are some general notes:</p>
-<a name="N100C6"></a><a name="status"></a>
+<a name="N100AF"></a><a name="status"></a>
 <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.
@@ -420,23 +388,23 @@
 <p>As you work on the plugin you should record all major changes in
           this file so that it can then be used as a changelog for your
           plugin.</p>
-<a name="N100D6"></a><a name="forrest-properties"></a>
+<a name="N100BF"></a><a name="forrest-properties"></a>
 <h5>forrest.properties</h5>
 <p>This file defines many configuration parameters for Forrest. It
           does not need to be customised in most cases. However, see
           for more details.</p>
-<a name="N100E0"></a><a name="skinconf"></a>
+<a name="N100C9"></a><a name="skinconf"></a>
 <h5>src/documentation/skinconf.xml</h5>
 <p>This configures the skin for your plugins documentation. There
           are some items that need to be configured in here, for example, the
           copyright information. The file is heavily commented so probably
           best to read through it, changing what you need to.</p>
-<a name="N100EA"></a><a name="doc"></a>
+<a name="N100D3"></a><a name="doc"></a>
 <h5>Documentation</h5>
 <p>It is also a good idea to start writing the documentation at this
           stage. The above process created a very simple plugin documentation
           site for you. All you have to do is add the content.</p>
-<a name="N100F4"></a><a name="hosted"></a>
+<a name="N100DD"></a><a name="hosted"></a>
 <h5>Style notes for plugins hosted at forrest.apapche.org</h5>
 <p>
             After seeding a new plugin, copy the configuration from an
@@ -444,7 +412,7 @@
             Copy src/documentation/skinconf.xml and 
             src/documentation/content/xdocs/images/project-logo.gif
           </p>
-<a name="N10100"></a><a name="edit-sitemap"></a>
+<a name="N100E9"></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
       at a strategic place in the Forrest pipeline. It is in this file
@@ -463,7 +431,7 @@
       all development work on Forrest, you will find
       the <a href="../../mail-lists.html#forrest-dev">developer mailing list</a>
       a very good resource (check the archives before posting, please).</p>
-<a name="N10127"></a><a name="components"></a>
+<a name="N10110"></a><a name="components"></a>
 <h4>Components, Actions and Resources</h4>
 <p>If your plugin uses any components (i.e. generators, transformers or
         serializers), actions or resources they must
@@ -478,13 +446,13 @@
         <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="N1014F"></a><a name="resources"></a>
+<a name="N10138"></a><a name="resources"></a>
 <h3 class="underlined_5">Create the Necessary Resource Files</h3>
 <div class="frame fixme">
 <div class="label">Fixme (rdg)</div>
 <div class="content">Discuss the XSL files and other such resources</div>
 </div>
-<a name="N1015A"></a><a name="samples"></a>
+<a name="N10143"></a><a name="samples"></a>
 <h3 class="underlined_5">Create Samples in the Documentation</h3>
 <p>Plugin documentation should provide (as a minimum) an
       index page that provides an overview and a set of samples that demonstrate
@@ -494,7 +462,7 @@
       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="N10170"></a><a name="test"></a>
+<a name="N10159"></a><a name="test"></a>
 <h3 class="underlined_5">Testing a Plugin</h3>
 <p>Since your documentation for the plugin illustrates all of its 
       functionality, you can use that site for testing the plugin. However, you
@@ -507,7 +475,7 @@
 <div class="frame note">
 <div class="label">Note</div>
 <div class="content">You can also use <span class="codefrag">forrest run</span> to interactively examine
-      your documentation (point your prowser at 
+      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 
@@ -520,9 +488,9 @@
       as writing your tests.</p>
 <p>Ensure that your sitemaps are robust and handle matches for files
       in sub-directories, as well as those at the root level.</p>
-<a name="N1019E"></a><a name="release"></a>
+<a name="N10187"></a><a name="release"></a>
 <h3 class="underlined_5">Releasing a Plugin</h3>
-<a name="N101A4"></a><a name="register"></a>
+<a name="N1018D"></a><a name="register"></a>
 <h4>Register the Plugin with Apache Forrest</h4>
 <div class="frame fixme">
 <div class="label">Fixme (rdg)</div>
@@ -533,7 +501,7 @@
 <div class="content">Describe making a request of Forrest devs for 
         inclusion</div>
 </div>
-<a name="N101B3"></a><a name="deploy"></a>
+<a name="N1019C"></a><a name="deploy"></a>
 <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 
@@ -562,29 +530,29 @@
         that your 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>
-<a name="N101E6"></a><a name="examples"></a>
+<a name="N101CF"></a><a name="examples"></a>
 <h3 class="underlined_5">Examples</h3>
 <p>This section will provide some example plugins to help illustrate the
       steps discussed above.</p>
-<a name="N101EF"></a><a name="input"></a>
+<a name="N101D8"></a><a name="input"></a>
 <h4>Input Plugin</h4>
 <div class="frame fixme">
 <div class="label">Fixme (RDG)</div>
 <div class="content">Discuss OpenOffice.org plugin here</div>
 </div>
-<a name="N101FA"></a><a name="output"></a>
+<a name="N101E3"></a><a name="output"></a>
 <h4>Output Plugin</h4>
 <div class="frame fixme">
 <div class="label">Fixme (RDG)</div>
 <div class="content">Discuss s5 plugin here</div>
 </div>
-<a name="N10205"></a><a name="internal"></a>
+<a name="N101EE"></a><a name="internal"></a>
 <h4>Internal Plugin</h4>
 <div class="frame fixme">
 <div class="label">Fixme (RDG)</div>
 <div class="content">Discuss IMSManifest plugin here</div>
 </div>
-<a name="N10211"></a><a name="extension"></a>
+<a name="N101FA"></a><a name="extension"></a>
 <h3 class="underlined_5">Further Reading</h3>
 <ul>
         
@@ -595,7 +563,7 @@
 <a href="../../docs/plugins/">Plugins Documentation</a> for users</li>
       
 </ul>
-<a name="N10227"></a><a name="summarise"></a>
+<a name="N10210"></a><a name="summarise"></a>
 <h3 class="underlined_5">Summarise the Entire Process</h3>
 <div class="frame fixme">
 <div class="label">Fixme (rdg)</div>
@@ -603,7 +571,6 @@
       This helps to reinforce the main points of your How-To.</div>
 </div>
 </div>
-
 </div>
 <!--+
     |end content
@@ -620,7 +587,9 @@
 //  --></script>
 </div>
 <div class="copyright">
- Copyright &copy; 2002-2005 The Apache Software Foundation.</div>
+        Copyright &copy;
+         2002-2005 <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
+</div>
 <!--+
     |end bottomstrip
     +-->

Modified: forrest/site/0.7/docs/howto/howto-buildPlugin.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/howto/howto-buildPlugin.pdf?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/0.7/docs/howto/howto-corner-images.html
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/howto/howto-corner-images.html?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
--- forrest/site/0.7/docs/howto/howto-corner-images.html (original)
+++ forrest/site/0.7/docs/howto/howto-corner-images.html Thu May  5 20:54:30 2005
@@ -203,26 +203,7 @@
 </li>
 </ul>
 </div>
- 
-<header>
-  
-<title>How to modify the color of generated corner images</title>
-  
-<a name="N10016"></a><a name="Overview"></a>
-<h2 class="underlined_10">Overview</h2>
-<div class="section">
-<p>
-    This How-To describes how to modify the corner images that appear in
-    the menu and tabs of the skins.
-  </p>
-</div>
-  
-<last-modified-content-date date="2004-11-05"></last-modified-content-date>
- 
-</header>
-
-  
-<a name="N10021"></a><a name="Intended Audience"></a>
+<a name="N10010"></a><a name="Intended Audience"></a>
 <h2 class="underlined_10">Intended Audience</h2>
 <div class="section">
 <p>
@@ -234,9 +215,7 @@
       the corner image generation process.
     </p>
 </div>
-  
-  
-<a name="N1002D"></a><a name="Purpose"></a>
+<a name="N1001B"></a><a name="Purpose"></a>
 <h2 class="underlined_10">Purpose</h2>
 <div class="section">
 <p>
@@ -246,9 +225,7 @@
       the corner images to be suitable for your own skin colors.
     </p>
 </div>
-
-  
-<a name="N1003A"></a><a name="Prerequisites"></a>
+<a name="N10027"></a><a name="Prerequisites"></a>
 <h2 class="underlined_10">Prerequisites</h2>
 <div class="section">
 <ul>
@@ -262,9 +239,7 @@
     
 </ul>
 </div>
-
-  
-<a name="N10051"></a><a name="Steps"></a>
+<a name="N1003D"></a><a name="Steps"></a>
 <h2 class="underlined_10">Steps</h2>
 <div class="section">
 <p>
@@ -273,7 +248,7 @@
       colors for these images by modifying the
       <span class="codefrag">src/documentation/skinconf.xml</span> of a project.
     </p>
-<a name="N1005C"></a><a name="css-files"></a>
+<a name="N10048"></a><a name="css-files"></a>
 <h3 class="underlined_5">Understand how corner images are named (the contract)</h3>
 <p>
         The corner images are referenced in some .css files of the
@@ -443,7 +418,7 @@
 </dd>
       
 </dl>
-<a name="N10137"></a><a name="skinconfig"></a>
+<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
@@ -505,7 +480,7 @@
         defined <span class="codefrag">#FF0000</span> as the "color" value of
         <span class="codefrag">tab-selected</span>).
       </p>
-<a name="N1018E"></a><a name="css_modify"></a>
+<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>
@@ -540,9 +515,7 @@
         foreground. Horrible, isn't it?
       </p>
 </div>
-
-  
-<a name="N101BF"></a><a name="Feedback"></a>
+<a name="N101AA"></a><a name="Feedback"></a>
 <h2 class="underlined_10">Feedback</h2>
 <div class="section">
 <p>
@@ -550,7 +523,6 @@
       <a href="../../mail-lists.html">mailing lists</a>.
     </p>
 </div>
-
 </div>
 <!--+
     |end content
@@ -567,7 +539,9 @@
 //  --></script>
 </div>
 <div class="copyright">
- Copyright &copy; 2002-2005 The Apache Software Foundation.</div>
+        Copyright &copy;
+         2002-2005 <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
+</div>
 <!--+
     |end bottomstrip
     +-->

Modified: forrest/site/0.7/docs/howto/howto-corner-images.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/0.7/docs/howto/howto-corner-images.pdf?rev=168512&r1=168511&r2=168512&view=diff
==============================================================================
Binary files - no diff available.



Mime
View raw message