forrest-site-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r529915 [6/20] - in /forrest/site: ./ docs_0_70/ docs_0_70/howto/ docs_0_70/howto/cvs-ssh/ docs_0_70/howto/multi/ docs_0_80/ docs_0_80/howto/ docs_0_80/howto/cvs-ssh/ docs_0_80/howto/multi/ dtdx/ plan/ pluginDocs/ pluginDocs/plugins_0_70/ p...
Date Wed, 18 Apr 2007 08:36:26 GMT
Modified: forrest/site/docs_0_70/faq.xml
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_70/faq.xml?view=diff&rev=529915&r1=529914&r2=529915
==============================================================================
--- forrest/site/docs_0_70/faq.xml (original)
+++ forrest/site/docs_0_70/faq.xml Wed Apr 18 01:36:14 2007
@@ -15,38 +15,51 @@
   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="faq"><title>1.1.  How to use these FAQs? </title>
         <p>
-          There is no particular order to these FAQs. Use your browser's
-          "Find in this page" facility to search for keywords.
+          There is no particular order to these FAQs. Use your browser's "Find
+          in this page" facility to search for keywords.
         </p>
       </section><section id="overview"><title>1.2.  Where can I read an overview about how to work with Forrest? </title>
-        <p> See the <link href="site:v0.70//your-project">Using Forrest</link> guide. </p>
+        <p>
+          See the <link href="site:v0.70//your-project">Using Forrest</link>
+          guide.
+        </p>
       </section><section id="requirements"><title>1.3.  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 Apache Ant.
+        <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 Apache Ant.
         </p>
         <p>
           Java 1.4 (or newer) is required. If you are only going to use Forrest
-          as-is then you need only the Java Runtime Environment (JRE).
-          If you intend to enhance and rebuild Forrest (or use the Forrest sources
-          with Subversion or use a source snapshot) then you need the full JDK.
+          as-is then you need only the Java Runtime Environment (JRE). If you
+          intend to enhance and rebuild Forrest (or use the Forrest sources with
+          Subversion or use a source snapshot) then you need the full JDK.
         </p>
       </section><section id="cvs"><title>1.4.  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 closed and not kept current. </p>
+        <p>
+          Forrest switched from a CVS code repository to SVN (Subversion) code
+          repository. The old CVS repository is closed and not kept current.
+        </p>
       </section><section id="svn"><title>1.5.  How can I use SVN to keep up to date with the latest codebase? </title>
-        <p> Follow these <link href="site:v0.70//build">Building Forrest</link> notes. </p>
-        <p> The <link href="site:v0.70//your-project">Using Forrest</link> guide provides further
-          step-by-step assistance in getting started with Forrest for your project. </p>
+        <p>
+          Follow these <link href="site:v0.70//build">Building Forrest</link>
+          notes.
+        </p>
+        <p>
+          The <link href="site:v0.70//your-project">Using Forrest</link> guide
+          provides further step-by-step assistance in getting started with
+          Forrest for your project.
+        </p>
       </section><section id="older-plugins"><title>1.6.  How to use older versions of specific plugins? </title>
         <p>
-          Sometimes one does not want to use the most recent functionality
-          of a plugin and instead need to use an older version.
-          Information about changes to each plugin can be found in its
+          Sometimes one does not want to use the most recent functionality of a
+          plugin and instead need to use an older version. Information about
+          changes to each plugin can be found in its
           <link href="site:v0.70//plugins/index">documentation</link>.
         </p>
         <p>
-          In the forrest.properties file, specify the version of the plugin
-          that you require, e.g.
+          In the forrest.properties file, specify the version of the plugin that
+          you require, e.g.
         </p>
         <source xml:space="preserve">project.required.plugins=org.apache.forrest.plugin.input.PhotoGallery-0.1,...</source>
         <p>
@@ -62,154 +75,227 @@
         </p>
         <source xml:space="preserve">project.required.plugins=org.apache.forrest.plugin.input.projectInfo-0.1,...</source>
       </section><section id="single-document"><title>1.7.  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:v0.70//your-project">Using Forrest</link> guide provides further
-          step-by-step assistance in getting started with Forrest for your project. </p>
+        <p>
+          forrest site -Dproject.start-uri=myfile.pdf
+        </p>
+        <p>
+          The <link href="site:v0.70//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.8.  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.apache.org/jira/secure/ViewIssue.jspa?key=FOR-10">appears
-            to be a bug in cygwin</link>. Please use the .bat script instead. </p>
+        <p>
+          This
+          <link href="http://issues.apache.org/jira/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.9.  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
+        <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>
+        <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:v0.70//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:v0.70//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>
+        <p>
+          If you are using the Apache Forrest xml
+          <link href="site:v0.70//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:v0.70//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="site-xml"><title>2.2. 
         How to use the <code>site.xml</code> configuration file for menus and linking.
       </title>
         <p>
