forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r527010 [18/26] - in /forrest/trunk/site-author/content: ./ skins/ xdocs/ xdocs/docs_0_70/ xdocs/docs_0_70/howto/ xdocs/docs_0_70/howto/bugzilla-patch/ xdocs/docs_0_70/howto/cvs-ssh/ xdocs/docs_0_70/howto/multi/ xdocs/docs_0_80/ xdocs/docs_...
Date Tue, 10 Apr 2007 03:48:57 GMT
Modified: forrest/trunk/site-author/content/xdocs/dtdx/document-v11.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/dtdx/document-v11.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/dtdx/document-v11.xml (original)
+++ forrest/trunk/site-author/content/xdocs/dtdx/document-v11.xml Mon Apr  9 20:48:52 2007
@@ -16,62 +16,67 @@
   limitations under the License.
 -->
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "http://forrest.apache.org/dtd/document-v11.dtd">
-<document> 
-  <header> 
-    <title>The document-v1.1 DTD</title> 
-    <notice>This document doesn't make any sense at all.</notice> 
-    <abstract>A nonsense document using all possible elements in the current
-      <code>document-v11.dtd</code>.</abstract> 
-  </header> 
-  <body> 
-    <note>document-v11 has been superceded by <link
-        href="site:v0.70//document-v12">document-v12</link></note> 
-
-     <p>This is a simple paragraph. Most documents contain a fair amount of
-      paragraphs. Paragraphs are called <code>&lt;p&gt;</code>.</p> 
-    <p xml:space="preserve"
-  >With the <code>&lt;p xml:space="preserve"&gt;</code> attribute, you can declare
-that whitespace should    be   preserved, without implying it is in any other
-way special.</p>
-    <p>A number of in-line elements are available in the DTD, we will show them
-      inside an unordered list (<code>&lt;ul&gt;</code>):</p> 
-    <ul> 
-      <li>Here is a simple list item (<code>&lt;li&gt;</code>).</li> 
+<document>
+  <header>
+    <title>The document-v1.1 DTD</title>
+    <notice>This document doesn't make any sense at all.</notice>
+    <abstract>
+      A nonsense document using all possible elements in the current
+      <code>document-v11.dtd</code>.
+    </abstract>
+  </header>
+  <body>
+    <note>
+      document-v11 has been superceded by
+      <link
+        href="site:v0.70//document-v12">document-v12</link>
+    </note>
+    <p>
+      This is a simple paragraph. Most documents contain a fair amount of
+      paragraphs. Paragraphs are called <code>&lt;p&gt;</code>.
+    </p>
+    <p xml:space="preserve">
+      With the <code>&lt;p xml:space="preserve"&gt;</code> attribute, you can declare
+      that whitespace should    be   preserved, without implying it is in any other
+      way special.
+    </p>
+    <p>
+      A number of in-line elements are available in the DTD, we will show them
+      inside an unordered list (<code>&lt;ul&gt;</code>):
+    </p>
+    <ul>
+      <li>Here is a simple list item (<code>&lt;li&gt;</code>).</li>
       <li>Have you seen the use of the <code>&lt;code&gt;</code> element in the
-        previous item?</li> 
+        previous item?</li>
       <li>Also, we have <code>&lt;sub&gt;</code> and <code>&lt;sup&gt;</code>
         elements to show content <sup>above</sup> or <sub>below</sub> the text
-        baseline.</li> 
+        baseline.</li>
       <li>There is a facility to <em>emphasize</em> certain words using the
-        <code>&lt;em&gt;</code> element.</li> 
+        <code>&lt;em&gt;</code> element.</li>
       <li>We can use
-        <icon height="22" width="26" src="images/icon.png" alt="feather"/>
-        <code>&lt;icon&gt;</code>s, too.</li> 
+        <icon height="22" width="26" src="images/icon.png" alt="feather"/><code>&lt;icon&gt;</code>s, too.</li>
       <li>Another possibility is the <code>&lt;img&gt;</code> element:
         <img src="images/icon.png" alt="another feather" height="22" width="26"/>,
-        which offers the ability to refer to an image map.</li> 
+        which offers the ability to refer to an image map.</li>
       <li>We have elements for hyperlinking: 
-        <dl> 
-          <dt><code>&lt;link href="your-project.html"&gt;</code></dt> 
+        <dl>
+          <dt><code>&lt;link href="your-project.html"&gt;</code></dt>
           <dd>Use this to
             <link href="your-project.html" title="Example of a document via link">link</link>
            to another document. As per normal, this will open the new document
-           in the same browser window.</dd> 
-
-          <dt><code>&lt;link href="#section"&gt;</code></dt> 
+           in the same browser window.</dd>
+          <dt><code>&lt;link href="#section"&gt;</code></dt>
           <dd>Use this to
             <link href="#section" title="Example of a document via local anchor">link</link>
            to the named anchor in the current document.
-          </dd> 
-
-          <dt><code>&lt;link href="your-project.html#images"&gt;</code></dt> 
+          </dd>
+          <dt><code>&lt;link href="your-project.html#images"&gt;</code></dt>
           <dd>Use this to
             <link href="your-project.html#images" title="Example of a document via link and anchor">link</link>
            to another document and go to the named anchor. This will open
            the new document in the same browser window.
-          </dd> 
-
-          <dt><code>&lt;jump href="your-project.html"&gt;</code></dt> 
+          </dd>
+          <dt><code>&lt;jump href="your-project.html"&gt;</code></dt>
           <dd>Use this to
             <jump href="your-project.html" title="Example of a document via jump">jump</jump>
            to another document and optionally go to a named
@@ -81,64 +86,77 @@
            The jump behaves differently, in that it will replace any frames
            in the current window.
            This is the equivalent of
-           <code>&lt;a ... target="_top"&gt;</code>
-          </dd>
-
-          <dt><code>&lt;fork href="your-project.html"&gt;</code></dt> 
+           <code>&lt;a ... target="_top"&gt;</code></dd>
+          <dt><code>&lt;fork href="your-project.html"&gt;</code></dt>
           <dd>Use this to
             <fork href="your-project.html" title="Example of a document via fork">fork</fork>
            your webbrowser to another document. This will open the document
            in a new, unnamed browser window.
            This is the equivalent of
-           <code>&lt;a ... target="_blank"&gt;</code>
-          </dd> 
-  </dl></li> 
-
-  <li>Oh, by the way, a definition list <code>&lt;dl&gt;</code> was used inside
+           <code>&lt;a ... target="_blank"&gt;</code></dd>
+        </dl></li>
+      <li>Oh, by the way, a definition list <code>&lt;dl&gt;</code> was used inside
    the previous list item. We could put another 
-    <ul> 
-      <li>unordered list</li> 
-      <li>inside the list item</li> 
-    </ul> too, but I believe this liberty gets quickly quite hairy as you
-    see.</li> 
-  </ul> 
-  <p>So far for the in-line elements, let's look at some paragraph-level
-    elements.</p> 
-  <fixme author="SN">The <code>&lt;fixme&gt;</code> element is used for stuff
-    which still needs work. Mind the <code>author</code> attribute!</fixme> 
-  <note>Use the <code>&lt;note&gt;</code> element to draw attention to something, e.g. ...The <code>&lt;code&gt;</code> element is used when the author can't
-    express himself clearly using normal sentences ;-)</note>
-  <warning>Sleep deprivation can be the result of being involved in an open
-    source project. (a.k.a. the <code>&lt;warning&gt;</code> element).</warning> 
-  <p>Apart from unordered lists, we have ordered lists too, of course.</p> 
-  <ol> 
-    <li>Item 1</li> 
-    <li>Item 2</li> 
-    <li>This should be 3 if my math is still OK.</li> 
-  </ol> 
-
-  <anchor id="section"/>
-  <section> 
-    <title>Using sections</title>
-    <p>You can use sections to put some structure in your document. For some
-      strange historical reason, the section title is an attribute of the
-      <code>&lt;section&gt;</code> element.</p> 
-  </section> 
-  <section>
-    <title>Sections, the sequel</title>
-    <p>Just some second section.</p> 
+    <ul>
+          <li>unordered list</li>
+          <li>inside the list item</li>
+        </ul> too, but I believe this liberty gets quickly quite hairy as you
+    see.</li>
+    </ul>
+    <p>
+      So far for the in-line elements, let's look at some paragraph-level
+      elements.
+    </p>
+    <fixme author="SN">
+      The <code>&lt;fixme&gt;</code> element is used for stuff which still needs
+      work. Mind the <code>author</code> attribute!
+    </fixme>
+    <note>
+      Use the <code>&lt;note&gt;</code> element to draw attention to something,
+      e.g. ...The <code>&lt;code&gt;</code> element is used when the author
+      can't express himself clearly using normal sentences ;-)
+    </note>
+    <warning>
+      Sleep deprivation can be the result of being involved in an open source
+      project. (a.k.a. the <code>&lt;warning&gt;</code> element).
+    </warning>
+    <p>
+      Apart from unordered lists, we have ordered lists too, of course.
+    </p>
+    <ol>
+      <li>Item 1</li>
+      <li>Item 2</li>
+      <li>This should be 3 if my math is still OK.</li>
+    </ol>
+    <anchor id="section"/>
     <section>
-	   <title>Section 2.1</title>
-      <p>Which contains a subsection (2.1).</p> 
-    </section> 
-  </section> 
-
-  <anchor id="source"/>
-  <section>
-  <title>Showing preformatted source code</title> 
-  <p>Enough about these sections. Let's have a look at more interesting
-    elements, <code>&lt;source&gt;</code> for instance:</p> 
-  <source>// This example is from the book _Java in a Nutshell_ by David Flanagan.
+      <title>Using sections</title>
+      <p>
+        You can use sections to put some structure in your document. For some
+        strange historical reason, the section title is an attribute of the
+        <code>&lt;section&gt;</code> element.
+      </p>
+    </section>
+    <section>
+      <title>Sections, the sequel</title>
+      <p>
+        Just some second section.
+      </p>
+      <section>
+        <title>Section 2.1</title>
+        <p>
+          Which contains a subsection (2.1).
+        </p>
+      </section>
+    </section>
+    <anchor id="source"/>
+    <section>
+      <title>Showing preformatted source code</title>
+      <p>
+        Enough about these sections. Let's have a look at more interesting
+        elements, <code>&lt;source&gt;</code> for instance:
+      </p>
+      <source>// This example is from the book _Java in a Nutshell_ by David Flanagan.
 // Written by David Flanagan.  Copyright (c) 1996 O'Reilly &amp; Associates.
 // You may study, use, modify, and distribute this example for any purpose.
 // This example is provided WITHOUT WARRANTY either expressed or implied.
