forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r357603 [8/11] - in /forrest/site: ./ docs_0_60/ docs_0_60/howto/ docs_0_60/howto/bugzilla-patch/ docs_0_70/ docs_0_70/howto/ docs_0_70/howto/cvs-ssh/ docs_0_80/ docs_0_80/howto/ docs_0_80/howto/cvs-ssh/ dtdx/ pluginDocs/plugins_0_70/ plugi...
Date Mon, 19 Dec 2005 01:33:15 GMT
Modified: forrest/site/docs_0_80/howto/howto-view-dsl.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-view-dsl.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-view-dsl.html (original)
+++ forrest/site/docs_0_80/howto/howto-view-dsl.html Sun Dec 18 17:31:25 2005
@@ -432,13 +432,13 @@
 </div>
 <p>
       We developed<strong> forrest:view</strong>  to let the user decide where to place elements in e.g. html pages.
-      We started this work with the <span class="codefrag ">skinconf.xml</span> where you could configure certain elements and
+      We started this work with the <span class="codefrag">skinconf.xml</span> where you could configure certain elements and
       their positions. These elements were known under certain names. It was up to the skin designer to support 
       this configuration and the elements.
     </p>
 <p>
      The work started with grouping elements (the ones from skinconf). We used css-contracts that 
-     we added as @attributes e.g. <span class="codefrag ">&lt;div id="content-main"/&gt; </span>. That made it 
+     we added as @attributes e.g. <span class="codefrag">&lt;div id="content-main"/&gt; </span>. That made it 
      possible to use the same elements in different skins. For the full list refer to the
       <a href="http://svn.apache.org/repos/asf/forrest/trunk/main/webapp/skins/leather-dev/contracts.initial.txt">
         initial contract list
@@ -454,8 +454,8 @@
      
 <strong>forrest:hook</strong>s are containers that are only used for layout reasons. They <strong>do not</strong> add 
      any content or functionality to the output. They add <strong>only</strong> layout information to 
-     the output. Actually a <span class="codefrag ">&lt;forrest:hook name="layoutId"/&gt;</span> will be transformed
-     to <span class="codefrag ">&lt;div id="layoutId"/&gt; </span>
+     the output. Actually a <span class="codefrag">&lt;forrest:hook name="layoutId"/&gt;</span> will be transformed
+     to <span class="codefrag">&lt;div id="layoutId"/&gt; </span>
     
 </p>
 <p>
@@ -484,17 +484,17 @@
 <p>
 				In this section we will create a new view. We will override the default view of the view-plugin
         for the index page of the <a href="../../docs_0_80/howto/howto-view-install.html">newSeed</a>.
-        For that we will create a file called <span class="codefrag ">index.fv</span> and save it in our xdocs directory. 
+        For that we will create a file called <span class="codefrag">index.fv</span> and save it in our xdocs directory. 
         This will make <strong>only</strong> the index.html page look different from the rest of the project.
 			</p>
 <p>
-        Remember: pointing your browser to <span class="codefrag ">http://localhost:8888/ls.contracts.html</span> will
+        Remember: pointing your browser to <span class="codefrag">http://localhost:8888/ls.contracts.html</span> will
         show a page with all contracts that you can use in your project.
       </p>
 <p>
         Let use the blank view from the earlier step and add the content-main contract. In 
         ls.contracts.html we find the information for how to use the contract in our view. Our 
-        <span class="codefrag ">index.fv</span> should look like:
+        <span class="codefrag">index.fv</span> should look like:
       </p>
 <pre class="code">&lt;forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0"&gt;
   &lt;forrest:view type="xhtml"&gt;
@@ -503,7 +503,7 @@
 &lt;/forrest:views&gt;
       </pre>
 <p>
-        Lets try our new view by pointing to <span class="codefrag ">http://localhost:8888/index.html</span>. 
+        Lets try our new view by pointing to <span class="codefrag">http://localhost:8888/index.html</span>. 
         We will see only the main content. Now let us add the section navigation to our view.
         The contract usage in the view can be looked up in ls.contracts.html. Our view now looks like:
       </p>
@@ -522,7 +522,7 @@
 <a name="N100D8"></a><a name="hookView"></a>
 <h3 class="underlined_5">Hooks in views</h3>
 <p>
-        We will use now the first time a <span class="codefrag ">&lt;forrest:hook name="layoutId"/&gt;</span>.
+        We will use now the first time a <span class="codefrag">&lt;forrest:hook name="layoutId"/&gt;</span>.
         Hooks are the styling side of views. We can imitate arbitrary html skeleton 
         with their help. Before we explain how to use your own css in views, we will use the default css.
         In the default.css we can find 
@@ -536,7 +536,7 @@
 }
       </pre>
 <p>
-        With this information we know to use <span class="codefrag ">&lt;forrest:hook name="leftbar"/&gt;</span> 
+        With this information we know to use <span class="codefrag">&lt;forrest:hook name="leftbar"/&gt;</span> 
         and add contracts into that container. 
       </p>
 <p>
@@ -564,10 +564,10 @@
 <p>
         We now know how to place contracts and hooks in our view. Until this stage we only used the default.css. 
         CSS-support of views is as easy as placing contracts/hooks. To override the default.css
-        stylesheet we use another tag within our view <span class="codefrag ">&lt;forrest:css url="default.css"/&gt;</span>.
+        stylesheet we use another tag within our view <span class="codefrag">&lt;forrest:css url="default.css"/&gt;</span>.
       </p>
 <p>
-        We will now create a file in <span class="codefrag ">{project:skins-dir}{path}/{name}.css</span>. In our case
+        We will now create a file in <span class="codefrag">{project:skins-dir}{path}/{name}.css</span>. In our case
         we will save a file called howTo.css in newSeed/src/documentation/skins/css/howTo.css containing only 
         the following css:
       </p>
@@ -582,14 +582,14 @@
 <p>
         We just changed the border-style to 'solid', the background to '#CCCCFF' and the color to '#000000'. 
         Now we have to add a new tag to tell that we want to override the default.css. We are doing this 
-        by adding the tag <span class="codefrag ">&lt;forrest:css url="howTo.css"/&gt;</span> to our view.
+        by adding the tag <span class="codefrag">&lt;forrest:css url="howTo.css"/&gt;</span> to our view.
       </p>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
         
-<span class="codefrag ">&lt;forrest:css url="howTo.css"/&gt;</span> needs to be the direct child of 
-        <span class="codefrag ">&lt;forrest:view type="xhtml"&gt;</span>
+<span class="codefrag">&lt;forrest:css url="howTo.css"/&gt;</span> needs to be the direct child of 
+        <span class="codefrag">&lt;forrest:view type="xhtml"&gt;</span>
       
 </div>
 </div>
@@ -606,7 +606,7 @@
 <p>
         Now you see a white page where the menu is surrounded by a solid border with the defined background.
          As a second example, let us change as well the content-main by adding another hook 
-         <span class="codefrag ">&lt;forrest:hook name="content"/&gt;</span> We need to add the new layout container
+         <span class="codefrag">&lt;forrest:hook name="content"/&gt;</span> We need to add the new layout container
          to our howTo.css:
       </p>
 <pre class="code">

Modified: forrest/site/docs_0_80/howto/howto-view-install.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-view-install.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-view-install.html (original)
+++ forrest/site/docs_0_80/howto/howto-view-install.html Sun Dec 18 17:31:25 2005
@@ -446,7 +446,7 @@
 ant local-deploy
       </pre>
 <p>
-        Alternatively, run the script <span class="codefrag ">etc/views.sh</span>
+        Alternatively, run the script <span class="codefrag">etc/views.sh</span>
       
 </p>
 <a name="N1005F"></a><a name="newSeed"></a>
@@ -488,13 +488,13 @@
 <pre class="code">
 forrest run
       </pre>
-<p>Then point to <span class="codefrag ">http://localhost:8888/</span> and you will see the default
+<p>Then point to <span class="codefrag">http://localhost:8888/</span> and you will see the default
         views-based site.</p>
 <a name="N10099"></a><a name="availableContracts"></a>
 <h3 class="underlined_5">Available contracts</h3>
 <p> 
 	     To start working with views, you need to know which contracts you can use. 
-	     For this we will install another plugin <span class="codefrag ">org.apache.forrest.plugin.input.viewHelper.xhtml.ls</span>.
+	     For this we will install another plugin <span class="codefrag">org.apache.forrest.plugin.input.viewHelper.xhtml.ls</span>.
 	     The setup is:
 	    </p>
 <pre class="code">
@@ -513,7 +513,7 @@
 project.required.plugins=org.apache.forrest.plugin.input.viewHelper.xhtml.ls
       </pre>
 <p>
-        Now point your browser to <span class="codefrag ">http://localhost:8888/ls.contracts.html</span>. 
+        Now point your browser to <span class="codefrag">http://localhost:8888/ls.contracts.html</span>. 
         On this page you will find all contracts that you can use in your project.
       </p>
 </div>

Modified: forrest/site/docs_0_80/libre-intro.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/libre-intro.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_80/libre-intro.html (original)
+++ forrest/site/docs_0_80/libre-intro.html Sun Dec 18 17:31:25 2005
@@ -499,7 +499,7 @@
   &lt;/collection&gt;
 &lt;/collection&gt;</pre>
 <p>And it's not getting any harder in fact: only 2 elements,
-          <span class="codefrag ">&lt;collection&gt;</span> and <span class="codefrag ">&lt;item&gt;</span> and that should
+          <span class="codefrag">&lt;collection&gt;</span> and <span class="codefrag">&lt;item&gt;</span> and that should
           do. The first maps to a menu-group in the navigation, guess what the second
           maps to?</p>
 <p>The number and value (and its meaning) of the attributes on these
@@ -569,15 +569,15 @@
 <li>libre doesn't yet support external hrefs (should be easy
               though)</li> 
             
-<li>there is no difference between <span class="codefrag ">&lt;menu&gt;</span> and
-              <span class="codefrag ">&lt;menu-item&gt;</span>, there just is <span class="codefrag ">&lt;entry&gt;</span>. It
-              will become a <span class="codefrag ">&lt;collection&gt;</span> or <span class="codefrag ">&lt;item&gt;</span> in
+<li>there is no difference between <span class="codefrag">&lt;menu&gt;</span> and
+              <span class="codefrag">&lt;menu-item&gt;</span>, there just is <span class="codefrag">&lt;entry&gt;</span>. It
+              will become a <span class="codefrag">&lt;collection&gt;</span> or <span class="codefrag">&lt;item&gt;</span> in
               the output based on the fact if the location points to a directory resp. a
               file.</li> 
             
 <li>For locations that point to a filter it doesn't make sense, but
