forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: rev 21140 - in forrest/trunk/src/documentation/content/xdocs: . docs
Date Sat, 12 Jun 2004 13:10:05 GMT
Author: crossley
Date: Sat Jun 12 06:10:04 2004
New Revision: 21140

Modified:
   forrest/trunk/src/documentation/content/xdocs/build.xml
   forrest/trunk/src/documentation/content/xdocs/contrib.xml
   forrest/trunk/src/documentation/content/xdocs/docs/compliance.xml
   forrest/trunk/src/documentation/content/xdocs/docs/dtd-docs.xml
   forrest/trunk/src/documentation/content/xdocs/docs/linking.xml
   forrest/trunk/src/documentation/content/xdocs/docs/primer.xml
   forrest/trunk/src/documentation/content/xdocs/docs/sitemap-ref.xml
   forrest/trunk/src/documentation/content/xdocs/docs/upgrading_05.xml
   forrest/trunk/src/documentation/content/xdocs/docs/validation.xml
   forrest/trunk/src/documentation/content/xdocs/docs/your-project.xml
   forrest/trunk/src/documentation/content/xdocs/faq.xml
   forrest/trunk/src/documentation/content/xdocs/index.xml
   forrest/trunk/src/documentation/content/xdocs/uri-namespace.xml
Log:
Fix some broken hard-coded links.
Put some link elements all on one line to make it easier to grep broken links.


Modified: forrest/trunk/src/documentation/content/xdocs/build.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/build.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/build.xml	Sat Jun 12 06:10:04 2004
@@ -24,8 +24,8 @@
       <title>Getting the Forrest source</title>
       <section>
         <title>Step-by-step Subversion (SVN) instructions</title>
-          <note>If you are behind a proxy, see <link 
-href="http://subversion.tigris.org/project_faq.html#proxy">this FAQ</link>.</note>
+          <note>If you are behind a proxy, see 
+          <link href="http://subversion.tigris.org/project_faq.html#proxy">this FAQ</link>.</note>
         <ol> 
           <li>Make sure you have a recent release of a
            <link href="http://subversion.tigris.org/">Subversion</link>

Modified: forrest/trunk/src/documentation/content/xdocs/contrib.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/contrib.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/contrib.xml	Sat Jun 12 06:10:04 2004
@@ -159,7 +159,7 @@
         <li> When making changes to XML documentation, or any XML document for
           that matter, use a validating XML editor. Here is some assistance
           with editor 
-          <link href="catalog.html">configuration</link>.
+          <link href="site:catalog">configuration</link>.
         </li>
       <li> Remember that most people are participating in development on a
         volunteer basis and in their "spare time". These enthusiasts will attempt to

Modified: forrest/trunk/src/documentation/content/xdocs/docs/compliance.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/docs/compliance.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/docs/compliance.xml	Sat Jun 12 06:10:04
2004
@@ -38,8 +38,8 @@
       <title>HTML</title>
 
       <p>
-        Tested using the W3C HTML Validation Service (<link
-          href="http://validator.w3.org/">validator.w3.org</link>). The
+        Tested using the W3C HTML Validation Service
+        (<link href="http://validator.w3.org/">validator.w3.org</link>). The
         index.html page of Forrest sites will have a link to this validator,
         unless the user has turned this off.
       </p>
@@ -77,8 +77,8 @@
   <li>
     Priority 1: alt text for images.
   </li>
-  <li>Priority 2: <link
-      href="http://bobby.watchfire.com/bobby/html/en/gls/g41.html">Explicitly
+  <li>Priority 2: 
+  <link href="http://bobby.watchfire.com/bobby/html/en/gls/g41.html">Explicitly
       associate form controls and their labels with the LABEL element</link>.
     Perhaps we could have a label hidden with CSS?</li>
   <li>FIXME: need to list other issues here, or attend to them.</li>

Modified: forrest/trunk/src/documentation/content/xdocs/docs/dtd-docs.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/docs/dtd-docs.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/docs/dtd-docs.xml	Sat Jun 12 06:10:04 2004
@@ -21,8 +21,7 @@
   </header>
   <body>
     <p>We use the