-          The <code>site.xml</code> configuration file is used for two different purposes:
-          defining the left-hand navigation menus, and as a method for defining references
-          to be used when linking between documents.
-          This file is fully explained in
-          <link href="site:v0.70//linking">Menus and Linking</link>. Here is a precis:
+          The <code>site.xml</code> configuration file is used for two different
+          purposes: defining the left-hand navigation menus, and as a method for
+          defining references to be used when linking between documents. This
+          file is fully explained in <link href="site:v0.70//linking">Menus and
+          Linking</link>. Here is a precis:
         </p>
         <p>
           The labels can be whatever text you want.
         </p>
-        <source xml:space="preserve">&lt;faq label="FAQs" href="faq.html"&gt;
+        <source xml:space="preserve">
+&lt;faq label="FAQs" href="faq.html"&gt;
   &lt;tech label="Technical" href="faq-tech.html"&gt;
     &lt;docbook href="#docbook"/&gt;
     &lt;ignoring_javadocs href="#ignoring_javadocs"/&gt;
   &lt;/tech&gt;
   &lt;user label="User" href="faq-user.html"&gt;
-&lt;/faq&gt;</source>
+&lt;/faq&gt;
+        </source>
         <p>
           That will create a menu like this with three links:
         </p>
         <source xml:space="preserve">FAQs
    Technical
    User</source>
-
         <p>
           These documents can be linked to from other documents, like this:
         </p>
-        <source xml:space="preserve">&lt;a href="site:v0.70//faq/tech"&gt; link to the top of the Tech FAQs
-&lt;a href="site:v0.70//faq/tech/docbook"&gt; link to the DocBook FAQ in the Tech FAQs</source>
-
+        <source xml:space="preserve">
+&lt;a href="site:v0.70//faq/tech"&gt; link to the top of the Tech FAQs
+&lt;a href="site:v0.70//faq/tech/docbook"&gt; link to the DocBook FAQ in the Tech FAQs
+        </source>
         <p>
           If that "docbook" entry was a unique name in your site.xml then you
           can shorten that latter link:
         </p>
-        <source xml:space="preserve">&lt;a href="site:v0.70//docbook"&gt; link to the DocBook FAQ in the Tech FAQs</source>
+        <source xml:space="preserve">
+&lt;a href="site:v0.70//docbook"&gt; link to the DocBook FAQ in the Tech FAQs
+        </source>
       </section><section id="examples"><title>2.3. 
         Where are examples of documents and site.xml and tabs.xml files?
       </title>
         <p>
-          There are examples in the 'forrest seed site' and also the Forrest website documents
-          are included with the distribution (cd forrest/site-author; forrest run).
+          There are examples in the 'forrest seed site' and also the Forrest
+          website documents are included with the distribution (cd
+          forrest/site-author; forrest run).
         </p>
       </section><section id="PDF-output"><title>2.4. 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>
+          Add the following entries to your site.xml file:
+        </p>
         <source xml:space="preserve">
+
   &lt;about tab="home" label="About" href=""&gt;
  	  ...
     &lt;all_site label="Full HTML" href="wholesite.html"/&gt;    
     &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:v0.70//howto/pdf-tab">How to create a PDF document for each
-          tab</link>.) </p>
-        <p> This assumes that you use the <link href="site:v0.70//linking">site.xml</link> method for your
-          site structure and navigation, rather than the old book.xml method. </p>
+  &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:v0.70//howto/pdf-tab">How to create a PDF document
+          for each tab</link>.)
+        </p>
+        <p>
+          This assumes that you use the
+          <link href="site:v0.70//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.5. 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> and/or
-            <em>pageBreakAfter</em> to the class attribute of the block you wish to force a
-            page break on. All the common block grouping elements support this class, for example, 
-            note, warning, p and so on.</p>
-        <p>If you want these classes to be processed in your HTML documents as well you should add
-          the following to the <code>extra-css</code> element in your projects
-          <code>skinconf.xml</code>
+        <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> and/or <em>pageBreakAfter</em> to the class
+          attribute of the block you wish to force a page break on. All the
+          common block grouping elements support this class, for example, note,
+          warning, p and so on.
+        </p>
+        <p>
+          If you want these classes to be processed in your HTML documents as
+          well you should add the following to the <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.6. 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>
+        <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.7. How do I link to raw files such as config.txt and brochure.pdf? </title>
-        <p>Handling of raw files was significantly changed in Forrest 0.7. See 
-          <link href="site:v0.70//upgrading_07/raw">Upgrading to Apache Forrest 0.7</link> for
-          all the details.</p>
+        <p>
+          Handling of raw files was significantly changed in Forrest 0.7. See
+          <link href="site:v0.70//upgrading_07/raw">Upgrading to Apache Forrest
+          0.7</link> for all the details.
+        </p>
       </section><section id="pdf_images"><title>2.8. Images don't display in PDFs. How do I fix this?</title>
-        <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>
+          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>
-        <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>
         </ol>
-        <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>
+        <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="tab-index"><title>2.9.  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>
+        <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>
+
+  &lt;tab label="User Manual" href="manual"/&gt;
+        </source>
+        <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>
+  &lt;/map:match&gt;
+        </source>
       </section><section id="tab-site"><title>2.10. I need help with the interaction between tabs.xml and site.xml </title>
         <p>
           See the <link href="site:v0.70//linking/tab-site">tips</link>.
         </p>
       </section><section id="defaultFileName"><title>2.11.  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.html' you need to