-              when it points to a directory it is nested <span class="codefrag ">&lt;filter&gt;</span> and
-              <span class="codefrag ">&lt;sort&gt;</span> elements get inherited down to the next level. </li> 
+              when it points to a directory it is nested <span class="codefrag">&lt;filter&gt;</span> and
+              <span class="codefrag">&lt;sort&gt;</span> elements get inherited down to the next level. </li> 
           
 </ul> 
           
@@ -591,18 +591,18 @@
 <pre class="code">&lt;auto&gt;</pre>
 <ul> 
             
-<li>Automatically generates more <span class="codefrag ">&lt;collection&gt;</span>
-              and <span class="codefrag ">&lt;item&gt;</span> elements in the output, based on the
-              specifications of the nested elements: <span class="codefrag ">&lt;filter&gt;</span> (which
-              resources?) and <span class="codefrag ">&lt;sort&gt;</span> (in which order?).</li> 
+<li>Automatically generates more <span class="codefrag">&lt;collection&gt;</span>
+              and <span class="codefrag">&lt;item&gt;</span> elements in the output, based on the
+              specifications of the nested elements: <span class="codefrag">&lt;filter&gt;</span> (which
+              resources?) and <span class="codefrag">&lt;sort&gt;</span> (in which order?).</li> 
           
 </ul>
 <pre class="code">&lt;filter logic="inverse" clear="no"&gt;</pre>
 <ul> 
             
 <li>This element wraps a so-called AttributeReader (there are
-              currently two of them: <span class="codefrag ">&lt;xpath&gt;</span> and
-              <span class="codefrag ">&lt;property&gt;</span>)</li> 
+              currently two of them: <span class="codefrag">&lt;xpath&gt;</span> and
+              <span class="codefrag">&lt;property&gt;</span>)</li> 
             
 <li>The AttributeReader is going to specify which
               information-element is going to be retrieved from the file or directory it is
@@ -615,7 +615,7 @@
               acceptance-logic (accept what normally should be rejected and vice versa).</li>
             
             
-<li>Using the <span class="codefrag ">clear="yes"</span> attribute stops the
+<li>Using the <span class="codefrag">clear="yes"</span> attribute stops the
               inheritance of the used filter strategy from the parent directory. Instead the
               default filter strategy (which is to accept all files) is slided in at this
               level.</li> 
@@ -625,20 +625,20 @@
 <ul> 
             
 <li>This element wraps a so called AttributeReader (there are
-              currently two of them: <span class="codefrag ">&lt;xpath&gt;</span> and
-              <span class="codefrag ">&lt;property&gt;</span>).</li> 
+              currently two of them: <span class="codefrag">&lt;xpath&gt;</span> and
+              <span class="codefrag">&lt;property&gt;</span>).</li> 
             
 <li>The AttributeReader is going to specify which
               information-element is going to be retrieved from the file or directory it is
               pointing at. This information element will be considered to be a simple
-              Key-String and <span class="codefrag ">&lt;collection&gt;</span> and <span class="codefrag ">&lt;item&gt;</span>
+              Key-String and <span class="codefrag">&lt;collection&gt;</span> and <span class="codefrag">&lt;item&gt;</span>
               elements in the output will appear in the order defined by the alphabetic
               sorting of these keys.</li> 
             
 <li>This wrapping sort element allows to reverse the order.
               (z-&gt;a instead of a-&gt;z)</li> 
             
-<li>Using the <span class="codefrag ">clear="yes"</span> attribute stops the
+<li>Using the <span class="codefrag">clear="yes"</span> attribute stops the
               inheritance of the used sort strategy from the parent directory. Instead the
               default sort strategy (which is to use default filesystem sorting, alphabetic
               on filename) is slided in at this level.</li> 
@@ -648,9 +648,9 @@
 <ul> 
             
 <li>The remainder of the elements inside the
-              <span class="codefrag ">&lt;auto&gt;</span> tag specify the attributes that need to be applied to
-              the generated <span class="codefrag ">&lt;collection&gt;</span> and <span class="codefrag ">&lt;item&gt;</span>
-              elements in the output: <span class="codefrag ">&lt;item label=".." href=".." YOURTAG=".."
+              <span class="codefrag">&lt;auto&gt;</span> tag specify the attributes that need to be applied to
+              the generated <span class="codefrag">&lt;collection&gt;</span> and <span class="codefrag">&lt;item&gt;</span>
+              elements in the output: <span class="codefrag">&lt;item label=".." href=".." YOURTAG=".."
               /&gt;</span>
 </li> 
             
@@ -671,39 +671,39 @@
 <ul> 
             
 <li>This element specifies an xpath AttributeReader to use inside
-              <span class="codefrag ">&lt;filter&gt;</span>, <span class="codefrag ">&lt;sort&gt;</span> or
+              <span class="codefrag">&lt;filter&gt;</span>, <span class="codefrag">&lt;sort&gt;</span> or
               {AttributeDefinitions}.</li> 
             
 <li>It allows to specify an xpath expression that should result in
               one single text node to be returned when applied to the root node of the xml
               file at the location of any given entry. The contents of this text-node is the
-              string value to sort (<span class="codefrag ">&lt;sort&gt;</span> usage) or to fill in the
-              specified attribute (<span class="codefrag ">&lt;label&gt;</span>, <span class="codefrag ">&lt;href&gt;</span>...
-              use). When inside a <span class="codefrag ">&lt;filter&gt;</span>: the presence of the node
+              string value to sort (<span class="codefrag">&lt;sort&gt;</span> usage) or to fill in the
+              specified attribute (<span class="codefrag">&lt;label&gt;</span>, <span class="codefrag">&lt;href&gt;</span>...
+              use). When inside a <span class="codefrag">&lt;filter&gt;</span>: the presence of the node
               results in passing the test.</li> 
           
 </ul>
 <div class="warning">
 <div class="label">Warning</div>
-<div class="content">This currently breaks for non xml (<span class="codefrag ">*.gif</span>)
+<div class="content">This currently breaks for non xml (<span class="codefrag">*.gif</span>)
             files, so get your filter right please, and in the mean time: sorry for not
