forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r602323 - in /forrest/trunk/site-author/content/xdocs: ./ docs_0_90/ docs_0_90/howto/ procedures/release/ tools/
Date Sat, 08 Dec 2007 05:34:00 GMT
Author: gmcdonald
Date: Fri Dec  7 21:33:57 2007
New Revision: 602323

Add rel=nofollow and convert to v2.0 DTD if needed


Modified: forrest/trunk/site-author/content/xdocs/contrib.xml
--- forrest/trunk/site-author/content/xdocs/contrib.xml (original)
+++ forrest/trunk/site-author/content/xdocs/contrib.xml Fri Dec  7 21:33:57 2007
@@ -15,7 +15,7 @@
   See the License for the specific language governing permissions and
   limitations under the License.
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "">
     <title>Contributing to Apache Forrest</title>
@@ -24,25 +24,25 @@
     <section id="introduction">
-        The Forrest Project is an <link href="">Open
-        Source</link> volunteer project released under a very liberal license.
+        The Forrest Project is an <a href="" rel="nofollow">Open
+        Source</a> volunteer project released under a very liberal license.
         This means there are many ways to contribute to the project - either
         with direct participation (coding, documenting, answering questions,
         proposing ideas, reporting bugs, suggesting bug-fixes, etc..) or by
         resource donations (staff time, conference presentations, publicity,
         software) and even general hardware/money
-        <link href="">donations</link>
+        <a href="">donations</a>
         via the ASF.
         To begin with, we suggest you to subscribe to the
-        <link href="site:mail-lists">Forrest mailing lists</link> (follow the
+        <a href="site:mail-lists">Forrest mailing lists</a> (follow the
         link for information on how to subscribe and to access the mail list
         archives). Listen-in for a while, to hear how others make contributions.
         You can get your local working copy of the
-        <link href="site:build">latest and greatest code</link> (which you find
+        <a href="site:build">latest and greatest code</a> (which you find
         in the Forrest module in the Subversion code repository). Review the
         todo list and the issue tracker, choose a task. Perhaps you have noticed
         something that needs patching, or have a new feature to contribute. Make
@@ -68,14 +68,14 @@
           and demonstrate features. Such samples can also enable automated testing.</li>
         <li>Debugging - producing reproduceable test cases and/or finding
           causes of bugs. Some known bugs are informally listed on To Do, and some are
-          recorded as issues (see <link href="#procedure">explanation
-      below</link>).</li>
+          recorded as issues (see <a href="#procedure">explanation
+      below</a>).</li>
         <li>Providing new use-cases and requirements. If you think that
         Forrest does not quite meet your needs then tell us about it.</li>
         <li>Specifying/analysing/designing new features - and beyond. If you
         wish to get further involved with this, please join the <code>forrest-dev</code> mailing
         list, install and try out Forrest and read some of the
-        <link href="site:mail-lists">mail archives</link>. You should have a reasonable
+        <a href="site:mail-lists">mail archives</a>. You should have a reasonable
       fluency in XML technologies, some Java and Ant skills, and a basic understanding of the Forrest
       architecture - don't just say "it should have XYZ" without reading anything
       first - because chances are, somebody has already thought of that feature!)</li>
@@ -95,11 +95,11 @@
         If you think that you have found a bug or you have a suggestion for
         improvement, then please discuss it on one of the
-        <link href="site:mail-lists">mailing lists</link>. However, please check
+        <a href="site:mail-lists">mailing lists</a>. However, please check
         our Issue Tracker first as it may be already reported.
-        The <link href="site:bugs">Apache Forrest Issue Tracker</link> collates
+        The <a href="site:bugs">Apache Forrest Issue Tracker</a> collates
         our known issues. Obviously not every issue is listed there. Some issues
         have been discussed on the mailing list but do not yet have an issue
@@ -126,7 +126,7 @@
         anonymous user. Therefore, you do not have the system permissions to
         change anything. You can only update your local repository and compare
         your revisions with the real repository. The
-        <link href="site:build">Building Forrest</link> document
+        <a href="site:build">Building Forrest</a> document
@@ -137,10 +137,10 @@
         documentation and discussion) and demonstrated committment, then the
         rest of the dev community may vote to grant this developer commit access
         to the Subversion repository. See the
-        <link href="">ASF developers resources</link>
+        <a href="">ASF developers resources</a>
         especially the