-          make the following changes:</p>
+        <p>
+          To change the default file name from 'index.html' (default) to
+          'overview.html' you need to make the following changes:
+        </p>
         <ol>
           <li> Create a '<link href="#cli-xconf">cli.xconf</link>' file for your project </li>
           <li> Edit that file to replace 'index.html' in
@@ -217,74 +303,129 @@
             with 'overview.html'. </li>
           <li> Edit your project's <link href="site:v0.70//project-sitemap">sitemap.xmap</link> file. </li>
           <li> Add the following code just before the end of the pipelines-element:<source xml:space="preserve">
+
   &lt;map:pipeline&gt;
     &lt;map:match type="regexp" pattern="^.+/$"&gt;
        &lt;map:redirect-to uri="overview.html"/&gt;
     &lt;/map:match&gt;
   &lt;/map:pipeline&gt;
-          </source></li>
+          
+            </source></li>
         </ol>
       </section><section id="defaultStartPage"><title>2.12.  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>
+        <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>Edit your project's <link href="site:v0.70//project-sitemap">sitemap.xmap</link> file.</li>
           <li>Add the following code just before the end of the pipelines-element:<source xml:space="preserve">
+
   &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;
-          </source></li>
+          
+            </source></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.13.  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>
+          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.apache.org/jira/browse/FOR-244">Issue
+          FOR-244</link>.
         </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.apache.org/jira/browse/FOR-244">Issue FOR-244</link>. </p>
       </section><section id="encoding"><title>2.14. Does Forrest handle accents for non-English languages?</title>
-        <p>Yes, Forrest can process text in any language, so you can include:</p>
+        <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>
-        <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>
+          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>
         <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>
-        <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>
+        <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 id="cleanSite"><title>2.15.  How to make Forrest clean up the project build directories? </title>
         <p>
           By default Forrest does not clean its build directories in the project
@@ -292,24 +433,32 @@
           successive runs of forrest.
         </p>
         <p>
-        Doing 'forrest clean-site' will remove the contents of the project's
-        generated documents directory. Doing 'forrest clean-work' will remove the
-        project's work directories (usually build/tmp and build/webapp which
-        include the Cocoon cache and the Cocoon logs).
-        Doing 'forrest clean' will remove both sections.
+          Doing 'forrest clean-site' will remove the contents of the project's
+          generated documents directory. Doing 'forrest clean-work' will remove
+          the project's work directories (usually build/tmp and build/webapp
+          which include the Cocoon cache and the Cocoon logs). Doing 'forrest
+          clean' will remove both sections.
         </p>
       </section><section id="i18n"><title>2.16. How can I internationalise (i18n) my content?</title>
-        <p>The i18n features of Forrest are still under development (as of 0.7) however there are
-        some features available. For example, navigation menus can be i18n'd (see fresh-site for an
-        example). Currently, <link href="http://issues.apache.org/jira/browse/FOR-506">work is underway</link> to 
-        i18n skins</p>
-        
-        <p>All internationalistation of tokens in, for example, the skins and the menus, is carried out
-        by the <link href="http://cocoon.apache.org/2.1/userdocs/transformers/i18n-transformer.html">Cocoon i18n 
-        Transformer</link>. You can see an example of how it works in the above linked issue.</p>
+        <p>
+          The i18n features of Forrest are still under development (as of 0.7)
+          however there are some features available. For example, navigation
+          menus can be i18n'd (see fresh-site for an example). Currently,
+          <link href="http://issues.apache.org/jira/browse/FOR-506">work is
+          underway</link> to i18n skins
+        </p>
+        <p>
+          All internationalistation of tokens in, for example, the skins and the
+          menus, is carried out by the
+          <link href="http://cocoon.apache.org/2.1/userdocs/transformers/i18n-transformer.html">Cocoon
+          i18n Transformer</link>. You can see an example of how it works in the
+          above linked issue.
+        </p>
       </section><section id="rawTML"><title>2.17. How can I include HTML content that is not to be skinned by Forrest?</title>
-        <p>To server, for example, a legacy HTML site add something like the following 
-        to your projects sitemap:</p>
+        <p>
+          To server, for example, a legacy HTML site add something like the
+          following to your projects sitemap:
+        </p>
         <source xml:space="preserve">
 &lt;map:match pattern="old_site/**.html"&gt;
  &lt;map:select type="exists"&gt;
@@ -323,8 +472,10 @@
   &lt;/map:when&gt;
 &lt;/map:match&gt;
         </source>
-        <p>There is a more detailed discussion of this topic in the samples
-        of a freshly seeded site. To see this documentation do the following:</p>
+        <p>
+          There is a more detailed discussion of this topic in the samples of a
+          freshly seeded site. To see this documentation do the following:
+        </p>
         <ol>
           <li>mkdir seed</li>
           <li>cd seed</li>
@@ -334,67 +485,106 @@
         </ol>
       </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.</p>