-      <link
-   href="http://www.apache.org/~andyc/neko/doc/dtd/index.html">NekoDTD</link> tool
+      <link href="http://www.apache.org/~andyc/neko/doc/dtd/index.html">NekoDTD</link>
tool
   packaged as a Cocoon Generator to generate automagically some hyperlinked DTD
   references. Note that these references do not reflect the modularity of our
   DTDs, they are primarily user-oriented.</p>

Modified: forrest/trunk/src/documentation/content/xdocs/docs/linking.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/docs/linking.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/docs/linking.xml	Sat Jun 12 06:10:04 2004
@@ -233,8 +233,8 @@
           unspecified, nodes inherit the <code>tab</code> of their parent.  Thus
           everything in the <strong>&lt;about&gt;</strong> section has
an implicit
           <code>tab="home"</code>.</p>
-        <note>You can see this by viewing your site's <link
-            href="abs-menulinks">abs-menulinks</link> pipeline in a
+        <note>You can see this by viewing your site's 
+        <link href="abs-menulinks">abs-menulinks</link> pipeline in a
           browser.</note>
         <p>Say that the user is viewing the <code>linking.html</code>
           page.  The <strong>&lt;linking&gt;</strong> node has an implicit
tab
@@ -345,9 +345,9 @@
         <p>
           The theoretical problem with this is that the content producer should
           not know or care how Forrest is going to render the source.  A URI
-          should only <em>identify</em> a resource, not specify it's type [<link
-            href="ext:semantic-linking">mail ref</link>] [<link
-            href="ext:cool-uris">cool URIs</link>]. In fact, as Forrest
+          should only <em>identify</em> a resource, not specify it's type
+          [<link href="ext:semantic-linking">mail ref</link>]
+          [<link href="ext:cool-uris">cool URIs</link>]. In fact, as Forrest
           typically renders to multiple output formats (HTML and PDF), links in
           one of them (here, the PDF) are likely to break.
         </p>
@@ -362,8 +362,8 @@
         <dl>
           <dt>site</dt>
           <dd>is a URI 'scheme'; a namespace that restricts
-            the syntax and semantics of the rest of the URI [<link
-              href="ext:uri-rfc">rfc2396</link>].  The semantics of 'site' are
+            the syntax and semantics of the rest of the URI
+            [<link href="ext:uri-rfc">rfc2396</link>].  The semantics of 'site'
are
             "this identifier locates something in the site's XML sources".</dd>
           <dt>todo</dt>
           <dd>identifies the content in <code>todo.xml</code>, by reference
to a
@@ -444,8 +444,8 @@
             ]]></source>
           <p>
             As an example, &lt;link href="ext:cocoon/ml"&gt;
-            generates the link <link
-              href="ext:cocoon/ml">http://xml.apache.org/cocoon/mail-lists.html</link>
+            generates the link
+            <link href="ext:cocoon/ml">http://xml.apache.org/cocoon/mail-lists.html</link>
           </p>
           <p>
             The general rules of &s; and <code>site:</code> linking apply.
@@ -543,9 +543,9 @@
     </section>
     <section id="implementation">
       <title>Implementation</title>
-      <p>Full details on the implementation of <link
-        href="site:linkrewriting_impl">link rewriting</link> and <link
-        href="site:menu_generation_impl">menu generation</link> are available in
+      <p>Full details on the implementation of
+      <link href="site:linkrewriting_impl">link rewriting</link> and
+      <link href="site:menu_generation_impl">menu generation</link> are available
in
       the <link href="site:sitemap-ref">Sitemap Reference</link></p>
     </section>
 

Modified: forrest/trunk/src/documentation/content/xdocs/docs/primer.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/docs/primer.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/docs/primer.xml	Sat Jun 12 06:10:04 2004
@@ -20,10 +20,9 @@
     <title>The Forrest Primer</title> 
     <subtitle>Don't panic!</subtitle> 
     <abstract>Forrest is a so-called
-      <link
-        href="http://www.dictionary.com/cgi-bin/dict.pl?term=fledgling">fledgling</link>
-      project that will have a broad impact on <link
-        href="http://xml.apache.org/">xml.apache.org</link> projects. This document
+      <link href="http://www.dictionary.com/cgi-bin/dict.pl?term=fledgling">fledgling</link>
+      project that will have a broad impact on
+      <link href="http://xml.apache.org/">xml.apache.org</link> projects. This
document
       helps you to better understand the vision and scope of Forrest, so that you
       learn what to expect (or not) from it, and eventually will help you discovering
       places where your contribution could be valuable to all of us.</abstract> 