-            being able to use it in the filter yet <span class="codefrag ">:-(</span>.</div>
+            being able to use it in the filter yet <span class="codefrag">:-(</span>.</div>
 </div>
 <pre class="code">&lt;property name="path" regex="(\.[\\/])*(.*)" substitute="$2"/&gt;
 &lt;property name="name"  mask="CVS"/&gt;</pre>
 <ul> 
             
 <li>This element specifies an xpath AttributeReader to use inside
-              <span class="codefrag ">&lt;filter&gt;</span>, <span class="codefrag ">&lt;sort&gt;</span> or
+              <span class="codefrag">&lt;filter&gt;</span>, <span class="codefrag">&lt;sort&gt;</span> or
               {AttributeDefinitions}.</li> 
             
 <li>It allows to specify a JavaBean-like property to read (this
               introspection behavior will probably not survive the future release) on the
               file at the 'location' of any given entry. The (object-)value of this property
               is automatically converted to a String (toString()) that becomes the value to
-              sort (<span class="codefrag ">&lt;sort&gt;</span> usage) or to fill in the specified attribute
-              (<span class="codefrag ">&lt;label&gt;</span>, <span class="codefrag ">&lt;href&gt;</span>... use). When inside a
-              <span class="codefrag ">&lt;filter&gt;</span>, the test passes if the read property is not null
+              sort (<span class="codefrag">&lt;sort&gt;</span> usage) or to fill in the specified attribute
+              (<span class="codefrag">&lt;label&gt;</span>, <span class="codefrag">&lt;href&gt;</span>... use). When inside a
+              <span class="codefrag">&lt;filter&gt;</span>, the test passes if the read property is not null
               or "".</li> 
             
 <li>Furthermore this element allows to express more elaborate
@@ -726,28 +726,28 @@
 <p>There are some things that libre is doing that you should be aware of.</p>
 <a name="N10175"></a><a name="No+libre.xml"></a>
 <h4>No libre.xml</h4>
-<p>When using an <span class="codefrag ">&lt;auto&gt; </span>section, the filter will
-            NEVER accept the <span class="codefrag ">libre.xml</span> file to be in the generated output. You
-            can however include a manual <span class="codefrag ">&lt;entry&gt;</span> to point to the
-            <span class="codefrag ">libre.xml</span> file if needed.</p>
+<p>When using an <span class="codefrag">&lt;auto&gt; </span>section, the filter will
+            NEVER accept the <span class="codefrag">libre.xml</span> file to be in the generated output. You
+            can however include a manual <span class="codefrag">&lt;entry&gt;</span> to point to the
+            <span class="codefrag">libre.xml</span> file if needed.</p>
 <a name="N1018B"></a><a name="No+Duplicates"></a>
 <h4>No Duplicates</h4>
-<p>You can combine multiple <span class="codefrag ">&lt;entry&gt;</span> and
-            <span class="codefrag ">&lt;auto&gt;</span> elements after each other. The system will make sure
-            that the resulting list of <span class="codefrag ">&lt;collection&gt;</span> and
-            <span class="codefrag ">&lt;item&gt;</span> will not contain duplicates. So the filters in
-            <span class="codefrag ">&lt;auto&gt;</span> sections lower down the <span class="codefrag ">libre.xml</span> file
+<p>You can combine multiple <span class="codefrag">&lt;entry&gt;</span> and
+            <span class="codefrag">&lt;auto&gt;</span> elements after each other. The system will make sure
+            that the resulting list of <span class="codefrag">&lt;collection&gt;</span> and
+            <span class="codefrag">&lt;item&gt;</span> will not contain duplicates. So the filters in
+            <span class="codefrag">&lt;auto&gt;</span> sections lower down the <span class="codefrag">libre.xml</span> file
             can include already accepted files or directories, they will only show up once
             in the output.</p>
 <a name="N101A8"></a><a name="Example+Constructs"></a>
 <h3 class="underlined_5">Example Constructs</h3>
 <p>Adding sorting and filtering to the filesystem with libre becomes a
           subtle play with editable filesystem properties, smart XML content and
-          <span class="codefrag ">libre.xml</span> configs. This should be considered as the 'extended'
+          <span class="codefrag">libre.xml</span> configs. This should be considered as the 'extended'
           contract between the following roles in the documentation system: the one
           choosing (or creating) the DTDs, the one applying those to create content and
           give the resulting files a name, the one that sets up the directories to store
-          those files and writes the <span class="codefrag ">libre.xml</span> files.</p>
+          those files and writes the <span class="codefrag">libre.xml</span> files.</p>
 <a name="N101B7"></a><a name="Sorting+your+files+or+your+menu+entries%3F"></a>
 <h4>Sorting your files or your menu entries?</h4>
 <p>In every case the very pragmatic approach can become something
@@ -778,14 +778,14 @@
 <ul> 
             
 <li>
-<span class="codefrag ">&lt;filter&gt;</span>: only resources which name starts
+<span class="codefrag">&lt;filter&gt;</span>: only resources which name starts
               with a 3-digit pattern</li> 
             
-<li>No <span class="codefrag ">&lt;sort&gt;</span>: in their natural filesystem order
+<li>No <span class="codefrag">&lt;sort&gt;</span>: in their natural filesystem order
               assured by the digit-prefix</li> 
             
 <li>
-<span class="codefrag ">&lt;label&gt;</span>: hold a label attribute that strips
+<span class="codefrag">&lt;label&gt;</span>: hold a label attribute that strips
               of the ugly number prefix</li> 
           
 </ul>
@@ -907,7 +907,7 @@
 <h4>Separating property-retrieval from formatting and
             testing</h4>
 <p>Playing around with the attributes in
-            <span class="codefrag ">&lt;property&gt;</span>:</p>
+            <span class="codefrag">&lt;property&gt;</span>:</p>
 <ul> 
             
 <li>poses hard to explain combinatory effects (@regex with
@@ -930,23 +930,23 @@
 &lt;/label&gt;</pre>
 <p>Allowing the formatter to be used around the xpath reader as well.
             And opening up the possibility to maybe format other stuff than Strings:
-            <span class="codefrag ">&lt;dateformat format="dd/mmm/yy"&gt; </span>
+            <span class="codefrag">&lt;dateformat format="dd/mmm/yy"&gt; </span>
 </p>
 <p>It would also clearly distinguish the semantical difference of
-            applying a test in the <span class="codefrag ">&lt;filter&gt;</span> context:</p>
+            applying a test in the <span class="codefrag">&lt;filter&gt;</span> context:</p>
 <pre class="code">&lt;filter&gt;
   &lt;regextest match="..."&gt;
     &lt;property ... /&gt;
   &lt;/regextest&gt;
 &lt;/filter&gt;</pre>
-<p>And more logically introduce other tests like <span class="codefrag ">&lt;globtest
-            match="..."&gt;</span> or <span class="codefrag ">&lt;availabletest&gt;</span> or...</p>
+<p>And more logically introduce other tests like <span class="codefrag">&lt;globtest
+            match="..."&gt;</span> or <span class="codefrag">&lt;availabletest&gt;</span> or...</p>
 <a name="N1028B"></a><a name="Replace+the+introspection+with+semantically+richer+named%0A++++++++++++properties+to+read."></a>
 <h4>Replace the introspection with semantically richer named
             properties to read.</h4>
-<p>Currently the <span class="codefrag ">&lt;property
+<p>Currently the <span class="codefrag">&lt;property
             name="someJavaBeanProp"&gt;</span> is applied in a java introspection for the
-            <span class="codefrag ">getSomeJavaBeanProp()</span> on the <span class="codefrag ">java.io.File</span> object that
+            <span class="codefrag">getSomeJavaBeanProp()</span> on the <span class="codefrag">java.io.File</span> object that
             is actually representing the node in the hierarchy at any given time. The DTD
             declares the attribute as of type CDATA. These decisions however:</p>
 <ul> 
@@ -954,7 +954,7 @@
 <li>lead to a lesser user guidance for the libre.xml writer using
               an XML (and DTD) savvy editor </li> 
             
-<li>leads to assuming the <span class="codefrag ">libre.xml</span> editor has access
+<li>leads to assuming the <span class="codefrag">libre.xml</span> editor has access
               to and knows how to interpret jdk javadoc</li> 
             
 <li>leads to poor semantical support and thus more possible RUNTIME
@@ -1013,9 +1013,9 @@
 <ul> 
           
 <li>do we need support for nested elements inside
-            <span class="codefrag ">&lt;item&gt;</span> output (retrieved by e.g. xpath expressions)?</li> 
+            <span class="codefrag">&lt;item&gt;</span> output (retrieved by e.g. xpath expressions)?</li> 
           
-<li>do we need an extra <span class="codefrag ">&lt;constant&gt;</span> like
+<li>do we need an extra <span class="codefrag">&lt;constant&gt;</span> like
             attributereader that would allow like book.xml to add fixed values for
             expressed attributes</li> 
           

Modified: forrest/site/docs_0_80/linking.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/linking.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_80/linking.html (original)
+++ forrest/site/docs_0_80/linking.html Sun Dec 18 17:31:25 2005
@@ -408,7 +408,7 @@
 <div class="section">
 <p>
         This document describes Forrest's internal URI space; how it is managed
-        with the "<span class="codefrag ">site.xml</span>" configuration file, how menus are generated,
+        with the "<span class="codefrag">site.xml</span>" configuration file, how menus are generated,
         and how various link schemes (site: and ext:) operate.
         An overview of the implementation is also provided.
       </p>
@@ -419,9 +419,9 @@
 <h2 class="underlined_10">site.xml</h2>
 <div class="section">
 <p>
-        The "<span class="codefrag ">site.xml</span>" configuration file is what we would call a "site map"
+        The "<span class="codefrag">site.xml</span>" configuration file is what we would call a "site map"
         if Cocoon hadn't already claimed that term. 
-        The "<span class="codefrag ">site.xml</span>" is a loosely structured XML file, acting as a map of the
+        The "<span class="codefrag">site.xml</span>" is a loosely structured XML file, acting as a map of the
         site's contents.  It provides a unique identifier (an XPath address)
         for "nodes" of information in the website.  A "node" of site information
         can be:
@@ -434,17 +434,17 @@
 <li>A specific page, e.g. "the FAQ page"</li>
         
 <li>A specific section in a page, e.g. the "general" section of the FAQ
-          page (identified by <span class="codefrag ">id="general"</span> attribute)</li>
+          page (identified by <span class="codefrag">id="general"</span> attribute)</li>
       
 </ul>
 <p>
-        In addition to providing fine-grained addressing of site info, the <span class="codefrag ">site.xml</span>
+        In addition to providing fine-grained addressing of site info, the <span class="codefrag">site.xml</span>
         allows <em>metadata</em> to be associated with each node, using
-        attributes or child elements.  Most commonly, a <span class="codefrag ">label</span>
+        attributes or child elements.  Most commonly, a <span class="codefrag">label</span>
         attribute is used to provide a text description of the node.
       </p>
 <p>
-        There are currently two applications of <span class="codefrag ">site.xml</span>
+        There are currently two applications of <span class="codefrag">site.xml</span>
       
 </p>
 <dl>
@@ -454,21 +454,21 @@
 </dt>
         
 <dd>
-<span class="codefrag ">site.xml</span> is used to generate the menus for the HTML website.</dd>
+<span class="codefrag">site.xml</span> is used to generate the menus for the HTML website.</dd>
         
 <dt>
 <a href="#indirect-linking">Indirect linking</a>
 </dt>
         
 <dd>
-<span class="codefrag ">site.xml</span> provides a basic aliasing mechanism for linking, e.g. one
+<span class="codefrag">site.xml</span> provides a basic aliasing mechanism for linking, e.g. one
           can write &lt;link href="site:v0.80//changes"&gt; from anywhere in the site, and
           link to the "changes" information node (translated to changes.html).
           More on this below.</dd>
       
 </dl>
 <p>
-        Here is a sample <span class="codefrag ">site.xml</span> ...
+        Here is a sample <span class="codefrag">site.xml</span> ...
       </p>
 <pre class="code">
 &lt;?xml version="1.0"?&gt;
@@ -529,25 +529,25 @@
 <ul>
         
 <li>The root element must be "site", and normal content should be in the
-          namespace <span class="codefrag ">http://apache.org/forrest/linkmap/1.0</span> (Feel
+          namespace <span class="codefrag">http://apache.org/forrest/linkmap/1.0</span> (Feel
           free to mix in your own content (RDF, dublin core, etc) under new
           namespaces)</li>
         
-<li>Element names are used as identifiers.  The "<span class="codefrag ">foo</span>" in
-          "<span class="codefrag ">site:foo</span>" must therefore be a valid NMTOKEN.</li>
+<li>Element names are used as identifiers.  The "<span class="codefrag">foo</span>" in
+          "<span class="codefrag">site:foo</span>" must therefore be a valid NMTOKEN.</li>
         
-<li>Elements with <span class="codefrag ">href</span> attributes can be used as identifiers
-          in "<span class="codefrag ">site:</span>" URIs</li>
+<li>Elements with <span class="codefrag">href</span> attributes can be used as identifiers
+          in "<span class="codefrag">site:</span>" URIs</li>
         
 <li>Relative href attribute contents are "accumulated" by prepending hrefs
           from ancestor nodes</li>
         
-<li>Elements without <span class="codefrag ">label</span> attributes (and their children)
+<li>Elements without <span class="codefrag">label</span> attributes (and their children)
           are not displayed in the menu.</li>
         
-<li>Elements below <span class="codefrag ">external-refs</span> are mapped to the
-          "<span class="codefrag ">ext:</span>" scheme.  So "<span class="codefrag ">ext:commons/resolver/</span>" becomes
-          "<span class="codefrag ">http://xml.apache.org/commons/resolver/</span>"</li>
+<li>Elements below <span class="codefrag">external-refs</span> are mapped to the
+          "<span class="codefrag">ext:</span>" scheme.  So "<span class="codefrag">ext:commons/resolver/</span>" becomes
+          "<span class="codefrag">http://xml.apache.org/commons/resolver/</span>"</li>
       
 </ul>
 <p>
@@ -560,11 +560,11 @@
 <h2 class="underlined_10">Generating Menus</h2>
 <div class="section">
 <p>
-        Two files are used to define a site's tabs and menu (<span class="codefrag ">site.xml</span> and
-        <span class="codefrag ">tabs.xml</span>).  Both files are located in
-        <span class="codefrag ">src/documentation/content/xdocs/</span>
+        Two files are used to define a site's tabs and menu (<span class="codefrag">site.xml</span> and
+        <span class="codefrag">tabs.xml</span>).  Both files are located in
+        <span class="codefrag">src/documentation/content/xdocs/</span>
 </p>