-        <p>You can also cross an authenticated proxy by setting the <code>proxy.user</code> and <code>proxy.password</code> accordingly.</p>
+        <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.
+        </p>
+        <p>
+          You can also cross an authenticated proxy by setting the
+          <code>proxy.user</code> and <code>proxy.password</code> accordingly.
+        </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
+        <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:v0.70//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>
+          displayed at the bottom of the page as "version 1.30". See for
+          example the bottom of the <link href="site:v0.70//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>
+          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>
-        <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;
    <strong>
+
    &lt;exclude pattern="**/"/&gt;
    &lt;exclude pattern="**apidocs**"/&gt;
    &lt;exclude pattern="api/**"/&gt;
    </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:v0.70//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>
+&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:v0.70//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>
+        <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.apache.org/jira/browse/FOR-217">FOR-217</link>).
+        <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.apache.org/jira/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><p>
-        <source xml:space="preserve">...
+        <source xml:space="preserve">
+...
 * [212/166] [0/0]  1.16s  62.4Kb  docs_0_60/your-project.pdf
 X [0]         /docs_0_80/upgrading_08.html  BROKEN: No pipeline matched...
 * [213/164] [0/0]  0.391s 29.2Kb  docs_0_70/howto/howto-buildPlugin.pdf
 ^                           apidocs/index.html
 * [214/170] [7/66] 1.476s 45.5Kb  docs_0_60/sitemap-ref.html
-...</source>
+...
+        </source>
         <ul>
           <li>Column 1 is the page build status (*=okay X=brokenLink ^=pageSkipped).</li>
           <li>Column 2 is the page count - the number of pages processed and the number remaining. The latter will change because during processing one page, Cocoon will discover more.</li>
@@ -404,118 +594,176 @@
         </ul>
       </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>
+          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>
+        <p>
+          See also
+          <link href="http://cocoon.apache.org/2.1/faq/faq-configure-environment.html">Cocoon
+          FAQ</link>.
+        </p>
       </section><section id="project-logo-svg"><title>3.8.  
         The project logo that is generated from SVG is truncating my project name.
       </title>
         <p>
-          In a 'forrest seed site' the project and the group logo are generated from a
-          Scalable Vector Graphics (SVG) file, using the text from the
-          <code>&lt;project-name&gt;</code> and
-          <code>&lt;group-name&gt;</code> elements of the <code>skinconf.xml</code> file.
-          If you have a long project-name then you may need to adjust the width of the image.
+          In a 'forrest seed site' the project and the group logo are generated
+          from a Scalable Vector Graphics (SVG) file, using the text from the
+          <code>&lt;project-name&gt;</code> and <code>&lt;group-name&gt;</code>
+          elements of the <code>skinconf.xml</code> file. If you have a long
+          project-name then you may need to adjust the width of the image.
           Perhaps you want to change the colours too. Edit the file at
-          <code>src/documentation/content/xdocs/images/project.svg</code> and adjust the "width"
-          attribute of the &lt;svg&gt; element. For further details see
-          <link href="http://www.w3.org/Graphics/SVG/">SVG</link> resources.
+          <code>src/documentation/content/xdocs/images/project.svg</code> and
+          adjust the "width" attribute of the &lt;svg&gt; element. For further
+          details see <link href="http://www.w3.org/Graphics/SVG/">SVG</link>
+          resources.
         </p>
       </section><section id="catalog"><title>3.9.  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:v0.70//catalog">Using Catalog Entity
-            Resolver for local DTDs</link>. </p>
+        <p>
+          Notes are provided for various tools at
+          <link href="site:v0.70//catalog">Using Catalog Entity Resolver for
+          local DTDs</link>.
+        </p>
       </section><section id="skin"><title>3.10.  How to make the site look better and change its skin? </title>
-        <p> There are <link href="site:v0.70//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:v0.70//your-project/skins">configuration</link> of the skins.
-          Some projects may have special needs and can define their <link href="site:v0.70//your-project/new-skin">own skin</link>. </p>
+        <p>
+          There are <link href="site:v0.70//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:v0.70//your-project/skins">configuration</link> of
+          the skins. Some projects may have special needs and can define their
+          <link href="site:v0.70//your-project/new-skin">own
+          skin</link>.
+        </p>
       </section><section id="xsp"><title>3.11. 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:v0.70//project-sitemap">project sitemap</link>
+          <li><p>
+              Add the following generator definition in the map:generators
+              section of your
+              <link href="site:v0.70//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>
+     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>
             <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>
-          </li>
+&lt;/map:match&gt;
+            </source>
+            <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>
+        <p>
+          See also the
+          <link href="http://wiki.apache.org/cocoon/AddingXSPToForrest">AddingXSPToForrest</link>
+          Wiki page.
+        </p>
       </section><section id="breadcrumbs"><title>3.12. 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>
+        <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>
+  &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>
       </section><section id="run_port"><title>3.13. 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>
+          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.apache.org/jira/browse/FOR-217">FOR-217</link>).
+        <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.apache.org/jira/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:v0.70//linking">Menus and
-            Linking</link>. </p>
+        <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:v0.70//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>simplifiedDocbook</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:v0.70//project-sitemap">project
-            sitemap</link> as explained in <link href="site:v0.70//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;
+        <p>
+          There are two ways. Forrest has a <code>simplifiedDocbook</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:v0.70//project-sitemap">project sitemap</link> as
+          explained in <link href="site:v0.70//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;
   &lt;map:pipeline&gt;