@@ -52,8 +51,8 @@
         alike.</p> 
       <p>The Forrest vision was articulated by Stefano Mazzocchi and Sam Ruby,
         both long-time contributors to Apache projects, in the beginning of 2002, and
-        was rapidly picked up by a bunch of other <link
-          href="site:who">contributors</link> as well, after a headstart by Nicola
Ken
+        was rapidly picked up by a bunch of other 
+        <link href="site:who">contributors</link> as well, after a headstart
by Nicola Ken
         Barozzi. So here we are, plenty of work-in-progress to erect what eventually
         will become a true community website infrastructure for Apache open source
         development.</p> 
@@ -86,8 +85,8 @@
         works, try using the <code>docs</code> target when invoking the
         <code>build</code> script. Add a <code>project.skin</code>
property when invoking
         the build script to experience Forrest skins: <code>build{.bat|.sh}
-          -Dproject.skin=&lt;thenameoftheskintouse&gt; docs</code>. Read our
<link
-          href="#cvs">CVS crash course</link> to get hold of the current codebase
and
+          -Dproject.skin=&lt;thenameoftheskintouse&gt; docs</code>. Read our
+        <link href="#cvs">CVS crash course</link> to get hold of the current
codebase and
         start playing with it.</note> 
       <ol> 
         <li>Forrest will harvest documentation and related source files from
@@ -166,8 +165,8 @@
       </section> 
       <section>
         <title>Getting Forrest</title>
-        <p>You can retrieve Forrest from its CVS repository or download <link
-            href="http://www.apache.org/dyn/closer.cgi/xml/forrest/">here</link>.
+        <p>You can retrieve Forrest from its CVS repository or download
+         <link href="http://www.apache.org/dyn/closer.cgi/xml/forrest/">here</link>.
           <br/>Some help with CVS follows (courtesy of our friends of the Cocoon project).</p>

       </section> 
       <section>
@@ -296,8 +295,8 @@
       <p>Forrest is the reference repository for the XML Apache documentation
         DTDs. Special care is taken to provide a set of modular, extensible and
         well-maintained DTDs for project documentation purposes. This modularity is
-        ensured using the <link
-          href="http://www.oasis-open.org/committees/entity/">OASIS catalog</link>
+        ensured using the
+        <link href="http://www.oasis-open.org/committees/entity/">OASIS catalog</link>
         mechanism, extensive use of external parameter entities and an entity resolver
         capable of resolving entities through the aforementioned catalog mechanism. For
         the docheads amongst us, this means we adhere to the strict use of
@@ -465,8 +464,8 @@
             developer resources, such as project-related news, download statistics,
             committer bio pages (with photos!), navigable source code listings and the
             like. Some of these resources need to be made available across content
-            syndication methods such as <link
-              href="http://blogspace.com/rss/">RSS</link>.</td> 
+            syndication methods such as 
+            <link href="http://blogspace.com/rss/">RSS</link>.</td> 
         </tr> 
         <tr> 
           <th>Build Management</th> 

Modified: forrest/trunk/src/documentation/content/xdocs/docs/sitemap-ref.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/docs/sitemap-ref.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/docs/sitemap-ref.xml	Sat Jun 12 06:10:04
2004
@@ -26,8 +26,8 @@
   </header>
   <body>
     <p>
-      Technically, Forrest can be thought of as a <link
-        href="ext:cocoon">Cocoon</link> distribution that has been stripped down
+      Technically, Forrest can be thought of as a 
+      <link href="ext:cocoon">Cocoon</link> distribution that has been stripped
down
       and optimized for people with simple site publishing needs.  Central to
       Cocoon, and hence Forrest, is the <strong>sitemap</strong>.  The sitemap
       defines the site's URI space (what pages are available), and how each page
@@ -35,8 +35,8 @@
       Forrest.
     </p>
     <p>
-      The Cocoon sitemap syntax is documented fully <link
-        href="site:cocoon/sitemap">in Cocoon's documentation</link>.  This page
+      The Cocoon sitemap syntax is documented fully 
+      <link href="site:cocoon/sitemap">in Cocoon's documentation</link>.  This
page
       provides an overview of the sitemap we have written for Forrest.
     </p>
     <section id="getting_started">