-<p>Assume that our <span class="codefrag ">tabs.xml</span> looks like this:</p>
+<p>Assume that our <span class="codefrag">tabs.xml</span> looks like this:</p>
 <pre class="code">
 &lt;tabs ...&gt;
     &lt;tab id="home" label="Home" dir=""/&gt;
@@ -572,48 +572,48 @@
     &lt;tab id="howto" label="How-Tos" dir="community/howto"/&gt;
 &lt;/tabs&gt;
       </pre>
-<p>Using the "<span class="codefrag ">site.xml</span>" listed above, we would get these menus:</p>
+<p>Using the "<span class="codefrag">site.xml</span>" listed above, we would get these menus:</p>
 <p>
         
 <img alt="Menu generated from site.xml" src="images/menu.png">&nbsp;&nbsp;&nbsp;
         <img alt="Community menu generated from site.xml" src="images/menu2.png">&nbsp;&nbsp;&nbsp;
         <img alt="Howto menu generated from site.xml" src="images/menu3.png">
       </p>
-<p>When using the "<span class="codefrag ">dir</span>" attribute as above the value of the
-      "<span class="codefrag ">indexfile</span>" parameter is appended to the value of the 
-      "<span class="codefrag ">dir</span>" attribute (together with a preceding '/'). For example,
+<p>When using the "<span class="codefrag">dir</span>" attribute as above the value of the
+      "<span class="codefrag">indexfile</span>" parameter is appended to the value of the 
+      "<span class="codefrag">dir</span>" attribute (together with a preceding '/'). For example,
       the link for the community tab above is 
-      <span class="codefrag ">community/mailLists.html</span>. Note that "<span class="codefrag ">indexfile</span>"
-      defaults to "<span class="codefrag ">index.html</span>" if no value is supplied. Therefore the
-      link for the howto tab is <span class="codefrag ">community/howto/index.html</span>
+      <span class="codefrag">community/mailLists.html</span>. Note that "<span class="codefrag">indexfile</span>"
+      defaults to "<span class="codefrag">index.html</span>" if no value is supplied. Therefore the
+      link for the howto tab is <span class="codefrag">community/howto/index.html</span>
 </p>
 <a name="N100F0"></a><a name="tabs-external"></a>
 <h3 class="underlined_5">Tabs for External Resources</h3>
 <p>A tab can refer to an external resource by using the 
-        "<span class="codefrag ">href</span>" attribute instead of the "<span class="codefrag ">dir</span>" attribute.
-        The value of "<span class="codefrag ">href</span>" should be the URI of the resource you wish 
+        "<span class="codefrag">href</span>" attribute instead of the "<span class="codefrag">dir</span>" attribute.
+        The value of "<span class="codefrag">href</span>" should be the URI of the resource you wish 
         to link to. For example:</p>
 <pre class="code">
 &lt;tab id="apache" label="XML Apache" href="http://xml.apache.org/"/&gt;
         </pre>
-<p>Unlike the "<span class="codefrag ">dir</span>" attribute, the value of "<span class="codefrag ">href</span>"
+<p>Unlike the "<span class="codefrag">dir</span>" attribute, the value of "<span class="codefrag">href</span>"
         is left unmodified by Forrest unless it is root-relative and obviously 
         specifies a directory (ends in '/'). In which case /index.html will be 
         added.</p>
 <a name="N10110"></a><a name="selecting-entries"></a>
 <h3 class="underlined_5">Selecting menu entries</h3>
 <p>Forrest decides which menu entries to display, by examining the
-          "<span class="codefrag ">tab</span>" attributes in the <span class="codefrag ">site.xml</span> file. The children of 
-          all <span class="codefrag ">site.xml</span> entries with a
-          "<span class="codefrag ">tab</span>" which is equal to that of the current page, are
+          "<span class="codefrag">tab</span>" attributes in the <span class="codefrag">site.xml</span> file. The children of 
+          all <span class="codefrag">site.xml</span> entries with a
+          "<span class="codefrag">tab</span>" which is equal to that of the current page, are
           added to the menu, whilst the element itself forms the root of that