@@ -527,46 +775,79 @@
    &lt;/map:match&gt;
   &lt;/map:pipeline&gt;
  &lt;/map:pipelines&gt;
-&lt;/map:sitemap&gt;</source>
-        <p>You need to define the xhtml serializer used in &lt;map:serialize type="xhtml"/&gt;
-        in the components section of the sitemap. See the 
-        <link href="http://cocoon.apache.org/2.1/userdocs/serializers/xhtml-serializer.html">Cocoon
-        docs</link> for the elements you need to add to define this component. You can see examples 
-        of other components being added in the <code>FORREST_HOME/main/webapp/sitemap.xmap</code> file.</p>
-        <p> You can also use a mixture of the two methods, some handled automatically by Forrest and
-          some directly using DocBook stylesheets. You can also have a mixture of source files as
-          "document-v*" DTD and DocBook. </p>
-        <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:v0.70//your-project/new_dtd">Using Forrest</link> for
-          configuration guidance. </p>
+&lt;/map:sitemap&gt;
+        </source>
+        <p>
+          You need to define the xhtml serializer used in &lt;map:serialize
+          type="xhtml"/&gt; in the components section of the sitemap. See the
+          <link href="http://cocoon.apache.org/2.1/userdocs/serializers/xhtml-serializer.html">Cocoon
+          docs</link> for the elements you need to add to define this component.
+          You can see examples of other components being added in the
+          <code>FORREST_HOME/main/webapp/sitemap.xmap</code> file.
+        </p>
+        <p>
+          You can also use a mixture of the two methods, some handled
+          automatically by Forrest and some directly using DocBook stylesheets.
+          You can also have a mixture of source files as "document-v*" DTD and
+          DocBook.
+        </p>
+        <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:v0.70//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>
+        <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>
+          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
+        <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>
+          <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>
+        <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>
+        <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/docs_0_70/forrest-contract.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_70/forrest-contract.html?view=diff&rev=529915&r1=529914&r2=529915
==============================================================================
--- forrest/site/docs_0_70/forrest-contract.html (original)
+++ forrest/site/docs_0_70/forrest-contract.html Wed Apr 18 01:36:14 2007
@@ -3,7 +3,7 @@
 <head>
 <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.8-dev">
+<meta name="Forrest-version" content="0.9-dev">
 <meta name="Forrest-skin-name" content="pelt">
 <title>Our Contract (v0.7)</title>
 <link type="text/css" href="../skin/basic.css" rel="stylesheet">
@@ -87,7 +87,7 @@
     |start Subtabs
     +-->
 <div id="level2tabs">
-<a class="selected" href="../docs_0_70/index.html">0.70 (current)</a><a class="unselected" href="../docs_0_80/index.html">0.80-dev (under development)</a><a class="unselected" href="../docs_0_60/index.html">0.60 (past)</a>
+<a class="unselected" href="../docs_0_80/index.html">0.80 (current)</a><a class="unselected" href="../docs_0_90/index.html">0.90-dev (under development)</a><a class="selected" href="../docs_0_70/index.html">0.70 (past)</a>
 </div>
 <!--+
     |end Endtabs
@@ -100,7 +100,7 @@
     |breadtrail
     +-->
 <div class="breadtrail">
-             
+
              &nbsp;
            </div>
 <!--+
@@ -283,7 +283,7 @@
 </div>
 <div id="credit">
 <hr>
-        This is documentation for current version v0.7
+        This is documentation for past version v0.7
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
 <div id="roundbottom">
 <img style="display: none" class="corner" height="15" width="15" alt="" src="../skin/images/rc-b-l-15-1body-2menu-3menu.png"></div>
@@ -311,10 +311,12 @@
 	          &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
 </div>
 <h1>Our Contract</h1>
-<div class="abstract">This document describes, in a very techy bullet-style way, how
-      to use Forrest.</div>
+<div class="abstract">
+      This document describes, in a very techy bullet-style way, how to use
+      Forrest.
+    </div>
 <div id="motd-area">
-        This is documentation for current version v0.7
+        This is documentation for past version v0.7
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
 <div id="minitoc-area">
 <ul class="minitoc">
@@ -328,16 +330,15 @@
 <a href="#project-can">TheProject can:</a>
 </li>
 </ul>
-</div> 
+</div>
     
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-      This document describes the formal contract between the
-      <strong>Forrest distribution code</strong>, hereafter referred as 
-      "Forrest", and
-      the <strong>Project (team)</strong> that is using it for generating
-      its documentation and  web-site, hereafter referred to as "TheProject".
+      This document describes the formal contract between the <strong>Forrest
+      distribution code</strong>, hereafter referred as "Forrest", and the
+      <strong>Project (team)</strong> that is using it for generating its
+      documentation and web-site, hereafter referred to as "TheProject".
     </div>
 </div>
     
@@ -350,14 +351,15 @@
       <span class="codefrag">{projecthome}/src/documentation</span>
     
 </div>