@@ -153,37 +171,42 @@
         g.drawString("Hello World", 25, 50);
     }
 }</source>
-  <p>Please take care to still use a sensible line-length within your
-   source elements.</p>
-  </section>
-
-  <anchor id="table"/>
-  <section>
-  <title>Using tables</title>
-  <p>And now for a table:</p>
-  <table> 
-    <caption>Table caption</caption> 
-    <tr> 
-      <th>heading cell</th> 
-      <th>heading cell</th> 
-    </tr> 
-    <tr> 
-      <td>data cell</td> 
-      <td>data cell</td> 
-    </tr> 
-  </table> 
-  <p>Not much of attributes with <code>&lt;table&gt;</code>, if you ask me.</p>
-  </section>
-
-  <anchor id="figure"/>
-  <section> 
-   <title>Using figures</title>
-  
-  <p>And a figure to end all of this.</p>
-  <figure src="images/project-logo.png" alt="The fine Forrest logo" width="220" height="65"/>	
-  </section>
-  </body> 
-  <footer> 
+      <p>
+        Please take care to still use a sensible line-length within your source
+        elements.
+      </p>
+    </section>
+    <anchor id="table"/>
+    <section>
+      <title>Using tables</title>
+      <p>
+        And now for a table:
+      </p>
+      <table>
+        <caption>Table caption</caption>
+        <tr>
+          <th>heading cell</th>
+          <th>heading cell</th>
+        </tr>
+        <tr>
+          <td>data cell</td>
+          <td>data cell</td>
+        </tr>
+      </table>
+      <p>
+        Not much of attributes with <code>&lt;table&gt;</code>, if you ask me.
+      </p>
+    </section>
+    <anchor id="figure"/>
+    <section>
+      <title>Using figures</title>
+      <p>
+        And a figure to end all of this.
+      </p>
+      <figure src="images/project-logo.png" alt="The fine Forrest logo" width="220" height="65"/>
+    </section>
+  </body>
+  <footer>
     <legal>Copyright 2002-2005 The Apache Software Foundation or its licensors,
       as applicable.</legal>
   </footer>

Modified: forrest/trunk/site-author/content/xdocs/dtdx/document-v12.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/dtdx/document-v12.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/dtdx/document-v12.xml (original)
+++ forrest/trunk/site-author/content/xdocs/dtdx/document-v12.xml Mon Apr  9 20:48:52 2007
@@ -16,17 +16,20 @@
   limitations under the License.
 -->
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
-<document> 
-  <header> 
-    <title>The document-v1.2 DTD</title> 
-    <notice>This document doesn't make any sense at all.</notice> 
-    <abstract>A nonsense document using all possible elements in the current
-      <code>document-v12.dtd</code>.</abstract> 
-  </header> 
-  <body> 
-    <note>The document-v12 has been superceded by
+<document>
+  <header>
+    <title>The document-v1.2 DTD</title>
+    <notice>This document doesn't make any sense at all.</notice>
+    <abstract>
+      A nonsense document using all possible elements in the current
+      <code>document-v12.dtd</code>.
+    </abstract>
+  </header>
+  <body>
+    <note>
+      The document-v12 has been superceded by
       <link href="site:v0.70//document-v13">document-v13</link>
-    </note> 
+    </note>
     <section>
       <title>Changes since document-v11</title>
       <p>
@@ -56,56 +59,58 @@
     </section>
     <section>
       <title>Sample Content</title>
-      <p><strong>Hint:</strong> See the xml source to see how the various
-      elements are used and see the
-      <link href="site:v0.70//dtd-docs">DTD documentation</link>.
-      </p>
-      <p>This is a simple paragraph. Most documents contain a fair amount of
-        paragraphs. Paragraphs are called <code>&lt;p&gt;</code>.</p> 
-      <p xml:space="preserve"
-        >With the <code>&lt;p xml:space="preserve"&gt;</code> attribute, you can declare
+      <p>
+        <strong>Hint:</strong> See the xml source to see how the various
+        elements are used and see the <link href="site:v0.70//dtd-docs">DTD
+        documentation</link>.
+      </p>
+      <p>
+        This is a simple paragraph. Most documents contain a fair amount of
+        paragraphs. Paragraphs are called <code>&lt;p&gt;</code>.
+      </p>
+      <p xml:space="preserve">
+        With the <code>&lt;p xml:space="preserve"&gt;</code> attribute, you can declare
         that whitespace should    be   preserved, without implying it is in any other
-        way special.</p>
-      <p>A number of in-line elements are available in the DTD, we will show them
-        inside an unordered list (<code>&lt;ul&gt;</code>):</p> 
-      <ul> 
-        <li>Here is a simple list item (<code>&lt;li&gt;</code>).</li> 
+        way special.
+      </p>
+      <p>
+        A number of in-line elements are available in the DTD, we will show them
+        inside an unordered list (<code>&lt;ul&gt;</code>):
+      </p>
+      <ul>
+        <li>Here is a simple list item (<code>&lt;li&gt;</code>).</li>
         <li>Have you seen the use of the <code>&lt;code&gt;</code> element in the
-          previous item?</li> 
+          previous item?</li>
         <li>Also, we have <code>&lt;sub&gt;</code> and <code>&lt;sup&gt;</code>
           elements to show content <sup>above</sup> or <sub>below</sub> the text
-          baseline.</li> 
+          baseline.</li>
         <li>There is a facility to <em>emphasize</em> certain words using the
-          <code>&lt;em&gt;</code> <strong><code>&lt;strong&gt;</code></strong>
-          elements.</li> 
+          <code>&lt;em&gt;</code><strong><code>&lt;strong&gt;</code></strong>
+          elements.</li>
         <li>We can use
-          <icon height="22" width="26" src="images/icon.png" alt="feather"/>
-          <code>&lt;icon&gt;</code>s, too.</li> 
+          <icon height="22" width="26" src="images/icon.png" alt="feather"/><code>&lt;icon&gt;</code>s, too.</li>
         <li>Another possibility is the <code>&lt;img&gt;</code> element:
           <img src="images/icon.png" alt="another feather" height="22" width="26"/>,
-          which offers the ability to refer to an image map.</li> 
+          which offers the ability to refer to an image map.</li>
         <li>We have elements for hyperlinking: 
-          <dl> 
-            <dt><code>&lt;link href="../index.html"&gt;</code></dt> 
+          <dl>
+            <dt><code>&lt;link href="../index.html"&gt;</code></dt>
             <dd>Use this to
               <link href="../index.html" title="Example of a document via link">link</link>
               to another document. As per normal, this will open the new document
-              in the same browser window.</dd> 
-
-            <dt><code>&lt;link href="#section"&gt;</code></dt> 
+              in the same browser window.</dd>
+            <dt><code>&lt;link href="#section"&gt;</code></dt>
             <dd>Use this to
               <link href="#section" title="Example of a document via local anchor">link</link>
               to the named anchor in the current document.
-            </dd> 
-
-            <dt><code>&lt;link href="../index.html#History"&gt;</code></dt> 
+            </dd>
+            <dt><code>&lt;link href="../index.html#History"&gt;</code></dt>
             <dd>Use this to
               <link href="../index.html#History" title="Example of a document via link and anchor">link</link>
               to another document and go to the named anchor. This will open
               the new document in the same browser window.
-            </dd> 
-
-            <dt><code>&lt;jump href="../index.html"&gt;</code></dt> 
+            </dd>
+            <dt><code>&lt;jump href="../index.html"&gt;</code></dt>
             <dd>Use this to
               <jump href="../index.html" title="Example of a document via jump">jump</jump>
               to another document and optionally go to a named
@@ -115,69 +120,86 @@
               The jump behaves differently, in that it will replace any frames
               in the current window.
               This is the equivalent of
-              <code>&lt;a ... target="_top"&gt;</code>
-            </dd>
-
-            <dt><code>&lt;fork href="../index.html"&gt;</code></dt> 
+              <code>&lt;a ... target="_top"&gt;</code></dd>
+            <dt><code>&lt;fork href="../index.html"&gt;</code></dt>
             <dd>Use this to
               <fork href="../index.html" title="Example of a document via fork">fork</fork>
               your webbrowser to another document. This will open the document
               in a new, unnamed browser window.
               This is the equivalent of
-              <code>&lt;a ... target="_blank"&gt;</code>
-            </dd> 
-        </dl></li> 
-
+              <code>&lt;a ... target="_blank"&gt;</code></dd>
+          </dl></li>
         <li>Oh, by the way, a definition list <code>&lt;dl&gt;</code> was used inside
           the previous list item. We could put another 
-          <ul> 
-            <li>unordered list</li> 
-            <li>inside the list item</li> 
+          <ul>
+            <li>unordered list</li>
+            <li>inside the list item</li>
           </ul>
           <table>
             <caption>A sample nested table</caption>