-          part of the menu (see the "<span class="codefrag ">community</span>" element in the 
+          part of the menu (see the "<span class="codefrag">community</span>" element in the 
           example below). Child elements that have a different 
-          "<span class="codefrag ">tab</span>" attribute value will appear in the menu for their
+          "<span class="codefrag">tab</span>" attribute value will appear in the menu for their
           parents, and will also form the root of a new menu for a tab with 
-          the appropriate name (see the "<span class="codefrag ">howto-samples</span>" element
+          the appropriate name (see the "<span class="codefrag">howto-samples</span>" element
           below).</p>
-<p>Consider our <span class="codefrag ">site.xml</span> example:</p>
+<p>Consider our <span class="codefrag">site.xml</span> example:</p>
 <pre class="code">
 &lt;site label="Forrest" href="" <strong>tab="home"</strong>
   xmlns="http://apache.org/forrest/linkmap/1.0"&gt;
@@ -638,25 +638,25 @@
         &lt;step1 label="Step 1" href="step1.html"/&gt;
       ...</pre>
 <p>
-          Every <span class="codefrag ">site.xml</span> node can potentially have a "<span class="codefrag ">tab</span>" attribute.  If
-          unspecified, nodes inherit the "<span class="codefrag ">tab</span>" of their parent.  Thus
+          Every <span class="codefrag">site.xml</span> node can potentially have a "<span class="codefrag">tab</span>" attribute.  If
+          unspecified, nodes inherit the "<span class="codefrag">tab</span>" of their parent.  Thus
           everything in the <strong>&lt;about&gt;</strong> section has an implicit
-          <span class="codefrag ">tab="home" </span>attribute.</p>
+          <span class="codefrag">tab="home" </span>attribute.</p>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">You can see this by viewing your site's 
         <a href="../abs-menulinks">abs-menulinks</a> pipeline in a
           browser.</div>
 </div>
-<p>Say that the user is viewing the <span class="codefrag ">linking.html</span>
+<p>Say that the user is viewing the <span class="codefrag">linking.html</span>
           page.  The <strong>&lt;linking&gt;</strong> node has an implicit tab
-          value of "<span class="codefrag ">home</span>".  Forrest will select <em>all nodes with
+          value of "<span class="codefrag">home</span>".  Forrest will select <em>all nodes with
             tab="home"</em> and put them in the menu.
         </p>
 <a name="N1016A"></a><a name="other-menu-selection"></a>
 <h3 class="underlined_5">Alternative menu selection mechanisms.</h3>
 <p>
-          The "<span class="codefrag ">tab</span>" attribute-based scheme for selecting a menu's
+          The "<span class="codefrag">tab</span>" attribute-based scheme for selecting a menu's
           entries is not the only one, although it is the most flexible.  Here
           we describe a few alternatives.
         </p>
@@ -675,11 +675,11 @@
           </p>
 <ul>
             
-<li>Edit <span class="codefrag ">forrest.properties</span> and set
-              <span class="codefrag ">project.menu-scheme=directories</span>
+<li>Edit <span class="codefrag">forrest.properties</span> and set
+              <span class="codefrag">project.menu-scheme=directories</span>
 </li>
             
-<li>Remove the "<span class="codefrag ">id</span>" attributes from <span class="codefrag ">tabs.xml</span>
+<li>Remove the "<span class="codefrag">id</span>" attributes from <span class="codefrag">tabs.xml</span>
               entries.</li>
           
 </ul>
@@ -687,19 +687,19 @@
 <h4>Specifying menus with book.xml</h4>
 <p>
             Historically, menus in Forrest have been generated from a
-            <span class="codefrag ">book.xml</span> file, one per directory.  This mechanism is
-            still available, and if a <span class="codefrag ">book.xml</span> is found, it will be
-            used in preference to the menu generated by the <span class="codefrag ">site.xml</span> file. The <span class="codefrag ">book.xml</span>
-            files can use "<span class="codefrag ">site:</span>" URIs to ease the maintenance burden
+            <span class="codefrag">book.xml</span> file, one per directory.  This mechanism is
+            still available, and if a <span class="codefrag">book.xml</span> is found, it will be
+            used in preference to the menu generated by the <span class="codefrag">site.xml</span> file. The <span class="codefrag">book.xml</span>
+            files can use "<span class="codefrag">site:</span>" URIs to ease the maintenance burden
             that led to obsolescence of book.xml files.  In general, however, we
-            recommend that users avoid <span class="codefrag ">book.xml</span> files.
+            recommend that users avoid <span class="codefrag">book.xml</span> files.
           </p>
 <a name="N101C3"></a><a name="tab-selection"></a>
 <h3 class="underlined_5">Selecting the current tab</h3>
 <p>
           The tab selection algorithm is quite simple: the tab with the
-          "<span class="codefrag ">id</span>" which matches that of the current <span class="codefrag ">site.xml</span>
-          node is "selected". However the interaction of <span class="codefrag ">tabs.xml</span> and <span class="codefrag ">site.xml</span>
+          "<span class="codefrag">id</span>" which matches that of the current <span class="codefrag">site.xml</span>
+          node is "selected". However the interaction of <span class="codefrag">tabs.xml</span> and <span class="codefrag">site.xml</span>
           while powerful, can be complex to establish.
         </p>
 <a name="N101D9"></a><a name="tab-site"></a>
@@ -720,8 +720,8 @@
           
 <li>
             The Forrest website also accompanies your software release
-            in the <span class="codefrag ">site-author</span> directory, so
-            inspect its <span class="codefrag ">tabs.xml</span> and <span class="codefrag ">site.xml</span> to see how it is done. Also see the
+            in the <span class="codefrag">site-author</span> directory, so
+            inspect its <span class="codefrag">tabs.xml</span> and <span class="codefrag">site.xml</span> to see how it is done. Also see the
             'forrest seed site' example. It is not as complex as the Forrest website.
           </li>
           
@@ -731,25 +731,25 @@
           
 <li>
             The value of the tab @id attribute cannot begin with a digit.
-            Likewise, element names in <span class="codefrag ">tabs.xml</span> and <span class="codefrag ">site.xml</span> cannot begin with a digit.
+            Likewise, element names in <span class="codefrag">tabs.xml</span> and <span class="codefrag">site.xml</span> cannot begin with a digit.
           </li>
           
 <li>
-            Add label attributes to <span class="codefrag ">site.xml</span> elements to make the menus show.
-            With nested elements in <span class="codefrag ">site.xml</span> if the outer element does not have a label
+            Add label attributes to <span class="codefrag">site.xml</span> elements to make the menus show.
+            With nested elements in <span class="codefrag">site.xml</span> if the outer element does not have a label
             attribute then the inner elements will not be displayed.
           </li>
           
 <li>
             To cause tabs and menu items to be highlighted, there need to be
-            corresponding elements in <span class="codefrag ">site.xml</span> that have href attributes which match
+            corresponding elements in <span class="codefrag">site.xml</span> that have href attributes which match
             the relevant path.
           </li>
           
 <li>
             When the tab points to a directory, then to make the tab highlighted
             when selected, you need an element which matches index.html within the
-            group of elements that define the menus for this tab in the <span class="codefrag ">site.xml</span>
+            group of elements that define the menus for this tab in the <span class="codefrag">site.xml</span>
             file. That element can be without a label attribute, so that it doesn't
             display as a menu item. However doing that causes that tab's menus
             to be collapsed.
@@ -758,7 +758,7 @@
 <li>
             Q: The tab link in my site assumes that 'index.html'
             is present in the linked-to directory. How do I fix this?
-            A: In <span class="codefrag ">tabs.xml</span> use @href instead of @dir attribute and omit the trailing '/'.
+            A: In <span class="codefrag">tabs.xml</span> use @href instead of @dir attribute and omit the trailing '/'.
             Which file to serve is then a concern of the sitemap.
             See more at the <a href="../docs_0_80/faq.html#tab-index">FAQ</a>.
           </li>
@@ -774,35 +774,35 @@
       is created from the titles of each section in your xdoc. By default only
       sections up to two levels deep are included and the table of contents is
       displayed at the top of the page. However, you can configure this
-      behaviour in <span class="codefrag ">src/documentation/skinconf.xml</span> using the 
-      "<span class="codefrag ">toc</span>" element.</p>
+      behaviour in <span class="codefrag">src/documentation/skinconf.xml</span> using the 
+      "<span class="codefrag">toc</span>" element.</p>
 <pre class="code">
 &lt;toc level="2" location="page"/&gt;
       </pre>
 <ul>
         
 <li>
-<strong><span class="codefrag ">level</span></strong> - is the depth to which you
+<strong><span class="codefrag">level</span></strong> - is the depth to which you
         want your table of contents to go. Setting it to "3" will therefore 
         include sections nested to 3 levels. Setting this to "0" will result in
         no table of contents being generated.</li>
         
 <li>
-<strong><span class="codefrag ">location</span></strong> - indicates where you
+<strong><span class="codefrag">location</span></strong> - indicates where you
         want the table of contents to be rendered. It can be set to one of
         three values:
           <ul>
             
 <li>
-<span class="codefrag ">page</span> - the table of contents will be rendered
+<span class="codefrag">page</span> - the table of contents will be rendered
             at the top of the body of your page</li>
             
 <li>
-<span class="codefrag ">menu</span> - the table of contents will be rendered
+<span class="codefrag">menu</span> - the table of contents will be rendered
             in the menu to the left of the body of the page</li>
             
 <li>
-<span class="codefrag ">menu, page</span> - table of contents will be rendered
+<span class="codefrag">menu, page</span> - table of contents will be rendered
             in both the page and the menu positions</li>
           
 </ul>
@@ -820,8 +820,8 @@
 <h3 class="underlined_5">Direct linking</h3>
 <p>
           In earlier versions of Forrest (and in similar systems), there has
-          been only one URI space: that of the generated site.  If <span class="codefrag ">index.xml</span> wants to
-          link to <span class="codefrag ">todo.xml</span> then <span class="codefrag ">index.xml</span> would use
+          been only one URI space: that of the generated site.  If <span class="codefrag">index.xml</span> wants to
+          link to <span class="codefrag">todo.xml</span> then <span class="codefrag">index.xml</span> would use
         </p>
 <pre class="code">
           &lt;a href="todo.html"&gt;to-do list&lt;a&gt;
@@ -852,8 +852,8 @@
           
 <dt>todo</dt>
           
-<dd>identifies the content in <span class="codefrag ">todo.xml</span> by reference to a
-            "node" of content declared in <span class="codefrag ">site.xml</span>
+<dd>identifies the content in <span class="codefrag">todo.xml</span> by reference to a
+            "node" of content declared in <span class="codefrag">site.xml</span>
 </dd>
         
 </dl>
@@ -866,13 +866,13 @@
 <a name="N102AC"></a><a name="resolve-site-uris"></a>
 <h4>Resolving site: URIs</h4>
 <p>
-            So how does "<span class="codefrag ">site:v0.80//todo</span>" get resolved?  A full answer
+            So how does "<span class="codefrag">site:v0.80//todo</span>" get resolved?  A full answer
             is provided in the <a href="#implementation">implementation</a>
-            section.  Essentially, the "<span class="codefrag ">todo</span>" part has
-            "<span class="codefrag ">/site//</span>" prepended, and "<span class="codefrag ">/@href</span>" appended, to
-            form the string "<span class="codefrag ">/site//todo/@href</span>".  This is
-            then used as an XPath expression in <span class="codefrag ">site.xml</span> to identify the string
-            replacement, in this case "<span class="codefrag ">todo.html</span>"
+            section.  Essentially, the "<span class="codefrag">todo</span>" part has
+            "<span class="codefrag">/site//</span>" prepended, and "<span class="codefrag">/@href</span>" appended, to
+            form the string "<span class="codefrag">/site//todo/@href</span>".  This is
+            then used as an XPath expression in <span class="codefrag">site.xml</span> to identify the string
+            replacement, in this case "<span class="codefrag">todo.html</span>"
           </p>
 <p>
             Thus by modifying the XPath prefix and suffix, almost any XML
@@ -882,33 +882,33 @@
 <div class="label">Note</div>
 <div class="content">
             Actually, the XPath is applied to XML generated dynamically from
-            <span class="codefrag ">site.xml</span>.  The generated XML has each "@href" fully expanded ("absolutized")
+            <span class="codefrag">site.xml</span>.  The generated XML has each "@href" fully expanded ("absolutized")
             and dot-dots (..) added as needed ("relativized").
           </div>
 </div>
 <p>
             Notice that the "//" allows us any degree of specificity when linking.
-            In the sample <span class="codefrag ">site.xml</span> above, both "<span class="codefrag ">site:v0.80//new_content_type</span>" and
-            "<span class="codefrag ">site:about/your-project/new_content_type</span>" identify the
+            In the sample <span class="codefrag">site.xml</span> above, both "<span class="codefrag">site:v0.80//new_content_type</span>" and
+            "<span class="codefrag">site:about/your-project/new_content_type</span>" identify the
             same node.  It is up to you to decide how specific to make links.  One
-            nice benefit of link "ambiguity" is that <span class="codefrag ">site.xml</span> can be reorganized
+            nice benefit of link "ambiguity" is that <span class="codefrag">site.xml</span> can be reorganized
             without breaking links.  For example, "new_content_type" currently
             identifies a node in "your-project".  By leaving that fact unspecified
-            in "<span class="codefrag ">site:new_content_type</span>" we are free to make
+            in "<span class="codefrag">site:new_content_type</span>" we are free to make
             "new_content_type" its own XML file, or a node in another file, in
             another category.
           </p>
 <a name="N102EA"></a><a name="resolve-ext-uris"></a>
 <h4>ext: URIs: linking to external URLs</h4>
 <p>
-            The "<span class="codefrag ">ext:</span>" scheme was created partly to demonstrate the
+            The "<span class="codefrag">ext:</span>" scheme was created partly to demonstrate the
             ease with which new schemes can be defined, and partly for practical
-            use. The "<span class="codefrag ">ext:</span>" URIs identify nodes in <span class="codefrag ">site.xml</span> below the
+            use. The "<span class="codefrag">ext:</span>" URIs identify nodes in <span class="codefrag">site.xml</span> below the
             &lt;external-refs&gt; node.  By convention, nodes here link to URLs
             outside the website, and are not listed in the menu generated from
-            the <span class="codefrag ">site.xml</span> file.
+            the <span class="codefrag">site.xml</span> file.
           </p>
-<p>Here is a <span class="codefrag ">site.xml</span> snippet illustrating "<span class="codefrag ">external-refs</span>":</p>
+<p>Here is a <span class="codefrag">site.xml</span> snippet illustrating "<span class="codefrag">external-refs</span>":</p>
 <pre class="code">
 &lt;site&gt;
   ...
@@ -929,30 +929,30 @@
           
 </p>
 <p>
-            The general rules of <span class="codefrag ">site.xml</span> and "<span class="codefrag ">site:</span>" linking apply.
+            The general rules of <span class="codefrag">site.xml</span> and "<span class="codefrag">site:</span>" linking apply.
             Specifically, the "@href" aggregation makes defining large numbers of
             related URLs easy.
           </p>
 <a name="N1031D"></a><a name="source-uris"></a>
 <h4>Theory: source URIs</h4>
 <p>
-            The "<span class="codefrag ">site:</span>" URIs like "<span class="codefrag ">site:v0.80//todo</span>" are examples of
+            The "<span class="codefrag">site:</span>" URIs like "<span class="codefrag">site:v0.80//todo</span>" are examples of
             "<em>source</em>" URIs, in contrast to the more usual
-            <span class="codefrag ">foo.html</span> style URIs, which we here call
+            <span class="codefrag">foo.html</span> style URIs, which we here call
             "<em>destination</em>" URIs.  This introduces an important concept: that
             the "<em>source</em>" URI space exists and is independent of that of the
             generated site.  Furthermore, URIs (i.e. links) are first-class objects,
             on par with XML documents, in that just as XML content is transformed,
             so are the links.  Within the source URI space, we can have all sorts of
             interesting schemes (person: mail: google: java: etc). These will
-            all be translated into plain old "<span class="codefrag ">http:</span>" or relative URIs
+            all be translated into plain old "<span class="codefrag">http:</span>" or relative URIs
             in the destination URI space, just like exotic XML source formats are
             translated into plain old HTML in the output.
           </p>
 <a name="N1033C"></a><a name="future-schemes"></a>
 <h4>Future schemes</h4>
 <p>
-            So far, the "<span class="codefrag ">site:</span>" and "<span class="codefrag ">ext:</span>" schemes are defined.
+            So far, the "<span class="codefrag">site:</span>" and "<span class="codefrag">ext:</span>" schemes are defined.
             To give you some ideas on other things we'd like to implement (and
             wouldd welcome help to implement) here are a few possibilities.
           </p>
@@ -966,10 +966,10 @@
               
 <td colspan="1" rowspan="1">java</td>
               <td colspan="1" rowspan="1">java:org.apache.proj.SomeClass</td>
-              <td colspan="1" rowspan="1"><span class="codefrag ">../../apidocs/org/apache/proj/SomeClass.html</span></td>
+              <td colspan="1" rowspan="1"><span class="codefrag">../../apidocs/org/apache/proj/SomeClass.html</span></td>
               <td colspan="1" rowspan="1">
                 Links to documentation for a Java class (typically generated by
-                <span class="codefrag ">javadoc</span>).
+                <span class="codefrag">javadoc</span>).
               </td>
             
 </tr>