-        <link href="">Source code
-        repositories</link>.
+        <a href="">Source code
+        repositories</a>.
         You will need secure access to the repository to be able to commit
@@ -154,7 +154,7 @@
         use both Linux and Windows. SVN can understand that files are text (as
         opposed to binary like images), but this must be specified for every new
         file added. Your SVN client can be
-        <link href="">configured</link>
+        <a href="">configured</a>
         to automatically do this for certain file extensions. To do it manually,
         make sure all line endings are in your current OS's native format (the
         dos2unix and unix2dos utilities may be useful) and then do a <code>svn
@@ -169,8 +169,8 @@
         So that everyone can be productive, it is important to know which method
         is appropriate for a certain situation and how to go about it without
         confusion. This section explains when to use the developer
-        <link href="site:mail-lists">mailing list</link> and the
-        <link href="site:bugs">issue tracker</link>.
+        <a href="site:mail-lists">mailing list</a> and the
+        <a href="site:bugs">issue tracker</a>.
         Research your topic thoroughly before beginning to discuss a new
@@ -224,8 +224,8 @@
         For more information about working with SVN, see
-        <link href="">Version Control with
-        Subversion</link> - the opensource SVN book.
+        <a href="" rel="nofollow">Version Control with
+        Subversion</a> - the opensource SVN book.
         If you use a downloaded released version of Forrest (or don't use SVN),
@@ -233,24 +233,24 @@
         faq.xml.orig faq.xml > mypatch.txt</code>' (better to do that from
         $FORREST_HOME directory). If you want to use the most recent version of
         the documentation then grab its source file directly from the
-        <link href="">SVN
-        server</link> (and tell us which Revision number you used).
+        <a href="">SVN
+        server</a> (and tell us which Revision number you used).
-        Please send all contributions via our <link href="site:bugs">issue
-        tracker</link>. and specify the Forrest version or svn version of the
+        Please send all contributions via our <a href="site:bugs">issue
+        tracker</a>. and specify the Forrest version or svn version of the
         It is always a good idea to check the Forrest
-        <link href="site:bugs">issue tracker</link> before diving in.
+        <a href="site:bugs">issue tracker</a> before diving in.
     <section id="revert">
       <title>How to revert changes in SVN</title>
         Check out
-        <link href=""></link>
+        <a href="" rel="nofollow"></a>
         for instructions on how to revert (roll back) changes to svn.
@@ -262,7 +262,7 @@
         <li>See general ASF
-          <link href="">Tips for email contributors</link></li>
+          <a href="">Tips for email contributors</a></li>
         <li> Every contribution is worthwhile. Even if the ensuing discussion
           proves it to be off-beam, then it may jog ideas for other people. </li>
         <li> Use sensible and concise email subject headings. Search engines,
@@ -284,7 +284,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="site:catalog">configuration</link>.
+          <a href="site:catalog">configuration</a>.
         <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/site-author/content/xdocs/docs_0_90/build.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_90/build.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_90/build.xml Fri Dec  7 21:33:57 2007
@@ -15,7 +15,8 @@
   See the License for the specific language governing permissions and
   limitations under the License.
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN"
+  "">
     <title>Building Forrest</title>
@@ -27,17 +28,17 @@
         <title>Step-by-step Subversion (SVN) instructions for developers</title>
           If you are behind a proxy, see
-          <link href="">this
-          FAQ</link>.
+          <a href="" rel="nofollow">this
+          FAQ</a>.
           <li>Make sure you have a recent release of a
-           <link href="">Subversion</link>
+           <a href="" rel="nofollow">Subversion</a>
            client installed and properly configured.</li>
           <li>Read the ASF notes about source repositories and
-           <link href="">version control</link>
+           <a href="">version control</a>
            and see Forrest's developer notes about our
-           <link href="site:version-control">SVN</link>.
+           <a href="site:version-control">SVN</a>.
           <li>At a command prompt, enter
            '<code>svn co forrest</code>'
@@ -54,8 +55,8 @@
           SVN is really powerful. See
-          <link href="">Version Control with
-          Subversion</link> - the opensource SVN book.
+          <a href="" rel="nofollow">Version Control with
+          Subversion</a> - the opensource SVN book.
       <section id="release">
@@ -73,7 +74,7 @@
         This document applies to this specific version. See other
         instructions for the 