@@ -85,8 +85,8 @@
         <tr>
           <th>linkmap.xmap</th>
           <td>Defines a mapping from abstract ('site:index') to physical
-            ('../index.html') links for the current page.  See <link
-              href="site:linking">Menus and Linking</link> for a conceptual
+            ('../index.html') links for the current page.  See 
+            <link href="site:linking">Menus and Linking</link> for a conceptual
             overview, and the <link href="#linkrewriting_impl">Link
               rewriting</link> section for technical details.</td>
         </tr>
@@ -110,8 +110,8 @@
         </tr>
         <tr>
           <th>status.xmap</th>
-          <td>Generates <link href="site:changes">changes</link> and <link
-              href="site:todo">todo</link> pages from a single
+          <td>Generates <link href="site:changes">changes</link> and 
+          <link href="site:todo">todo</link> pages from a single
             <code>status.xml</code> in the project root.
           </td>
         </tr>
@@ -132,8 +132,8 @@
         <tr>
           <th>dtd.xmap</th>
           <td>A Source pipeline that generates XML from a DTD, using Andy
-            Clark's <link
-              href="http://xml.apache.org/~andyc/neko/doc/dtd/index.html">DTD
+            Clark's 
+            <link href="http://xml.apache.org/~andyc/neko/doc/dtd/index.html">DTD
               Parser</link>.  Useful for documenting DTD-based XML schemas, such
             as <link href="site:dtd-docs">Forrest's own DTDs</link>.
           </td>
@@ -168,11 +168,11 @@
         format.
       </p>
       <p>
-        Source pipelines always have a <code>.xml</code> extension.  Thus, <link
-          href="index.xml">index.xml</link> gives you the XML source for the
+        Source pipelines always have a <code>.xml</code> extension.  Thus, 
+        <link href="index.xml">index.xml</link> gives you the XML source for
the
         index page.  Likewise, <link href="faq.xml">faq.xml</link> gives you
XML
-        for the FAQ (transformed from FAQ syntax), and <link
-          href="changes.xml">changes.xml</link> returns XML from status.xml.
+        for the FAQ (transformed from FAQ syntax), and 
+        <link href="changes.xml">changes.xml</link> returns XML from status.xml.
         Take any page, and replace its extension (<code>.html</code> or
         <code>.pdf</code>) with <code>.xml</code>, and you'll have
the Source
         XML.
@@ -200,8 +200,8 @@
         <p>
           Most of the usual Source pipelines are defined in
           <code>forrest.xmap</code>, which is the default (fallback) handler
for
-          <code>**.xml</code> pages.  forrest.xmap uses the <link
-            href="site:cap">SourceTypeAction</link> to work out the type of XML
+          <code>**.xml</code> pages.  forrest.xmap uses the 
+          <link href="site:cap">SourceTypeAction</link> to work out the type
of XML
           it is processing, and converts it to doc-v12 if necessary.
         </p>
         <p>For instance, say we are rendering <link href="site:multi-page/step1">a
@@ -216,8 +216,8 @@
           </map:when>
           ]]></source>
         <p>
-          The intermediate result is visible at the URL <link
-            href="community/howto/multi/step1.xml">community/howto/multi/step1.xml</link>.
+          The intermediate result is visible at the URL 
+          <link href="community/howto/multi/step1.xml">community/howto/multi/step1.xml</link>.
         </p>
       </section>
       <section>
@@ -343,9 +343,9 @@
         </source>
         <p>
           So <link href="index.html">index.html</link> is formed from
-          aggregating <link href="body-index.html">body-index.html</link>, <link
-            href="menu-index.html">menu-index.html</link> and <link
-            href="tab-index.html">tab-index.html</link>, and then applying the
+          aggregating <link href="body-index.html">body-index.html</link>, 
+          <link href="menu-index.html">menu-index.html</link> and 
+          <link href="tab-index.html">tab-index.html</link>, and then applying
the
           <code>site2xhtml.xsl</code> stylesheet to the result.
         </p>
         <p>
@@ -434,12 +434,12 @@
         </map:call>
       </map:match>
       ]]></source>
-        <p>We get XML from a 'book' pipeline, <link
-            href="#linkrewriting_impl">rewrite links</link>, and apply the
+        <p>We get XML from a 'book' pipeline, 
+        <link href="#linkrewriting_impl">rewrite links</link>, and apply the
           <code>book2menu.xsl</code> stylesheet to generate HTML.</p>
         <p>How the menu XML is actually generated (the *book-*.html pipeline) is