-            <tr><td>Or even tables</td><td>inside lists</td></tr>
-          </table>
-        </li>
-      </ul> 
-      <p>So far for the in-line elements, let's look at some paragraph-level
-        elements.</p> 
-      <fixme author="SN">The <code>&lt;fixme&gt;</code> element is used for stuff
-        which still needs work. Mind the <code>author</code> attribute!</fixme> 
-      <note>Use the <code>&lt;note&gt;</code> element to draw attention to something, e.g. ...The <code>&lt;code&gt;</code> element is used when the author can't
-        express himself clearly using normal sentences ;-)</note>
-      <warning>Sleep deprivation can be the result of being involved in an open
-        source project. (a.k.a. the <code>&lt;warning&gt;</code> element).</warning>
-      <note label="Important">If you want your own labels for notes and warnings, specify them
-        using the <code>label</code> attribute.</note>
-      <p>Apart from unordered lists, we have ordered lists too, of course.</p> 
-      <ol> 
-        <li>Item 1</li> 
-        <li>Item 2</li> 
-        <li>This should be 3 if my math is still OK.</li> 
-      </ol> 
-
+            <tr>
+              <td>Or even tables</td>
+              <td>inside lists</td>
+            </tr>
+          </table></li>
+      </ul>
+      <p>
+        So far for the in-line elements, let's look at some paragraph-level
+        elements.
+      </p>
+      <fixme author="SN">
+        The <code>&lt;fixme&gt;</code> element is used for stuff which still
+        needs work. Mind the <code>author</code> attribute!
+      </fixme>
+      <note>
+        Use the <code>&lt;note&gt;</code> element to draw attention to
+        something, e.g. ...The <code>&lt;code&gt;</code> element is used when
+        the author can't express himself clearly using normal sentences ;-)
+      </note>
+      <warning>
+        Sleep deprivation can be the result of being involved in an open source
+        project. (a.k.a. the <code>&lt;warning&gt;</code> element).
+      </warning>
+      <note label="Important">
+        If you want your own labels for notes and warnings, specify them using
+        the <code>label</code> attribute.
+      </note>
+      <p>
+        Apart from unordered lists, we have ordered lists too, of course.
+      </p>
+      <ol>
+        <li>Item 1</li>
+        <li>Item 2</li>
+        <li>This should be 3 if my math is still OK.</li>
+      </ol>
       <anchor id="section"/>
-      <section> 
+      <section>
         <title>Using sections</title>
-        <p>You can use sections to put some structure in your document. For some
+        <p>
+          You can use sections to put some structure in your document. For some
           strange historical reason, the section title is an attribute of the
-          <code>&lt;section&gt;</code> element.</p> 
-      </section> 
+          <code>&lt;section&gt;</code> element.
+        </p>
+      </section>
       <section>
         <title>Sections, the sequel</title>
-        <p>Just some second section.</p> 
+        <p>
+          Just some second section.
+        </p>
         <section>
           <title>Section 2.1</title>
-          <p>Which contains a subsection (2.1).</p> 
-        </section> 
-      </section> 
-
+          <p>
+            Which contains a subsection (2.1).
+          </p>
+        </section>
+      </section>
       <anchor id="source"/>
       <section>
-        <title>Showing preformatted source code</title> 
-        <p>Enough about these sections. Let's have a look at more interesting
-          elements, <code>&lt;source&gt;</code> for instance:</p> 
+        <title>Showing preformatted source code</title>
+        <p>
+          Enough about these sections. Let's have a look at more interesting
+          elements, <code>&lt;source&gt;</code> for instance:
+        </p>
         <source>// This example is from the book _Java in a Nutshell_ by David Flanagan.
           // Written by David Flanagan.  Copyright (c) 1996 O'Reilly &amp; Associates.
           // You may study, use, modify, and distribute this example for any purpose.
@@ -193,48 +215,53 @@
           g.drawString("Hello World", 25, 50);
           }
           }</source>
-        <p>Please take care to still use a sensible line-length within your
-          source elements.</p>
+        <p>
+          Please take care to still use a sensible line-length within your
+          source elements.
+        </p>
       </section>
-
       <section id="table">
         <title>Using tables</title>
-        <p>And now for a table:</p>
-        <table> 
-          <caption>Table caption</caption> 
-          <tr> 
-            <th>heading cell</th> 
-            <th>heading cell</th> 
-          </tr> 
-          <tr> 
-            <td>data cell</td> 
-            <td>data cell</td> 
-          </tr> 
+        <p>
+          And now for a table:
+        </p>
+        <table>
+          <caption>Table caption</caption>
+          <tr>
+            <th>heading cell</th>
+            <th>heading cell</th>
+          </tr>
+          <tr>
+            <td>data cell</td>
+            <td>data cell</td>
+          </tr>
           <tr>
             <td>
               Tables can be nested
             </td>
             <td>
-              <ul><li>and can include most other elements, like lists</li></ul>
+              <ul>
+                <li>and can include most other elements, like lists</li>
+              </ul>
             </td>
           </tr>
-        </table> 
-        <p>Not much of attributes with <code>&lt;table&gt;</code>, if you ask me.</p>
+        </table>
+        <p>
+          Not much of attributes with <code>&lt;table&gt;</code>, if you ask me.
+        </p>
       </section>
-
       <anchor id="second-figure-anchor"/>
-      <section id="figure"> 
+      <section id="figure">
         <title>Using figures</title>
-
-        <p>And a <code>&lt;figure&gt;</code> to end all of this.
-          Note that this can also be implemented with an
-          <code>&lt;img&gt;</code> element.
+        <p>
+          And a <code>&lt;figure&gt;</code> to end all of this. Note that this
+          can also be implemented with an <code>&lt;img&gt;</code> element.
         </p>
-        <figure src="images/project-logo.png" alt="The fine Forrest logo" width="220" height="65"/>	
+        <figure src="images/project-logo.png" alt="The fine Forrest logo" width="220" height="65"/>
       </section>
     </section>
-  </body> 
-  <footer> 
+  </body>
+  <footer>
     <legal>Copyright 2002-2005 The Apache Software Foundation or its licensors,
       as applicable.</legal>
   </footer>

Modified: forrest/trunk/site-author/content/xdocs/dtdx/document-v13.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/dtdx/document-v13.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/dtdx/document-v13.xml (original)
+++ forrest/trunk/site-author/content/xdocs/dtdx/document-v13.xml Mon Apr  9 20:48:52 2007
@@ -16,90 +16,92 @@
   limitations under the License.
 -->
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
-<document> 
-  <header> 
-    <title>The Apache Forrest xdocs document-v1.3 DTD</title> 
+<document>
+  <header>
+    <title>The Apache Forrest xdocs document-v1.3 DTD</title>
     <notice>The content of this document doesn't make any sense at all.</notice>
-    <abstract>This is a demonstration document using all possible elements in
-      the current Apache Forrest xdocs <code>document-v13.dtd</code>
-    </abstract> 
-  </header> 
-  <body> 
-    <note>
+    <abstract>
       This is a demonstration document using all possible elements in the
       current Apache Forrest xdocs <code>document-v13.dtd</code>
-      (See the <link href="#changes">DTD changes</link> section at the bottom.)
+    </abstract>
+  </header>
+  <body>
+    <note>
+      This is a demonstration document using all possible elements in the
+      current Apache Forrest xdocs <code>document-v13.dtd</code> (See the
+      <link href="#changes">DTD changes</link> section at the bottom.)
     </note>
     <section id="sample">
       <title>Sample Content</title>
-      <p><strong>Hint:</strong> See the xml source to see how the various
-      elements are used and see the
-      <link href="site:dtd-docs">DTD reference documentation</link>.
+      <p>
+        <strong>Hint:</strong> See the xml source to see how the various
+        elements are used and see the <link href="site:dtd-docs">DTD reference
+        documentation</link>.
       </p>
       <section id="block-inline">
         <title>Block and inline elements</title>
-      <p>This is a simple paragraph. Most documents contain a fair amount of
-        paragraphs. Paragraphs are called <code>&lt;p&gt;</code>.</p> 
-      <p xml:space="preserve"
-        >With the <code>&lt;p xml:space="preserve"&gt;</code> attribute, you can declare
-        that whitespace should    be   preserved, without implying it is in any other
-        way special.</p>
-      <p>
-        This next paragraph has a class attribute of 'quote'.  CSS can
-        be used to present this <code>&lt;p class='quote'&gt;</code> in
-        a different style than the other paragraphs.  The handling of
-        this quoted paragraph is defined in the &lt;extra-css&gt;
-        element in the skinconf.xml.
-      </p>
-      <p class="quote">
-        Anyway, like I was sayin', shrimp is the fruit of the sea. You can
-        barbecue it, boil it, broil it, bake it, sautee it. Dey's uh,
-        shrimp-kabobs, shrimp creole, shrimp gumbo. Pan fried, deep fried,
-        stir-fried. There's pineapple shrimp, lemon shrimp, coconut shrimp,
-        pepper shrimp, shrimp soup, shrimp stew, shrimp salad, shrimp and
-        potatoes, shrimp burger, shrimp sandwich. That- that's about it.
-      </p>
-      <p>A number of in-line elements are available in the DTD, we will show them
-        inside an unordered list (<code>&lt;ul&gt;</code>):</p> 
-      <ul> 
-        <li>Here is a simple list item (<code>&lt;li&gt;</code>).</li> 
-        <li>Have you seen the use of the <code>&lt;code&gt;</code> element in the
-          previous item?</li> 
-        <li>Also, we have <code>&lt;sub&gt;</code> and <code>&lt;sup&gt;</code>
+        <p>
+          This is a simple paragraph. Most documents contain a fair amount of
+          paragraphs. Paragraphs are called <code>&lt;p&gt;</code>.
+        </p>
+        <p xml:space="preserve">
+          With the <code>&lt;p xml:space="preserve"&gt;</code> attribute, you can declare
+          that whitespace should    be   preserved, without implying it is in any other
+          way special.
+        </p>
+        <p>
+          This next paragraph has a class attribute of 'quote'. CSS can be used
+          to present this <code>&lt;p class='quote'&gt;</code> in a different
+          style than the other paragraphs. The handling of this quoted paragraph
+          is defined in the &lt;extra-css&gt; element in the skinconf.xml.
+        </p>
+        <p class="quote">
+          Anyway, like I was sayin', shrimp is the fruit of the sea. You can
+          barbecue it, boil it, broil it, bake it, sautee it. Dey's uh,
+          shrimp-kabobs, shrimp creole, shrimp gumbo. Pan fried, deep fried,
+          stir-fried. There's pineapple shrimp, lemon shrimp, coconut shrimp,
+          pepper shrimp, shrimp soup, shrimp stew, shrimp salad, shrimp and
+          potatoes, shrimp burger, shrimp sandwich. That- that's about it.
+        </p>
+        <p>
+          A number of in-line elements are available in the DTD, we will show
+          them inside an unordered list (<code>&lt;ul&gt;</code>):
+        </p>
+        <ul>
+          <li>Here is a simple list item (<code>&lt;li&gt;</code>).</li>
+          <li>Have you seen the use of the <code>&lt;code&gt;</code> element in the
+          previous item?</li>
+          <li>Also, we have <code>&lt;sub&gt;</code> and <code>&lt;sup&gt;</code>
           elements to show content <sup>above</sup> or <sub>below</sub> the text