-        <link href="">development</link>
+        <a href="">development</a>
@@ -122,7 +123,7 @@
         in content/xdocs/*.xml see the immediate effect.
-        The document <link href="site:your-project">Using Forrest</link> is your
+        The document <a href="site:your-project">Using Forrest</a> is your
         next step.

Modified: forrest/trunk/site-author/content/xdocs/docs_0_90/catalog.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_90/catalog.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_90/catalog.xml Fri Dec  7 21:33:57 2007
@@ -15,7 +15,8 @@
   See the License for the specific language governing permissions and
   limitations under the License.
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN"
+  "">
     <title>Using Catalog Entity Resolver for local DTDs</title>
@@ -121,16 +122,16 @@
           See other notes about using
-          <link href="">Vim as XML
-          editor</link>.
+          <a href="" rel="nofollow">Vim as XML
+          editor</a>.
       <section id="emacs">
-          See <link href="">nXML
-          mode</link> and
-          <link href="">FAQ</link>.
+          See <a href="" rel="nofollow">nXML
+          mode</a> and
+          <a href="" rel="nofollow">FAQ</a>.
       <section id="onsgmls">
@@ -215,8 +216,8 @@
             XXE supports catalogs by automatic detection via configuration
             files. Download the
-            <fork href="">XXE
-            Forrest Config</fork> files from; this also add support
+            <a href="" rel="nofollow">XXE
+            Forrest Config</a> files from; this also add support
             for WYSIWYG editing of forrest documents. Note: This configuration
             suite has recently been added to the Forrest scratchpad.
@@ -227,20 +228,20 @@
       <title>Further information and resources</title>
         Forrest and Cocoon use the
-        <link href="">Catalog
-        Entity Resolver</link> that is provided by the
-        <link href="">Apache XML Commons</link>
+        <a href="">Catalog
+        Entity Resolver</a> that is provided by the
+        <a href="">Apache XML Commons</a>
         project. The resolver is packaged with the Forrest distribution at
         Other Forrest documentation has some notes about configuring the entity
-        resolver for your own DTDs. See <link href="site:validation">XML
-        Validation</link>.
+        resolver for your own DTDs. See <a href="site:validation">XML
+        Validation</a>.
         Cocoon has extensive documentation about the entity resolver. See
-        <link href="ext:cocoon/catalogs">Entity resolution with catalogs</link>.
+        <a href="ext:cocoon/catalogs">Entity resolution with catalogs</a>.

Modified: forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-buildPlugin.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-buildPlugin.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-buildPlugin.xml Fri Dec  7 21:33:57 2007
@@ -315,7 +315,7 @@
         It is also a really good idea to build proper tests for your plugins
         using a suitable testing framework, for example,
-        <a href="">WebTest</a>. We recommend that you
+        <a href="" rel="nofollow">WebTest</a>. We recommend that you
         extend the <code>test</code> target in your plugins build file because
         this target is also used when performing integration tests on Forrest.
         In addition, we recommend that you use the samples in your documentation

Modified: forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-corner-images.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-corner-images.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-corner-images.xml Fri Dec  7 21:33:57 2007
@@ -38,7 +38,7 @@
   <purpose title="Purpose">
       Forrest renders the corner images through
-      <a href="">Scalable Vector Graphics (SVG)</a>. It
+      <a href="" rel="nofollow">Scalable Vector Graphics (SVG)</a>. It
       may be necessary to change the color of the corner images to be suitable
       for your own skin colors.

Modified: forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-editcss.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-editcss.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-editcss.xml Fri Dec  7 21:33:57 2007
@@ -61,11 +61,11 @@
         Firefox-Browser installed on your system. 
         If you don't already use it, you can 
         download it from <a 
-        href=""></a></li>
+        href="" rel="nofollow"></a></li>
       <li>The Firefox-PlugIn EditCSS. It downloads 
         and installs in just a few seconds from the 
         Install-Link at <a 
-        href=""></a>
+        href="" rel="nofollow"></a>
           With standard security settings in place, Firefox will pop up a line
           at the top of the window because this site has by default no
@@ -77,7 +77,7 @@
       <li>A basic understanding of CSS and access to 
         a good CSS-reference. Tutorials and 
         Reference can be found at <a 
-        href=""></a>.</li>
+        href="" rel="nofollow"></a>.</li>
   <steps title="Steps">

Modified: forrest/trunk/site-author/content/xdocs/docs_0_90/your-project.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_90/your-project.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_90/your-project.xml Fri Dec  7 21:33:57 2007
@@ -15,7 +15,8 @@
   See the License for the specific language governing permissions and
   limitations under the License.
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN"
+  "">
     <title>Using Forrest</title>
@@ -34,10 +35,10 @@
     <section id="installing">
       <title>Installing Forrest</title>
-        <link href="ext:forrest/download">Download</link> the latest release of
+        <a href="ext:forrest/download">Download</a> the latest release of
         Forrest and follow the index.html in the top-level, or if you want to
-        try the development version, then <link href="site:build">build
-        Forrest</link> from source.
+        try the development version, then <a href="site:build">build
+        Forrest</a> from source.
         <title>Setting up the Environment</title>
@@ -47,7 +48,7 @@
           available everywhere and it can locate its home directory and
           resources. It is beyond the scope of Forrest to explain how to manage
           your operating system. Some tips are listed below and this
-          <link href="">message</link>
+          <a href="" rel="nofollow">message</a>
           explains further and provides other tips about using Windows.
@@ -358,7 +359,7 @@
         Forrest where the XML sources are, rather than rearrange your project
         directories to accommodate Forrest. This can be done by editing
         <code></code> (consult the
-        <link href="#Changing_the_layout">Changing the layout</link> section for
+        <a href="#Changing_the_layout">Changing the layout</a> section for
         more details).
@@ -456,9 +457,9 @@
     (if the skin supports it).
-    <link1 name="myGroup" href=""/>
-    <link2 name="myProject" href=""/>
-    <link3 name="" href=""/>
+    <a1 name="myGroup" href=""/>
+    <a2 name="myProject" href=""/>
+    <a3 name="" href=""/>
   <!-- Configure the TOC, i.e. the Table of Contents.
@@ -596,7 +597,7 @@
           For example, to emulate the simple
-          <link href="">Maven</link> format:
+          <a href="">Maven</a> format:
@@ -638,7 +639,7 @@
           index, and is rendered as the vertical column of links in the default
           skin. Look at Forrest's own xdocs for an example. More detailed info
           about site.xml is provided in the document
-          <link href="site:linking">Menus and Linking</link>.
+          <a href="site:linking">Menus and Linking</a>.
       <section id="tabs.xml">
@@ -646,7 +647,7 @@
           The <code>tabs.xml</code> file is used to produce the 'tabs'. which
           enable users to quickly jump to sections of your site. See the
-          <link href="site:menu_generation">menu generation</link> documentation
+          <a href="site:menu_generation">menu generation</a> documentation
           for more details, and again, consult Forrest's own docs for a usage
@@ -688,8 +689,8 @@
         The Cocoon sitemap is a set of rules for generating content (HTML, PDFs
         etc) from XML sources. Forrest has a default sitemap, which is adequate
-        for everyday sites. For example, the <link href="site:forrest">Forrest
-        website</link> itself uses the default sitemap.
+        for everyday sites. For example, the <a href="site:forrest">Forrest
+        website</a> itself uses the default sitemap.
         Sometimes, one needs to go beyond the default set of rules. This is
@@ -699,7 +700,7 @@
         <li>Transform custom XML content types with XSLT stylesheets.</li>
         <li>Generate PNG or JPEG images from 
-        <link href="">SVG</link> XML files.
+        <a href="" rel="nofollow">SVG</a> XML files.
           (<strong>Note:</strong> Forrest's sitemap now does this natively.)</li>
         <li>Integrate external XML feeds (e.g. RSS) into your site's content.
           (<strong>Note:</strong> See issues.xmap for an example.)</li>
@@ -710,9 +711,9 @@
           and PDF, available as the standard names <code>wholesite.html</code>
           and <code>wholesite.pdf</code>.)</li>
         <li>Read content from exotic sources like
-        <link href="">XML
-            databases</link>.</li>
-        <li>Integrate any of <link href="ext:cocoon">Cocoon's</link> vast array
+        <a href="" rel="nofollow">XML
+            databases</a>.</li>
+        <li>Integrate any of <a href="ext:cocoon">Cocoon's</a> vast array
           of capabilities.  The possibilities are best appreciated by
           downloading the latest Cocoon distribution and playing with the
@@ -729,17 +730,17 @@
         Any match that is not handled, passes through to be handled by the
         default Forrest sitemaps - obviously extremely powerful. The capability
-        is described in "<link href="site:project-sitemap">Using project
-        sitemaps</link>" and some worked examples are shown in the following
+        is described in "<a href="site:project-sitemap">Using project
+        sitemaps</a>" and some worked examples are shown in the following
         sections here.
         We advise you to spend time to understand the Apache Cocoon sitemap. See
-        <link href="ext:cocoon/sitemap">Cocoon sitemap</link> and
-        <link href="ext:cocoon/concepts">Cocoon concepts</link> and related
+        <a href="ext:cocoon/sitemap">Cocoon sitemap</a> and
+        <a href="ext:cocoon/concepts">Cocoon concepts</a> and related
         component documentation. 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>
+        others. See the <a href="site:sitemap-ref">Sitemap Reference</a>
         for a tour of the default sitemap.
       <section id="adding_new_content_type">
@@ -747,7 +748,7 @@
           There are two methods for detecting types of documents and doing
           special handling. The more complete solution is
-          <link href="#adding_new_content_type_2">described</link> in the
+          <a href="#adding_new_content_type_2">described</a> in the
           advanced section below. However, this basic method is also worth
@@ -835,7 +836,7 @@
   <xsl:template match="file">
-      <td><link href="{@url}"><xsl:value-of select="@name"/></link></td>
+      <td><a href="{@url}"><xsl:value-of select="@name"/></a></td>
            select="format-number(@size div (1024*1024), '##.##')"/> MB</td>
@@ -862,7 +863,7 @@
-          The <link href="site:sitemap-ref">Sitemap Reference</link> provides
+          The <a href="site:sitemap-ref">Sitemap Reference</a> provides
           details about how the sitemap works.
@@ -902,7 +903,7 @@
             By default, Forrest requires that all XML files be valid, i.e. they
             must have a DOCTYPE declaration and associated DTD, and validate
             against it. Our new 'downloads' document type is no exception. The
-            <link href="site:validation">XML Validation</link> document
+            <a href="site:validation">XML Validation</a> document
             continues this example, showing how to register a new document type.
             Briefly, this involves:
@@ -916,7 +917,7 @@
             <li>Tell the system about your catalog.</li>
-            Please see <link href="site:validation">XML Validation</link> for
+            Please see <a href="site:validation">XML Validation</a> for
             the complete description for those steps.
@@ -931,8 +932,8 @@
           We need to digress and explain the powerful
-          <link href="site:cap">SourceTypeAction (content aware
-          pipelines)</link>. It is a Cocoon sitemap component that peeks at the
+          <a href="site:cap">SourceTypeAction (content aware
+          pipelines)</a>. It is a Cocoon sitemap component that peeks at the
           top-part of a document to look for hints about the type of the
           document. It has four methods: document-declaration, document-element
           and namespace, processing-instruction, w3c-xml-schema.
@@ -994,10 +995,10 @@
           This is the type of processing that happens in the main
           <code>main/webapp/forrest.xmap</code> sitemap. We have added similar
           handling to our project sitemap. Basically, this uses the
-          <link href="site:cap">SourceTypeAction (content aware
-          pipelines)</link> to detect the doctype. The new document-v11.dtd
+          <a href="site:cap">SourceTypeAction (content aware
+          pipelines)</a> to detect the doctype. The new document-v11.dtd
           needs to be also added to your project Catalog as
-          <link href="#new_dtd">described above</link>.
+          <a href="#new_dtd">described above</a>.
           Note that any sitemap component must be declared before it can be
@@ -1056,8 +1057,8 @@
         dynamic mode you need to restart Forrest in order to see the new skin.
-        Forrest supplies a collection of <link href="site:default-skins">default
-        skins</link> which are configurable and so should meet the needs of most
+        Forrest supplies a collection of <a href="site:default-skins">default
+        skins</a> 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.
@@ -1144,9 +1145,9 @@
       <title>Interactive Forrest: faster turnaround when developing your docs</title>
         In comparison to simpler tools (like
-        <link href="ext:anakia">Anakia</link>) the Cocoon command-line mode (and
+        <a href="ext:anakia">Anakia</a>) the Cocoon command-line mode (and
         hence Forrest command-line mode) is slow. As the
-        <link href="site:dreams">dream list</link> notes, Forrest was originally
+        <a href="site:dreams">dream list</a> notes, Forrest was originally
         intended to be used for dynamic sites, and the Cocoon crawler used only
         to create static snapshots for mirroring. This section describes how, by
         using a "live" Forrest webapp instance, the Forrest-based documentation
@@ -1158,7 +1159,7 @@
           Type '<code>forrest run</code>' in your project root to start
           Forrest's built-in Jetty web server. Once it has started, point your
           browser at
-          <link href="http://localhost:8888/">http://localhost:8888/</link>,
+          <a href="http://localhost:8888/">http://localhost:8888/</a>,
           which will show your website, rendered on demand as each link is
@@ -1181,7 +1182,7 @@
       <title>Invoking Forrest from Ant</title>
         Ant has an
-        <link href="">&lt;import&gt;</link>
+        <a href="">&lt;import&gt;</a>
         task which can be used to invoke Forrest from Ant. All targets and
         properties are imported and can be used in your project build. Here is a
         simple example:
@@ -1203,7 +1204,7 @@
         See issue
-        <link href="">FOR-145</link>
+        <a href="">FOR-145</a>
         which causes clashes of Ant target names.
@@ -1228,11 +1229,11 @@
         Another option is to use the Forrest Antlet from the Krysalis Project's
-        <link href="">Antworks
-        Importer</link>.
+        <a href="">Antworks
+        Importer</a>.
-        The <link href="site:forrestbot">Forrestbot</link> provides workstages
+        The <a href="site:forrestbot">Forrestbot</a> provides workstages
         to get source, build, deploy, and notify. This is very useful for
         automating builds; you may want to consider using the Forrestbot.

Modified: forrest/trunk/site-author/content/xdocs/howto-dev.xml
--- forrest/trunk/site-author/content/xdocs/howto-dev.xml (original)
+++ forrest/trunk/site-author/content/xdocs/howto-dev.xml Fri Dec  7 21:33:57 2007
@@ -140,7 +140,7 @@
         Whether you use the svn command-line client or a fancy client, then you
         still need to make sure you know how to operate SVN properly.
-        <a href=""></a>
+        <a href="" rel="nofollow"></a>
         is a must.
       <section id="multiple">
@@ -224,7 +224,7 @@
           More information can be found at
-          <a href="">Common
+          <a href="" rel="nofollow">Common
           use-cases for merging</a> section of the Red Bean SVN Book.
@@ -249,7 +249,7 @@
             Keep a copy of this book, or the online version, close at hand:
-            <a href="">Version Control with Subversion</a>
+            <a href="" rel="nofollow">Version Control with Subversion</a>
             - the opensource SVN book.
@@ -310,7 +310,7 @@
         <fixme author="open">
           The issues of whitespace and line endings needs to be very clearly
           described. See some
-          <a href=";m=112450886218545">mail
+          <a href=";m=112450886218545" rel="nofollow">mail
           discussion</a> references.

Modified: forrest/trunk/site-author/content/xdocs/howto-howto.xml
--- forrest/trunk/site-author/content/xdocs/howto-howto.xml (original)
+++ forrest/trunk/site-author/content/xdocs/howto-howto.xml Fri Dec  7 21:33:57 2007
@@ -223,10 +223,10 @@
       <li>Joel D. Canfield's <a
-      href="">How
+      href="" rel="nofollow">How
       to Write a How-To</a> on</li>
       <li>The Linux Documentation Project's <a
-      href="">HOWTO</a>
+      href="" rel="nofollow">HOWTO</a>
       index page provides many excellent How-To documents to inspire your

Modified: forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
--- forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml (original)
+++ forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml Fri Dec  7 21:33:57 2007
@@ -228,7 +228,7 @@
             Look at
-                            href="">msg02310.html</a>
+                            href="" rel="nofollow">msg02310.html</a>
             for an example of such a message.
@@ -315,7 +315,7 @@
         ensures that it is the PMC as a whole that prepares and issues the
         release, rather than an individual. Such procedures give us the
         protection accorded by the ASF being a corporation. See a good
-        discussion <a href="">in
+        discussion <a href="" rel="nofollow">in
         the archives</a>.
@@ -1024,30 +1024,30 @@
             See previous announcements for examples:
-            <a href=";m=117688881228702">0.8</a>
+            <a href=";m=117688881228702" rel="nofollow">0.8</a>
-            <a href=";m=111960678028211">0.7</a>
+            <a href=";m=111960678028211" rel="nofollow">0.7</a>
-            <a href=";m=109784461425740">0.6</a>
+            <a href=";m=109784461425740" rel="nofollow">0.6</a>
-            <a href=";m=106541447606765">0.5.1</a>
+            <a href=";m=106541447606765" rel="nofollow">0.5.1</a>
-            <a href=";m=106352706005681">0.5</a>
+            <a href=";m=106352706005681" rel="nofollow">0.5</a>
-            <a href=";m=104510734501302">0.4</a>
+            <a href=";m=104510734501302" rel="nofollow">0.4</a>
-            <a href=";m=104399934113331">0.3</a>
+            <a href=";m=104399934113331" rel="nofollow">0.3</a>
-            <a href=";m=103746673310573">0.2</a>
+            <a href=";m=103746673310573" rel="nofollow">0.2</a>
             Do the Freshmeat announcement:
-            <a href=""></a>
+            <a href="" rel="nofollow"></a>
                   Update the release information at our
-                  <a href="">Wikipedia</a> page.
+                  <a href="" rel="nofollow">Wikipedia</a> page.

Modified: forrest/trunk/site-author/content/xdocs/subversion_bestpractices.xml
--- forrest/trunk/site-author/content/xdocs/subversion_bestpractices.xml (original)
+++ forrest/trunk/site-author/content/xdocs/subversion_bestpractices.xml Fri Dec  7 21:33:57 2007
@@ -40,12 +40,12 @@
         <li>See ASF-wide notes for <a href="">developers</a>.
-        <li>Use the <a href="">SVN Book</a> - Version Control with Subversion.
+        <li>Use the <a href="" rel="nofollow">SVN Book</a> - Version Control with Subversion.
         <li><a href="contrib.html#svn-config">Configure</a> your svn client.
           <fixme author="">
             Move the notes from contrib.html to here. See other notes in
-            <a href="">email</a>.
+            <a href="" rel="nofollow">email</a>.
         <li>When moving an existing file  please use "svn move fromFile toFile". This ensures 
              that the history of the item is not lost.</li>

Modified: forrest/trunk/site-author/content/xdocs/tools/eclipse.xml
--- forrest/trunk/site-author/content/xdocs/tools/eclipse.xml (original)
+++ forrest/trunk/site-author/content/xdocs/tools/eclipse.xml Fri Dec  7 21:33:57 2007
@@ -38,8 +38,7 @@
         To get you started while the documentation is being developed, see this
         forrest-dev mail thread:
-        <a href=""> [eclipse] How
-        to install? </a> .
+        <a href="" rel="nofollow"> [eclipse] How to install? </a> .

Modified: forrest/trunk/site-author/content/xdocs/tools/xxe.xml
--- forrest/trunk/site-author/content/xdocs/tools/xxe.xml (original)
+++ forrest/trunk/site-author/content/xdocs/tools/xxe.xml Fri Dec  7 21:33:57 2007
@@ -15,8 +15,7 @@
   See the License for the specific language governing permissions and
   limitations under the License.
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" 
-  "">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "">
     <title>XXE Forrest Configuration</title>
@@ -27,7 +26,7 @@
       just that we provide this tool to take advantage of XXE.
-      <link href="">XMLmind XML Editor</link>
+      <a href="" rel="nofollow">XMLmind XML Editor</a>
       is a validating XML editor featuring a word processor-like view. We
       support the Forrest plugin for XXE only, please direct all XXE-related
       questions to XXE support or mailing lists.
@@ -71,9 +70,9 @@
         the build there to copy the DTDs
-        <link 
-          href="">
-        XXE Custom Configuration Info</link>
+        <a 
+          href="" rel="nofollow">
+        XXE Custom Configuration Info</a>

Modified: forrest/trunk/site-author/content/xdocs/zone.xml
--- forrest/trunk/site-author/content/xdocs/zone.xml (original)
+++ forrest/trunk/site-author/content/xdocs/zone.xml Fri Dec  7 21:33:57 2007
@@ -217,7 +217,7 @@
       <title>Other notes</title>
         <li>See some other discussion in the thread
-          <a href=";m=111717382712670">Re: zone for testing forrest</a></li>
+          <a href=";m=111717382712670" rel="nofollow">Re: zone for testing forrest</a></li>

View raw message