@@ -978,9 +978,9 @@
               
 <td colspan="1" rowspan="1">mail</td>
               <td colspan="1" rowspan="1">mail::&lt;Message-Id&gt;</td>
-              <td colspan="1" rowspan="1"><span class="codefrag ">http://marc.theaimsgroup.com?t=12345678</span></td>
+              <td colspan="1" rowspan="1"><span class="codefrag">http://marc.theaimsgroup.com?t=12345678</span></td>
               <td colspan="1" rowspan="1">
-                Links to an email, identified by its <span class="codefrag ">Message-Id</span>
+                Links to an email, identified by its <span class="codefrag">Message-Id</span>
                 header. Any mail archive website could be used.
               </td>
             
@@ -990,7 +990,7 @@
               
 <td colspan="1" rowspan="1">search</td>
               <td colspan="1" rowspan="1">search:&lt;searchterm&gt;</td>
-              <td colspan="1" rowspan="1"><span class="codefrag ">http://www.google.com/search?q=searchterm</span></td>
+              <td colspan="1" rowspan="1"><span class="codefrag">http://www.google.com/search?q=searchterm</span></td>
               <td colspan="1" rowspan="1">Link to set of results from a search engine</td>
             
 </tr>
@@ -999,10 +999,10 @@
               
 <td colspan="1" rowspan="1">person</td>
               <td colspan="1" rowspan="1">person:JT, person:JT/blog etc</td>
-              <td colspan="1" rowspan="1"><span class="codefrag ">mailto:jefft&lt;at&gt;apache.org</span>,
-                <span class="codefrag ">http://www.webweavertech.com/jefft/weblog/</span></td>
+              <td colspan="1" rowspan="1"><span class="codefrag">mailto:jefft&lt;at&gt;apache.org</span>,
+                <span class="codefrag">http://www.webweavertech.com/jefft/weblog/</span></td>
               <td colspan="1" rowspan="1">
-                A "<span class="codefrag ">person:</span>" scheme could be used, say, to insert an
+                A "<span class="codefrag">person:</span>" scheme could be used, say, to insert an
                 automatically obfuscated email address, or link to a URI in some
                 way associated with that person.
               </td>
@@ -1012,10 +1012,10 @@
 </table>
 <p>
             There are even more possibilities in specific environments.  In an
-            intranet, a "<span class="codefrag ">project:XYZ</span>" scheme could identify company
+            intranet, a "<span class="codefrag">project:XYZ</span>" scheme could identify company
             project pages.  In a project like <a href="http://ant.apache.org/">Apache
               Ant</a>, each Task could be identified with
-            <span class="codefrag ">task:&lt;taskname&gt;</span>, e.g. <span class="codefrag ">task:pathconvert</span>.
+            <span class="codefrag">task:&lt;taskname&gt;</span>, e.g. <span class="codefrag">task:pathconvert</span>.
           </p>
 </div>
     
@@ -1023,13 +1023,13 @@
 <h2 class="underlined_10">Concept</h2>
 <div class="section">
 <p>
-        The "<span class="codefrag ">site:</span>" scheme and associated ideas for <span class="codefrag ">site.xml</span> were
+        The "<span class="codefrag">site:</span>" scheme and associated ideas for <span class="codefrag">site.xml</span> were
         originally described in <a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=103444028129281&w=2">the 'linkmap' RT
           email</a> to the forrest-dev list (RT means 'random thought'; a
         Cocoon invention).   Only section 2 has been implemented, and there is
         still significant work required to implement the full system
         described.  In particular, there is much scope for automating the
-        creation of <span class="codefrag ">site.xml</span> (section 4).  However, what is currently implemented
+        creation of <span class="codefrag">site.xml</span> (section 4).  However, what is currently implemented
         gains most of the advantages of the system.
       </p>
 </div>

Modified: forrest/site/docs_0_80/locationmap.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/locationmap.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_80/locationmap.html (original)
+++ forrest/site/docs_0_80/locationmap.html Sun Dec 18 17:31:25 2005
@@ -351,6 +351,9 @@
 <a href="#source-from-remote-cms">Retrieving HTML from a CMS</a>
 </li>
 <li>
+<a href="#sourceResolving">Source Resolving</a>
+</li>
+<li>
 <a href="#linkrewriting">Link Rewriting</a>
 </li>
 </ul>
@@ -376,7 +379,7 @@
 </ul>
 <p>In other words, the locationmap enables content to be retrieved from a location
         that is defined in a locationmap file (located at 
-        <span class="codefrag ">PROJECT_HOME/src/documentation/content/locationmap.xml</span> file. The
+        <span class="codefrag">PROJECT_HOME/src/documentation/content/locationmap.xml</span> file. The
         advantage of this is that the URL seen by the user need bear no relation to the location
         of the source document, thus Forrest can separate the client URL space from the source
         document URL space. Thus, using the locationmap it is possible to pull together
@@ -388,7 +391,7 @@
       the locationmap however the leaf does not identify a pipeline, but instead identifies
       a location string.</p>
 <p>Apache Forrest looks in the standard location for the source file first (by default
-      <span class="codefrag ">PROJECT_HOME/src/documentation/content/...</span>), if a file is found in this
+      <span class="codefrag">PROJECT_HOME/src/documentation/content/...</span>), if a file is found in this
       location then the locationmap is not consulted. However, if one is not found then the 
       locationmap is used to resolve the source file. The locationmap is resolved via the
       core sitemap, this means that you can generate it dynamically if you so wish. Simply
@@ -470,7 +473,7 @@
 <div class="section">
 <a name="N1008A"></a><a name="source-via-http"></a>
 <h3 class="underlined_5">Retrieving an XDoc via HTTP</h3>
-<p>Normally files are generated from <span class="codefrag ">{project:content.xdocs}</span>.
+<p>Normally files are generated from <span class="codefrag">{project:content.xdocs}</span>.
         Using the Locationmap it is possible to make these files come from elsewhere.
         This is useful if you want to pull files from different directory structures,
         or even remote repositories. For example, the following location match 
@@ -485,12 +488,12 @@
         </pre>
 <p>Note that because this is a wildcard matcher you can request any page
         from the svn server simply by requesting 
-        <span class="codefrag ">/remoteDemo/PATH/TO/FILE/FILENAME.html</span>. In addition, we
+        <span class="codefrag">/remoteDemo/PATH/TO/FILE/FILENAME.html</span>. In addition, we
         can request any other output format available via Forrest plugins.</p>
 <p>When including resources from remote repositories one has to
-        be careful about things like <span class="codefrag ">site</span> and <span class="codefrag ">ext</span>
+        be careful about things like <span class="codefrag">site</span> and <span class="codefrag">ext</span>
         linking. If the targets are not defined in the local 
-        <span class="codefrag ">site.xml</span> file then these links will be broken.</p>
+        <span class="codefrag">site.xml</span> file then these links will be broken.</p>
 <div class="warning">
 <div class="label">Warning</div>
 <div class="content">Because of the above limitation many of the links in the
@@ -506,8 +509,8 @@
         on open standards such as XML and XSLT and the Apache Software Stack, in particular the XML publishing 
         framework Apache Cocoon.</p>
 <p>The following locationmap matcher will instruct Forrest to retrieve content from