-          baseline.</li> 
-        <li>There is a facility to <em>emphasize</em> certain words using the
-          <code>&lt;em&gt;</code> <strong><code>&lt;strong&gt;</code></strong>
-          elements.</li> 
-        <li>We can use
-          <icon height="22" width="26" src="images/icon.png" alt="feather"/>
-          <code>&lt;icon&gt;</code>s too.</li> 
-        <li>Another possibility is the <code>&lt;img&gt;</code> element:
+          baseline.</li>
+          <li>There is a facility to <em>emphasize</em> certain words using the
+          <code>&lt;em&gt;</code><strong><code>&lt;strong&gt;</code></strong>
+          elements.</li>
+          <li>We can use
+          <icon height="22" width="26" src="images/icon.png" alt="feather"/><code>&lt;icon&gt;</code>s too.</li>
+          <li>Another possibility is the <code>&lt;img&gt;</code> element:
           <img src="images/icon.png" alt="another feather" height="22" width="26"/>,
-          which offers the ability to refer to an image map.</li> 
-        <li>We have elements for hyperlinking: 
-          <dl> 
-            <dt><code>&lt;link href="../index.html"&gt;</code></dt> 
-            <dd>Use this to
+          which offers the ability to refer to an image map.</li>
+          <li>We have elements for hyperlinking: 
+          <dl>
+              <dt><code>&lt;link href="../index.html"&gt;</code></dt>
+              <dd>Use this to
               <link href="../index.html" title="Example of a document via link">link</link>
               to another document. As per normal, this will open the new document
-              in the same browser window.</dd> 
-
-            <dt><code>&lt;link href="#section"&gt;</code></dt> 
-            <dd>Use this to
+              in the same browser window.</dd>
+              <dt><code>&lt;link href="#section"&gt;</code></dt>
+              <dd>Use this to
               <link href="#section" title="Example of a document via local anchor">link</link>
               to the named anchor in the current document.
-            </dd> 
-
-            <dt><code>&lt;link href="../index.html#History"&gt;</code></dt> 
-            <dd>Use this to
+            </dd>
+              <dt><code>&lt;link href="../index.html#History"&gt;</code></dt>
+              <dd>Use this to
               <link href="../index.html#History" title="Example of a document via link and anchor">link</link>
               to another document and go to the named anchor. This will open
               the new document in the same browser window.
-            </dd> 
-
-            <dt><code>&lt;jump href="../index.html"&gt;</code></dt> 
-            <dd>Use this to
+            </dd>
+              <dt><code>&lt;jump href="../index.html"&gt;</code></dt>
+              <dd>Use this to
               <jump href="../index.html" title="Example of a document via jump">jump</jump>
               to another document and optionally go to a named
               <jump href="../index.html#overview" title="Example of a document via jump to anchor">anchor</jump>
@@ -108,143 +110,151 @@
               The jump behaves differently, in that it will replace any frames
               in the current window.
               This is the equivalent of
-              <code>&lt;a ... target="_top"&gt;</code>
-            </dd>
-
-            <dt><code>&lt;fork href="../index.html"&gt;</code></dt> 
-            <dd>Use this to
+              <code>&lt;a ... target="_top"&gt;</code></dd>
+              <dt><code>&lt;fork href="../index.html"&gt;</code></dt>
+              <dd>Use this to
               <fork href="../index.html" title="Example of a document via fork">fork</fork>
               your webbrowser to another document. This will open the document
               in a new, unnamed browser window.
               This is the equivalent of
-              <code>&lt;a ... target="_blank"&gt;</code>
-            </dd> 
-        </dl></li> 
-
-        <li>Oh, by the way, a definition list <code>&lt;dl&gt;</code> was used inside
+              <code>&lt;a ... target="_blank"&gt;</code></dd>
+            </dl></li>
+          <li>Oh, by the way, a definition list <code>&lt;dl&gt;</code> was used inside
           the previous list item. We could put another 
-          <ul> 
-            <li>unordered list</li> 
-            <li>inside the list item</li> 
-          </ul>
-          <table>
-            <caption>A sample nested table</caption>
-            <tr><td>Or even tables.. </td><td>
-                <table><tr><td>inside tables..</td></tr></table>
-            </td></tr>
-            <tr><td>or inside lists, but I believe this liberty gets quickly quite
-                hairy as you see.</td></tr>
-          </table>
-        </li>
-      </ul> 
-      <p>So far for the in-line elements, let's look at some paragraph-level
-        elements.</p> 
-      <fixme author="SN">The <code>&lt;fixme&gt;</code> element is used for stuff
-        which still needs work. Mind the <code>author</code> attribute!</fixme> 
-      <note>Use the <code>&lt;note&gt;</code> element to draw attention to something, e.g. ...The <code>&lt;code&gt;</code> element is used when the author can't
-        express himself clearly using normal sentences ;-)</note>
-      <warning>Sleep deprivation can be the result of being involved in an open
-        source project. (a.k.a. the <code>&lt;warning&gt;</code> element).
-      </warning>
-      <note label="Important">If you want your own labels for notes and
-        warnings, specify them using the <code>label</code> attribute.
-      </note>
-      <p>Apart from unordered lists, we have ordered lists too, of course.</p> 
-      <ol> 
-        <li>Item 1</li> 
-        <li>Item 2</li> 
-        <li>This should be 3 if my math is still OK.</li> 
-      </ol>
+          <ul>
+              <li>unordered list</li>
+              <li>inside the list item</li>
+            </ul>
+            <table>
+              <caption>A sample nested table</caption>
+              <tr>
+                <td>Or even tables.. </td>
+                <td>
+                  <table>
+                    <tr>
+                      <td>inside tables..</td>
+                    </tr>
+                  </table>
+                </td>
+              </tr>
+              <tr>
+                <td>or inside lists, but I believe this liberty gets quickly quite
+                hairy as you see.</td>
+              </tr>
+            </table></li>
+        </ul>
+        <p>
+          So far for the in-line elements, let's look at some paragraph-level
+          elements.
+        </p>
+        <fixme author="SN">
+          The <code>&lt;fixme&gt;</code> element is used for stuff which still
+          needs work. Mind the <code>author</code> attribute!
+        </fixme>
+        <note>
+          Use the <code>&lt;note&gt;</code> element to draw attention to
+          something, e.g. ...The <code>&lt;code&gt;</code> element is used when
+          the author can't express himself clearly using normal sentences ;-)
+        </note>
+        <warning>
+          Sleep deprivation can be the result of being involved in an open
+          source project. (a.k.a. the <code>&lt;warning&gt;</code> element).
+        </warning>
+        <note label="Important">
+          If you want your own labels for notes and warnings, specify them using
+          the <code>label</code> attribute.
+        </note>
+        <p>
+          Apart from unordered lists, we have ordered lists too, of course.
+        </p>
+        <ol>
+          <li>Item 1</li>
+          <li>Item 2</li>
+          <li>This should be 3 if my math is still OK.</li>
+        </ol>
       </section>
-
       <section id="presentations">
         <title>Various presentation formats</title>
-
-        <p>This sample document, written in document-v13 XML can be presented
-        via Forrest in a number of different formats. The links in the
-        following list show this document in each of the currently available
-        formats.</p>
-
-        <p>Each of the formats can be made available as a link near the top of
-        the page. Actual placement of those links depends on the skin
-        currently in use. Those links are enabled in the skinconf.xml via the
-        &#60;disable-XXX-link&#62; elements in the skinconf.xml</p>
-
+        <p>
+          This sample document, written in document-v13 XML can be presented via
+          Forrest in a number of different formats. The links in the following
+          list show this document in each of the currently available formats.
+        </p>
+        <p>
+          Each of the formats can be made available as a link near the top of
+          the page. Actual placement of those links depends on the skin
+          currently in use. Those links are enabled in the skinconf.xml via the
+          &#60;disable-XXX-link&#62; elements in the skinconf.xml
+        </p>
         <table>
           <tr>
             <th>Presentation Format</th>
-
             <th>Description</th>
-
             <th>skinconf.xml Element</th>
           </tr>
-
           <tr>
-            <td><link href="document-v13.html">HTML</link></td>
-
+            <td><link href="document-v13.html">HTML</link>
+            </td>
             <td>This document in HTML format. </td>
-
             <td>Always generated by default. Cannot be turned off.</td>
           </tr>
-
           <tr>
-            <td><link href="document-v13.xml">XML</link></td>
-
+            <td><link href="document-v13.xml">XML</link>
+            </td>
             <td>This document in its raw XML format.</td>
-
             <td>&#60;disable-xml-link&#62;. By default, set to true, meaning
             that this link will not be shown.</td>
           </tr>
-
           <tr>
-            <td><link href="document-v13.pdf">PDF</link></td>
-
+            <td><link href="document-v13.pdf">PDF</link>
+            </td>
             <td>This document as Adobe PDF</td>
-
             <td>&#60;disable-pdf-link&#62;. By default, set to false, meaning
             that this link will be shown.</td>
           </tr>