-          sufficiently complex to require a <link
-            href="#menu_xml_generation">section of its own</link>.</p>
+          sufficiently complex to require a 
+          <link href="#menu_xml_generation">section of its own</link>.</p>
       </section>
 
       <section id="tab_pipeline">
@@ -575,8 +575,8 @@
           <code>inputmodule:key</code>.  The transformer then uses the named
           InputModule to look up the key value. The <code>scheme:address</code>
           URI is then rewritten with the found value.  This transformer was
-          implemented as <link
-            href="ext:linkrewritertransformer">LinkRewriterTransformer</link>,
+          implemented as 
+          <link href="ext:linkrewritertransformer">LinkRewriterTransformer</link>,
           currently distributed as a "block" in Cocoon 2.1.
         </p>
       </section>
@@ -739,9 +739,9 @@
 </map:match>
             ]]></source>
           <p>You can try these URIs out directly on a live Forrest to see what
-            is going on (for example, Forrest's own <link
-              href="abs-linkmap">abs-linkmap</link> and <link
-              href="linkmap-index.html">linkmap-index.html</link>.
+            is going on (for example, Forrest's own 
+            <link href="abs-linkmap">abs-linkmap</link> and 
+            <link href="linkmap-index.html">linkmap-index.html</link>.
           </p>
         </section>
       </section>

Modified: forrest/trunk/src/documentation/content/xdocs/docs/upgrading_05.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/docs/upgrading_05.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/docs/upgrading_05.xml	Sat Jun 12 06:10:04
2004
@@ -98,8 +98,8 @@
         <li>Move their overridden sitemap (<code>src/documentation/sitemap.xmap</code>)
out the way</li>
         <li>Copy the new sitemap, $FORREST_HOME/context/sitemap.xmap, to <code>src/documentation</code></li>
         <li>Reapply your customizations to the new sitemap.xmap.  Customizations can
be determined by comparing your modified
-          sitemap.xmap with <link
-            href="http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/conf/sitemap.xmap?rev=1.66&amp;only_with_tag=FORREST_04">original
+          sitemap.xmap with 
+          <link href="http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/conf/sitemap.xmap?rev=1.66&amp;only_with_tag=FORREST_04">original
             Forrest 0.4 sitemap</link>.</li>
       </ol>
     </section>
@@ -165,8 +165,8 @@
 
     <section>
       <title>Upgrading skinconf.xml</title>
-      <p>Look at the <link
-        href="http://cvs.apache.org/viewcvs/xml-forrest/src/resources/fresh-site/src/documentation/skinconf.xml.diff?r1=1.7%3AFORREST_04&#38;r2=1.15%3AFORREST_05&#38;diff_format=h">differences
+      <p>Look at the 
+      <link href="http://cvs.apache.org/viewcvs/xml-forrest/src/resources/fresh-site/src/documentation/skinconf.xml.diff?r1=1.7%3AFORREST_04&#38;r2=1.15%3AFORREST_05&#38;diff_format=h">differences
         for the sample skinconf.xml</link> as a guide.
         You will need to update the internal DTD and add several new elements.
       </p>
@@ -174,8 +174,8 @@
 
     <section>
       <title>Upgrading forrest.properties</title>
-      <p>Look at the <link
-        href="http://cvs.apache.org/viewcvs/xml-forrest/src/resources/fresh-site/forrest.properties.diff?r1=1.20%3AFORREST_04&#38;r2=1.32%3AFORREST_05&#38;diff_format=h">differences
+      <p>Look at the 
+      <link href="http://cvs.apache.org/viewcvs/xml-forrest/src/resources/fresh-site/forrest.properties.diff?r1=1.20%3AFORREST_04&#38;r2=1.32%3AFORREST_05&#38;diff_format=h">differences
         for the sample forrest.properties</link> as a guide. Note that
         project.sitemap has changed to project.sitemap-dir and note that
         cli.xconf now controls some settings that were previously controlled
@@ -205,8 +205,8 @@
 
     <section>
       <title>To be continued...</title>
-      <p>..as more issues are discovered/remembered :)  Please send feedback to the
<link
-          href="site:mail-lists/forrest-dev">mailing list</link>.</p>
+      <p>..as more issues are discovered/remembered :)  Please send feedback to the