-        <span class="codefrag ">http://lenya.zones.apache.org:8888/default/live/*.html?raw=true</span>, whenever a local URL of
-        <span class="codefrag ">lenya/**</span> is encountered.</p>
+        <span class="codefrag">http://lenya.zones.apache.org:8888/default/live/*.html?raw=true</span>, whenever a local URL of
+        <span class="codefrag">lenya/**</span> is encountered.</p>
 <pre class="code">
  &lt;match pattern="lenya/**.xml"&gt;
    &lt;location src="http://lenya.zones.apache.org:8888/default/live/{1}.html?raw=true" /&gt;
@@ -515,7 +518,7 @@
         </pre>
 <p>However, since the source returned by this match is HTML and not XDoc we must convert this
         to our internal XDoc format before we can use it. We do this by adding the match below to our 
-        project's <span class="codefrag ">sitemap.xmap</span> file.</p>
+        project's <span class="codefrag">sitemap.xmap</span> file.</p>
 <pre class="code">
 &lt;map:match pattern="lenya/**.xml"&gt;
   &lt;map:generate type="html" src="{lm:{0}}" /&gt;
@@ -536,7 +539,7 @@
 &lt;/map:components&gt;
         </pre>
 <p>Since the HTML generator uses JTidy we need to make available a JTidy configuration file.
-        This is placed in <span class="codefrag ">PROJECT_HOME/src/documentation/WEB-INF/jtidy.properties</span> (the
+        This is placed in <span class="codefrag">PROJECT_HOME/src/documentation/WEB-INF/jtidy.properties</span> (the
         location can be changed in the above sitemap snippet). A sample config file is given below:</p>
 <pre class="code">
 indent=yes
@@ -566,7 +569,17 @@
 <div class="content">This demo is an example only, it does not fully work at this time. For example, absolute URLs
         in the source document need to be rewritten to ensure that they are matched by the locationmap.</div>
 </div>
-<a name="N100EE"></a><a name="linkrewriting"></a>
+<a name="N100EE"></a><a name="sourceResolving"></a>
+<h3 class="underlined_5">Source Resolving</h3>
+<p>As well as being able to use the locationmap as a parameter in the sitemap,
+        it is also possible to use it as a psuedo-protocol within resources processed
+        by Forrest. For example, you can use it to import an XSL provided by one plugin
+        within another plugin:</p>
+<pre class="code">
+          &lt;xsl:import src="lm://OOo.transform.write.xdoc"/&gt;
+        
+        </pre>
+<a name="N100FC"></a><a name="linkrewriting"></a>
 <h3 class="underlined_5">Link Rewriting</h3>
 <p>The locationmap can be used to rewrite URLs when the page is generated.
         For example, when the locationmap has:</p>
@@ -575,8 +588,8 @@
    &lt;location src="http://www.domain.org/{1}.xml" /&gt;
  &lt;/match&gt;
         </pre>
-<p>With the above match in the locationmap, a link which has <span class="codefrag ">href="lm:rewriteDemo/index"</span>
-        will be rewritten to an offsite address at <span class="codefrag ">domain.org</span>
+<p>With the above match in the locationmap, a link which has <span class="codefrag">href="lm:rewriteDemo/index"</span>
+        will be rewritten to an offsite address at <span class="codefrag">domain.org</span>
 </p>
 </div>
   

Modified: forrest/site/docs_0_80/locationmap.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/locationmap.pdf?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/docs_0_80/primer.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/primer.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_80/primer.html (original)
+++ forrest/site/docs_0_80/primer.html Sun Dec 18 17:31:25 2005
@@ -447,9 +447,9 @@
 <div class="label">Note</div>
 <div class="content">This process is not quite ready for prime time yet, but it gives
         you an idea where we are heading to. Website generation with skins currently
-        works, try using the <span class="codefrag ">docs</span> target when invoking the
-        <span class="codefrag ">build</span> script. Add a <span class="codefrag ">project.skin</span> property when invoking
-        the build script to experience Forrest skins: <span class="codefrag ">build{.bat|.sh}
+        works, try using the <span class="codefrag">docs</span> target when invoking the
+        <span class="codefrag">build</span> script. Add a <span class="codefrag">project.skin</span> property when invoking
+        the build script to experience Forrest skins: <span class="codefrag">build{.bat|.sh}
           -Dproject.skin=&lt;thenameoftheskintouse&gt; docs</span>. Read our
         <a href="#cvs">CVS crash course</a> to get hold of the current codebase and
         start playing with it.</div>
@@ -579,7 +579,7 @@
 <li>Click on Admin-&gt;Preferences;</li> 
           
 <li> In "Enter the CVSROOT:" enter
-            "<span class="codefrag ">:pserver:anoncvs@cvs.apache.org:/home/cvspublic</span>" (without
+            "<span class="codefrag">:pserver:anoncvs@cvs.apache.org:/home/cvspublic</span>" (without
             quotes);</li> 
           
 <li>In "Authentication:" choose "passwd file on the cvs server";</li> 
@@ -588,12 +588,12 @@
           
 <li>Click Admin-&gt;Login;</li> 
           
-<li> When asked for the password: answer "<span class="codefrag ">anoncvs</span>"
+<li> When asked for the password: answer "<span class="codefrag">anoncvs</span>"
             (without quotes);</li> 
           
 <li> Click "Create-&gt;Checkout module";</li> 
           
-<li>Module name and path on the server is "<span class="codefrag ">xml-forrest</span>"
+<li>Module name and path on the server is "<span class="codefrag">xml-forrest</span>"
             (no quotes);</li> 
           
 <li>Choose a dir to put the source code in;</li> 
@@ -603,7 +603,7 @@
 <li>If everything goes well, messages will start to appear in the log
             window;</li> 
           
-<li>Wait until you see "<span class="codefrag ">*****CVS exited normally with code
+<li>Wait until you see "<span class="codefrag">*****CVS exited normally with code
               0*****</span>" in the log window;</li> 
           
 <li>The Forrest source is now on your harddrive.</li> 
@@ -618,15 +618,15 @@
           
 <li>Start the shell of your choice.</li> 
           
-<li>Enter "<span class="codefrag ">cvs -d
+<li>Enter "<span class="codefrag">cvs -d
               :pserver:anoncvs@cvs.apache.org:/home/cvspublic login</span>".</li> 
           
-<li>When asked for the password: answer "<span class="codefrag ">anoncvs</span>".</li> 
+<li>When asked for the password: answer "<span class="codefrag">anoncvs</span>".</li> 
           
-<li>Enter "<span class="codefrag ">cvs -d
+<li>Enter "<span class="codefrag">cvs -d
               :pserver:anoncvs@cvs.apache.org:/home/cvspublic -z3 checkout
               xml-forrest</span>". This will create a directory called
-            "<span class="codefrag ">xml-forrest</span>" where the Forrest source will be stored.</li> 
+            "<span class="codefrag">xml-forrest</span>" where the Forrest source will be stored.</li> 
           
 <li>Wait until cvs has finished.</li> 
           
@@ -634,15 +634,15 @@
         
 </ol>
 <p>In case you want to update your Forrest source tree to the current
-          version, change to the "<span class="codefrag ">xml-forrest</span>" directory and invoke
-          "<span class="codefrag ">cvs -z3 update -d -P</span>".</p>
+          version, change to the "<span class="codefrag">xml-forrest</span>" directory and invoke
+          "<span class="codefrag">cvs -z3 update -d -P</span>".</p>
 </div> 
     
 <a name="N1017F"></a><a name="Forrest+distribution"></a>
 <h2 class="underlined_10">Forrest distribution</h2>
 <div class="section">
 <p>Once you retrieved Forrest from its CVS repository, you will end up
-        with a filesystem hierarchy similar to this inside the <span class="codefrag ">xml-forrest</span>
+        with a filesystem hierarchy similar to this inside the <span class="codefrag">xml-forrest</span>
         home directory:</p>
 <div class="warning">
 <div class="label">Warning</div>
@@ -691,34 +691,34 @@
     +---ant                         Ant 1.6-dev scripts and jars
 +---stylesheets                     Stylesheets used for project root XML files
 </pre>
-<p>The <span class="codefrag ">xml-forrest</span> home directory consists of the main Ant
-        build script (<span class="codefrag ">build.xml</span>) and platform-specific batch files/shell
+<p>The <span class="codefrag">xml-forrest</span> home directory consists of the main Ant
+        build script (<span class="codefrag">build.xml</span>) and platform-specific batch files/shell
         scripts to invoke it. Forrest comes with Ant included, so you do not need to
         install Ant separately.</p>
 <p>Running Forrest is a batch operation you can start using the provided
-        <span class="codefrag ">build.{sh|bat} &lt;targetname&gt;</span>. The current main targets
+        <span class="codefrag">build.{sh|bat} &lt;targetname&gt;</span>. The current main targets
         are:</p>
 <ul> 
         
 <li>
-<strong><span class="codefrag ">docs</span></strong> - generates an HTML rendition of
-          the Forrest website using the default <span class="codefrag ">forrest-site</span> skin</li> 
+<strong><span class="codefrag">docs</span></strong> - generates an HTML rendition of
+          the Forrest website using the default <span class="codefrag">forrest-site</span> skin</li> 
         
 <li>
-<strong><span class="codefrag ">clean</span></strong> - cleans out the
-          <span class="codefrag ">build</span> directory</li> 
+<strong><span class="codefrag">clean</span></strong> - cleans out the
+          <span class="codefrag">build</span> directory</li> 
         
 <li>
-<strong><span class="codefrag ">webapp</span></strong> - for those who cannot resist
+<strong><span class="codefrag">webapp</span></strong> - for those who cannot resist
           running Forrest live instead of its commandline invocation, this target builds
           a WAR file you can deploy in your servlet container (currently only tested for
           Tomcat 4.0.1). Mount-point of the web application will be
-          <span class="codefrag ">xml-forrest</span>.</li> 
+          <span class="codefrag">xml-forrest</span>.</li> 
       
 </ul>
-<p>After a build run, Forrest creates a <span class="codefrag ">build</span> directory. You
-        can find the generated website in the <span class="codefrag ">build/xml-forrest/docs/</span>
-        directory. Forrest also creates a <span class="codefrag ">tools/tmp/anttasks/</span> upon its
+<p>After a build run, Forrest creates a <span class="codefrag">build</span> directory. You
+        can find the generated website in the <span class="codefrag">build/xml-forrest/docs/</span>
+        directory. Forrest also creates a <span class="codefrag">tools/tmp/anttasks/</span> upon its
         first invocation. These are Centipede-specific compiled Ant tasks.</p>
 </div> 
     
@@ -733,30 +733,30 @@
         mechanism, extensive use of external parameter entities and an entity resolver
         capable of resolving entities through the aforementioned catalog mechanism. For
         the docheads amongst us, this means we adhere to the strict use of
-        <span class="codefrag ">PUBLIC</span> entity identifiers both in document instances and DTD
+        <span class="codefrag">PUBLIC</span> entity identifiers both in document instances and DTD
         modules.</p>
 <p>We have currently identified the following document types:</p>
 <ul> 
         
-<li>General documents (<span class="codefrag ">document-v11.dtd</span>),</li> 
+<li>General documents (<span class="codefrag">document-v11.dtd</span>),</li> 
         
-<li>How-Tos (<span class="codefrag ">howto-v10.dtd</span>),</li> 
+<li>How-Tos (<span class="codefrag">howto-v10.dtd</span>),</li> 
         
-<li>Collections of FAQs (<span class="codefrag ">faq-v11.dtd)</span>.</li> 
+<li>Collections of FAQs (<span class="codefrag">faq-v11.dtd)</span>.</li> 
       
 </ul>
 <p>Some work is also under its way for other document types, in close
         collaboration with the Cocoon project. You will also find some older document
-        types such as <span class="codefrag ">changes</span>, <span class="codefrag ">javadoc</span>,
-        <span class="codefrag ">specification</span> and <span class="codefrag ">todo</span>, which are currently under
+        types such as <span class="codefrag">changes</span>, <span class="codefrag">javadoc</span>,
+        <span class="codefrag">specification</span> and <span class="codefrag">todo</span>, which are currently under
         consideration for automatic generation and maintenance using Gump or Centipede
         descriptors and the like. DTDs will be subject of serious version management as
         soon as Forrest has a 1.0 release: they are made to depend upon.</p>
-<p>The DTDs are located in <span class="codefrag ">src/resources/schema/dtd</span> and also
+<p>The DTDs are located in <span class="codefrag">src/resources/schema/dtd</span> and also
         refer to some character entity collections stored in the
-        <span class="codefrag ">src/resources/schema/entity</span> directory. These are referred to by
-        the declarations found in the <span class="codefrag ">src/resources/schema/catalog</span> OASIS
-        Catalog file. Take special care using the correct <span class="codefrag ">PUBLIC</span>
+        <span class="codefrag">src/resources/schema/entity</span> directory. These are referred to by
+        the declarations found in the <span class="codefrag">src/resources/schema/catalog</span> OASIS
+        Catalog file. Take special care using the correct <span class="codefrag">PUBLIC</span>
         identifiers in the DTD declaration of your instances:</p>
 <pre class="code">&lt;?xml version="1.0"?&gt;
 &lt;!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://apache.org/forrest/dtd/document-v12.dtd"&gt;
@@ -765,7 +765,7 @@
   </pre>
 <p>The exact local location of the DTD for validation purposes is
         obtained by the entity resolver evaluating the mapping scheme as defined in the
-        <span class="codefrag ">catalog</span> file. This makes sure that you can move and re-arrange
+        <span class="codefrag">catalog</span> file. This makes sure that you can move and re-arrange
         your document instances apart from your DTD files. Later on, the DTDs will be
         web-accessible from the Forrest website for your perusal.</p>
 </div> 
@@ -773,7 +773,7 @@
 <a name="N1021D"></a><a name="sitemap"></a>
 <h2 class="underlined_10">Forrest site generation using Cocoon</h2>
 <div class="section">
-<p>The <span class="codefrag ">docs</span> target of the Forrest build environment invokes
+<p>The <span class="codefrag">docs</span> target of the Forrest build environment invokes
         Cocoon as a command-line application to generate an HTML rendition of the
         project's documentation. It is not within the scope of this document to explain
         the Cocoon internals, please read its own
@@ -791,7 +791,7 @@
         transformed by a different XSLT stylesheet, aggregated by Cocoon with a
         post-aggregation stylesheet adding the overall page grid and look &amp; feel.
         This simple example is handled by the following <em>sitemap</em> snippets
-        (<span class="codefrag ">src/documentation/conf/sitemap.xmap</span>):</p>
+        (<span class="codefrag">src/documentation/conf/sitemap.xmap</span>):</p>
 <pre class="code">&lt;map:match pattern="*.html"&gt;
   &lt;map:aggregate element="site"&gt;
     &lt;map:part src="cocoon:/book-{1}.xml"/&gt;
@@ -820,63 +820,63 @@
   &lt;map:serialize/&gt;
 &lt;/map:resource&gt;</pre>
 <p>When an URL (e.g.
-        <span class="codefrag ">http://forrest.apache.org/index.html</span>) is passed through the
+        <span class="codefrag">http://forrest.apache.org/index.html</span>) is passed through the
         Cocoon system to generate the required page, the pipeline flow is basically as
         follows:</p>
 <ol> 
         
-<li>The URL is matched by the <span class="codefrag ">*.html</span> pattern</li> 
+<li>The URL is matched by the <span class="codefrag">*.html</span> pattern</li> 
         
 <li>Cocoon responds by aggregating two 'sub-requests'. The first is for
-          the resource <span class="codefrag ">book-{1}.xml</span>, the second is for the resource
-          <span class="codefrag ">body-{1}.xml</span>. The <span class="codefrag ">{1}</span> parameter is replaced by the
+          the resource <span class="codefrag">book-{1}.xml</span>, the second is for the resource
+          <span class="codefrag">body-{1}.xml</span>. The <span class="codefrag">{1}</span> parameter is replaced by the
           values of the first wildcard in the matching pattern above. These
           'sub-requests' are passed through the Cocoon pipeline just like any other
           request. This results in the following flow:</li> 
         
 <ol> 
           
-<li>The first 'sub-request' (for <span class="codefrag ">book-index.xml</span> is matched
-            by the <span class="codefrag ">**book-**.xml</span> pattern. This results in the file
-            <span class="codefrag ">content/xdocs/book.xml</span> being read. This document is then run
-            through the <span class="codefrag ">book2menu</span> stylesheet (which produces an HTML fragment
+<li>The first 'sub-request' (for <span class="codefrag">book-index.xml</span> is matched
+            by the <span class="codefrag">**book-**.xml</span> pattern. This results in the file
+            <span class="codefrag">content/xdocs/book.xml</span> being read. This document is then run
+            through the <span class="codefrag">book2menu</span> stylesheet (which produces an HTML fragment
             comprising the site navigation, the red area in the image above.</li> 
           
-<li>The second 'sub-request' is matched by the <span class="codefrag ">body-**.xml</span>
-            pattern. This results in the file <span class="codefrag ">index.xml</span> being transformed
-            using the <span class="codefrag ">document2html</span> stylesheet, the yellow area in the
+<li>The second 'sub-request' is matched by the <span class="codefrag">body-**.xml</span>
+            pattern. This results in the file <span class="codefrag">index.xml</span> being transformed
+            using the <span class="codefrag">document2html</span> stylesheet, the yellow area in the
             screenshot.</li> 
         
 </ol> 
         
 <li>The aggregation result is then transformed using the
-          <span class="codefrag ">site2xhtml</span> stylesheet which adds the cherries to the cake. The
+          <span class="codefrag">site2xhtml</span> stylesheet which adds the cherries to the cake. The
           grey zone.</li> 
       
 </ol>
 <p>These <em>skin-specific</em> stylesheets are located in
-        <span class="codefrag ">src/documentation/skins/&lt;nameoftheskin&gt;/xslt/html</span>, so if you
+        <span class="codefrag">src/documentation/skins/&lt;nameoftheskin&gt;/xslt/html</span>, so if you
         want to add your own skin, this is the place to be. Apart from these, there
         exist a number of other stylesheets located in
-        <span class="codefrag ">src/documentation/library/xslt</span> and more importantly:</p>
+        <span class="codefrag">src/documentation/library/xslt</span> and more importantly:</p>
 <ul> 
         
 <li>
-<span class="codefrag ">faq2document</span>: transforms documents following the
-          <span class="codefrag ">faq-v11</span> DTD to <span class="codefrag ">document-v11</span> grammar</li> 
+<span class="codefrag">faq2document</span>: transforms documents following the
+          <span class="codefrag">faq-v11</span> DTD to <span class="codefrag">document-v11</span> grammar</li> 
         
 <li>
-<span class="codefrag ">howto2document</span>: transforms documents following the
-          <span class="codefrag ">howto-v10</span> DTD to <span class="codefrag ">document-v11</span> grammar</li> 
+<span class="codefrag">howto2document</span>: transforms documents following the
+          <span class="codefrag">howto-v10</span> DTD to <span class="codefrag">document-v11</span> grammar</li> 
         
 <li>and some others.</li> 
       
 </ul>
 <p>As you see, all documents, regardless of their original DTD, are
-        transformed to the <span class="codefrag ">document</span> DTD prior to rendition. This
+        transformed to the <span class="codefrag">document</span> DTD prior to rendition. This
         alleviates the burden of adding new skins to implementing 3 simple stylesheets:
-        <span class="codefrag ">book2menu</span>, <span class="codefrag ">document2html</span> and
-        <span class="codefrag ">site2xhtml</span>.</p>
+        <span class="codefrag">book2menu</span>, <span class="codefrag">document2html</span> and
+        <span class="codefrag">site2xhtml</span>.</p>
 </div> 
     
 <a name="N102CC"></a><a name="Where+we+are+heading+to"></a>
@@ -919,7 +919,7 @@
           
 <th colspan="1" rowspan="1">Skins</th> 
           <td colspan="1" rowspan="1">We currently have a nice set of skins which should be solidified.
-            Furthermore, we need some serious finetuning of the <span class="codefrag ">forrest-site</span>
+            Furthermore, we need some serious finetuning of the <span class="codefrag">forrest-site</span>
             skin that will become the new xml.apache.org look&amp;feel.</td> 
         
 </tr> 
@@ -940,7 +940,7 @@
           
 <th colspan="1" rowspan="1">Build Management</th> 
           <td colspan="1" rowspan="1">Fool-proof automation of Forrest runs and site publication using
-            secure transfer methods and <span class="codefrag ">cron</span> jobs.</td> 
+            secure transfer methods and <span class="codefrag">cron</span> jobs.</td> 
         
 </tr> 
         

Modified: forrest/site/docs_0_80/project-sitemap.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/project-sitemap.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_80/project-sitemap.html (original)
+++ forrest/site/docs_0_80/project-sitemap.html Sun Dec 18 17:31:25 2005
@@ -375,7 +375,7 @@
 <a name="N10029"></a><a name="how"></a>
 <h2 class="underlined_10">How does it work?</h2>
 <div class="section">
-<p>If a project has a <span class="codefrag ">sitemap.xmap</span> file in it's 
+<p>If a project has a <span class="codefrag">sitemap.xmap</span> file in it's 
       documentation dir, that gets mounted automatically by Forrest and 
       becomes part of the processing: it is a preprocessing step, and 
       is the first one to handle the request. Because of this it can 



Mime
View raw message