-
           <tr>
             <td>Text</td>
-
             <td>This document as straight text.</td>
-
             <td>&#60;disable-txt-link&#62;. By default, set to true, meaning
             that this link will not be shown. NOT YET IMPLEMENTED.</td>
           </tr>
-
           <tr>
-            <td><link href="document-v13.pod">POD</link></td>
-
+            <td><link href="document-v13.pod">POD</link>
+            </td>
             <td>This document as Perl POD (Plain Old Documentation). Text with
             minimal formatting directives. If on a *nix system with perl
             installed, see &#34;man perlpod&#34;.</td>
-
             <td>&#60;disable-pod-link&#62;. By default, set to true, meaning
             that this link will not be shown.</td>
           </tr>
         </table>
       </section>
-      <section id="section"> 
+      <section id="section">
         <title>Using sections</title>
-        <p>You can use sections to put some structure in your document. For some
+        <p>
+          You can use sections to put some structure in your document. For some
           strange historical reason, the section title is an attribute of the
-          <code>&lt;section&gt;</code> element.</p> 
-      </section> 
+          <code>&lt;section&gt;</code> element.
+        </p>
+      </section>
       <section id="sub-section">
         <title>Sections, the sequel</title>
-        <p>Just some second section.</p> 
+        <p>
+          Just some second section.
+        </p>
         <section id="sub-sub-section">
           <title>Section 2.1</title>
-          <p>Which contains a subsection (2.1).</p> 
-        </section> 
-      </section> 
-
+          <p>
+            Which contains a subsection (2.1).
+          </p>
+        </section>
+      </section>
       <section id="source">
-        <title>Showing preformatted source code</title> 
-        <p>Enough about these sections. Let's have a look at more interesting
-          elements, <code>&lt;source&gt;</code> for instance:</p> 
+        <title>Showing preformatted source code</title>
+        <p>
+          Enough about these sections. Let's have a look at more interesting
+          elements, <code>&lt;source&gt;</code> for instance:
+        </p>
         <source>
 // This example is from the book _Java in a Nutshell_ by David Flanagan.
 // Written by David Flanagan.  Copyright (c) 1996 O'Reilly &amp; Associates.
@@ -261,23 +271,28 @@
         g.drawString("Hello World", 25, 50);
     }
 }</source>
-        <p>CDATA sections are used within 
-          <code>&lt;source&gt;</code> elements so that you can write pointy
-           brackets without needing to escape them with messy
-          <code>&amp;lt;</code> entities ...
-        </p> 
-        <source><![CDATA[
+        <p>
+          CDATA sections are used within <code>&lt;source&gt;</code> elements so
+          that you can write pointy brackets without needing to escape them with
+          messy <code>&amp;lt;</code> entities ...
+        </p>
+        <source>
+<![CDATA[
 <pointy>
   easy
 </pointy>
-]]></source>
-        <p>Please take care to still use a sensible line-length within your
-          source elements.</p>
+]]>
+        </source>
+        <p>
+          Please take care to still use a sensible line-length within your
+          source elements.
+        </p>
       </section>
-
       <section id="table">
         <title>Using tables</title>
-        <p>And now for a table:</p>
+        <p>
+          And now for a table:
+        </p>
         <table>
           <caption>Table caption</caption>
           <tr>
@@ -298,7 +313,7 @@
                 <tr>
                   <th>column 1</th>
                   <th>column 2</th>
-                </tr> 
+                </tr>
                 <tr>
                   <td>cell A</td>
                   <td>cell B</td>
@@ -306,27 +321,29 @@
               </table>
             </td>
             <td>
-              <ul><li>and can include most other elements</li><li>such as lists</li></ul>
+              <ul>
+                <li>and can include most other elements</li>
+                <li>such as lists</li>
+              </ul>
             </td>
           </tr>
-        </table> 
+        </table>
       </section>
-
       <anchor id="second-figure-anchor"/>
-      <section id="figure"> 
+      <section id="figure">
         <title>Using figures</title>
-        <p>And a <code>&lt;figure&gt;</code> to end all of this.
-          Note that this can also be implemented with an
-          <code>&lt;img&gt;</code> element.
+        <p>
+          And a <code>&lt;figure&gt;</code> to end all of this. Note that this
+          can also be implemented with an <code>&lt;img&gt;</code> element.
         </p>
-        <figure src="images/project-logo.png" alt="The fine Forrest logo" width="220" height="65"/>	
+        <figure src="images/project-logo.png" alt="The fine Forrest logo" width="220" height="65"/>
       </section>
     </section>
-
     <section id="changes">
       <title>DTD changes</title>
-      <p>See the generated
-        <link href="site:dtd-docs">DTD reference documentation</link>.
+      <p>
+        See the generated <link href="site:dtd-docs">DTD reference
+        documentation</link>.
       </p>
       <section id="changes-13">
         <title>Changes since document-v12</title>
@@ -364,8 +381,8 @@
         </ul>
       </section>
     </section>
-  </body> 
-  <footer> 
-    <legal>This is a legal notice, so it is <strong>important</strong>.</legal> 
+  </body>
+  <footer>
+    <legal>This is a legal notice, so it is <strong>important</strong>.</legal>
   </footer>
 </document>

Modified: forrest/trunk/site-author/content/xdocs/dtdx/document-v20.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/dtdx/document-v20.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/dtdx/document-v20.xml (original)
+++ forrest/trunk/site-author/content/xdocs/dtdx/document-v20.xml Mon Apr  9 20:48:52 2007
@@ -16,220 +16,244 @@
   limitations under the License.
 -->
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
-<document> 
-  <header> 
-    <title>The Apache Forrest xdocs document-v2.0 DTD</title> 
+<document>
+  <header>
+    <title>The Apache Forrest xdocs document-v2.0 DTD</title>
     <notice>The content of this document doesn't make any sense at all.</notice>
-    <abstract>This is a demonstration document using all possible elements in
-      the current Apache Forrest xdocs <code>document-v20.dtd</code>
-    </abstract> 
-  </header> 
-  <body> 
-    <note>
+    <abstract>
       This is a demonstration document using all possible elements in the
       current Apache Forrest xdocs <code>document-v20.dtd</code>
-      (See the <a href="#changes">DTD changes</a> section at the bottom.)
+    </abstract>
+  </header>
+  <body>
+    <note>
+      This is a demonstration document using all possible elements in the
+      current Apache Forrest xdocs <code>document-v20.dtd</code> (See the
+      <a href="#changes">DTD changes</a> section at the bottom.)
     </note>
     <section id="sample">
       <title>Sample Content</title>
-      <p><strong>Hint:</strong> See the xml source to see how the various
-      elements are used and see the
-      <a href="site:dtd-docs">DTD reference documentation</a>.
+      <p>
+        <strong>Hint:</strong> See the xml source to see how the various
+        elements are used and see the <a href="site:dtd-docs">DTD reference
+        documentation</a>.
       </p>
       <section id="block-inline">
         <title>Block and inline elements</title>
-      <p>This is a simple paragraph. Most documents contain a fair amount of
-        paragraphs. Paragraphs are called <code>&lt;p&gt;</code>.</p> 
-      <p xml:space="preserve"
-        >With the <code>&lt;p xml:space="preserve"&gt;</code> attribute, you can declare
-        that whitespace should    be   preserved, without implying it is in any other
-        way special.</p>
-      <p>
-        This next paragraph has a class attribute of 'quote'.  CSS can
-        be used to present this <code>&lt;p class='quote'&gt;</code> in
-        a different style than the other paragraphs.  The handling of
-        this quoted paragraph is defined in the &lt;extra-css&gt;
-        element in the skinconf.xml.
-      </p>
-      <p class="quote">
-        Anyway, like I was sayin', shrimp is the fruit of the sea. You can
-        barbecue it, boil it, broil it, bake it, sautee it. Dey's uh,
-        shrimp-kabobs, shrimp creole, shrimp gumbo. Pan fried, deep fried,
-        stir-fried. There's pineapple shrimp, lemon shrimp, coconut shrimp,
-        pepper shrimp, shrimp soup, shrimp stew, shrimp salad, shrimp and
-        potatoes, shrimp burger, shrimp sandwich. That- that's about it.
-      </p>
-      <p>A number of in-line elements are available in the DTD, we will show them
-        inside an unordered list (<code>&lt;ul&gt;</code>):</p> 
-      <ul> 
-        <li>Here is a simple list item (<code>&lt;li&gt;</code>).</li> 
-        <li>Have you seen the use of the <code>&lt;code&gt;</code> element in the
-          previous item?</li> 
-        <li>Also, we have <code>&lt;sub&gt;</code> and <code>&lt;sup&gt;</code>
+        <p>
+          This is a simple paragraph. Most documents contain a fair amount of
+          paragraphs. Paragraphs are called <code>&lt;p&gt;</code>.
+        </p>
+        <p xml:space="preserve">
+          With the <code>&lt;p xml:space="preserve"&gt;</code> attribute, you can declare
+          that whitespace should    be   preserved, without implying it is in any other
+          way special.
+        </p>
+        <p>
+          This next paragraph has a class attribute of 'quote'. CSS can be used
+          to present this <code>&lt;p class='quote'&gt;</code> in a different
+          style than the other paragraphs. The handling of this quoted paragraph
+          is defined in the &lt;extra-css&gt; element in the skinconf.xml.
+        </p>
+        <p class="quote">
+          Anyway, like I was sayin', shrimp is the fruit of the sea. You can
+          barbecue it, boil it, broil it, bake it, sautee it. Dey's uh,
+          shrimp-kabobs, shrimp creole, shrimp gumbo. Pan fried, deep fried,
+          stir-fried. There's pineapple shrimp, lemon shrimp, coconut shrimp,
+          pepper shrimp, shrimp soup, shrimp stew, shrimp salad, shrimp and
+          potatoes, shrimp burger, shrimp sandwich. That- that's about it.
+        </p>
+        <p>
+          A number of in-line elements are available in the DTD, we will show
+          them inside an unordered list (<code>&lt;ul&gt;</code>):
+        </p>
+        <ul>
+          <li>Here is a simple list item (<code>&lt;li&gt;</code>).</li>
+          <li>Have you seen the use of the <code>&lt;code&gt;</code> element in the
+          previous item?</li>
+          <li>Also, we have <code>&lt;sub&gt;</code> and <code>&lt;sup&gt;</code>
           elements to show content <sup>above</sup> or <sub>below</sub> the text