+      <link href="site:mail-lists/forrest-dev">mailing list</link>.</p>
     </section>
   </body>
 </document>

Modified: forrest/trunk/src/documentation/content/xdocs/docs/validation.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/docs/validation.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/docs/validation.xml	Sat Jun 12 06:10:04
2004
@@ -244,8 +244,8 @@
         </source>
         <p>This custom DTD should be placed in <code>src/documentation/resources/schema/dtd/</code></p>
         <p>
-          The &lt;!ENTITY % ... &gt; blocks are so-called <link
-            href="http://www.xml.com/axml/target.html#dt-PERef">parameter
+          The &lt;!ENTITY % ... &gt; blocks are so-called 
+          <link href="http://www.xml.com/axml/target.html#dt-PERef">parameter
             entities</link>.  They are like macros, whose content will be
           inserted when a parameter-entity reference, like
           <code>%common-charents;</code> or <code>%document;</code>
is
@@ -266,8 +266,8 @@
         <p>
           We now have a DTD for the 'download' document type. 
         </p>
-        <note><link
-            href="http://www.oasis-open.org/docbook/documentation/reference/html/ch05.html">Chapter
+        <note>
+        <link href="http://www.oasis-open.org/docbook/documentation/reference/html/ch05.html">Chapter
             5: Customizing DocBook</link> of Norman Walsh's "DocBook: The
           Definitive Guide" gives a complete overview of the process of
           customizing a DTD.
@@ -361,7 +361,7 @@
         it know where the Forrest catalog file is, and you will be able to
         validate any Forrest XML file, regardless of location, as you edit
         your files. See the 
-        <link href="catalog.html">configuration notes</link> your favourite
+        <link href="site:catalog">configuration notes</link> your favourite
         editor.
       </p>
     </section>

Modified: forrest/trunk/src/documentation/content/xdocs/docs/your-project.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/docs/your-project.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/docs/your-project.xml	Sat Jun 12 06:10:04
2004
@@ -423,8 +423,8 @@
          project.xdocs-dir=src/xdocs
        </source>
        <p>
-         Say we wish to emulate the nice and simple <link
-           href="http://maven.apache.org/">Maven</link> format:
+         Say we wish to emulate the nice and simple 
+         <link href="http://maven.apache.org/">Maven</link> format:
        </p>
        <p xml:space="preserve">
          /xdocs
@@ -464,8 +464,8 @@
           Whenever adding a new file, you should add an entry to the project's
           <code>site.xml</code> file. site.xml is like a site index, and is rendered
as
           the vertical column of links in the default skin.  Have a look at Forrest's own
-          xdocs for an example.  More detailed info about site.xml is provided in <link
-            href="site:linking">Menus and Linking</link>.
+          xdocs for an example.  More detailed info about site.xml is provided in 
+          <link href="site:linking">Menus and Linking</link>.
         </p>
       </section>
       <section id="tabs.xml">
@@ -526,8 +526,8 @@
       </p>
       <ul>
         <li>Transform custom XML content types with XSLT stylesheets</li>