-</div> 
-
+</div>
     
 <a name="N1002C"></a><a name="forrest-will"></a>
 <h2 class="underlined_10">Forrest will:</h2>
 <div class="section">
-<p>Provide infrastructure ...</p>
-<ul> 
+<p>
+        Provide infrastructure ...
+      </p>
+<ul>
         
 <li>Provide document type definitions (DTDs), skins, default sitemaps,
          Cocoon pipelines.
@@ -368,72 +370,71 @@
         </li>
         
 <li>Use Cocoon to generate the HTML and PDF documentation for
-          TheProject.</li> 
+          TheProject.</li>
       
 </ul>
 </div>
-
     
 <a name="N10046"></a><a name="project-must"></a>
 <h2 class="underlined_10">TheProject must:</h2>
 <div class="section">
-<p>Provide content and configuration ...</p>
-<ul> 
+<p>
+        Provide content and configuration ...
+      </p>
+<ul>
         
 <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>
         
 <li>Provide navigation metadata using the configuration files
           <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>
-        
 </li>
       
 </ul>
-</div> 
-
+</div>
     
-<a name="N10068"></a><a name="project-can"></a>
+<a name="N10066"></a><a name="project-can"></a>
 <h2 class="underlined_10">TheProject can:</h2>
 <div class="section">
-<p>Add extra abilities ...</p>
-<ul> 
+<p>
+        Add extra abilities ...
+      </p>
+<ul>
         
 <li>Provide its own skin in
           <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> 
+          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> 
+<ul>
             
 <li>and extra stylesheets to convert own grammar to the
-              intermediate 'document' structure.</li> 
+              intermediate 'document' structure.</li>
             
 <li>and declare those extra DTDs in
               <span class="codefrag">{docroot}/resources/schema/catalog.xcat</span>
-</li> 
+</li>
           
 </ul>