-          baseline.</li> 
-        <li>There is a facility to <em>emphasize</em> certain words using the
-          <code>&lt;em&gt;</code> <strong><code>&lt;strong&gt;</code></strong>
-          elements.</li> 
-        <li>We can use
-          <icon height="22" width="26" src="images/icon.png" alt="feather"/>
-          <code>&lt;icon&gt;</code>s too.</li> 
-        <li>Another possibility is the <code>&lt;img&gt;</code> element:
+          baseline.</li>
+          <li>There is a facility to <em>emphasize</em> certain words using the
+          <code>&lt;em&gt;</code><strong><code>&lt;strong&gt;</code></strong>
+          elements.</li>
+          <li>We can use
+          <icon height="22" width="26" src="images/icon.png" alt="feather"/><code>&lt;icon&gt;</code>s too.</li>
+          <li>Another possibility is the <code>&lt;img&gt;</code> element:
           <img src="images/icon.png" alt="another feather" height="22" width="26"/>,
-          which offers the ability to refer to an image map.</li> 
-        <li>We have elements for hyperlinking: 
-          <dl> 
-            <dt><code>&lt;a href="../index.html"&gt;</code></dt> 
-            <dd>Use this to
+          which offers the ability to refer to an image map.</li>
+          <li>We have elements for hyperlinking: 
+          <dl>
+              <dt><code>&lt;a href="../index.html"&gt;</code></dt>
+              <dd>Use this to
               <a href="../index.html" title="Example of a document via link">link</a>
               to another document. As per normal, this will open the new document
-              in the same browser window.</dd> 
-
-            <dt><code>&lt;a href="#section"&gt;</code></dt> 
-            <dd>Use this to
+              in the same browser window.</dd>
+              <dt><code>&lt;a href="#section"&gt;</code></dt>
+              <dd>Use this to
               <a href="#section" title="Example of a document via local anchor">link</a>
               to the named anchor in the current document.
-            </dd> 
-
-            <dt><code>&lt;a href="../index.html#status"&gt;</code></dt> 
-            <dd>Use this to
+            </dd>
+              <dt><code>&lt;a href="../index.html#status"&gt;</code></dt>
+              <dd>Use this to
               <a href="../index.html#status" title="Example of a document via link and anchor">link</a>
               to another document and go to the named anchor. This will open
               the new document in the same browser window.
-            </dd> 
-            <dt>Targetted window control with jump and fork.</dt> 
-            <dd>See demonstration
+            </dd>
+              <dt>Targetted window control with jump and fork.</dt>
+              <dd>See demonstration
              <a href="#link-class">using class attribute on links</a>.
-            </dd> 
-        </dl></li> 
-
-        <li>Oh, by the way, a definition list <code>&lt;dl&gt;</code> was used inside
+            </dd>
+            </dl></li>
+          <li>Oh, by the way, a definition list <code>&lt;dl&gt;</code> was used inside
           the previous list item. We could put another 
-          <ul> 
-            <li>unordered list</li> 
-            <li>inside the list item</li> 
-          </ul>
-          <table>
-            <caption>A sample nested table</caption>
-            <tr><td>Or even tables.. </td><td>
-                <table><tr><td>inside tables..</td></tr></table>
-            </td></tr>
-            <tr><td>or inside lists, but I believe this liberty gets quickly quite
-                hairy as you see.</td></tr>
-          </table>
-        </li>
-      </ul> 
-      <p>So far for the in-line elements, let's look at some paragraph-level
-        elements.</p> 
-      <fixme author="SN">The <code>&lt;fixme&gt;</code> element is used for stuff
-        which still needs work. Mind the <code>author</code> attribute!</fixme> 
-      <note>Use the <code>&lt;note&gt;</code> element to draw attention to something, e.g. ...The <code>&lt;code&gt;</code> element is used when the author can't
-        express himself clearly using normal sentences ;-)</note>
-      <warning>Sleep deprivation can be the result of being involved in an open
-        source project. (a.k.a. the <code>&lt;warning&gt;</code> element).
-      </warning>
-      <note label="Important">If you want your own labels for notes and
-        warnings, specify them using the <code>label</code> attribute.
-      </note>
-      <p>Apart from unordered lists, we have ordered lists too, of course.</p> 
-      <ol> 
-        <li>Item 1</li> 
-        <li>Item 2</li> 
-        <li>This should be 3 if my math is still OK.</li> 
-      </ol>
+          <ul>
+              <li>unordered list</li>
+              <li>inside the list item</li>
+            </ul>
+            <table>
+              <caption>A sample nested table</caption>
+              <tr>
+                <td>Or even tables.. </td>
+                <td>
+                  <table>
+                    <tr>
+                      <td>inside tables..</td>
+                    </tr>
+                  </table>
+                </td>
+              </tr>
+              <tr>
+                <td>or inside lists, but I believe this liberty gets quickly quite
+                hairy as you see.</td>
+              </tr>
+            </table></li>
+        </ul>
+        <p>
+          So far for the in-line elements, let's look at some paragraph-level
+          elements.
+        </p>
+        <fixme author="SN">
+          The <code>&lt;fixme&gt;</code> element is used for stuff which still
+          needs work. Mind the <code>author</code> attribute!
+        </fixme>
+        <note>
+          Use the <code>&lt;note&gt;</code> element to draw attention to
+          something, e.g. ...The <code>&lt;code&gt;</code> element is used when
+          the author can't express himself clearly using normal sentences ;-)
+        </note>
+        <warning>
+          Sleep deprivation can be the result of being involved in an open
+          source project. (a.k.a. the <code>&lt;warning&gt;</code> element).
+        </warning>
+        <note label="Important">
+          If you want your own labels for notes and warnings, specify them using
+          the <code>label</code> attribute.
+        </note>
+        <p>
+          Apart from unordered lists, we have ordered lists too, of course.
+        </p>
+        <ol>
+          <li>Item 1</li>
+          <li>Item 2</li>
+          <li>This should be 3 if my math is still OK.</li>
+        </ol>
       </section>
-
       <section id="presentations">
         <title>Various presentation formats</title>
-
-        <p>This sample document, written in document-v20 XML can be presented
-        via Forrest in a number of different formats. The links in the
-        following list show this document in each of the currently available
-        formats.</p>
-
-        <p>Each of the formats can be made available as a link near the top of
-        the page. Actual placement of those links depends on the skin
-        currently in use. Those links are enabled in the skinconf.xml via the
-        &#60;disable-XXX-link&#62; elements in the skinconf.xml</p>
-
+        <p>
+          This sample document, written in document-v20 XML can be presented via
+          Forrest in a number of different formats. The links in the following
+          list show this document in each of the currently available formats.
+        </p>
+        <p>
+          Each of the formats can be made available as a link near the top of
+          the page. Actual placement of those links depends on the skin
+          currently in use. Those links are enabled in the skinconf.xml via the
+          &#60;disable-XXX-link&#62; elements in the skinconf.xml
+        </p>
         <table>
           <tr>
             <th>Presentation Format</th>
-
             <th>Description</th>
-
             <th>skinconf.xml Element</th>
           </tr>
-
           <tr>
-            <td><a href="document-v20.html">HTML</a></td>
-
+            <td><a href="document-v20.html">HTML</a>
+            </td>
             <td>This document in HTML format. </td>
-
             <td>Always generated by default. Cannot be turned off.</td>
           </tr>
-
           <tr>
-            <td><a href="document-v20.xml">XML</a></td>
-
+            <td><a href="document-v20.xml">XML</a>
+            </td>
             <td>This document in its raw XML format.</td>
-
             <td>&#60;disable-xml-link&#62;. By default, set to true, meaning
             that this link will not be shown.</td>
           </tr>
-
           <tr>
-            <td><a href="document-v20.pdf">PDF</a></td>
-
+            <td><a href="document-v20.pdf">PDF</a>
+            </td>
             <td>This document as Adobe PDF</td>
-
             <td>&#60;disable-pdf-link&#62;. By default, set to false, meaning
             that this link will be shown.</td>
           </tr>
-
           <tr>
-            <td><a href="document-v20.txt">Text</a></td>
-
-            <td><p>This document as straight text.</p>
-            <p>For additional information see the Forrest text-output
-            plugin.</p></td>
-
+            <td><a href="document-v20.txt">Text</a>
+            </td>
+            <td>
+              <p>
+                This document as straight text.
+              </p>
+              <p>
+                For additional information see the Forrest text-output plugin.
+              </p>
+            </td>
             <td>&#60;disable-txt-link&#62;. By default, set to true, meaning
             that this link will not be shown.</td>
           </tr>
-
           <tr>
-            <td><a href="document-v20.pod">POD</a></td>
-
-            <td><p>This document as Perl POD (Plain Old Documentation). Text
-            with minimal formatting directives. If on a *nix system with perl
-            installed, see &#34;man perlpod&#34;.</p>
-            <p>For additional information see the Forrest pod-output
-            plugin.</p></td>
-
+            <td><a href="document-v20.pod">POD</a>
+            </td>
+            <td>
+              <p>
+                This document as Perl POD (Plain Old Documentation). Text with
+                minimal formatting directives. If on a *nix system with perl
+                installed, see &#34;man perlpod&#34;.
+              </p>
+              <p>
+                For additional information see the Forrest pod-output plugin.
+              </p>
+            </td>
             <td>&#60;disable-pod-link&#62;. By default, set to true, meaning
             that this link will not be shown.</td>
           </tr>
         </table>
       </section>