-        <li>Generate PNG or JPEG images from <link
-            href="http://www.w3.org/TR/SVG/">SVG</link> XML files.
+        <li>Generate PNG or JPEG images from 
+        <link href="http://www.w3.org/TR/SVG/">SVG</link> XML files.
           (<strong>Update:</strong> Forrest's sitemap now does this natively).</li>
         <li>Integrate external XML feeds (eg RSS) into your site's content
           (<strong>Update:</strong> See issues.xmap for an example.</li>
@@ -535,8 +535,8 @@
           sources available as "virtual" files.
           (<strong>Update:</strong>: Forrest's default sitemap defines a whole-site
HTML
           and PDF, available as <code>site.html</code> and <code>site.pdf</code>.</li>
-        <li>Read content from exotic sources like <link
-            href="http://www.rpbourret.com/xml/XMLDBLinks.htm">XML
+        <li>Read content from exotic sources like
+        <link href="http://www.rpbourret.com/xml/XMLDBLinks.htm">XML
             databases</link></li>
         <li>Integrate any of <link href="ext:cocoon">Cocoon's</link> vast
array
           of capabilities.  The possibilities are best appreciated by
@@ -551,11 +551,11 @@
         <code>${project.sitemap-dir}</code> points to).
       </p>
       <p>
-        The sitemap syntax is described in the <link
-          href="ext:cocoon/sitemap">Cocoon sitemap docs</link>.  The Forrest
+        The sitemap syntax is described in the 
+        <link href="ext:cocoon/sitemap">Cocoon sitemap docs</link>.  The Forrest
         sitemap is broken into multiple files. The main one is
-        <strong>sitemap.xmap</strong>, which delegates to others.  See the <link
-          href="site:sitemap-ref">Sitemap Reference</link> for a tour of the
+        <strong>sitemap.xmap</strong>, which delegates to others.  See the
+         <link href="site:sitemap-ref">Sitemap Reference</link> for a tour of
the
         default sitemap.
       </p>
       <section id="adding_new_content_type">
@@ -716,8 +716,8 @@
           <section id="integrating_rss">
             <title>Example: integrating external RSS content</title>
             <p>Similar to the previous example, we can integrate RSS into our
-              site by overriding and editing the sitemap.  As described in <link
-                href="site:sitemap-ref/source_pipelines">the 'source pipelines'
+              site by overriding and editing the sitemap.  As described in 
+              <link href="site:sitemap-ref/source_pipelines">the 'source pipelines'
                 section of sitemap reference</link>, Forrest's
               <code>sitemap.xmap</code> delegates source
               handling to various subsitemaps in a <code>**.xml</code> block.
@@ -830,8 +830,8 @@
     <section id="webapp">
       <title>Interactive Forrest: developing docs faster</title>
       <p>
-        In comparison to simpler tools like <link
-          href="ext:anakia">Anakia</link>, Cocoon's command-line mode (and hence
+        In comparison to simpler tools like 
+        <link href="ext:anakia">Anakia</link>, Cocoon's command-line mode (and
hence
         Forrest) is painfully slow.  As the <link href="site:dreams">dream
           list</link> notes, Forrest was originally intended to be used for
         dynamic sites, and the Cocoon crawler used only to create static

Modified: forrest/trunk/src/documentation/content/xdocs/faq.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/faq.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/faq.xml	Sat Jun 12 06:10:04 2004
@@ -94,8 +94,8 @@
       </question>
       <answer>
         <p>
-          This <link
-            href="http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-10">appears
+          This 
+          <link href="http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-10">appears
             to be a bug in cygwin</link>. Please use the .bat script instead.
         </p>
       </answer>
@@ -273,8 +273,8 @@
         </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>lib/optional/jimi-1.0.jar</code> (or to
             <code>src/documentation/lib/jimi-1.0.jar</code> so that each
@@ -283,8 +283,8 @@
         </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 
+          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
@@ -344,7 +344,7 @@
       <answer>
         <p>
           Notes are provided for various tools at
-          <link href="catalog.html">Using Catalog Entity Resolver for
+          <link href="site:catalog">Using Catalog Entity Resolver for
           local DTDs</link>.
         </p>
       </answer>
@@ -358,8 +358,8 @@
         <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>,
+          <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/WEB-INF/lib directory (or lib/core/ directory
in the source
             distribution).</li>
           <li><p>Override sitemap.xmap in your local project (copy $FORREST_HOME/context/sitemap.xmap
to
@@ -379,8 +379,8 @@
             <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.cocoondev.org/Wiki.jsp?page=AddingXSPToForrest">AddingXSPToForrest</link>
Wiki page.</p>
+        <p>See also the 
+        <link href="http://wiki.cocoondev.org/Wiki.jsp?page=AddingXSPToForrest">AddingXSPToForrest</link>
Wiki page.</p>
       </answer>
     </faq>
     
@@ -589,8 +589,8 @@
           else. Don't be shy!
         </p>
         <p>
-          More info about contributing can be found at the <link
-            href="site:contrib">Contributing to Forrest</link> page.  Its always
+          More info about contributing can be found at the 
+          <link href="site:contrib">Contributing to Forrest</link> page.  Its
always
           a good idea to check the Forrest <link href="site:todo">to do</link>
           list before diving in.
         </p>

Modified: forrest/trunk/src/documentation/content/xdocs/index.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/index.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/index.xml	Sat Jun 12 06:10:04 2004
@@ -46,8 +46,8 @@
           complete website from the XML. Various website styles (known as skins)
           are available, and custom skins can be developed.</li>
       </ul>
-      <note>For more information on Forrest installation and use, see the <link
-          href="site:your-project">Getting Started</link> guide.
+      <note>For more information on Forrest installation and use, see the 
+      <link href="site:your-project">Getting Started</link> guide.
       </note>
       <p>
         Forrest's focus on low "startup cost" makes it ideal for rapid
@@ -72,17 +72,17 @@
       <title>Powerful</title>
       <p>
         Forrest is far from a quick and dirty solution however.  Forrest is
-        built on one of the world's leading XML application frameworks, <link
-          href="ext:cocoon">Apache Cocoon</link>, which provides advanced
+        built on one of the world's leading XML application frameworks, 
+        <link href="ext:cocoon">Apache Cocoon</link>, which provides advanced
         users with extremely powerful publishing capabilities.
       </p>
       <ul>
-        <li>Multiple task-specific source XML formats can be used (<link
-            href="site:howto-samples/overview">howtos</link>, <link
-            href="site:faq"><acronym title="Frequently Asked
+        <li>Multiple task-specific source XML formats can be used
+         (<link href="site:howto-samples/overview">howtos</link>,
+          <link href="site:faq"><acronym title="Frequently Asked
               Questions">FAQ</acronym>s</link>,
-          <link href="site:changes">changelogs</link> and <link
-            href="site:todo">todo lists</link> supported natively).
+          <link href="site:changes">changelogs</link> and
+          <link href="site:todo">todo lists</link> supported natively).
           Source formats include: Apache xdocs, DocBook, and Wiki formats.</li>
         <li>Multiple output formats supported, for example HTML and PDF (using
           <link href="ext:fop">Apache FOP</link>).
@@ -91,12 +91,12 @@
             Batik</link>); simply drop a SVG in the appropriate directory and it
           will be rendered as PNG.</li>
         <li>
-          Transparent inclusion and aggregation of external content, like <link
-            href="site:changes-rss">RSS feeds</link>.
+          Transparent inclusion and aggregation of external content, like
+          <link href="site:changes-rss">RSS feeds</link>.
         </li>
         <li>
-          Anything else possible with the <link
-            href="ext:cocoon/sitemap">Cocoon sitemap</link>.  Using database
+          Anything else possible with the
+          <link href="ext:cocoon/sitemap">Cocoon sitemap</link>.  Using database
           queries, <link href="ext:apache-stats">charting</link>, web services
           integration; the possibilities are constantly growing as Cocoon grows.
           See the <link href="ext:cocoon/features">Cocoon Features</link> list
@@ -135,8 +135,8 @@
     <section>
       <title>History</title>
       <p>Forrest was started in January 2002, with the major use-case being to
-        create a consistent and efficient <link
-          href="http://xml.apache.org/">xml.apache.org</link> group of project
+        create a consistent and efficient 
+        <link href="http://xml.apache.org/">xml.apache.org</link> group of project
         websites with a
         uniform, lightweight, easy-to-navigate layout and structure.  In
         addition, Forrest was to be a Sourceforge-like project management
@@ -179,8 +179,8 @@
         </p>
         <p>
           The <link href="ext:forrest">Forrest website</link> is updated
-          manually as needed, while we develop the <link
-            href="site:forrestbot">forrestbot</link> facility which produces the
+          manually as needed, while we develop the 
+          <link href="site:forrestbot">forrestbot</link> facility which produces
the
           <link href="http://forrestbot.cocoondev.org/">automatically
             generated</link> site.
         </p>

Modified: forrest/trunk/src/documentation/content/xdocs/uri-namespace.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/uri-namespace.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/uri-namespace.xml	Sat Jun 12 06:10:04 2004
@@ -26,8 +26,7 @@
   <body> 
     <p>Since Forrest uses Cocoon as its documentation generation mechanism, it
       ships with a Cocoon
-      <link
-  href="http://cocoon.apache.org/userdocs/concepts/sitemap.html">sitemap</link>
+      <link href="http://cocoon.apache.org/userdocs/concepts/sitemap.html">sitemap</link>
   stating the so-called URI namespace being declared by Forrest. So this document
   serves as a background reader for people trying to understand the sitemap and
   the internal workings of the Cocoon link crawling. It should answer questions

Mime
View raw message