-        
-</li> 
+</li>
         
 <li>Provide its own overwriting versions of sitemaps
           (<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> 
+        </li>
       
 </ul>
-</div> 
+</div>
   
 </div>
 <!--+

Modified: forrest/site/docs_0_70/forrest-contract.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_70/forrest-contract.pdf?view=diff&rev=529915&r1=529914&r2=529915
==============================================================================
Binary files - no diff available.

Modified: forrest/site/docs_0_70/howto/cvs-ssh/howto-cvs-ssh.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_70/howto/cvs-ssh/howto-cvs-ssh.html?view=diff&rev=529915&r1=529914&r2=529915
==============================================================================
--- forrest/site/docs_0_70/howto/cvs-ssh/howto-cvs-ssh.html (original)
+++ forrest/site/docs_0_70/howto/cvs-ssh/howto-cvs-ssh.html Wed Apr 18 01:36:14 2007
@@ -3,7 +3,7 @@
 <head>
 <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.8-dev">
+<meta name="Forrest-version" content="0.9-dev">
 <meta name="Forrest-skin-name" content="pelt">
 <title>CVS through SSH (v0.7)</title>
 <link type="text/css" href="../../../skin/basic.css" rel="stylesheet">
@@ -87,7 +87,7 @@
     |start Subtabs
     +-->
 <div id="level2tabs">
-<a class="selected" href="../../../docs_0_70/index.html">0.70 (current)</a><a class="unselected" href="../../../docs_0_80/index.html">0.80-dev (under development)</a><a class="unselected" href="../../../docs_0_60/index.html">0.60 (past)</a>
+<a class="unselected" href="../../../docs_0_80/index.html">0.80 (current)</a><a class="unselected" href="../../../docs_0_90/index.html">0.90-dev (under development)</a><a class="selected" href="../../../docs_0_70/index.html">0.70 (past)</a>
 </div>
 <!--+
     |end Endtabs
@@ -100,7 +100,7 @@
     |breadtrail
     +-->
 <div class="breadtrail">
-             
+
              &nbsp;
            </div>
 <!--+
@@ -124,7 +124,7 @@
 </div>
 <div id="credit">
 <hr>
-        This is documentation for current version v0.7
+        This is documentation for past version v0.7
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
 <div id="roundbottom">
 <img style="display: none" class="corner" height="15" width="15" alt="" src="../../../skin/images/rc-b-l-15-1body-2menu-3menu.png"></div>
@@ -152,9 +152,13 @@
 	          &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
 </div>
 <h1>CVS through SSH</h1>
-<div class="abstract">This How-To describes the steps necessary to configure an SSH enabled CVS connection. It is recommended to configure an SSH enabled CVS connection to work with Apache code repositories.</div>
+<div class="abstract">
+      This How-To describes the steps necessary to configure an SSH enabled CVS
+      connection. It is recommended to configure an SSH enabled CVS connection
+      to work with Apache code repositories.
+    </div>
 <div id="motd-area">
-        This is documentation for current version v0.7
+        This is documentation for past version v0.7
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
 <div id="minitoc-area">
 <ul class="minitoc">
@@ -198,41 +202,52 @@
 <a name="N10013"></a><a name="Intended audience"></a>
 <h2 class="underlined_10">Intended audience</h2>
 <div class="section">
-<p>This How-to is aimed at developers who have been granted committer access to CVS repositories for particular projects.</p>
+<p>
+      This How-to is aimed at developers who have been granted committer access
+      to CVS repositories for particular projects.
+    </p>
 </div>
 <a name="N1001B"></a><a name="Purpose"></a>
 <h2 class="underlined_10">Purpose</h2>
 <div class="section">
-<p> 
-              Using SSH to access CVS repositories is recommended for security reasons. By configuring CVS to work with remote repository using private/public SSH keys you'll be able to run CVS commands without a need to enter your password every time you need access to CVS through SSH.
-        </p>
+<p>
+      Using SSH to access CVS repositories is recommended for security reasons.
+      By configuring CVS to work with remote repository using private/public SSH
+      keys you'll be able to run CVS commands without a need to enter your
+      password every time you need access to CVS through SSH.
+    </p>
 </div>
 <a name="N10023"></a><a name="Prerequisites"></a>
 <h2 class="underlined_10">Prerequisites</h2>
 <div class="section">
 <ul>
-            
+      
 <li>Account on the local machine.</li>
-            
+      
 <li>Commiter access to the project(s). <em>This also imply having account on the CVS host machine.</em>
-</li>        
-            
+</li>
+      
 <li>Cygwin - a Unix environment for Windows systems. You can get it <a href="http://www.redhat.com/software/tools/cygwin/">here</a>. <em>Not required for Linux/*nix users.</em>
 </li>
-            
+      
 <li>A CVS GUI application (for Windows users only), e.g. WinCVS. <em>It is not required, but can be very useful.</em>
 </li>
-        
+    
 </ul>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">If you are behind a firewall check that you can communicate through the 22 port. For anonymous access you will need 2401 one.</div>
+<div class="content">
+      If you are behind a firewall check that you can communicate through the 22
+      port. For anonymous access you will need 2401 one.
+    </div>
 </div>
 </div>
 <a name="N10044"></a><a name="Steps"></a>
 <h2 class="underlined_10">Steps</h2>
 <div class="section">
-<p>How to proceed.</p>
+<p>
+      How to proceed.
+    </p>
 <a name="N1004C"></a><a name="Terms"></a>
 <h3 class="underlined_5">Terms</h3>
 <dl>
@@ -246,25 +261,33 @@
         
 <dd>Concurrent Version System See <a href="http://www.cvshome.org">CVS Home Page</a>
 </dd>
-         
+      
 </dl>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-<strong>$</strong> represents local, <strong>%</strong> remote machine.</div>
+      
+<strong>$</strong> represents local, <strong>%</strong> remote machine.
+    </div>
 </div>
-<a name="N10070"></a><a name="Setting+up+domain+users"></a>
+<a name="N10071"></a><a name="Setting+up+domain+users"></a>
 <h3 class="underlined_5">Setting up domain users</h3>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">This step is necessary only for Windows users. Linux users can happily skip this section and pass to <a href="#ssh_access">Setting up SSH access</a> section</div>
+<div class="content">
+        This step is necessary only for Windows users. Linux users can happily
+        skip this section and pass to <a href="#ssh_access">Setting up SSH
+        access</a> section
+      </div>
 </div>
-<p>If you are a domain user then you should be added to Cygwin users list (See <span class="codefrag">[cygwin-dir]/etc/passwd</span>). 
-            </p>
+<p>
+        If you are a domain user then you should be added to Cygwin users list
+        (See <span class="codefrag">[cygwin-dir]/etc/passwd</span>).
+      </p>
 <ul>
-              
+        
 <li>Start Cygwin, then enter following commands:</li>
-            
+      
 </ul>
 <pre class="code">
 $ whoami
@@ -275,20 +298,24 @@
     </pre>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">Replace 'userxxx' by your account name</div>
+<div class="content">
+        Replace 'userxxx' by your account name
+      </div>
 </div>
 <ul>
-      
+        
 <li>Start Cygwin/shell again and check that everything's Ok:</li>
-    
+      
 </ul>
 <pre class="code">
 $ whoami
 userxxx
             </pre>
-<a name="N1009B"></a><a name="ssh_access"></a>
+<a name="N1009C"></a><a name="ssh_access"></a>
 <h3 class="underlined_5">Setting up SSH access</h3>
-<p>Start Cygwin/shell, then enter:</p>
+<p>
+        Start Cygwin/shell, then enter:
+      </p>
 <pre class="code">
 $ ssh-user-config
   Shall I create an SSH1 RSA identity file for you? (yes/no) no
@@ -303,15 +330,22 @@
   Configuration finished. Have fun!
     </pre>
 <p>
-      Now you have configured SSH on your machine. Next you have to setup access to the CVS machine.
-    </p>
+        Now you have configured SSH on your machine. Next you have to setup
+        access to the CVS machine.
+      </p>
 <div class="warning">
 <div class="label">Warning</div>
-<div class="content">Having an empty passphrase isn't recommended for security reasons. See <span class="codefrag">ssh-agent</span> documentation on how to configure automatic passphrase retaining.</div>
+<div class="content">
+        Having an empty passphrase isn't recommended for security reasons. See
+        <span class="codefrag">ssh-agent</span> documentation on how to configure automatic
+        passphrase retaining.
+      </div>
 </div>
-<a name="N100B2"></a><a name="Setting+up+passphrase+access"></a>
+<a name="N100B3"></a><a name="Setting+up+passphrase+access"></a>
 <h3 class="underlined_5">Setting up passphrase access</h3>
-<p>Perform the following:</p>
+<p>
+        Perform the following:
+      </p>
 <pre class="code">
 $ scp ~/.ssh/id_dsa.pub userxxx@cvs.apache.org:.
 $ ssh -l userxxx -L 2401:localhost:2401 cvs.apache.org
@@ -324,86 +358,99 @@
             </pre>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">Note, that the account name on CVS machine can differ from your local account name.</div>
+<div class="content">
+        Note, that the account name on CVS machine can differ from your local
+        account name.
+      </div>
 </div>
 <p>
-            Check that your configuration is correct:
-            </p>
+        Check that your configuration is correct:
+      </p>
 <pre class="code">
 $ ssh userxxx@cvs.apache.org
             </pre>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">If this command doesn't work then it can mean that you have an old version of SSH. In this case try <span class="codefrag">ssh -l userxxx cvs.apache.org</span>. Run <span class="codefrag">ssh --help</span> to get all available options.</div>
+<div class="content">
+        If this command doesn't work then it can mean that you have an old
+        version of SSH. In this case try <span class="codefrag">ssh -l userxxx
+        cvs.apache.org</span>. Run <span class="codefrag">ssh --help</span> to get all available
+        options.
+      </div>
 </div>
 <p>
-            If now you are logged in to the to the CVS machine without entering the password then everything's Ok.
-            </p>
-<a name="N100D6"></a><a name="Getting+the+project+from+CVS"></a>
+        If now you are logged in to the to the CVS machine without entering the
+        password then everything's Ok.
+      </p>
+<a name="N100D7"></a><a name="Getting+the+project+from+CVS"></a>
 <h3 class="underlined_5">Getting the project from CVS</h3>
-<p>Now you are ready to get a project from CVS using SSH connection.</p>
-<p>E.g. how it is done using Cygwin/shell</p>
+<p>
+        Now you are ready to get a project from CVS using SSH connection.
+      </p>
+<p>
+        E.g. how it is done using Cygwin/shell
+      </p>
 <pre class="code">
 $ export CVS_RSH=/bin/ssh
 $ cvs -d :ext:userxxx@cvs.apache.org:/home/cvs co xml-cocoon2            
             </pre>
-<a name="N100E7"></a><a name="How+to+setup+WinCVS"></a>
+<a name="N100E8"></a><a name="How+to+setup+WinCVS"></a>
 <h3 class="underlined_5">How to setup WinCVS</h3>
 <ul>
-                
+        
 <li>Add ssh.exe directory to your system PATH environment variable. Say: <br>
-                
 <span class="codefrag">C:\&gt;set PATH=%PATH%;C:\cygwin\bin</span>
 </li>
-                
+        
 <li>Add <span class="codefrag">CVS_RSH=ssh</span> environment variable</li>
-            
+      
 </ul>
 <p>
-            Start WinCVS, then:
-            </p>
+        Start WinCVS, then:
+      </p>
 <ul>
-                
+        
 <li>From the main menu select <strong>Admin</strong>
 </li>
-                
+        
 <li>Then select <strong>Preferences</strong>
 </li>
-                
+        
 <li>In the dialog that comes up: <br>
                 Set the CVSROOT to <span class="codefrag">userxxx@cvs.apache.org:/home/cvs</span>
 </li>
-                
-<li>Set the Authentication to SSH Server</li>                
-                
+        
+<li>Set the Authentication to SSH Server</li>
+        
 <li>Click Ok</li>
-            
+      
 </ul>
 <a name="N1011B"></a><a name="References"></a>
 <h3 class="underlined_5">References</h3>
 <p>
-                You can find more on CVS, SSH and WinCVS here:
-            </p>
+        You can find more on CVS, SSH and WinCVS here:
+      </p>
 <ul>
-                
+        
 <li>
 <a href="http://www.cvshome.org">CVS Home Page</a>
-</li>            
-                
+</li>
+        
 <li>
 <a href="http://www.openssh.org">OpenSSH</a>
-</li>            
-                
+</li>
+        
 <li>
 <a href="http://www.redhat.com/software/tools/cygwin/">Cygwin Home Page</a>
-</li>            
-                
+</li>
+        
 <li>
 <a href="http://odin.himinbi.org/wincvs-over-ssh/">WinCVS over SSH</a>
 </li>
-            
+      
 </ul>
 </div>
+<span class="version">1.0</span>
 </div>
 <!--+
     |end content

Modified: forrest/site/docs_0_70/howto/cvs-ssh/howto-cvs-ssh.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_70/howto/cvs-ssh/howto-cvs-ssh.pdf?view=diff&rev=529915&r1=529914&r2=529915
==============================================================================
Binary files - no diff available.



Mime
View raw message