-      <section id="section"> 
+      <section id="section">
         <title>Using sections</title>
-        <p>You can use sections to put some structure in your document.
+        <p>
+          You can use sections to put some structure in your document.
         </p>
-      </section> 
+      </section>
       <section id="sub-section">
         <title>Sections, the sequel</title>
-        <p>Just some second section.</p> 
+        <p>
+          Just some second section.
+        </p>
         <section id="sub-sub-section">
           <title>Section 2.1</title>
-          <p>Which contains a subsection (2.1).</p> 
-        </section> 
-      </section> 
-
+          <p>
+            Which contains a subsection (2.1).
+          </p>
+        </section>
+      </section>
       <section id="source">
-        <title>Showing preformatted source code</title> 
-        <p>Enough about these sections. Let's have a look at more interesting
-          elements, <code>&lt;source&gt;</code> for instance:</p> 
+        <title>Showing preformatted source code</title>
+        <p>
+          Enough about these sections. Let's have a look at more interesting
+          elements, <code>&lt;source&gt;</code> for instance:
+        </p>
         <source>
 // This example is from the book _Java in a Nutshell_ by David Flanagan.
 // Written by David Flanagan.  Copyright (c) 1996 O'Reilly &amp; Associates.
@@ -246,23 +270,28 @@
         g.drawString("Hello World", 25, 50);
     }
 }</source>
-        <p>CDATA sections are used within 
-          <code>&lt;source&gt;</code> elements so that you can write pointy
-           brackets without needing to escape them with messy
-          <code>&amp;lt;</code> entities ...
-        </p> 
-        <source><![CDATA[
+        <p>
+          CDATA sections are used within <code>&lt;source&gt;</code> elements so
+          that you can write pointy brackets without needing to escape them with
+          messy <code>&amp;lt;</code> entities ...
+        </p>
+        <source>
+<![CDATA[
 <pointy>
   easy
 </pointy>
-]]></source>
-        <p>Please take care to still use a sensible line-length within your
-          source elements.</p>
+]]>
+        </source>
+        <p>
+          Please take care to still use a sensible line-length within your
+          source elements.
+        </p>
       </section>
-
       <section id="table">
         <title>Using tables</title>
-        <p>And now for a table:</p>
+        <p>
+          And now for a table:
+        </p>
         <table>
           <caption>Table caption</caption>
           <tr>
@@ -283,7 +312,7 @@
                 <tr>
                   <th>column 1</th>
                   <th>column 2</th>
-                </tr> 
+                </tr>
                 <tr>
                   <td>cell A</td>
                   <td>cell B</td>
@@ -291,65 +320,82 @@
               </table>
             </td>
             <td>
-              <ul><li>and can include most other elements</li><li>such as lists</li></ul>
+              <ul>
+                <li>and can include most other elements</li>
+                <li>such as lists</li>
+              </ul>
             </td>
           </tr>
-        </table> 
+        </table>
       </section>
-
       <anchor id="second-figure-anchor"/>
-      <section id="figure"> 
+      <section id="figure">
         <title>Using figures</title>
-        <p>And a <code>&lt;figure&gt;</code> to end all of this.
-          Note that this can also be implemented with an
-          <code>&lt;img&gt;</code> element.
+        <p>
+          And a <code>&lt;figure&gt;</code> to end all of this. Note that this
+          can also be implemented with an <code>&lt;img&gt;</code> element.
         </p>
-        <figure src="images/project-logo.png" alt="The fine Forrest logo" width="220" height="65"/>	
+        <figure src="images/project-logo.png" alt="The fine Forrest logo" width="220" height="65"/>
       </section>
       <section id="link-class">
         <title>Using class attribute on links</title>
-
-        <p>The document-v13 had elements &lt;fork&gt; and &lt;jump&gt;. In
-        document-v20, those elements no longer exist but the functionality can
-        be duplicated by using the @class attribute.
-        Even though the opening of separate windows should be under the
-        control of the user, these techniques can still be employed.</p>
-
+        <p>
+          The document-v13 had elements &lt;fork&gt; and &lt;jump&gt;. In
+          document-v20, those elements no longer exist but the functionality can
+          be duplicated by using the @class attribute. Even though the opening
+          of separate windows should be under the control of the user, these
+          techniques can still be employed.
+        </p>
         <table>
           <tr>
-            <th><p>Document V1.3</p></th>
-
-            <th><p>Document V2.0</p></th>
+            <th>
+              <p>
+                Document V1.3
+              </p>
+            </th>
+            <th>
+              <p>
+                Document V2.0
+              </p>
+            </th>
           </tr>
-
           <tr>
-            <td><p>&lt;fork href="../index.html"&gt;</p></td>
-
+            <td>
+              <p>
+                &lt;fork href="../index.html"&gt;
+              </p>
+            </td>
             <td><a class="fork" href="../index.html">&lt;a class="fork"
-            href="../index.html"&gt;</a></td>
+            href="../index.html"&gt;</a>
+            </td>
           </tr>
-
           <tr>
-            <td><p>&lt;jump href="../index.html"&gt;</p></td>
-
-            <td><p><a class="jump" href="../index.html">&lt;a class="jump"
-            href="../index.html"&gt;</a></p></td>
+            <td>
+              <p>
+                &lt;jump href="../index.html"&gt;
+              </p>
+            </td>
+            <td>
+              <p>
+                <a class="jump" href="../index.html">&lt;a class="jump"
+                href="../index.html"&gt;</a>
+              </p>
+            </td>
           </tr>
         </table>
       </section>
     </section>
-
     <section id="changes">
       <title>DTD changes</title>
-      <p>See the generated
-        <a href="site:dtd-docs">DTD reference documentation</a>.
+      <p>
+        See the generated <a href="site:dtd-docs">DTD reference
+        documentation</a>.
       </p>
       <section id="changes-20">
         <title>Changes between document-v13 and document-v20</title>
         <ul>
           <li>Renamed <strong>&lt;link&gt;</strong>
-             to <strong>&lt;a&gt;</strong>
-          </li>
+             to <strong>&lt;a&gt;</strong></li>
           <li>Removed <strong>&lt;fork&gt;</strong>
              and <strong>&lt;jump&gt;</strong> in favour of the
              <strong>&lt;a&gt;</strong> element. See demonstration
@@ -393,8 +439,8 @@
         </ul>
       </section>
     </section>
-  </body> 
-  <footer> 
-    <legal>This is a legal notice, so it is <strong>important</strong>.</legal> 
+  </body>
+  <footer>
+    <legal>This is a legal notice, so it is <strong>important</strong>.</legal>
   </footer>
 </document>

Modified: forrest/trunk/site-author/content/xdocs/dtdx/dtd-docs.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/dtdx/dtd-docs.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/dtdx/dtd-docs.xml (original)
+++ forrest/trunk/site-author/content/xdocs/dtdx/dtd-docs.xml Mon Apr  9 20:48:52 2007
@@ -23,24 +23,32 @@
   <body>
     <section id="overview">
       <title>Overview</title>
-      <p>We use the
+      <p>
+        We use the
         <a href="http://www.apache.org/~andyc/neko/doc/dtd/index.html">NekoDTD</a>
-        tool packaged as a Cocoon Generator to automatically generate
-        some hyperlinked DTD reference documentation. Note that these references
-        do not reflect the modularity of our DTDs, they are primarily
-        "user-oriented help" documentation.</p>
-      <p>The actual DTDs are located in the Forrest distribution at
-        <code>main/webapp/resources/schema/</code></p>
+        tool packaged as a Cocoon Generator to automatically generate some
+        hyperlinked DTD reference documentation. Note that these references do
+        not reflect the modularity of our DTDs, they are primarily
+        "user-oriented help" documentation.
+      </p>
+      <p>
+        The actual DTDs are located in the Forrest distribution at
+        <code>main/webapp/resources/schema/</code>
+      </p>
     </section>
     <section id="dtdx">
       <title>The generated documentation</title>
-      <p>Generated documentation for Apache Forrest document-v20 ...</p>
+      <p>
+        Generated documentation for Apache Forrest document-v20 ...
+      </p>
       <ul>
         <li><a href="document-v20.dtdx.html">document-v20</a></li>
         <li><a href="howto-v20.dtdx.html">howto-v20</a></li>
         <li><a href="faq-v20.dtdx.html">faq-v20</a></li>
       </ul>
-      <p>Generated documentation for Apache Forrest document-v13 ...</p>
+      <p>
+        Generated documentation for Apache Forrest document-v13 ...
+      </p>
       <ul>
         <li><a href="document-v13.dtdx.html">document-v13</a></li>
         <li><a href="howto-v13.dtdx.html">howto-v13</a></li>

Modified: forrest/trunk/site-author/content/xdocs/events.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/events.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/events.xml (original)
+++ forrest/trunk/site-author/content/xdocs/events.xml Mon Apr  9 20:48:52 2007
@@ -23,27 +23,24 @@
   <body>
     <section id="upcoming">
       <title>Upcoming events</title>
-
       <section id="forrest-friday">
         <title>ForrestFriday monthly get-together</title>
         <p>
-          On the second Friday of each month we have a 24-hour get-together using
-          IRC and other collaborative tools, to work on Forrest development and
-          get to know each other. See how to
+          On the second Friday of each month we have a 24-hour get-together
+          using IRC and other collaborative tools, to work on Forrest
+          development and get to know each other. See how to
           <a href="site:forrest-friday">participate</a>.
         </p>
       </section>
     </section>
-
     <section id="past">
-            <title>Past events</title>
-
+      <title>Past events</title>
       <section id="apachecon-us-2006">
         <title>ApacheCon US 2006 (9-13 October 2006)</title>
         <p>
-         <a href="http://www.us.apachecon.com/">ApacheCon US 2006</a>
-         - Please make plans to join us for the conference in
-         Austin, Texas, USA on 9-13 October 2006.
+          <a href="http://www.us.apachecon.com/">ApacheCon US 2006</a> - Please
+          make plans to join us for the conference in Austin, Texas, USA on 9-13
+          October 2006.
         </p>
         <p>
           Apart from all of the general ApacheCon events, there are a number of
@@ -52,135 +49,132 @@
         <section id="WE21-austin-2006">
           <title>ApacheCon Session: WE21: Single Source Publishing with Apache Forrest</title>
           <p>
-            Wednesday 11 October - Official ApacheCon session
-            conducted by Ferdinand Soethe.
-            <a href="http://www.us.apachecon.com/html/sessions.html">Read more</a>.
+            Wednesday 11 October - Official ApacheCon session conducted by
+            Ferdinand Soethe.
+            <a href="http://www.us.apachecon.com/html/sessions.html">Read
+            more</a>.
           </p>
         </section>
       </section>
-
       <section id="apachecon-eu-2006">
         <title>ApacheCon EU 2006 (26-30 June)</title>
         <p>
-         <a href="http://apachecon.com/2006/EU/">ApacheCon EU 2006</a>
-         - Please make plans to join us for the conference in
-         Dublin, Ireland on 26-30 June 2006.
+          <a href="http://apachecon.com/2006/EU/">ApacheCon EU 2006</a> - Please
+          make plans to join us for the conference in Dublin, Ireland on 26-30
+          June 2006.
         </p>
         <p>
           Apart from all of the general ApacheCon events, there are a number of
           Forrest-specific events. In chronological order ...
         </p>
-
         <section id="FR19-dublin-2006">
           <title>ApacheCon Session: FR19: Single Source Publishing with Apache Forrest</title>
           <p>
-            Friday 30 June - Official ApacheCon session
-              conducted by Ferdinand Soethe. <a
+            Friday 30 June - Official ApacheCon session conducted by Ferdinand
+            Soethe.
+            <a
                   href="http://www.eu.apachecon.com/konferenzen/psecom,id,488,track,3,nodeid,,_language,uk.html#session-fr19">Read
-              more ...</a>
+            more ...</a>
           </p>
-          <note>This session was re-scheduled for Friday 30 June 14:30-15:30.</note>
+          <note>
+            This session was re-scheduled for Friday 30 June 14:30-15:30.
+          </note>
         </section>
       </section>
-
       <section id="apachecon-us-2005">
         <title>ApacheCon US 2005 (10-14 December)</title>
         <p>
-          <a href="http://apachecon.com/2005/US/">ApacheCon US 2005</a>
-          took place in San Diego, California, USA on 10-14 December 2005.
+          <a href="http://apachecon.com/2005/US/">ApacheCon US 2005</a> took
+          place in San Diego, California, USA on 10-14 December 2005.
         </p>
         <p>
           Apart from all of the general ApacheCon events, there is one
           Forrest-specific event.
         </p>
-
         <section id="fs-ac-us-2005">
           <title>ApacheCon Session: Single Source Publishing with Apache Forrest</title>
           <p>
             Tuesday 13 December at 09:00 to 10:00 - Official ApacheCon session
             conducted by Ferdinand Soethe. See the
             <a href="http://apachecon.com/2005/US/html/sessions.html">ApacheCon
-            Schedule</a> Session TU01.
-            The event is only open to ApacheCon attendees.
+            Schedule</a> Session TU01. The event is only open to ApacheCon
+            attendees.
           </p>
         </section>
       </section>
-
-    <section id="apachecon-eu-2005">
-      <title>ApacheCon Europe 2005 (18-22 July)</title>
-      <p>
-        <a href="http://apachecon.com/2005/EU/">ApacheCon Europe 2005</a>
-        in Stuttgart, Germany on 18-22 July 2005. For the first time there is
-        a session related to Apache Forrest.
-      </p>
-      <p>
-        Apart from all of the general ApacheCon events, there are a number of
-        Forrest-specific events. In chronological order ...
-      </p>
-
-      <section id="ht-stuttgart-2005">
-        <title>Apache committers hackathon</title>
-        <p>
-          Monday 18 July and Tuesday 19 July all day - Open to any Apache
-          committer. Among the many topics, some of us will informally chat
-          about Apache Forrest and maybe fix some bugs. We will probably
-          collaborate with the Apache Lenya committers too.
-        </p>
-      </section>
-
-      <section id="ws-stuttgart-2005">
-        <title>Apache Forrest workshop on Views</title>
-        <p>
-          Monday 18 July commencing at 18:30 - We will go out to dinner and then
-          meet for a developers workshop specifically about the new Views plugin
-          development. Topics will include Views, XHTML2 internal format, and
-          general project planning. Discussions will be technical and will assume
-          knowledge of Forrest. We will certainly answer questions to ensure that
-          people understand the background. However the main aim is an intensive
-          project design session.
-          The event is open to anybody, you don't need to be attending ApacheCon.
-          Venue and Directions: Gather at the foyer of the ApacheCon.
-        </p>
-      </section>
-
-      <section id="ua-stuttgart-2005">
-        <title>Usability professionals meeting</title>
-        <p>
-          Tuesday 19 July commencing at 18:30 - Johannes Schaefer will
-          present Apache Forrest to an informal meeting of usability
-          professionals. The event is open to other German-speaking people.
-          See
-          <a href="http://www.gui-design.de/ak/ak_050719.htm">further information</a>.
+      <section id="apachecon-eu-2005">
+        <title>ApacheCon Europe 2005 (18-22 July)</title>
+        <p>
+          <a href="http://apachecon.com/2005/EU/">ApacheCon Europe 2005</a> in
+          Stuttgart, Germany on 18-22 July 2005. For the first time there is a
+          session related to Apache Forrest.
         </p>
-      </section>
-
-      <section id="rf-stuttgart-2005">
-        <title>ApacheCon Session: Single Source Publishing with Apache Forrest</title>
-        <p>
-          Wednesday 20 July at 14:30 to 15:30 - Official ApacheCon session
-          conducted by Ross Gardler and Ferdinand Soethe. See the
-          <a href="http://apachecon.com/2005/EU/html/sessions.html">ApacheCon
-          Schedule</a> Session WE16.
-          The event is only open to ApacheCon attendees.
+        <p>
+          Apart from all of the general ApacheCon events, there are a number of
+          Forrest-specific events. In chronological order ...
         </p>
+        <section id="ht-stuttgart-2005">
+          <title>Apache committers hackathon</title>
+          <p>
+            Monday 18 July and Tuesday 19 July all day - Open to any Apache
+            committer. Among the many topics, some of us will informally chat
+            about Apache Forrest and maybe fix some bugs. We will probably
+            collaborate with the Apache Lenya committers too.
+          </p>
+        </section>
+        <section id="ws-stuttgart-2005">
+          <title>Apache Forrest workshop on Views</title>
+          <p>
+            Monday 18 July commencing at 18:30 - We will go out to dinner and
+            then meet for a developers workshop specifically about the new Views
+            plugin development. Topics will include Views, XHTML2 internal
+            format, and general project planning. Discussions will be technical
+            and will assume knowledge of Forrest. We will certainly answer
+            questions to ensure that people understand the background. However
+            the main aim is an intensive project design session. The event is
+            open to anybody, you don't need to be attending ApacheCon. Venue and
+            Directions: Gather at the foyer of the ApacheCon.
+          </p>
+        </section>
+        <section id="ua-stuttgart-2005">
+          <title>Usability professionals meeting</title>
+          <p>
+            Tuesday 19 July commencing at 18:30 - Johannes Schaefer will present
+            Apache Forrest to an informal meeting of usability professionals.
+            The event is open to other German-speaking people. See
+            <a href="http://www.gui-design.de/ak/ak_050719.htm">further
+            information</a>.
+          </p>
+        </section>
+        <section id="rf-stuttgart-2005">
+          <title>ApacheCon Session: Single Source Publishing with Apache Forrest</title>
+          <p>
+            Wednesday 20 July at 14:30 to 15:30 - Official ApacheCon session
+            conducted by Ross Gardler and Ferdinand Soethe. See the
+            <a href="http://apachecon.com/2005/EU/html/sessions.html">ApacheCon
+            Schedule</a> Session WE16. The event is only open to ApacheCon
+            attendees.
+          </p>
+        </section>
+        <section id="gt-stuttgart-2005">
+          <title>Apache Forrest get-together</title>
+          <p>
+            Wednesday 20 July commencing at 20:00 - Informal get together to
+            discuss any topic related to Apache Forrest. Follows on from the
+            session earlier in the day. Please come and meet other Forrest
+            developers and users. Describe your own use cases. The event is open
+            to anybody, you don't need to be attending ApacheCon. Venue and
+            Directions: Gather at the foyer of the ApacheCon at 20:00. The event
+            will be held at Stuttgart University of Applied Sciences Many thanks
+            to HfT. See
+            (<a href="http://www.hft-stuttgart.de/Hochschule/wirueberuns/Lageplan/">HfT
+            map</a>) which is just a few steps north-west of the ApacheCon-site:
+          </p>
+          <p>
+            <img src="apacheconsites.jpg" alt="map of sites"/>
+          </p>
+        </section>
       </section>
-
-      <section id="gt-stuttgart-2005">
-        <title>Apache Forrest get-together</title>
-        <p>
-          Wednesday 20 July commencing at 20:00 - Informal get together to
-          discuss any topic related to Apache Forrest. Follows on from
-          the session earlier in the day. Please come and meet other
-          Forrest developers and users. Describe your own use cases.
-          The event is open to anybody, you don't need to be attending ApacheCon.
-          Venue and Directions: Gather at the foyer of the ApacheCon at 20:00.
-          The event will be held at Stuttgart University of Applied Sciences
-          Many thanks to HfT.
-          See (<a href="http://www.hft-stuttgart.de/Hochschule/wirueberuns/Lageplan/">HfT map</a>)
-          which is just a few steps north-west of the ApacheCon-site:</p>
-          <p><img src="apacheconsites.jpg" alt="map of sites"/></p>
-      </section>
-    </section>
     </section>
   </body>
 </document>



Mime
View raw message