Modified: forrest/site/docs_0_80/faq.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/faq.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/faq.html (original)
+++ forrest/site/docs_0_80/faq.html Thu Jan 20 06:47:23 2011
@@ -544,21 +544,21 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10008"></a><a name="getting_started"></a>
+<a name="getting_started"></a>
<h2 class="underlined_10">1. Getting Started and Building Forrest</h2>
<div class="section">
-<a name="N1000C"></a><a name="faq"></a>
+<a name="faq"></a>
<h3 class="underlined_5">1.1. How to use these FAQs? </h3>
<p>
There is no particular order to these FAQs. Use your browser's "Find
in this page" facility to search for keywords.
</p>
-<a name="N10014"></a><a name="overview"></a>
+<a name="overview"></a>
<h3 class="underlined_5">1.2. Where can I read an overview about how to work with Forrest? </h3>
<p>
See the <a href="../docs_0_90/your-project.html">Using Forrest</a> guide.
</p>
-<a name="N10020"></a><a name="docs"></a>
+<a name="docs"></a>
<h3 class="underlined_5">1.3. Where is all of the documentation?</h3>
<p>
You have a local copy of the main documentation with your version of
@@ -576,7 +576,7 @@ document.write("Last Published: " + docu
forrest run'. Every hour the forrestbot generates a static version of
this documentation on our <a href="http://forrest.zones.apache.org/">testing zone</a>.
</p>
-<a name="N10036"></a><a name="requirements"></a>
+<a name="requirements"></a>
<h3 class="underlined_5">1.4. What are the system requirements for Forrest? </h3>
<p>
Forrest includes everything necessary to build and run, except of
@@ -589,13 +589,13 @@ document.write("Last Published: " + docu
intend to enhance and rebuild Forrest (or use the Forrest sources with
Subversion or use a source snapshot) then you need the full JDK.
</p>
-<a name="N10041"></a><a name="cvs"></a>
+<a name="cvs"></a>
<h3 class="underlined_5">1.5. The old xml-forrest CVS code repository seems to be stale. What happened? </h3>
<p>
Forrest switched from a CVS code repository to SVN (Subversion) code
repository. The old CVS repository is closed and not kept current.
</p>
-<a name="N10049"></a><a name="svn"></a>
+<a name="svn"></a>
<h3 class="underlined_5">1.6. How can I use SVN to keep up to date with the latest codebase? </h3>
<p>
Follow these <a href="../docs_0_90/howto/../build.html">Building Forrest</a> notes.
@@ -605,7 +605,7 @@ document.write("Last Published: " + docu
further step-by-step assistance in getting started with Forrest for
your project.
</p>
-<a name="N1005C"></a><a name="older-plugins"></a>
+<a name="older-plugins"></a>
<h3 class="underlined_5">1.7. How to use older versions of specific plugins? </h3>
<p>
Sometimes one does not want to use the most recent functionality of a
@@ -630,7 +630,7 @@ document.write("Last Published: " + docu
(due in version 0.8). So do this ...
</p>
<pre class="code">project.required.plugins=org.apache.forrest.plugin.input.projectInfo-0.1,...</pre>
-<a name="N1007D"></a><a name="single-document"></a>
+<a name="single-document"></a>
<h3 class="underlined_5">1.8. What is the best way to generate "standalone documents" using Forrest? </h3>
<p>
There is a trick that can cut down your turnaround time with building.
@@ -674,7 +674,7 @@ forrest -Dproject.start-uri=live-sites.h
retrieve individual files, e.g. Do 'forrest run' and then 'wget
http://localhost:8888/index.pdf'.
</p>
-<a name="N100A3"></a><a name="cygwin_mutex_error"></a>
+<a name="cygwin_mutex_error"></a>
<h3 class="underlined_5">1.9. When running ./build.sh in cygwin, I get an error: cygpath.exe:
*** can't create title mutex, Win32 error 6. </h3>
<p>
@@ -682,7 +682,7 @@ forrest -Dproject.start-uri=live-sites.h
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=FOR-10">appears
to be a bug in cygwin</a>. Please use the .bat script instead.
</p>
-<a name="N100B5"></a><a name="maxmemory"></a>
+<a name="maxmemory"></a>
<h3 class="underlined_5">1.10. How can I specify the amount of memory to be used by Java? </h3>
<p>
There are two ways to control this. If you get an OutOfMemoryError
@@ -702,7 +702,7 @@ forrest -Dproject.start-uri=live-sites.h
forrest. The exact value you set it to is dependant on your JVM, but
something like <span class="codefrag">ANT_OPTS=-Xmx500M</span> will probably work.
</p>
-<a name="N100D2"></a><a name="debug"></a>
+<a name="debug"></a>
<h3 class="underlined_5">1.11. How can I start forrest in Java debug mode? </h3>
<p>
The <span class="codefrag">forrest.jvmargs</span> property in the
@@ -712,10 +712,10 @@ forrest -Dproject.start-uri=live-sites.h
</p>
</div>
-<a name="N100E3"></a><a name="content_faqs"></a>
+<a name="content_faqs"></a>
<h2 class="underlined_10">2. Content Creation</h2>
<div class="section">
-<a name="N100E7"></a><a name="edit-content"></a>
+<a name="edit-content"></a>
<h3 class="underlined_5">2.1. What tools can be used to edit the content?</h3>
<p>
If you are using the Apache Forrest XML
@@ -737,7 +737,7 @@ forrest -Dproject.start-uri=live-sites.h
can use text editors or "html editors" such as the one provided with
the Mozilla web browser.
</p>
-<a name="N10101"></a><a name="site-xml"></a>
+<a name="site-xml"></a>
<h3 class="underlined_5">2.2.
How to use the site.xml configuration file for menus and linking.
</h3>
@@ -780,7 +780,7 @@ forrest -Dproject.start-uri=live-sites.h
<pre class="code">
<a href="site:docbook"> link to the DocBook FAQ in the Tech FAQs
</pre>
-<a name="N1012F"></a><a name="examples"></a>
+<a name="examples"></a>
<h3 class="underlined_5">2.3.
Where are examples of documents and site.xml and tabs.xml files?
</h3>
@@ -789,7 +789,7 @@ forrest -Dproject.start-uri=live-sites.h
website documents are included with the distribution (<span class="codefrag">cd
forrest/site-author; forrest run</span>).
</p>
-<a name="N1013A"></a><a name="crawler"></a>
+<a name="crawler"></a>
<h3 class="underlined_5">2.4.
Help, one of my documents is not being rendered.
</h3>
@@ -808,7 +808,7 @@ forrest -Dproject.start-uri=live-sites.h
not follow and process off-site links. The new locationmap (0.8+)
enables content to be drawn from remote sources.
</p>
-<a name="N10148"></a><a name="PDF-output"></a>
+<a name="PDF-output"></a>
<h3 class="underlined_5">2.5. How can I generate one pdf-file out of the whole site or selected pages of the site?</h3>
<p>
Add the following entries to your site.xml file.
@@ -846,7 +846,7 @@ forrest -Dproject.start-uri=live-sites.h
(<a href="http://issues.apache.org/jira/browse/FOR-733">FOR-733</a>).
</div>
</div>
-<a name="N1016C"></a><a name="pageBreaks"></a>
+<a name="pageBreaks"></a>
<h3 class="underlined_5">2.6. How do I insert page breaks into documents?</h3>
<p>
Page breaks do not make a great deal of sense in HTML documents
@@ -875,7 +875,7 @@ forrest -Dproject.start-uri=live-sites.h
margin-bottom: 0;
page-break-after: always;
} </pre>
-<a name="N1018A"></a><a name="clickable-email-address"></a>
+<a name="clickable-email-address"></a>
<h3 class="underlined_5">2.7. How can I generate html-pages to show a 'clickable' email-address (of the
author-element)?</h3>
<p>
@@ -883,14 +883,14 @@ forrest -Dproject.start-uri=live-sites.h
$FORREST_HOME/main/webapp/skins/common/xslt/html/document-to-html.xsl</span>
and edit the "headers/authors" template.
</p>
-<a name="N10195"></a><a name="link_raw"></a>
+<a name="link_raw"></a>
<h3 class="underlined_5">2.8. How do I link to raw files such as config.txt and brochure.pdf? </h3>
<p>
Handling of raw files was significantly changed in Forrest 0.7. See
<a href="../docs_0_70/upgrading_07.html#raw">Upgrading to Apache Forrest
0.7</a> for all the details.
</p>
-<a name="N101A1"></a><a name="pdf_images"></a>
+<a name="pdf_images"></a>
<h3 class="underlined_5">2.9. Images don't display in PDFs. How do I fix this?</h3>
<p>
Forrest uses <a href="http://xml.apache.org/fop/">Apache FOP</a>
@@ -929,7 +929,7 @@ forrest -Dproject.start-uri=live-sites.h
Forrest.
</div>
</div>
-<a name="N101D0"></a><a name="tab-index"></a>
+<a name="tab-index"></a>
<h3 class="underlined_5">2.10. The tab link in my site incorrectly assumes that 'index.html' is present in the
linked-to directory. How do I fix this? </h3>
<p>
@@ -952,12 +952,12 @@ forrest -Dproject.start-uri=live-sites.h
<map:redirect-to uri="manual/Introduction.html"/>
</map:match>
</pre>
-<a name="N101EC"></a><a name="tab-site"></a>
+<a name="tab-site"></a>
<h3 class="underlined_5">2.11. I need help with the interaction between tabs.xml and site.xml </h3>
<p>
See the <a href="../docs_0_90/linking.html#tab-site">tips</a>.
</p>
-<a name="N101F8"></a><a name="defaultFileName"></a>
+<a name="defaultFileName"></a>
<h3 class="underlined_5">2.12. How can I change the default file name that Forrest will look for when I request a
URL like http://myserver or http://myserver/mydir/ ? </h3>
<p>
@@ -986,7 +986,7 @@ forrest -Dproject.start-uri=live-sites.h
</li>
</ol>
-<a name="N10220"></a><a name="defaultStartPage"></a>
+<a name="defaultStartPage"></a>
<h3 class="underlined_5">2.13. How can I use a start-up-page other than index.html? </h3>
<p>
Forrest by default assumes that the first page (home page) of your
@@ -1022,7 +1022,7 @@ forrest -Dproject.start-uri=live-sites.h
<li>Don't forget to create that page and refer to it in your site.xml</li>
</ol>
-<a name="N10244"></a><a name="label-entity"></a>
+<a name="label-entity"></a>
<h3 class="underlined_5">2.14. How to use special characters in the labels of the site.xml file? </h3>
<p>
Use the numeric values for character entities. For example, rather
@@ -1040,7 +1040,7 @@ forrest -Dproject.start-uri=live-sites.h
<a href="http://issues.apache.org/jira/browse/FOR-244">Issue
FOR-244</a>.
</p>
-<a name="N1025D"></a><a name="encoding"></a>
+<a name="encoding"></a>
<h3 class="underlined_5">2.15. Does Forrest handle accents for non-English languages?</h3>
<p>
Yes, Forrest can process text in any language, so you can include:
@@ -1114,7 +1114,7 @@ forrest -Dproject.start-uri=live-sites.h
<a href="http://www.alanwood.net/unicode/">Alan Wood's Unicode
resources</a>.
</p>
-<a name="N102AF"></a><a name="xml-entities"></a>
+<a name="xml-entities"></a>
<h3 class="underlined_5">2.16. How to use XML entities, for example string
replacement?</h3>
<p>
@@ -1124,7 +1124,7 @@ forrest -Dproject.start-uri=live-sites.h
trademark symbol "My Project Name™". Avoid lengthy typing and
potential spelling errors.
</p>
-<a name="N102BA"></a><a name="cleanSite"></a>
+<a name="cleanSite"></a>
<h3 class="underlined_5">2.17. How to make Forrest clean up the project build directories? </h3>
<p>
By default Forrest does not clean its build directories in the project
@@ -1138,7 +1138,7 @@ forrest -Dproject.start-uri=live-sites.h
which include the Cocoon cache and the Cocoon logs). Doing 'forrest
clean' will remove both sections.
</p>
-<a name="N102C5"></a><a name="i18n"></a>
+<a name="i18n"></a>
<h3 class="underlined_5">2.18. How can I internationalise (i18n) my content?</h3>
<p>
The i18n features of Forrest are still under development (as of 0.7)
@@ -1154,7 +1154,7 @@ forrest -Dproject.start-uri=live-sites.h
i18n Transformer</a>. You can see an example of how it works in the
above linked issue.
</p>
-<a name="N102D8"></a><a name="rawHTML"></a>
+<a name="rawHTML"></a>
<h3 class="underlined_5">2.19. How can I include HTML content that is not to be skinned by Forrest?</h3>
<p>
To serve, for example a legacy HTML site, add something like the
@@ -1200,7 +1200,7 @@ forrest -Dproject.start-uri=live-sites.h
</li>
</ol>
-<a name="N10304"></a><a name="javascript"></a>
+<a name="javascript"></a>
<h3 class="underlined_5">2.20. How to include additional Javascript and CSS files?</h3>
<p>
Place various resources (e.g. javascript, css) into the "project
@@ -1217,7 +1217,7 @@ forrest -Dproject.start-uri=live-sites.h
forrest/main/webapp/resources.xmap Search for "javascript" then follow
to the <map:resource name="skin-read"> section.
</p>
-<a name="N10312"></a><a name="linkmap"></a>
+<a name="linkmap"></a>
<h3 class="underlined_5">2.21. How to show a Table Of Contents for the whole site?</h3>
<p>
Every site has an automatically generated document at
@@ -1241,10 +1241,10 @@ forrest -Dproject.start-uri=live-sites.h
project.start-uri in the forrest.properties file.
</p>
</div>
-<a name="N10330"></a><a name="technical"></a>
+<a name="technical"></a>
<h2 class="underlined_10">3. Technical</h2>
<div class="section">
-<a name="N10334"></a><a name="java-code"></a>
+<a name="java-code"></a>
<h3 class="underlined_5">3.1. Where is the Java code?</h3>
<p>
Because we are based on Apache Cocoon, a lot of the functionality is
@@ -1263,7 +1263,7 @@ forrest -Dproject.start-uri=live-sites.h
Locationmap and Dispatcher. There is also Java code for some plugins
with specialised purpose, e.g. PhotoGallery.
</p>
-<a name="N10342"></a><a name="populate-cache"></a>
+<a name="populate-cache"></a>
<h3 class="underlined_5">3.2. How to enhance the responsiveness of the cache?</h3>
<p>
Apache Cocoon has a sophisticated cache. When running Forrest in
@@ -1288,7 +1288,7 @@ forrest -Dproject.start-uri=live-sites.h
proxy server, e.g. Apache HTTP Server as a frontend. See
<a href="http://wiki.apache.org/cocoon/ApacheModProxy">CocoonAndApacheModProxy</a>.
</p>
-<a name="N1035C"></a><a name="proxy_config"></a>
+<a name="proxy_config"></a>
<h3 class="underlined_5">3.3. I'm behind a proxy and it's preventing Plugins from being downloaded, what should I
do?</h3>
<p>
@@ -1309,7 +1309,7 @@ forrest -Dproject.start-uri=live-sites.h
<span class="codefrag">${user.home}/forrest.properties</span> !
</div>
</div>
-<a name="N10380"></a><a name="CVS_revison_tags"></a>
+<a name="CVS_revison_tags"></a>
<h3 class="underlined_5">3.4. How can I generate html-pages to show the Revision tag of CVS or SVN?</h3>
<p>
If you have:<span class="codefrag"><version>$Revision: 1.30
@@ -1326,7 +1326,7 @@ forrest -Dproject.start-uri=live-sites.h
When using Subversion, remember to set the relevant svn:keywords
properties.
</p>
-<a name="N10395"></a><a name="cli-xconf"></a>
+<a name="cli-xconf"></a>
<h3 class="underlined_5">3.5. How to control the processing of URIs by Cocoon, e.g. exclude certain URIs, include
other additional ones. </h3>
<p>
@@ -1380,7 +1380,7 @@ forrest -Dproject.start-uri=live-sites.h
that.
</div>
</div>
-<a name="N103D2"></a><a name="ignoring_javadocs"></a>
+<a name="ignoring_javadocs"></a>
<h3 class="underlined_5">3.6. How do I stop Forrest breaking on links to external files that may not exist, like
javadocs? </h3>
<p>
@@ -1388,7 +1388,7 @@ forrest -Dproject.start-uri=live-sites.h
<span class="codefrag">cli.xconf</span> </a> Cocoon config file, and defining
patterns for URLs to exclude.
</p>
-<a name="N103E1"></a><a name="claimed_patterns"></a>
+<a name="claimed_patterns"></a>
<h3 class="underlined_5">3.7. Some of my files are not being processed because they use common filenames. </h3>
<p>
Certain patterns are claimed by the default sitemaps for special
@@ -1402,7 +1402,7 @@ forrest -Dproject.start-uri=live-sites.h
of Forrest we will attempt to deal with this issue
(<a href="http://issues.apache.org/jira/browse/FOR-217">FOR-217</a>).
</p>
-<a name="N103F3"></a><a name="build_msg_a"></a>
+<a name="build_msg_a"></a>
<h3 class="underlined_5">3.8. What do the symbols and numbers mean when Forrest lists each document that it has
built? </h3>
<p>
@@ -1431,7 +1431,7 @@ X [0] /docs_0_80/upgrading_08.ht
<li>Column 5 is the page size.</li>
</ul>
-<a name="N10411"></a><a name="headless_operation"></a>
+<a name="headless_operation"></a>
<h3 class="underlined_5">3.9. When generating PNG images from SVG, I get an error: Can't connect to X11 window
server using ':0.0' as the value of the DISPLAY variable. </h3>
<p>
@@ -1445,7 +1445,7 @@ X [0] /docs_0_80/upgrading_08.ht
<a href="http://cocoon.apache.org/2.1/faq/faq-configure-environment.html">Cocoon
FAQ</a>.
</p>
-<a name="N1042D"></a><a name="project-logo-svg"></a>
+<a name="project-logo-svg"></a>
<h3 class="underlined_5">3.10.
The project logo that is generated from SVG is truncating my project name.
</h3>
@@ -1461,7 +1461,7 @@ X [0] /docs_0_80/upgrading_08.ht
details see <a href="http://www.w3.org/Graphics/SVG/">SVG</a>
resources.
</p>
-<a name="N10445"></a><a name="catalog"></a>
+<a name="catalog"></a>
<h3 class="underlined_5">3.11. How do i configure my favourite XML editor or parser to find the local Forrest
DTDs? </h3>
<p>
@@ -1469,24 +1469,24 @@ X [0] /docs_0_80/upgrading_08.ht
<a href="../docs_0_90/catalog.html">Using Catalog Entity Resolver for local
DTDs</a>.
</p>
-<a name="N10451"></a><a name="project-dtd"></a>
+<a name="project-dtd"></a>
<h3 class="underlined_5">3.12. How to configure the Catalog Entity Resolver to use my own local project DTDs?</h3>
<p>
See <a href="../docs_0_90/your-project.html#new_dtd">Using Forrest</a> for
configuration guidance.
</p>
-<a name="N1045D"></a><a name="local-catalog"></a>
+<a name="local-catalog"></a>
<h3 class="underlined_5">3.13. We need an additional system-wide catalog to share DTDs between projects</h3>
<p>
See <a href="../docs_0_90/validation.html#catalog">Using Forrest</a> for
configuration guidance.
</p>
-<a name="N10469"></a><a name="debug-catalog"></a>
+<a name="debug-catalog"></a>
<h3 class="underlined_5">3.14. How to debug the Catalog Entity Resolver and local DTDs?</h3>
<p>
See <a href="../docs_0_90/validation.html#debug-catalog">XML validation</a>.
</p>
-<a name="N10475"></a><a name="skin"></a>
+<a name="skin"></a>
<h3 class="underlined_5">3.15. How to make the site look better and change its skin? </h3>
<p>
There are <a href="../docs_0_90/your-project.html#skins">default skins</a> provided, which
@@ -1500,7 +1500,7 @@ X [0] /docs_0_80/upgrading_08.ht
skins. Some projects may have special needs and can define their
<a href="../docs_0_90/your-project.html#new_skin">own skin</a>.
</p>
-<a name="N1048C"></a><a name="xsp"></a>
+<a name="xsp"></a>
<h3 class="underlined_5">3.16. How do I enable XSP processing?</h3>
<p>
First consider whether your needs would be better met by Cocoon
@@ -1559,7 +1559,7 @@ X [0] /docs_0_80/upgrading_08.ht
<a href="http://wiki.apache.org/cocoon/AddingXSPToForrest">AddingXSPToForrest</a>
Wiki page.
</p>
-<a name="N104C3"></a><a name="breadcrumbs"></a>
+<a name="breadcrumbs"></a>
<h3 class="underlined_5">3.17. How do breadcrumbs work? Why don't they work locally?</h3>
<p>
Breadcrumbs begin with up to three URLs specified in
@@ -1580,7 +1580,7 @@ X [0] /docs_0_80/upgrading_08.ht
there is no domain and so there will be no extra breadcrumbs, only the
ones that are specified in <span class="codefrag">skinconf.xml</span>.
</p>
-<a name="N104D8"></a><a name="run_port"></a>
+<a name="run_port"></a>
<h3 class="underlined_5">3.18. How do I make forrest run listen on a different port?</h3>
<p>
@@ -1593,7 +1593,7 @@ X [0] /docs_0_80/upgrading_08.ht
do <span class="codefrag">forrest run</span>
</p>
-<a name="N104EC"></a><a name="debugging"></a>
+<a name="debugging"></a>
<h3 class="underlined_5">3.19. Can I run Forrest with Java debugging turned on?</h3>
<p>
If you use an IDE like Eclipse and want to debug java code in Forrest
@@ -1604,7 +1604,7 @@ X [0] /docs_0_80/upgrading_08.ht
<span class="codefrag">forrest.properties</span> file. Don't forget to ensure the
property is uncommented in that file.
</p>
-<a name="N104FD"></a><a name="checksums"></a>
+<a name="checksums"></a>
<h3 class="underlined_5">3.20. How do I enable Cocoon's document checksum feature?</h3>
<p>
Why might you want to do this? There is really no effect on Cocoon
@@ -1633,10 +1633,10 @@ X [0] /docs_0_80/upgrading_08.ht
installation-wide cli.xconf file.
</p>
</div>
-<a name="N10519"></a><a name="old_faqs"></a>
+<a name="old_faqs"></a>
<h2 class="underlined_10">4. Older version: 0.6</h2>
<div class="section">
-<a name="N1051D"></a><a name="old_claimed_patterns"></a>
+<a name="old_claimed_patterns"></a>
<h3 class="underlined_5">4.1. Some of my files are not being processed because they use common filenames. </h3>
<p>
Certain patterns are claimed by the default sitemaps for special
@@ -1651,10 +1651,10 @@ X [0] /docs_0_80/upgrading_08.ht
(<a href="http://issues.apache.org/jira/browse/FOR-217">FOR-217</a>).
</p>
</div>
-<a name="N1052F"></a><a name="general"></a>
+<a name="general"></a>
<h2 class="underlined_10">5. General</h2>
<div class="section">
-<a name="N10533"></a><a name="generating_menus"></a>
+<a name="generating_menus"></a>
<h3 class="underlined_5">5.1. What is the relationship between site.xml and book.xml? </h3>
<p>
One <span class="codefrag">site.xml</span> file in your project root can replace all the book.xml files
@@ -1666,7 +1666,7 @@ X [0] /docs_0_80/upgrading_08.ht
where <span class="codefrag">site.xml</span>-generated menus aren't appropriate. See
<a href="../docs_0_90/linking.html">Menus and Linking</a>.
</p>
-<a name="N1054E"></a><a name="docbook"></a>
+<a name="docbook"></a>
<h3 class="underlined_5">5.2. How do I use DocBook as the XML documentation format? </h3>
<p>
There are two ways. Forrest has a <span class="codefrag">simplifiedDocbook</span>
@@ -1776,7 +1776,7 @@ X [0] /docs_0_80/upgrading_08.ht
<a href="../docs_0_90/your-project.html#new_dtd">Using Forrest</a> for
configuration guidance.
</p>
-<a name="N10587"></a><a name="version"></a>
+<a name="version"></a>
<h3 class="underlined_5">5.3. How to report which version of Forrest is being used and the properties that are
set? </h3>
<p>
@@ -1788,7 +1788,7 @@ X [0] /docs_0_80/upgrading_08.ht
forrest.properties file and watch the build messages. Doing
<span class="codefrag">'forrest -v'</span> will provide verbose build messages.
</p>
-<a name="N1059B"></a><a name="logs"></a>
+<a name="logs"></a>
<h3 class="underlined_5">5.4. Where are the log files to find more infomation about errors? </h3>
<p>
The logfiles are at <span class="codefrag">build/webapp/WEB-INF/logs/</span>
@@ -1810,7 +1810,7 @@ X [0] /docs_0_80/upgrading_08.ht
Doing <span class="codefrag">'forrest -v'</span> will provide verbose build messages to
the standard output.
</p>
-<a name="N105BF"></a><a name="how_can_I_help"></a>
+<a name="how_can_I_help"></a>
<h3 class="underlined_5">5.5. How to help? </h3>
<p>
Join one of the Forrest project <a href="../mail-lists.html">mailing
@@ -1819,7 +1819,7 @@ X [0] /docs_0_80/upgrading_08.ht
newcomers—often, close proximity blinds software developers to
faults that are obvious to everyone else. Don't be shy!
</p>
-<a name="N105CB"></a><a name="patch"></a>
+<a name="patch"></a>
<h3 class="underlined_5">5.6. How to contribute a patch? </h3>
<p>
Please send all contributions via our <a href="../issues.html">issue
@@ -1833,7 +1833,7 @@ X [0] /docs_0_80/upgrading_08.ht
<a href="../issues.html">issue tracker</a> before diving
in.
</p>
-<a name="N105E6"></a><a name="jobs"></a>
+<a name="jobs"></a>
<h3 class="underlined_5">5.7. How can job positions be advertised? </h3>
<p>
Employers can send notices about employment opportunities. There is a
Modified: forrest/site/docs_0_80/glossary.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/glossary.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/glossary.html (original)
+++ forrest/site/docs_0_80/glossary.html Thu Jan 20 06:47:23 2011
@@ -337,20 +337,16 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10008"></a><a name="Introduction"></a>
+<a name="Introduction"></a>
<h2 class="underlined_10">Introduction</h2>
<div class="section">
-<introduction>
-
<p>
This is a glossary of terms and their definitions for the Apache Forrest
project. Some plugins also have a glossary, for example
<a href="http://forrest.apache.org/pluginDocs/dev/org.apache.forrest.plugin.internal.dispatcher/">Dispatcher</a>.
</p>
-
-</introduction>
</div>
-<a name="N10015"></a><a name="a"></a>
+<a name="a"></a>
<h2 class="underlined_10">A</h2>
<div class="section">
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -396,7 +392,7 @@ document.write("Last Published: " + docu
</tr>
</table>
</div>
-<a name="N10055"></a><a name="c"></a>
+<a name="c"></a>
<h2 class="underlined_10">C</h2>
<div class="section">
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -429,7 +425,7 @@ document.write("Last Published: " + docu
</tr>
</table>
</div>
-<a name="N10082"></a><a name="r"></a>
+<a name="r"></a>
<h2 class="underlined_10">R</h2>
<div class="section">
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -446,7 +442,7 @@ document.write("Last Published: " + docu
</tr>
</table>
</div>
-<a name="N1009F"></a><a name="s"></a>
+<a name="s"></a>
<h2 class="underlined_10">S</h2>
<div class="section">
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -499,7 +495,7 @@ document.write("Last Published: " + docu
</tr>
</table>
</div>
-<a name="N100E7"></a><a name="x"></a>
+<a name="x"></a>
<h2 class="underlined_10">X</h2>
<div class="section">
<table class="ForrestTable" cellspacing="1" cellpadding="4">
Modified: forrest/site/docs_0_80/howto/cvs-ssh/howto-cvs-ssh.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/cvs-ssh/howto-cvs-ssh.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/cvs-ssh/howto-cvs-ssh.html (original)
+++ forrest/site/docs_0_80/howto/cvs-ssh/howto-cvs-ssh.html Thu Jan 20 06:47:23 2011
@@ -197,7 +197,7 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10013"></a><a name="Intended-audience"></a>
+<a name="Intended-audience"></a>
<h2 class="underlined_10">Intended audience</h2>
<div class="section">
<p>
@@ -205,7 +205,7 @@ document.write("Last Published: " + docu
to CVS repositories for particular projects.
</p>
</div>
-<a name="N1001B"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
@@ -215,7 +215,7 @@ document.write("Last Published: " + docu
password every time you need access to CVS through SSH.
</p>
</div>
-<a name="N10023"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<ul>
@@ -240,13 +240,13 @@ document.write("Last Published: " + docu
</div>
</div>
</div>
-<a name="N10044"></a><a name="Steps"></a>
+<a name="Steps"></a>
<h2 class="underlined_10">Steps</h2>
<div class="section">
<p>
How to proceed.
</p>
-<a name="N1004C"></a><a name="Terms"></a>
+<a name="Terms"></a>
<h3 class="underlined_5">Terms</h3>
<dl>
@@ -268,7 +268,7 @@ document.write("Last Published: " + docu
<strong>$</strong> represents local, <strong>%</strong> remote machine.
</div>
</div>
-<a name="N10071"></a><a name="Setting+up+domain+users"></a>
+<a name="Setting+up+domain+users"></a>
<h3 class="underlined_5">Setting up domain users</h3>
<div class="note">
<div class="label">Note</div>
@@ -309,7 +309,7 @@ $ exit
$ whoami
userxxx
</pre>
-<a name="N1009C"></a><a name="ssh_access"></a>
+<a name="ssh_access"></a>
<h3 class="underlined_5">Setting up SSH access</h3>
<p>
Start Cygwin/shell, then enter:
@@ -339,7 +339,7 @@ $ ssh-user-config
passphrase retaining.
</div>
</div>
-<a name="N100B3"></a><a name="Setting+up+passphrase+access"></a>
+<a name="Setting+up+passphrase+access"></a>
<h3 class="underlined_5">Setting up passphrase access</h3>
<p>
Perform the following:
@@ -380,7 +380,7 @@ $ ssh userxxx@cvs.apache.org
If now you are logged in to the to the CVS machine without entering the
password then everything's Ok.
</p>
-<a name="N100D7"></a><a name="Getting+the+project+from+CVS"></a>
+<a name="Getting+the+project+from+CVS"></a>
<h3 class="underlined_5">Getting the project from CVS</h3>
<p>
Now you are ready to get a project from CVS using SSH connection.
@@ -392,7 +392,7 @@ $ ssh userxxx@cvs.apache.org
$ export CVS_RSH=/bin/ssh
$ cvs -d :ext:userxxx@cvs.apache.org:/home/cvs co xml-cocoon2
</pre>
-<a name="N100E8"></a><a name="How+to+setup+WinCVS"></a>
+<a name="How+to+setup+WinCVS"></a>
<h3 class="underlined_5">How to setup WinCVS</h3>
<ul>
@@ -423,7 +423,7 @@ $ cvs -d :ext:userxxx@cvs.apache.org:/ho
<li>Click Ok</li>
</ul>
-<a name="N1011B"></a><a name="References"></a>
+<a name="References"></a>
<h3 class="underlined_5">References</h3>
<p>
You can find more on CVS, SSH and WinCVS here:
Modified: forrest/site/docs_0_80/howto/howto-asf-mirror.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-asf-mirror.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-asf-mirror.html (original)
+++ forrest/site/docs_0_80/howto/howto-asf-mirror.html Thu Jan 20 06:47:23 2011
@@ -353,7 +353,7 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10010"></a><a name="Intended-Audience"></a>
+<a name="Intended-Audience"></a>
<h2 class="underlined_10">Intended Audience</h2>
<div class="section">
<ul>
@@ -366,7 +366,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N1001E"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
@@ -380,7 +380,7 @@ document.write("Last Published: " + docu
from anywhere in the site. So we explain how to process additional files.
</p>
</div>
-<a name="N10029"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<ul>
@@ -398,10 +398,10 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10042"></a><a name="Steps"></a>
+<a name="Steps"></a>
<h2 class="underlined_10">Steps</h2>
<div class="section">
-<a name="N10047"></a><a name="cgi"></a>
+<a name="cgi"></a>
<h3 class="underlined_5">Add the mirrors.cgi as a raw file</h3>
<p>
As explained in the mirrors document, there will be a two-line CGI
@@ -415,7 +415,7 @@ document.write("Last Published: " + docu
project's
<a href="http://svn.apache.org/repos/asf/forrest/trunk/site-author/content/mirrors.cgi">mirrors.cgi</a>)
</p>
-<a name="N1005E"></a><a name="html"></a>
+<a name="html"></a>
<h3 class="underlined_5">Add the mirrors.html to xdocs directory</h3>
<p>
This file contains the html content of your mirror page, including the
@@ -433,7 +433,7 @@ document.write("Last Published: " + docu
Note that the special tokens (e.g. [if-any http] [for http]) need to be
encompassed by xml comments.
</p>
-<a name="N10075"></a><a name="menu"></a>
+<a name="menu"></a>
<h3 class="underlined_5">Add a menu entry for Download</h3>
<p>
Add an entry to your site.xml navigation. For example ...
@@ -447,7 +447,7 @@ document.write("Last Published: " + docu
<download_html href="mirrors.html"/><!-- so the page is part of a tab -->
...
</pre>
-<a name="N10083"></a><a name="link"></a>
+<a name="link"></a>
<h3 class="underlined_5">Cause the mirrors.html to be processed as an extra file</h3>
<p>
Forrest gathers the links that are to be crawled, by reading site.xml
@@ -470,7 +470,7 @@ document.write("Last Published: " + docu
<uri type="append" src="mirrors.html"/>
</uris>
</pre>
-<a name="N1009E"></a><a name="forrest"></a>
+<a name="forrest"></a>
<h3 class="underlined_5">Run 'forrest' to build your site</h3>
<p>
That is all that you need to do, Forrest will take care of it from
Modified: forrest/site/docs_0_80/howto/howto-buildPlugin.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-buildPlugin.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-buildPlugin.html (original)
+++ forrest/site/docs_0_80/howto/howto-buildPlugin.html Thu Jan 20 06:47:23 2011
@@ -431,7 +431,7 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10013"></a><a name="Intended-Audience"></a>
+<a name="Intended-Audience"></a>
<h2 class="underlined_10">Intended Audience</h2>
<div class="section">
<p>
@@ -446,7 +446,7 @@ document.write("Last Published: " + docu
</div>
</div>
</div>
-<a name="N1001E"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
@@ -454,7 +454,7 @@ document.write("Last Published: " + docu
configure a Forrest project to use their plugin.
</p>
</div>
-<a name="N10026"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<p>
@@ -475,20 +475,20 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10040"></a><a name="Steps"></a>
+<a name="Steps"></a>
<h2 class="underlined_10">Steps</h2>
<div class="section">
<p>
Here is how to proceed.
</p>
-<a name="N10048"></a><a name="typeOfPlugin"></a>
+<a name="typeOfPlugin"></a>
<h3 class="underlined_5">Type of Plugin</h3>
<p>
There are three types of plugin, each with a clear purpose, you must
first decide which <a href="../../pluginDocs/plugins_0_90/pluginInfrastructure.html">type of
plugin</a> you need to build.
</p>
-<a name="N10056"></a><a name="ant"></a>
+<a name="ant"></a>
<h3 class="underlined_5">Make ant available on the command-line</h3>
<p>
The following instructions rely heavily on
@@ -507,7 +507,7 @@ document.write("Last Published: " + docu
network to get the DTDs on every xml parse. Be aware that Forrest might
be relying on some Ant features in its version.
</p>
-<a name="N1006A"></a><a name="seed"></a>
+<a name="seed"></a>
<h3 class="underlined_5">Seed a New Plugin</h3>
<p>
Regardless of the type of plugin you are building, the directory
@@ -569,7 +569,7 @@ document.write("Last Published: " + docu
more information about the plugin directory structure and configuration
files.
</p>
-<a name="N100A8"></a><a name="edit-template"></a>
+<a name="edit-template"></a>
<h4>Edit the Plugin Template</h4>
<p>
You now have a skeleton plugin project. However, it doesn't do
@@ -579,7 +579,7 @@ document.write("Last Published: " + docu
<p>
Here are some general notes:
</p>
-<a name="N100B4"></a><a name="status"></a>
+<a name="status"></a>
<h5>status.xml</h5>
<p>
This file is used to track changes to the plugin project and to
@@ -593,14 +593,14 @@ document.write("Last Published: " + docu
this file so that it can then be used as a changelog for your
plugin.
</p>
-<a name="N100C4"></a><a name="forrest-properties"></a>
+<a name="forrest-properties"></a>
<h5>forrest.properties</h5>
<p>
This file defines many configuration parameters for Forrest. It does
not need to be customised in most cases. However, see for more
details.
</p>
-<a name="N100CE"></a><a name="skinconf"></a>
+<a name="skinconf"></a>
<h5>src/documentation/skinconf.xml</h5>
<p>
This configures the skin for your plugins documentation. There are
@@ -608,14 +608,14 @@ document.write("Last Published: " + docu
copyright information. The file is heavily commented so probably
best to read through it, changing what you need to.
</p>
-<a name="N100D8"></a><a name="doc"></a>
+<a name="doc"></a>
<h5>Documentation</h5>
<p>
It is also a good idea to start writing the documentation at this
stage. The above process created a very simple plugin documentation
site for you. All you have to do is add the content.
</p>
-<a name="N100E2"></a><a name="hosted"></a>
+<a name="hosted"></a>
<h5>Style notes for plugins hosted at forrest.apache.org</h5>
<p>
After seeding a new plugin, copy the configuration from an existing
@@ -623,7 +623,7 @@ document.write("Last Published: " + docu
src/documentation/skinconf.xml (and edit to suit) and
src/documentation/content/xdocs/images/project-logo.gif
</p>
-<a name="N100EE"></a><a name="edit-sitemap"></a>
+<a name="edit-sitemap"></a>
<h3 class="underlined_5">Edit the Plugin sitemap file(s)</h3>
<p>
The plugin <span class="codefrag">xmap</span> file is a Cocoon sitemap that is mounted at
@@ -653,7 +653,7 @@ document.write("Last Published: " + docu
<a href="../../mail-lists.html#forrest-dev">developer mailing list</a> a very
good resource (check the archives before posting, please).
</p>
-<a name="N1011B"></a><a name="components"></a>
+<a name="components"></a>
<h4>Components, Actions and Resources</h4>
<p>
If your plugin uses any components (i.e. generators, transformers or
@@ -674,7 +674,7 @@ document.write("Last Published: " + docu
<p>
See the examples below for more details.
</p>
-<a name="N10144"></a><a name="resources"></a>
+<a name="resources"></a>
<h3 class="underlined_5">Create the Necessary Resource Files</h3>
<div class="fixme">
<div class="label">Fixme (open)</div>
@@ -682,7 +682,7 @@ document.write("Last Published: " + docu
Discuss the XSL files and other such resources
</div>
</div>
-<a name="N1014E"></a><a name="dtd-catalog"></a>
+<a name="dtd-catalog"></a>
<h4>Entity catalog for DTDs and other resources</h4>
<p>
If the plugin uses non-core DTDs and other entities, then add them to
@@ -691,7 +691,7 @@ document.write("Last Published: " + docu
another plugin (e.g. "listLocations" has a simple example; "glossary"
has a more complex example) and edit it to suit.
</p>
-<a name="N1015C"></a><a name="samples"></a>
+<a name="samples"></a>
<h3 class="underlined_5">Create Samples in the Documentation</h3>
<p>
Plugin documentation should provide (as a minimum) an index page that
@@ -705,7 +705,7 @@ document.write("Last Published: " + docu
Try to provide a sample for all the major functions of your plugin and
document any configuration that is available.
</p>
-<a name="N10172"></a><a name="test"></a>
+<a name="test"></a>
<h3 class="underlined_5">Testing a Plugin</h3>
<p>
Since your documentation for the plugin illustrates all of its
@@ -742,7 +742,7 @@ document.write("Last Published: " + docu
Ensure that your sitemaps are robust and handle matches for files in
sub-directories, as well as those at the root level.
</p>
-<a name="N1019F"></a><a name="Testing+During+Development"></a>
+<a name="Testing+During+Development"></a>
<h4>Testing During Development</h4>
<p>
In the current plugin system plugins are not used from their src
@@ -769,9 +769,9 @@ document.write("Last Published: " + docu
files in the <span class="codefrag">conf</span> directory you will, most likely, have
to restart Forrest to see these changes.
</p>
-<a name="N101B9"></a><a name="release"></a>
+<a name="release"></a>
<h3 class="underlined_5">Releasing a Plugin</h3>
-<a name="N101BF"></a><a name="register"></a>
+<a name="register"></a>
<h4>Register the Plugin with Apache Forrest</h4>
<div class="fixme">
<div class="label">Fixme (rdg)</div>
@@ -779,7 +779,7 @@ document.write("Last Published: " + docu
Describe making a request of Forrest devs for inclusion
</div>
</div>
-<a name="N101CA"></a><a name="deploy"></a>
+<a name="deploy"></a>
<h4>Deploying the Plugin</h4>
<p>
To deploy the plugin so that others can use it, it must be made
@@ -817,7 +817,7 @@ document.write("Last Published: " + docu
cycle, but we feel the peace of mind is worth it.
</div>
</div>
-<a name="N101FC"></a><a name="descriptor"></a>
+<a name="descriptor"></a>
<h4>Managing the plugins descriptors</h4>
<p>
The files plugins/plugins.xml and whiteboard/plugins/plugins.xml are
@@ -876,7 +876,7 @@ document.write("Last Published: " + docu
Start adding changes notes.</li>
</ul>
-<a name="N1023B"></a><a name="experimental"></a>
+<a name="experimental"></a>
<h3 class="underlined_5">Experimental Functionality</h3>
<div class="warning">
<div class="label">Warning</div>
@@ -895,7 +895,7 @@ document.write("Last Published: " + docu
<span class="codefrag">org.apache.forrest.internal.NoteTaking</span> plugin.
</div>
</div>
-<a name="N1024A"></a><a name="Locationmap"></a>
+<a name="Locationmap"></a>
<h4>Locationmap</h4>
<p>
Plugins can use the Forrest locationmap to expose resources to your
@@ -907,7 +907,7 @@ document.write("Last Published: " + docu
<a href="http://issues.apache.org/jira/browse/FOR-200">issue</a> for
the status of locationmap development.
</p>
-<a name="N1025E"></a><a name="Dispatcher"></a>
+<a name="Dispatcher"></a>
<h4>Dispatcher</h4>
<p>
Dispatcher (previous codename Forrest Views) is the collective name
@@ -954,7 +954,7 @@ document.write("Last Published: " + docu
locationmap which is generated when you seed a new plugin, but for now
it must be done manually.
</p>
-<a name="N1027E"></a><a name="Plugin+Properties"></a>
+<a name="Plugin+Properties"></a>
<h4>Plugin Properties</h4>
<p>
Plugins can define properties that each project can over-ride. For
@@ -965,13 +965,13 @@ document.write("Last Published: " + docu
<a href="http://issues.apache.org/jira/browse/FOR-588">issue</a> for
the status of this new configuration system.
</p>
-<a name="N10290"></a><a name="examples"></a>
+<a name="examples"></a>
<h3 class="underlined_5">Examples</h3>
<p>
This section will provide some example plugins to help illustrate the
steps discussed above.
</p>
-<a name="N10299"></a><a name="input"></a>
+<a name="input"></a>
<h4>Input Plugin</h4>
<div class="fixme">
<div class="label">Fixme (RDG)</div>
@@ -979,7 +979,7 @@ document.write("Last Published: " + docu
Discuss OpenOffice.org plugin here
</div>
</div>
-<a name="N102A4"></a><a name="output"></a>
+<a name="output"></a>
<h4>Output Plugin</h4>
<div class="fixme">
<div class="label">Fixme (RDG)</div>
@@ -987,7 +987,7 @@ document.write("Last Published: " + docu
Discuss s5 plugin here
</div>
</div>
-<a name="N102AF"></a><a name="internal"></a>
+<a name="internal"></a>
<h4>Internal Plugin</h4>
<div class="fixme">
<div class="label">Fixme (RDG)</div>
@@ -995,7 +995,7 @@ document.write("Last Published: " + docu
Discuss IMSManifest plugin here
</div>
</div>
-<a name="N102BB"></a><a name="extension"></a>
+<a name="extension"></a>
<h3 class="underlined_5">Further Reading</h3>
<ul>
@@ -1006,7 +1006,7 @@ document.write("Last Published: " + docu
<a href="../../pluginDocs/plugins_0_90/">Plugins Documentation</a> for users</li>
</ul>
-<a name="N102D1"></a><a name="summarise"></a>
+<a name="summarise"></a>
<h3 class="underlined_5">Summarise the Entire Process</h3>
<div class="fixme">
<div class="label">Fixme (open)</div>
Modified: forrest/site/docs_0_80/howto/howto-corner-images.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-corner-images.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-corner-images.html (original)
+++ forrest/site/docs_0_80/howto/howto-corner-images.html Thu Jan 20 06:47:23 2011
@@ -349,7 +349,7 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10010"></a><a name="Intended-Audience"></a>
+<a name="Intended-Audience"></a>
<h2 class="underlined_10">Intended Audience</h2>
<div class="section">
<p>
@@ -361,7 +361,7 @@ document.write("Last Published: " + docu
corner image generation process.
</p>
</div>
-<a name="N1001B"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
@@ -371,7 +371,7 @@ document.write("Last Published: " + docu
for your own skin colors.
</p>
</div>
-<a name="N10027"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<ul>
@@ -385,7 +385,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N1003D"></a><a name="Steps"></a>
+<a name="Steps"></a>
<h2 class="underlined_10">Steps</h2>
<div class="section">
<p>
@@ -394,7 +394,7 @@ document.write("Last Published: " + docu
for these images by modifying the
<span class="codefrag">src/documentation/skinconf.xml</span> of a project.
</p>
-<a name="N10048"></a><a name="css-files"></a>
+<a name="css-files"></a>
<h3 class="underlined_5">Understand how corner images are named (the contract)</h3>
<p>
The corner images are referenced in some .css files of the above-named
@@ -561,7 +561,7 @@ images/{$name}-{$v-orientation}-{$h-orie
directly generating it.
</div>
</div>
-<a name="N10121"></a><a name="skinconfig"></a>
+<a name="skinconfig"></a>
<h3 class="underlined_5">Modifying the skinconf.xml of your project</h3>
<p>
modifying the <span class="codefrag">skinconf.xml</span> of your project (by default you
@@ -623,7 +623,7 @@ images/{$name}-{$v-orientation}-{$h-orie
color (<span class="codefrag">-3tab-selected</span>) are set to red (remember: we defined
<span class="codefrag">#FF0000</span> as the "color" value of <span class="codefrag">tab-selected</span>).
</p>
-<a name="N10178"></a><a name="css_modify"></a>
+<a name="css_modify"></a>
<h3 class="underlined_5">Modifying .css files</h3>
<p>
In addition to the modification of <span class="codefrag">skinconf.xml</span> you can
@@ -658,7 +658,7 @@ images/{$name}-{$v-orientation}-{$h-orie
Horrible, isn't it?
</p>
</div>
-<a name="N101A8"></a><a name="Feedback"></a>
+<a name="Feedback"></a>
<h2 class="underlined_10">Feedback</h2>
<div class="section">
<p>
Modified: forrest/site/docs_0_80/howto/howto-custom-html-source.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-custom-html-source.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-custom-html-source.html (original)
+++ forrest/site/docs_0_80/howto/howto-custom-html-source.html Thu Jan 20 06:47:23 2011
@@ -392,7 +392,7 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10010"></a><a name="Intended-Audience"></a>
+<a name="Intended-Audience"></a>
<h2 class="underlined_10">Intended Audience</h2>
<div class="section">
<p>
@@ -400,7 +400,7 @@ document.write("Last Published: " + docu
everybody who wants to learn more about Forrest's pipelines in general.
</p>
</div>
-<a name="N10018"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
@@ -410,7 +410,7 @@ document.write("Last Published: " + docu
does not suffice.
</p>
</div>
-<a name="N10020"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<p>
@@ -448,7 +448,7 @@ document.write("Last Published: " + docu
</ol>
</div>
-<a name="N10043"></a><a name="Understanding-the-HTML-Pipeline"></a>
+<a name="Understanding-the-HTML-Pipeline"></a>
<h2 class="underlined_10">Understanding the HTML-Pipeline</h2>
<div class="section">
<p>
@@ -457,7 +457,7 @@ document.write("Last Published: " + docu
documents. If you already know how pipelines work, then skip to the
section about <a href="#custom">Customizing the html pipeline</a>.
</p>
-<a name="N1004F"></a><a name="example"></a>
+<a name="example"></a>
<h3 class="underlined_5">Driven by Example</h3>
<p>
The best way to learn about Forrest pipelines is follow the processing
@@ -469,7 +469,7 @@ document.write("Last Published: " + docu
<br>
'http://my.domain.org/mytest/mybad.html'.
</p>
-<a name="N1005E"></a><a name="sitemap"></a>
+<a name="sitemap"></a>
<h3 class="underlined_5">Finding the Sitemap</h3>
<p>
Like all applications based on Apache Cocoon, each request for a given
@@ -498,7 +498,7 @@ map:sitemap
are other sitemaps (which we will see later on), we always start looking
for a matching pattern right here.
</p>
-<a name="N10079"></a><a name="pipelines"></a>
+<a name="pipelines"></a>
<h3 class="underlined_5">Find the Beginning of the Pipelines Section</h3>
<p>
Modular as everything else in Cocoon, Forrest's sitemap starts with a
@@ -522,7 +522,7 @@ map:pipelines
bottom until it encounters a Pipeline that will take care of our
request.
</p>
-<a name="N10090"></a><a name="matches"></a>
+<a name="matches"></a>
<h3 class="underlined_5">Looking for a Match</h3>
<p>
Like all Cocoon applications, Forrest knows which pipeline to use for
@@ -562,7 +562,7 @@ map:pipelines
*.something in Cocoon matches only files in the root directory.
</div>
</div>
-<a name="N100B4"></a><a name="html-pipeline"></a>
+<a name="html-pipeline"></a>
<h3 class="underlined_5">Processing in the '**/*.html' Pipeline</h3>
<p>
Let's take a quick look at this pipeline to understand what's happening
@@ -616,7 +616,7 @@ map:pipelines
comes from. To find out, we have to look at the sources of the
aggregation.
</p>
-<a name="N100D5"></a><a name="protocols"></a>
+<a name="protocols"></a>
<h3 class="underlined_5">Following the Pseudo-Protocols</h3>
<p>
To find out what goes into our aggregation, we'll need to look at the
@@ -680,7 +680,7 @@ map:pipelines
As you can easily tell, we are suddenly calling for a whole new
document. Let's see where that takes us:
</p>
-<a name="N10139"></a><a name="call"></a>
+<a name="call"></a>
<h3 class="underlined_5">Second Call for Content</h3>
<p>
Processing of cocoon-calls is not much different from normal requests by
@@ -699,7 +699,7 @@ map:pipelines
</span> from the beginning of the sitemap to see where we find our next
match.
</p>
-<a name="N10151"></a><a name="match-1"></a>
+<a name="match-1"></a>
<h3 class="underlined_5">First Match for '**body-*.html'</h3>
<p>
Our first match is different to the previous ones because there is a
@@ -721,7 +721,7 @@ map:pipelines
So we have a pipeline, but it doesn't do anything. In this case Forrest
will simply keep looking for the next match further down.
</p>
-<a name="N10167"></a><a name="match-2"></a>
+<a name="match-2"></a>
<h3 class="underlined_5">Second Match for '**body-*.html'</h3>
<p class="instruction">
Continue searching downwards for '**body-*.html' in the sitemap-file.
@@ -784,7 +784,7 @@ map:pipelines
<pre class="code">
<map:generate src="cocoon:/mytests/mybad.xml"/>
</pre>
-<a name="N101CF"></a><a name="match-3"></a>
+<a name="match-3"></a>
<h3 class="underlined_5">Third Call for Content</h3>
<p class="instruction">
So let's scan the main sitemap looking for a match for
@@ -844,7 +844,7 @@ map:pipelines
for the existence of the file with different extensions. '.html' is
third in this list and leads to the processing steps shown below:
</p>
-<a name="N1020A"></a><a name="process-html"></a>
+<a name="process-html"></a>
<h3 class="underlined_5">html-Default Processing</h3>
<p>
The default processing of html-files consists of three processing steps:
@@ -897,7 +897,7 @@ map:pipelines
that name).
</div>
</div>
-<a name="N1023E"></a><a name="body"></a>
+<a name="body"></a>
<h3 class="underlined_5">Returning to the '**body-*.html'-Pipeline</h3>
<p>
On returning into the '**body-*.html'-Pipeline (in sitemap.xmap),
@@ -944,7 +944,7 @@ map:pipelines
that name).
</div>
</div>
-<a name="N10266"></a><a name="aggregate"></a>
+<a name="aggregate"></a>
<h3 class="underlined_5">Returning to the '**/*.html'-Pipeline</h3>
<p>
At the end of this pipeline, processing returns the results into the
@@ -952,13 +952,13 @@ map:pipelines
Pipeline</a>, merges it with other data, skins and serializes for
presentation in the requesting client.
</p>
-<a name="N10274"></a><a name="custom"></a>
+<a name="custom"></a>
<h3 class="underlined_5">Customizing the html pipeline</h3>
<p>
In this last part of this document, we will show how to customize the
HTML-pipeline to add your additional steps to the default processing.
</p>
-<a name="N1027D"></a><a name="when"></a>
+<a name="when"></a>
<h4>When to customize?</h4>
<p>
The html-Pipeline in Forrest is designed to be able to also integrate
@@ -980,7 +980,7 @@ map:pipelines
will see the original page from your legacy website, menu and all,
embedded in your new Forrest site.
</p>
-<a name="N1028D"></a><a name="how"></a>
+<a name="how"></a>
<h4>How to customize?</h4>
<p>
To add your own custom processing for a group of pages, you will
@@ -1000,7 +1000,7 @@ map:pipelines
pipeline'), your pipeline intercepts practically all of Forrest's
standard pipelines.
</p>
-<a name="N1029D"></a><a name="what"></a>
+<a name="what"></a>
<h4>What to intercept?</h4>
<p>
Where to intercept standard processing is really a matter of your
@@ -1018,7 +1018,7 @@ map:pipelines
new pipeline that intercepts **.xml for our pages, copy the steps the
original processor is doing and add a transformation of our own to it.
</p>
-<a name="N102AD"></a><a name="intercept"></a>
+<a name="intercept"></a>
<h4>Intercept pattern</h4>
<p>
Take great care when intercepting very basic pipelines. Instead of
Modified: forrest/site/docs_0_80/howto/howto-editcss.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-editcss.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-editcss.html (original)
+++ forrest/site/docs_0_80/howto/howto-editcss.html Thu Jan 20 06:47:23 2011
@@ -354,7 +354,7 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10010"></a><a name="Intended-Audience"></a>
+<a name="Intended-Audience"></a>
<h2 class="underlined_10">Intended Audience</h2>
<div class="section">
<p>
@@ -362,7 +362,7 @@ document.write("Last Published: " + docu
with changing certain CSS-styles settings to see what happens.
</p>
</div>
-<a name="N10018"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
@@ -377,7 +377,7 @@ document.write("Last Published: " + docu
property will have on the look and feel of your Forrest.
</p>
</div>
-<a name="N10023"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<p>
@@ -426,10 +426,10 @@ document.write("Last Published: " + docu
</ol>
</div>
-<a name="N10049"></a><a name="Steps"></a>
+<a name="Steps"></a>
<h2 class="underlined_10">Steps</h2>
<div class="section">
-<a name="N1004E"></a><a name="openForrest"></a>
+<a name="openForrest"></a>
<h3 class="underlined_5">Open your Forrest</h3>
<p class="instruction">
Start your Firefox Browser and open the Forrest you'd like to work
@@ -438,7 +438,7 @@ document.write("Last Published: " + docu
<p>
The page you have pointed to will show up in Firefox's main window.
</p>
-<a name="N1005C"></a><a name="OpenEditCSS"></a>
+<a name="OpenEditCSS"></a>
<h3 class="underlined_5">Open the EditCSS-Sidebar</h3>
<p class="instruction">
Select View-Sidebar-EditCSS from Firefox's main menu to open the EditCSS
@@ -448,7 +448,7 @@ document.write("Last Published: " + docu
The EditCSS sidebar will show next to the main window and load all the
styles from the main page.
</p>
-<a name="N1006A"></a><a name="changeCSS"></a>
+<a name="changeCSS"></a>
<h3 class="underlined_5">Change any CSS</h3>
<p class="instruction">
Change any style you'd like to experiment with or add new settings and
@@ -466,7 +466,7 @@ document.write("Last Published: " + docu
windows for every character you type.
</div>
</div>
-<a name="N1007B"></a><a name="saveChanges"></a>
+<a name="saveChanges"></a>
<h3 class="underlined_5">How to save changes?</h3>
<p>
Since it takes a few explanations to apply the changes to your Forrest,
@@ -474,7 +474,7 @@ document.write("Last Published: " + docu
extend Forrest-CSS"
</p>
</div>
-<a name="N10085"></a><a name="Feedback-and-further-development-of-this-How-To"></a>
+<a name="Feedback-and-further-development-of-this-How-To"></a>
<h2 class="underlined_10">Feedback and further development of this How-To</h2>
<div class="section">
<p>
Modified: forrest/site/docs_0_80/howto/howto-forrest-from-maven.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-forrest-from-maven.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-forrest-from-maven.html (original)
+++ forrest/site/docs_0_80/howto/howto-forrest-from-maven.html Thu Jan 20 06:47:23 2011
@@ -352,14 +352,14 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10010"></a><a name="Intended-Audience"></a>
+<a name="Intended-Audience"></a>
<h2 class="underlined_10">Intended Audience</h2>
<div class="section">
<p>
Users who want to run Forrest from within Maven.
</p>
</div>
-<a name="N10018"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
@@ -367,7 +367,7 @@ document.write("Last Published: " + docu
using Forrest in lieu of Maven's site plugin.
</p>
</div>
-<a name="N10020"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<ul>
@@ -376,21 +376,21 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N1002F"></a><a name="Steps"></a>
+<a name="Steps"></a>
<h2 class="underlined_10">Steps</h2>
<div class="section">
<p>
The procedure outlined below describes how to add a goal to your project's
maven.xml that will invoke Forrest's <span class="codefrag">site</span> target.
</p>
-<a name="N1003A"></a><a name="set-maven-home"></a>
+<a name="set-maven-home"></a>
<h3 class="underlined_5">Set the FORREST_HOME environment variable</h3>
<p>
Make sure the FORREST_HOME environment variable points to your Forrest
home directory (i.e. the directory that contains
<span class="codefrag">forrest.build.xml</span>) (e.g. C:\opt\apache-forrest-0.7)
</p>
-<a name="N10047"></a><a name="define-ant-environment-prop"></a>
+<a name="define-ant-environment-prop"></a>
<h3 class="underlined_5">Initialize an Ant environment property at the top of
maven.xml</h3>
<p>
@@ -399,7 +399,7 @@ document.write("Last Published: " + docu
<pre class="code">
<property environment="env" />
</pre>
-<a name="N10055"></a><a name="add-forrest-goal-to-maven-xml"></a>
+<a name="add-forrest-goal-to-maven-xml"></a>
<h3 class="underlined_5">Add forrest goal to maven.xml</h3>
<p>
Paste the following goal into your project's maven.xml:
@@ -429,14 +429,14 @@ document.write("Last Published: " + docu
makes use of the copy of Ant 1.6 that is bundled with Forrest, so it's
not even necessary to have Ant 1.6 installed separately.
</p>
-<a name="N10066"></a><a name="Alternative+file"></a>
+<a name="Alternative+file"></a>
<h3 class="underlined_5">Alternative file</h3>
<p>
Under <span class="codefrag">$FORREST_HOME/tools/targets/maven.xml</span>
</p>
</div>
-<a name="N10073"></a><a name="Feedback"></a>
+<a name="Feedback"></a>
<h2 class="underlined_10">Feedback</h2>
<div class="section">
<p>
Modified: forrest/site/docs_0_80/howto/howto-pdf-tab.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-pdf-tab.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-pdf-tab.html (original)
+++ forrest/site/docs_0_80/howto/howto-pdf-tab.html Thu Jan 20 06:47:23 2011
@@ -358,7 +358,7 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10010"></a><a name="Intended-Audience"></a>
+<a name="Intended-Audience"></a>
<h2 class="underlined_10">Intended Audience</h2>
<div class="section">
<p>
@@ -366,7 +366,7 @@ document.write("Last Published: " + docu
of documents.
</p>
</div>
-<a name="N10018"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
@@ -376,7 +376,7 @@ document.write("Last Published: " + docu
certain parts of the site.
</p>
</div>
-<a name="N10020"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<ul>
@@ -386,26 +386,26 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N1002F"></a><a name="Steps"></a>
+<a name="Steps"></a>
<h2 class="underlined_10">Steps</h2>
<div class="section">
<p>
The procedure outlined below will define a project
<span class="codefrag">sitemap.xmap</span> and create a new <span class="codefrag">pdf-tab.xmap</span>.
</p>
-<a name="N1003D"></a><a name="sitemap"></a>
+<a name="sitemap"></a>
<h3 class="underlined_5">Create your project's main sitemap.xmap</h3>
<p>
If you do not have already a sitemap then create a new empty one in your
<span class="codefrag">src/documentation</span> directory (or wherever
${project.sitemap-dir} points to).
</p>
-<a name="N1004A"></a><a name="aggregator"></a>
+<a name="aggregator"></a>
<h3 class="underlined_5">Create another sitemap: pdf-tab.xmap</h3>
<p>
Like before create an empty sitemap and name it pdf-tab.xmap.
</p>
-<a name="N10054"></a><a name="mount"></a>
+<a name="mount"></a>
<h3 class="underlined_5">Edit project sitemap.xmap to mount pdf-tab.xmap</h3>
<p>
Your sitemap should look something like this.
@@ -427,7 +427,7 @@ document.write("Last Published: " + docu
</map:pipelines>
</map:sitemap>
</pre>
-<a name="N10062"></a><a name="edit-aggregator"></a>
+<a name="edit-aggregator"></a>
<h3 class="underlined_5">Edit the file pdf-tab.xmap</h3>
<p>
The <span class="codefrag">
@@ -459,7 +459,7 @@ document.write("Last Published: " + docu
</map:pipelines>
</map:sitemap>
</pre>
-<a name="N10075"></a><a name="edit-site"></a>
+<a name="edit-site"></a>
<h3 class="underlined_5">Edit your site.xml</h3>
<div class="note">
<div class="label">Note</div>
@@ -516,7 +516,7 @@ document.write("Last Published: " + docu
do)!!!
</div>
</div>
-<a name="N100A9"></a><a name="explain"></a>
+<a name="explain"></a>
<h3 class="underlined_5">Explanation of the operation</h3>
<p>
Line 4 of our example
@@ -571,7 +571,7 @@ document.write("Last Published: " + docu
</p>
</div>
-<a name="N100E0"></a><a name="Feedback-and-further-development-of-this-How-To"></a>
+<a name="Feedback-and-further-development-of-this-How-To"></a>
<h2 class="underlined_10">Feedback and further development of this How-To</h2>
<div class="section">
<p>
Modified: forrest/site/docs_0_80/howto/index.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/index.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/index.html (original)
+++ forrest/site/docs_0_80/howto/index.html Thu Jan 20 06:47:23 2011
@@ -329,7 +329,7 @@ document.write("Last Published: " + docu
</div>
</div>
-<a name="N1000D"></a><a name="Forrest+Site+and+Documentation"></a>
+<a name="Forrest+Site+and+Documentation"></a>
<h2 class="underlined_10">Forrest Site and Documentation</h2>
<div class="section">
<ul>
@@ -352,7 +352,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10023"></a><a name="Using+and+developing+with+Forrest"></a>
+<a name="Using+and+developing+with+Forrest"></a>
<h2 class="underlined_10">Using and developing with Forrest</h2>
<div class="section">
<p>
@@ -395,7 +395,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N1004E"></a><a name="Extending+Forrest"></a>
+<a name="Extending+Forrest"></a>
<h2 class="underlined_10">Extending Forrest</h2>
<div class="section">
<ul>
Modified: forrest/site/docs_0_80/howto/multi/howto-multi.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/multi/howto-multi.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/multi/howto-multi.html (original)
+++ forrest/site/docs_0_80/howto/multi/howto-multi.html Thu Jan 20 06:47:23 2011
@@ -346,21 +346,21 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10010"></a><a name="Intended-audience"></a>
+<a name="Intended-audience"></a>
<h2 class="underlined_10">Intended audience</h2>
<div class="section">
<p>
Describe the audience here.
</p>
</div>
-<a name="N10018"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
Explain the purpose of the howto here.
</p>
</div>
-<a name="N10020"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<p>
@@ -384,7 +384,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N1003D"></a><a name="Various-Steps"></a>
+<a name="Various-Steps"></a>
<h2 class="underlined_10">Various Steps</h2>
<div class="section">
<p>
@@ -407,14 +407,14 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10057"></a><a name="Real-World-Extension"></a>
+<a name="Real-World-Extension"></a>
<h2 class="underlined_10">Real World Extension</h2>
<div class="section">
<p>
Briefly describe some relevant extensions that go beyond these basics.
</p>
</div>
-<a name="N1005F"></a><a name="Tips"></a>
+<a name="Tips"></a>
<h2 class="underlined_10">Tips</h2>
<div class="section">
<p>
@@ -429,7 +429,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10070"></a><a name="Related-Resources"></a>
+<a name="Related-Resources"></a>
<h2 class="underlined_10">Related Resources</h2>
<div class="section">
<p>
@@ -443,7 +443,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10082"></a><a name="Feedback"></a>
+<a name="Feedback"></a>
<h2 class="underlined_10">Feedback</h2>
<div class="section">
<p>
Modified: forrest/site/docs_0_80/howto/multi/step1.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/multi/step1.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/multi/step1.html (original)
+++ forrest/site/docs_0_80/howto/multi/step1.html Thu Jan 20 06:47:23 2011
@@ -330,15 +330,15 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N1000D"></a><a name="Step-1:-Do-foo"></a>
+<a name="Step-1:-Do-foo"></a>
<h2 class="underlined_10">Step 1: Do foo</h2>
<div class="section">
-<a name="N10012"></a><a name="First+section+of+this+step"></a>
+<a name="First+section+of+this+step"></a>
<h3 class="underlined_5">First section of this step</h3>
<p>
Description here.
</p>
-<a name="N1001C"></a><a name="Second+section+of+this+step"></a>
+<a name="Second+section+of+this+step"></a>
<h3 class="underlined_5">Second section of this step</h3>
<p>
Description here.
Modified: forrest/site/docs_0_80/howto/multi/step2.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/multi/step2.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/multi/step2.html (original)
+++ forrest/site/docs_0_80/howto/multi/step2.html Thu Jan 20 06:47:23 2011
@@ -330,15 +330,15 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N1000D"></a><a name="Step-2:-Do-foobar"></a>
+<a name="Step-2:-Do-foobar"></a>
<h2 class="underlined_10">Step 2: Do foobar</h2>
<div class="section">
-<a name="N10012"></a><a name="First+section+of+this+step"></a>
+<a name="First+section+of+this+step"></a>
<h3 class="underlined_5">First section of this step</h3>
<p>
Description here.
</p>
-<a name="N1001C"></a><a name="Second+section+of+this+step"></a>
+<a name="Second+section+of+this+step"></a>
<h3 class="underlined_5">Second section of this step</h3>
<p>
Description here.
Modified: forrest/site/docs_0_80/howto/multi/step3.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/multi/step3.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/multi/step3.html (original)
+++ forrest/site/docs_0_80/howto/multi/step3.html Thu Jan 20 06:47:23 2011
@@ -330,15 +330,15 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N1000D"></a><a name="Step-3:-Finish-up"></a>
+<a name="Step-3:-Finish-up"></a>
<h2 class="underlined_10">Step 3: Finish up</h2>
<div class="section">
-<a name="N10012"></a><a name="First+section+of+this+step"></a>
+<a name="First+section+of+this+step"></a>
<h3 class="underlined_5">First section of this step</h3>
<p>
Description here.
</p>
-<a name="N1001C"></a><a name="Second+section+of+this+step"></a>
+<a name="Second+section+of+this+step"></a>
<h3 class="underlined_5">Second section of this step</h3>
<p>
Description here.
Modified: forrest/site/docs_0_80/libre-intro.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/libre-intro.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/libre-intro.html (original)
+++ forrest/site/docs_0_80/libre-intro.html Thu Jan 20 06:47:23 2011
@@ -403,7 +403,7 @@ document.write("Last Published: " + docu
</div>
</div>
-<a name="N10010"></a><a name="Intro"></a>
+<a name="Intro"></a>
<h2 class="underlined_10">Intro</h2>
<div class="section">
<div class="warning">
@@ -445,7 +445,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10029"></a><a name="Using+Libre+now+%280.0+alfa%29"></a>
+<a name="Using+Libre+now+%280.0+alfa%29"></a>
<h2 class="underlined_10">Using Libre now (0.0 alfa)</h2>
<div class="section">
<div class="warning">
@@ -459,7 +459,7 @@ document.write("Last Published: " + docu
this time)
</div>
</div>
-<a name="N10034"></a><a name="Generated+Output"></a>
+<a name="Generated+Output"></a>
<h3 class="underlined_5">Generated Output</h3>
<p>
The XML output that comes out of the generator largely follows this
@@ -507,7 +507,7 @@ document.write("Last Published: " + docu
The number and value (and its meaning) of the attributes on these
elements are specified in the libre.xml file.
</p>
-<a name="N1004E"></a><a name="Contents"></a>
+<a name="Contents"></a>
<h3 class="underlined_5">libre.xml Contents</h3>
<p>
That libre.xml file follows the
@@ -552,7 +552,7 @@ document.write("Last Published: " + docu
regex CDATA #IMPLIED
substitute CDATA #IMPLIED
></pre>
-<a name="N10060"></a><a name="Building+Blocks"></a>
+<a name="Building+Blocks"></a>
<h4>Building Blocks</h4>
<p>
The following elements get the following meaning when interpreted by
@@ -732,12 +732,12 @@ document.write("Last Published: " + docu
</ul>
</ul>
-<a name="N1016C"></a><a name="Important+Side+Effects"></a>
+<a name="Important+Side+Effects"></a>
<h3 class="underlined_5">Important Side Effects</h3>
<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>
+<a name="No+libre.xml"></a>
<h4>No libre.xml</h4>
<p>
When using an <span class="codefrag"><auto> </span>section, the filter will
@@ -745,7 +745,7 @@ document.write("Last Published: " + docu
output. You can however include a manual <span class="codefrag"><entry></span>
to point to the <span class="codefrag">libre.xml</span> file if needed.
</p>
-<a name="N1018B"></a><a name="No+Duplicates"></a>
+<a name="No+Duplicates"></a>
<h4>No Duplicates</h4>
<p>
You can combine multiple <span class="codefrag"><entry></span> and
@@ -756,7 +756,7 @@ document.write("Last Published: " + docu
<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>
+<a name="Example+Constructs"></a>
<h3 class="underlined_5">Example Constructs</h3>
<p>
Adding sorting and filtering to the filesystem with libre becomes a
@@ -768,7 +768,7 @@ document.write("Last Published: " + docu
that sets up the directories to store 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>
+<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 like
@@ -821,7 +821,7 @@ document.write("Last Published: " + docu
directory structures can all benefit from this same
filenaming/sorting strategy.
</p>
-<a name="N101E5"></a><a name="Naming+your+files+or+asking+them+their+name%3F"></a>
+<a name="Naming+your+files+or+asking+them+their+name%3F"></a>
<h4>Naming your files or asking them their name?</h4>
<p>
Given the poor expressiveness of the filesystem, the labels that
@@ -853,7 +853,7 @@ document.write("Last Published: " + docu
</libre></pre>
</div>
-<a name="N101F5"></a><a name="Next+Libre+%280.1%29"></a>
+<a name="Next+Libre+%280.1%29"></a>
<h2 class="underlined_10">Next Libre (0.1)</h2>
<div class="section">
<div class="note">
@@ -864,7 +864,7 @@ document.write("Last Published: " + docu
happens...
</div>
</div>
-<a name="N10202"></a><a name="Itches"></a>
+<a name="Itches"></a>
<h3 class="underlined_5">Itches</h3>
<p>
There is quite a number of fast code patches that can/need to happen
@@ -901,14 +901,14 @@ document.write("Last Published: " + docu
early optimizations :-P</li>
</ul>
-<a name="N1022A"></a><a name="Upcoming+Features"></a>
+<a name="Upcoming+Features"></a>
<h3 class="underlined_5">Upcoming Features</h3>
<p>
More importantly however there is a major set of new features that is
waiting to get in there. It all boils down in fact to having a more
expressive libre.xml file... some of the thoughts:
</p>
-<a name="N10233"></a><a name="Combinations+of+filter+logic"></a>
+<a name="Combinations+of+filter+logic"></a>
<h4>Combinations of filter logic</h4>
<p>
Some itching stuff:
@@ -943,7 +943,7 @@ document.write("Last Published: " + docu
</not>
</filter>
</pre>
-<a name="N10253"></a><a name="Separating+property-retrieval+from+formatting+and%0A++++++++++++testing"></a>
+<a name="Separating+property-retrieval+from+formatting+and%0A++++++++++++testing"></a>
<h4>Separating property-retrieval from formatting and
testing</h4>
<p>
@@ -990,7 +990,7 @@ document.write("Last Published: " + docu
And more logically introduce other tests like <span class="codefrag"><globtest
match="..."></span> or <span class="codefrag"><availabletest></span> or...
</p>
-<a name="N1028C"></a><a name="Replace+the+introspection+with+semantically+richer+named%0A++++++++++++properties+to+read."></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>
@@ -1043,7 +1043,7 @@ document.write("Last Published: " + docu
<p>
The DTD would then list the possible attributeValues.
</p>
-<a name="N102D0"></a><a name="Avalonising"></a>
+<a name="Avalonising"></a>
<h3 class="underlined_5">Avalonising</h3>
<p>
There are a number of perceived opportunities in taking up a stronger
@@ -1066,7 +1066,7 @@ document.write("Last Published: " + docu
HierarchyReader the (avalon) environment he needs.</li>
</ul>
-<a name="N102E6"></a><a name="Unresolved+Discussions"></a>
+<a name="Unresolved+Discussions"></a>
<h3 class="underlined_5">Unresolved Discussions</h3>
<ul>
@@ -1086,7 +1086,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10303"></a><a name="Libre+Design"></a>
+<a name="Libre+Design"></a>
<h2 class="underlined_10">Libre Design</h2>
<div class="section">
<p>
@@ -1128,7 +1128,7 @@ document.write("Last Published: " + docu
<p>
... hope this somewhat clarifies how things have been setup for now.
</p>
-<a name="N1032E"></a><a name="Dependencies"></a>
+<a name="Dependencies"></a>
<h3 class="underlined_5">Dependencies</h3>
<ul>
Modified: forrest/site/docs_0_80/linking.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/linking.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/linking.html (original)
+++ forrest/site/docs_0_80/linking.html Thu Jan 20 06:47:23 2011
@@ -388,7 +388,7 @@ document.write("Last Published: " + docu
</div>
</div>
-<a name="N1000D"></a><a name="intro"></a>
+<a name="intro"></a>
<h2 class="underlined_10">Introduction</h2>
<div class="section">
<p>
@@ -407,7 +407,7 @@ document.write("Last Published: " + docu
</p>
</div>
-<a name="N10025"></a><a name="site"></a>
+<a name="site"></a>
<h2 class="underlined_10">site.xml</h2>
<div class="section">
<p>
@@ -552,7 +552,7 @@ document.write("Last Published: " + docu
</p>
</div>
-<a name="N100B4"></a><a name="menu_generation"></a>
+<a name="menu_generation"></a>
<h2 class="underlined_10">Generating Menus</h2>
<div class="section">
<p>
@@ -595,7 +595,7 @@ document.write("Last Published: " + docu
<span class="codefrag">community/howto/index.html</span>
</p>
-<a name="N100FD"></a><a name="tabs-external"></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
@@ -614,7 +614,7 @@ document.write("Last Published: " + docu
root-relative and obviously specifies a directory (ends in '/'). In
which case /index.html will be added.
</p>
-<a name="N1011D"></a><a name="selecting-entries"></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
@@ -673,14 +673,14 @@ document.write("Last Published: " + docu
"<span class="codefrag">home</span>". Forrest will select <em>all nodes with
tab="home"</em> and put them in the menu.
</p>
-<a name="N10177"></a><a name="other-menu-selection"></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
entries is not the only one, although it is the most flexible. Here we
describe a few alternatives.
</p>
-<a name="N10183"></a><a name="dir-menu-selection"></a>
+<a name="dir-menu-selection"></a>
<h4>Directory-based selection</h4>
<p>
In this scheme, each tab corresponds to a directory within the site.
@@ -707,7 +707,7 @@ document.write("Last Published: " + docu
entries.</li>
</ul>
-<a name="N101B3"></a><a name="book-menu-selection"></a>
+<a name="book-menu-selection"></a>
<h4>Specifying menus with book.xml</h4>
<p>
Historically, menus in Forrest have been generated from a
@@ -719,7 +719,7 @@ document.write("Last Published: " + docu
files. In general, however, we recommend that users avoid
<span class="codefrag">book.xml</span> files.
</p>
-<a name="N101D0"></a><a name="tab-selection"></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
@@ -727,7 +727,7 @@ document.write("Last Published: " + docu
"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="N101E6"></a><a name="tab-site"></a>
+<a name="tab-site"></a>
<h3 class="underlined_5">Configuring the interaction between tabs.xml and site.xml</h3>
<p>
This is a collection of tips to assist with getting your menus and
@@ -797,7 +797,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10239"></a><a name="toc-generation"></a>
+<a name="toc-generation"></a>
<h2 class="underlined_10">Table of Contents Generation</h2>
<div class="section">
<p>
@@ -845,10 +845,10 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N1026D"></a><a name="linking"></a>
+<a name="linking"></a>
<h2 class="underlined_10">Linking systems</h2>
<div class="section">
-<a name="N10273"></a><a name="direct-linking"></a>
+<a name="direct-linking"></a>
<h3 class="underlined_5">Direct linking</h3>
<p>
In earlier versions of Forrest (and in similar systems), there has
@@ -867,7 +867,7 @@ document.write("Last Published: " + docu
typically renders to multiple output formats (HTML and PDF), links in
one of them (here, the PDF) are likely to break.
</p>
-<a name="N10298"></a><a name="indirect-linking"></a>
+<a name="indirect-linking"></a>
<h3 class="underlined_5">Indirect linking</h3>
<p>
Forrest's solution is simple: instead of <a href="todo.html">,
@@ -895,7 +895,7 @@ document.write("Last Published: " + docu
"idea" of "the todo file". It doesn't matter where it physically
lives; that will be sorted out by Forrest.
</p>
-<a name="N102BF"></a><a name="resolve-site-uris"></a>
+<a name="resolve-site-uris"></a>
<h4>Resolving site: URIs</h4>
<p>
So how does "<span class="codefrag">site:todo</span>" get resolved? A full answer is
@@ -931,7 +931,7 @@ document.write("Last Published: " + docu
make "new_content_type" its own XML file, or a node in another file,
in another category.
</p>
-<a name="N102FD"></a><a name="resolve-ext-uris"></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
@@ -970,7 +970,7 @@ document.write("Last Published: " + docu
Specifically, the "@href" aggregation makes defining large numbers
of related URLs easy.
</p>
-<a name="N10330"></a><a name="source-uris"></a>
+<a name="source-uris"></a>
<h4>Theory: source URIs</h4>
<p>
The "<span class="codefrag">site:</span>" URIs like "<span class="codefrag">site:todo</span>" are
@@ -987,7 +987,7 @@ document.write("Last Published: " + docu
just like exotic XML source formats are translated into plain old
HTML in the output.
</p>
-<a name="N1034F"></a><a name="future-schemes"></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
@@ -1068,7 +1068,7 @@ document.write("Last Published: " + docu
</p>
</div>
-<a name="N103FB"></a><a name="concept"></a>
+<a name="concept"></a>
<h2 class="underlined_10">Concept</h2>
<div class="section">
<p>
@@ -1083,7 +1083,7 @@ document.write("Last Published: " + docu
</p>
</div>
-<a name="N10412"></a><a name="implementation"></a>
+<a name="implementation"></a>
<h2 class="underlined_10">Implementation</h2>
<div class="section">
<p>
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/faq.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/faq.html (original)
+++ forrest/site/docs_0_80/faq.html Thu Jan 20 06:47:23 2011
@@ -544,21 +544,21 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10008"></a><a name="getting_started"></a>
+<a name="getting_started"></a>
<h2 class="underlined_10">1. Getting Started and Building Forrest</h2>
<div class="section">
-<a name="N1000C"></a><a name="faq"></a>
+<a name="faq"></a>
<h3 class="underlined_5">1.1. How to use these FAQs? </h3>
<p>
There is no particular order to these FAQs. Use your browser's "Find
in this page" facility to search for keywords.
</p>
-<a name="N10014"></a><a name="overview"></a>
+<a name="overview"></a>
<h3 class="underlined_5">1.2. Where can I read an overview about how to work with Forrest? </h3>
<p>
See the <a href="../docs_0_90/your-project.html">Using Forrest</a> guide.
</p>
-<a name="N10020"></a><a name="docs"></a>
+<a name="docs"></a>
<h3 class="underlined_5">1.3. Where is all of the documentation?</h3>
<p>
You have a local copy of the main documentation with your version of
@@ -576,7 +576,7 @@ document.write("Last Published: " + docu
forrest run'. Every hour the forrestbot generates a static version of
this documentation on our <a href="http://forrest.zones.apache.org/">testing zone</a>.
</p>
-<a name="N10036"></a><a name="requirements"></a>
+<a name="requirements"></a>
<h3 class="underlined_5">1.4. What are the system requirements for Forrest? </h3>
<p>
Forrest includes everything necessary to build and run, except of
@@ -589,13 +589,13 @@ document.write("Last Published: " + docu
intend to enhance and rebuild Forrest (or use the Forrest sources with
Subversion or use a source snapshot) then you need the full JDK.
</p>
-<a name="N10041"></a><a name="cvs"></a>
+<a name="cvs"></a>
<h3 class="underlined_5">1.5. The old xml-forrest CVS code repository seems to be stale. What happened? </h3>
<p>
Forrest switched from a CVS code repository to SVN (Subversion) code
repository. The old CVS repository is closed and not kept current.
</p>
-<a name="N10049"></a><a name="svn"></a>
+<a name="svn"></a>
<h3 class="underlined_5">1.6. How can I use SVN to keep up to date with the latest codebase? </h3>
<p>
Follow these <a href="../docs_0_90/howto/../build.html">Building Forrest</a> notes.
@@ -605,7 +605,7 @@ document.write("Last Published: " + docu
further step-by-step assistance in getting started with Forrest for
your project.
</p>
-<a name="N1005C"></a><a name="older-plugins"></a>
+<a name="older-plugins"></a>
<h3 class="underlined_5">1.7. How to use older versions of specific plugins? </h3>
<p>
Sometimes one does not want to use the most recent functionality of a
@@ -630,7 +630,7 @@ document.write("Last Published: " + docu
(due in version 0.8). So do this ...
</p>
<pre class="code">project.required.plugins=org.apache.forrest.plugin.input.projectInfo-0.1,...</pre>
-<a name="N1007D"></a><a name="single-document"></a>
+<a name="single-document"></a>
<h3 class="underlined_5">1.8. What is the best way to generate "standalone documents" using Forrest? </h3>
<p>
There is a trick that can cut down your turnaround time with building.
@@ -674,7 +674,7 @@ forrest -Dproject.start-uri=live-sites.h
retrieve individual files, e.g. Do 'forrest run' and then 'wget
http://localhost:8888/index.pdf'.
</p>
-<a name="N100A3"></a><a name="cygwin_mutex_error"></a>
+<a name="cygwin_mutex_error"></a>
<h3 class="underlined_5">1.9. When running ./build.sh in cygwin, I get an error: cygpath.exe:
*** can't create title mutex, Win32 error 6. </h3>
<p>
@@ -682,7 +682,7 @@ forrest -Dproject.start-uri=live-sites.h
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=FOR-10">appears
to be a bug in cygwin</a>. Please use the .bat script instead.
</p>
-<a name="N100B5"></a><a name="maxmemory"></a>
+<a name="maxmemory"></a>
<h3 class="underlined_5">1.10. How can I specify the amount of memory to be used by Java? </h3>
<p>
There are two ways to control this. If you get an OutOfMemoryError
@@ -702,7 +702,7 @@ forrest -Dproject.start-uri=live-sites.h
forrest. The exact value you set it to is dependant on your JVM, but
something like <span class="codefrag">ANT_OPTS=-Xmx500M</span> will probably work.
</p>
-<a name="N100D2"></a><a name="debug"></a>
+<a name="debug"></a>
<h3 class="underlined_5">1.11. How can I start forrest in Java debug mode? </h3>
<p>
The <span class="codefrag">forrest.jvmargs</span> property in the
@@ -712,10 +712,10 @@ forrest -Dproject.start-uri=live-sites.h
</p>
</div>
-<a name="N100E3"></a><a name="content_faqs"></a>
+<a name="content_faqs"></a>
<h2 class="underlined_10">2. Content Creation</h2>
<div class="section">
-<a name="N100E7"></a><a name="edit-content"></a>
+<a name="edit-content"></a>
<h3 class="underlined_5">2.1. What tools can be used to edit the content?</h3>
<p>
If you are using the Apache Forrest XML
@@ -737,7 +737,7 @@ forrest -Dproject.start-uri=live-sites.h
can use text editors or "html editors" such as the one provided with
the Mozilla web browser.
</p>
-<a name="N10101"></a><a name="site-xml"></a>
+<a name="site-xml"></a>
<h3 class="underlined_5">2.2.
How to use the site.xml configuration file for menus and linking.
</h3>
@@ -780,7 +780,7 @@ forrest -Dproject.start-uri=live-sites.h
<pre class="code">
<a href="site:docbook"> link to the DocBook FAQ in the Tech FAQs
</pre>
-<a name="N1012F"></a><a name="examples"></a>
+<a name="examples"></a>
<h3 class="underlined_5">2.3.
Where are examples of documents and site.xml and tabs.xml files?
</h3>
@@ -789,7 +789,7 @@ forrest -Dproject.start-uri=live-sites.h
website documents are included with the distribution (<span class="codefrag">cd
forrest/site-author; forrest run</span>).
</p>
-<a name="N1013A"></a><a name="crawler"></a>
+<a name="crawler"></a>
<h3 class="underlined_5">2.4.
Help, one of my documents is not being rendered.
</h3>
@@ -808,7 +808,7 @@ forrest -Dproject.start-uri=live-sites.h
not follow and process off-site links. The new locationmap (0.8+)
enables content to be drawn from remote sources.
</p>
-<a name="N10148"></a><a name="PDF-output"></a>
+<a name="PDF-output"></a>
<h3 class="underlined_5">2.5. How can I generate one pdf-file out of the whole site or selected pages of the site?</h3>
<p>
Add the following entries to your site.xml file.
@@ -846,7 +846,7 @@ forrest -Dproject.start-uri=live-sites.h
(<a href="http://issues.apache.org/jira/browse/FOR-733">FOR-733</a>).
</div>
</div>
-<a name="N1016C"></a><a name="pageBreaks"></a>
+<a name="pageBreaks"></a>
<h3 class="underlined_5">2.6. How do I insert page breaks into documents?</h3>
<p>
Page breaks do not make a great deal of sense in HTML documents
@@ -875,7 +875,7 @@ forrest -Dproject.start-uri=live-sites.h
margin-bottom: 0;
page-break-after: always;
} </pre>
-<a name="N1018A"></a><a name="clickable-email-address"></a>
+<a name="clickable-email-address"></a>
<h3 class="underlined_5">2.7. How can I generate html-pages to show a 'clickable' email-address (of the
author-element)?</h3>
<p>
@@ -883,14 +883,14 @@ forrest -Dproject.start-uri=live-sites.h
$FORREST_HOME/main/webapp/skins/common/xslt/html/document-to-html.xsl</span>
and edit the "headers/authors" template.
</p>
-<a name="N10195"></a><a name="link_raw"></a>
+<a name="link_raw"></a>
<h3 class="underlined_5">2.8. How do I link to raw files such as config.txt and brochure.pdf? </h3>
<p>
Handling of raw files was significantly changed in Forrest 0.7. See
<a href="../docs_0_70/upgrading_07.html#raw">Upgrading to Apache Forrest
0.7</a> for all the details.
</p>
-<a name="N101A1"></a><a name="pdf_images"></a>
+<a name="pdf_images"></a>
<h3 class="underlined_5">2.9. Images don't display in PDFs. How do I fix this?</h3>
<p>
Forrest uses <a href="http://xml.apache.org/fop/">Apache FOP</a>
@@ -929,7 +929,7 @@ forrest -Dproject.start-uri=live-sites.h
Forrest.
</div>
</div>
-<a name="N101D0"></a><a name="tab-index"></a>
+<a name="tab-index"></a>
<h3 class="underlined_5">2.10. The tab link in my site incorrectly assumes that 'index.html' is present in the
linked-to directory. How do I fix this? </h3>
<p>
@@ -952,12 +952,12 @@ forrest -Dproject.start-uri=live-sites.h
<map:redirect-to uri="manual/Introduction.html"/>
</map:match>
</pre>
-<a name="N101EC"></a><a name="tab-site"></a>
+<a name="tab-site"></a>
<h3 class="underlined_5">2.11. I need help with the interaction between tabs.xml and site.xml </h3>
<p>
See the <a href="../docs_0_90/linking.html#tab-site">tips</a>.
</p>
-<a name="N101F8"></a><a name="defaultFileName"></a>
+<a name="defaultFileName"></a>
<h3 class="underlined_5">2.12. How can I change the default file name that Forrest will look for when I request a
URL like http://myserver or http://myserver/mydir/ ? </h3>
<p>
@@ -986,7 +986,7 @@ forrest -Dproject.start-uri=live-sites.h
</li>
</ol>
-<a name="N10220"></a><a name="defaultStartPage"></a>
+<a name="defaultStartPage"></a>
<h3 class="underlined_5">2.13. How can I use a start-up-page other than index.html? </h3>
<p>
Forrest by default assumes that the first page (home page) of your
@@ -1022,7 +1022,7 @@ forrest -Dproject.start-uri=live-sites.h
<li>Don't forget to create that page and refer to it in your site.xml</li>
</ol>
-<a name="N10244"></a><a name="label-entity"></a>
+<a name="label-entity"></a>
<h3 class="underlined_5">2.14. How to use special characters in the labels of the site.xml file? </h3>
<p>
Use the numeric values for character entities. For example, rather
@@ -1040,7 +1040,7 @@ forrest -Dproject.start-uri=live-sites.h
<a href="http://issues.apache.org/jira/browse/FOR-244">Issue
FOR-244</a>.
</p>
-<a name="N1025D"></a><a name="encoding"></a>
+<a name="encoding"></a>
<h3 class="underlined_5">2.15. Does Forrest handle accents for non-English languages?</h3>
<p>
Yes, Forrest can process text in any language, so you can include:
@@ -1114,7 +1114,7 @@ forrest -Dproject.start-uri=live-sites.h
<a href="http://www.alanwood.net/unicode/">Alan Wood's Unicode
resources</a>.
</p>
-<a name="N102AF"></a><a name="xml-entities"></a>
+<a name="xml-entities"></a>
<h3 class="underlined_5">2.16. How to use XML entities, for example string
replacement?</h3>
<p>
@@ -1124,7 +1124,7 @@ forrest -Dproject.start-uri=live-sites.h
trademark symbol "My Project Name™". Avoid lengthy typing and
potential spelling errors.
</p>
-<a name="N102BA"></a><a name="cleanSite"></a>
+<a name="cleanSite"></a>
<h3 class="underlined_5">2.17. How to make Forrest clean up the project build directories? </h3>
<p>
By default Forrest does not clean its build directories in the project
@@ -1138,7 +1138,7 @@ forrest -Dproject.start-uri=live-sites.h
which include the Cocoon cache and the Cocoon logs). Doing 'forrest
clean' will remove both sections.
</p>
-<a name="N102C5"></a><a name="i18n"></a>
+<a name="i18n"></a>
<h3 class="underlined_5">2.18. How can I internationalise (i18n) my content?</h3>
<p>
The i18n features of Forrest are still under development (as of 0.7)
@@ -1154,7 +1154,7 @@ forrest -Dproject.start-uri=live-sites.h
i18n Transformer</a>. You can see an example of how it works in the
above linked issue.
</p>
-<a name="N102D8"></a><a name="rawHTML"></a>
+<a name="rawHTML"></a>
<h3 class="underlined_5">2.19. How can I include HTML content that is not to be skinned by Forrest?</h3>
<p>
To serve, for example a legacy HTML site, add something like the
@@ -1200,7 +1200,7 @@ forrest -Dproject.start-uri=live-sites.h
</li>
</ol>
-<a name="N10304"></a><a name="javascript"></a>
+<a name="javascript"></a>
<h3 class="underlined_5">2.20. How to include additional Javascript and CSS files?</h3>
<p>
Place various resources (e.g. javascript, css) into the "project
@@ -1217,7 +1217,7 @@ forrest -Dproject.start-uri=live-sites.h
forrest/main/webapp/resources.xmap Search for "javascript" then follow
to the <map:resource name="skin-read"> section.
</p>
-<a name="N10312"></a><a name="linkmap"></a>
+<a name="linkmap"></a>
<h3 class="underlined_5">2.21. How to show a Table Of Contents for the whole site?</h3>
<p>
Every site has an automatically generated document at
@@ -1241,10 +1241,10 @@ forrest -Dproject.start-uri=live-sites.h
project.start-uri in the forrest.properties file.
</p>
</div>
-<a name="N10330"></a><a name="technical"></a>
+<a name="technical"></a>
<h2 class="underlined_10">3. Technical</h2>
<div class="section">
-<a name="N10334"></a><a name="java-code"></a>
+<a name="java-code"></a>
<h3 class="underlined_5">3.1. Where is the Java code?</h3>
<p>
Because we are based on Apache Cocoon, a lot of the functionality is
@@ -1263,7 +1263,7 @@ forrest -Dproject.start-uri=live-sites.h
Locationmap and Dispatcher. There is also Java code for some plugins
with specialised purpose, e.g. PhotoGallery.
</p>
-<a name="N10342"></a><a name="populate-cache"></a>
+<a name="populate-cache"></a>
<h3 class="underlined_5">3.2. How to enhance the responsiveness of the cache?</h3>
<p>
Apache Cocoon has a sophisticated cache. When running Forrest in
@@ -1288,7 +1288,7 @@ forrest -Dproject.start-uri=live-sites.h
proxy server, e.g. Apache HTTP Server as a frontend. See
<a href="http://wiki.apache.org/cocoon/ApacheModProxy">CocoonAndApacheModProxy</a>.
</p>
-<a name="N1035C"></a><a name="proxy_config"></a>
+<a name="proxy_config"></a>
<h3 class="underlined_5">3.3. I'm behind a proxy and it's preventing Plugins from being downloaded, what should I
do?</h3>
<p>
@@ -1309,7 +1309,7 @@ forrest -Dproject.start-uri=live-sites.h
<span class="codefrag">${user.home}/forrest.properties</span> !
</div>
</div>
-<a name="N10380"></a><a name="CVS_revison_tags"></a>
+<a name="CVS_revison_tags"></a>
<h3 class="underlined_5">3.4. How can I generate html-pages to show the Revision tag of CVS or SVN?</h3>
<p>
If you have:<span class="codefrag"><version>$Revision: 1.30
@@ -1326,7 +1326,7 @@ forrest -Dproject.start-uri=live-sites.h
When using Subversion, remember to set the relevant svn:keywords
properties.
</p>
-<a name="N10395"></a><a name="cli-xconf"></a>
+<a name="cli-xconf"></a>
<h3 class="underlined_5">3.5. How to control the processing of URIs by Cocoon, e.g. exclude certain URIs, include
other additional ones. </h3>
<p>
@@ -1380,7 +1380,7 @@ forrest -Dproject.start-uri=live-sites.h
that.
</div>
</div>
-<a name="N103D2"></a><a name="ignoring_javadocs"></a>
+<a name="ignoring_javadocs"></a>
<h3 class="underlined_5">3.6. How do I stop Forrest breaking on links to external files that may not exist, like
javadocs? </h3>
<p>
@@ -1388,7 +1388,7 @@ forrest -Dproject.start-uri=live-sites.h
<span class="codefrag">cli.xconf</span> </a> Cocoon config file, and defining
patterns for URLs to exclude.
</p>
-<a name="N103E1"></a><a name="claimed_patterns"></a>
+<a name="claimed_patterns"></a>
<h3 class="underlined_5">3.7. Some of my files are not being processed because they use common filenames. </h3>
<p>
Certain patterns are claimed by the default sitemaps for special
@@ -1402,7 +1402,7 @@ forrest -Dproject.start-uri=live-sites.h
of Forrest we will attempt to deal with this issue
(<a href="http://issues.apache.org/jira/browse/FOR-217">FOR-217</a>).
</p>
-<a name="N103F3"></a><a name="build_msg_a"></a>
+<a name="build_msg_a"></a>
<h3 class="underlined_5">3.8. What do the symbols and numbers mean when Forrest lists each document that it has
built? </h3>
<p>
@@ -1431,7 +1431,7 @@ X [0] /docs_0_80/upgrading_08.ht
<li>Column 5 is the page size.</li>
</ul>
-<a name="N10411"></a><a name="headless_operation"></a>
+<a name="headless_operation"></a>
<h3 class="underlined_5">3.9. When generating PNG images from SVG, I get an error: Can't connect to X11 window
server using ':0.0' as the value of the DISPLAY variable. </h3>
<p>
@@ -1445,7 +1445,7 @@ X [0] /docs_0_80/upgrading_08.ht
<a href="http://cocoon.apache.org/2.1/faq/faq-configure-environment.html">Cocoon
FAQ</a>.
</p>
-<a name="N1042D"></a><a name="project-logo-svg"></a>
+<a name="project-logo-svg"></a>
<h3 class="underlined_5">3.10.
The project logo that is generated from SVG is truncating my project name.
</h3>
@@ -1461,7 +1461,7 @@ X [0] /docs_0_80/upgrading_08.ht
details see <a href="http://www.w3.org/Graphics/SVG/">SVG</a>
resources.
</p>
-<a name="N10445"></a><a name="catalog"></a>
+<a name="catalog"></a>
<h3 class="underlined_5">3.11. How do i configure my favourite XML editor or parser to find the local Forrest
DTDs? </h3>
<p>
@@ -1469,24 +1469,24 @@ X [0] /docs_0_80/upgrading_08.ht
<a href="../docs_0_90/catalog.html">Using Catalog Entity Resolver for local
DTDs</a>.
</p>
-<a name="N10451"></a><a name="project-dtd"></a>
+<a name="project-dtd"></a>
<h3 class="underlined_5">3.12. How to configure the Catalog Entity Resolver to use my own local project DTDs?</h3>
<p>
See <a href="../docs_0_90/your-project.html#new_dtd">Using Forrest</a> for
configuration guidance.
</p>
-<a name="N1045D"></a><a name="local-catalog"></a>
+<a name="local-catalog"></a>
<h3 class="underlined_5">3.13. We need an additional system-wide catalog to share DTDs between projects</h3>
<p>
See <a href="../docs_0_90/validation.html#catalog">Using Forrest</a> for
configuration guidance.
</p>
-<a name="N10469"></a><a name="debug-catalog"></a>
+<a name="debug-catalog"></a>
<h3 class="underlined_5">3.14. How to debug the Catalog Entity Resolver and local DTDs?</h3>
<p>
See <a href="../docs_0_90/validation.html#debug-catalog">XML validation</a>.
</p>
-<a name="N10475"></a><a name="skin"></a>
+<a name="skin"></a>
<h3 class="underlined_5">3.15. How to make the site look better and change its skin? </h3>
<p>
There are <a href="../docs_0_90/your-project.html#skins">default skins</a> provided, which
@@ -1500,7 +1500,7 @@ X [0] /docs_0_80/upgrading_08.ht
skins. Some projects may have special needs and can define their
<a href="../docs_0_90/your-project.html#new_skin">own skin</a>.
</p>
-<a name="N1048C"></a><a name="xsp"></a>
+<a name="xsp"></a>
<h3 class="underlined_5">3.16. How do I enable XSP processing?</h3>
<p>
First consider whether your needs would be better met by Cocoon
@@ -1559,7 +1559,7 @@ X [0] /docs_0_80/upgrading_08.ht
<a href="http://wiki.apache.org/cocoon/AddingXSPToForrest">AddingXSPToForrest</a>
Wiki page.
</p>
-<a name="N104C3"></a><a name="breadcrumbs"></a>
+<a name="breadcrumbs"></a>
<h3 class="underlined_5">3.17. How do breadcrumbs work? Why don't they work locally?</h3>
<p>
Breadcrumbs begin with up to three URLs specified in
@@ -1580,7 +1580,7 @@ X [0] /docs_0_80/upgrading_08.ht
there is no domain and so there will be no extra breadcrumbs, only the
ones that are specified in <span class="codefrag">skinconf.xml</span>.
</p>
-<a name="N104D8"></a><a name="run_port"></a>
+<a name="run_port"></a>
<h3 class="underlined_5">3.18. How do I make forrest run listen on a different port?</h3>
<p>
@@ -1593,7 +1593,7 @@ X [0] /docs_0_80/upgrading_08.ht
do <span class="codefrag">forrest run</span>
</p>
-<a name="N104EC"></a><a name="debugging"></a>
+<a name="debugging"></a>
<h3 class="underlined_5">3.19. Can I run Forrest with Java debugging turned on?</h3>
<p>
If you use an IDE like Eclipse and want to debug java code in Forrest
@@ -1604,7 +1604,7 @@ X [0] /docs_0_80/upgrading_08.ht
<span class="codefrag">forrest.properties</span> file. Don't forget to ensure the
property is uncommented in that file.
</p>
-<a name="N104FD"></a><a name="checksums"></a>
+<a name="checksums"></a>
<h3 class="underlined_5">3.20. How do I enable Cocoon's document checksum feature?</h3>
<p>
Why might you want to do this? There is really no effect on Cocoon
@@ -1633,10 +1633,10 @@ X [0] /docs_0_80/upgrading_08.ht
installation-wide cli.xconf file.
</p>
</div>
-<a name="N10519"></a><a name="old_faqs"></a>
+<a name="old_faqs"></a>
<h2 class="underlined_10">4. Older version: 0.6</h2>
<div class="section">
-<a name="N1051D"></a><a name="old_claimed_patterns"></a>
+<a name="old_claimed_patterns"></a>
<h3 class="underlined_5">4.1. Some of my files are not being processed because they use common filenames. </h3>
<p>
Certain patterns are claimed by the default sitemaps for special
@@ -1651,10 +1651,10 @@ X [0] /docs_0_80/upgrading_08.ht
(<a href="http://issues.apache.org/jira/browse/FOR-217">FOR-217</a>).
</p>
</div>
-<a name="N1052F"></a><a name="general"></a>
+<a name="general"></a>
<h2 class="underlined_10">5. General</h2>
<div class="section">
-<a name="N10533"></a><a name="generating_menus"></a>
+<a name="generating_menus"></a>
<h3 class="underlined_5">5.1. What is the relationship between site.xml and book.xml? </h3>
<p>
One <span class="codefrag">site.xml</span> file in your project root can replace all the book.xml files
@@ -1666,7 +1666,7 @@ X [0] /docs_0_80/upgrading_08.ht
where <span class="codefrag">site.xml</span>-generated menus aren't appropriate. See
<a href="../docs_0_90/linking.html">Menus and Linking</a>.
</p>
-<a name="N1054E"></a><a name="docbook"></a>
+<a name="docbook"></a>
<h3 class="underlined_5">5.2. How do I use DocBook as the XML documentation format? </h3>
<p>
There are two ways. Forrest has a <span class="codefrag">simplifiedDocbook</span>
@@ -1776,7 +1776,7 @@ X [0] /docs_0_80/upgrading_08.ht
<a href="../docs_0_90/your-project.html#new_dtd">Using Forrest</a> for
configuration guidance.
</p>
-<a name="N10587"></a><a name="version"></a>
+<a name="version"></a>
<h3 class="underlined_5">5.3. How to report which version of Forrest is being used and the properties that are
set? </h3>
<p>
@@ -1788,7 +1788,7 @@ X [0] /docs_0_80/upgrading_08.ht
forrest.properties file and watch the build messages. Doing
<span class="codefrag">'forrest -v'</span> will provide verbose build messages.
</p>
-<a name="N1059B"></a><a name="logs"></a>
+<a name="logs"></a>
<h3 class="underlined_5">5.4. Where are the log files to find more infomation about errors? </h3>
<p>
The logfiles are at <span class="codefrag">build/webapp/WEB-INF/logs/</span>
@@ -1810,7 +1810,7 @@ X [0] /docs_0_80/upgrading_08.ht
Doing <span class="codefrag">'forrest -v'</span> will provide verbose build messages to
the standard output.
</p>
-<a name="N105BF"></a><a name="how_can_I_help"></a>
+<a name="how_can_I_help"></a>
<h3 class="underlined_5">5.5. How to help? </h3>
<p>
Join one of the Forrest project <a href="../mail-lists.html">mailing
@@ -1819,7 +1819,7 @@ X [0] /docs_0_80/upgrading_08.ht
newcomers—often, close proximity blinds software developers to
faults that are obvious to everyone else. Don't be shy!
</p>
-<a name="N105CB"></a><a name="patch"></a>
+<a name="patch"></a>
<h3 class="underlined_5">5.6. How to contribute a patch? </h3>
<p>
Please send all contributions via our <a href="../issues.html">issue
@@ -1833,7 +1833,7 @@ X [0] /docs_0_80/upgrading_08.ht
<a href="../issues.html">issue tracker</a> before diving
in.
</p>
-<a name="N105E6"></a><a name="jobs"></a>
+<a name="jobs"></a>
<h3 class="underlined_5">5.7. How can job positions be advertised? </h3>
<p>
Employers can send notices about employment opportunities. There is a
Modified: forrest/site/docs_0_80/glossary.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/glossary.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/glossary.html (original)
+++ forrest/site/docs_0_80/glossary.html Thu Jan 20 06:47:23 2011
@@ -337,20 +337,16 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10008"></a><a name="Introduction"></a>
+<a name="Introduction"></a>
<h2 class="underlined_10">Introduction</h2>
<div class="section">
-<introduction>
-
<p>
This is a glossary of terms and their definitions for the Apache Forrest
project. Some plugins also have a glossary, for example
<a href="http://forrest.apache.org/pluginDocs/dev/org.apache.forrest.plugin.internal.dispatcher/">Dispatcher</a>.
</p>
-
-</introduction>
</div>
-<a name="N10015"></a><a name="a"></a>
+<a name="a"></a>
<h2 class="underlined_10">A</h2>
<div class="section">
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -396,7 +392,7 @@ document.write("Last Published: " + docu
</tr>
</table>
</div>
-<a name="N10055"></a><a name="c"></a>
+<a name="c"></a>
<h2 class="underlined_10">C</h2>
<div class="section">
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -429,7 +425,7 @@ document.write("Last Published: " + docu
</tr>
</table>
</div>
-<a name="N10082"></a><a name="r"></a>
+<a name="r"></a>
<h2 class="underlined_10">R</h2>
<div class="section">
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -446,7 +442,7 @@ document.write("Last Published: " + docu
</tr>
</table>
</div>
-<a name="N1009F"></a><a name="s"></a>
+<a name="s"></a>
<h2 class="underlined_10">S</h2>
<div class="section">
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -499,7 +495,7 @@ document.write("Last Published: " + docu
</tr>
</table>
</div>
-<a name="N100E7"></a><a name="x"></a>
+<a name="x"></a>
<h2 class="underlined_10">X</h2>
<div class="section">
<table class="ForrestTable" cellspacing="1" cellpadding="4">
Modified: forrest/site/docs_0_80/howto/cvs-ssh/howto-cvs-ssh.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/cvs-ssh/howto-cvs-ssh.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/cvs-ssh/howto-cvs-ssh.html (original)
+++ forrest/site/docs_0_80/howto/cvs-ssh/howto-cvs-ssh.html Thu Jan 20 06:47:23 2011
@@ -197,7 +197,7 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10013"></a><a name="Intended-audience"></a>
+<a name="Intended-audience"></a>
<h2 class="underlined_10">Intended audience</h2>
<div class="section">
<p>
@@ -205,7 +205,7 @@ document.write("Last Published: " + docu
to CVS repositories for particular projects.
</p>
</div>
-<a name="N1001B"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
@@ -215,7 +215,7 @@ document.write("Last Published: " + docu
password every time you need access to CVS through SSH.
</p>
</div>
-<a name="N10023"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<ul>
@@ -240,13 +240,13 @@ document.write("Last Published: " + docu
</div>
</div>
</div>
-<a name="N10044"></a><a name="Steps"></a>
+<a name="Steps"></a>
<h2 class="underlined_10">Steps</h2>
<div class="section">
<p>
How to proceed.
</p>
-<a name="N1004C"></a><a name="Terms"></a>
+<a name="Terms"></a>
<h3 class="underlined_5">Terms</h3>
<dl>
@@ -268,7 +268,7 @@ document.write("Last Published: " + docu
<strong>$</strong> represents local, <strong>%</strong> remote machine.
</div>
</div>
-<a name="N10071"></a><a name="Setting+up+domain+users"></a>
+<a name="Setting+up+domain+users"></a>
<h3 class="underlined_5">Setting up domain users</h3>
<div class="note">
<div class="label">Note</div>
@@ -309,7 +309,7 @@ $ exit
$ whoami
userxxx
</pre>
-<a name="N1009C"></a><a name="ssh_access"></a>
+<a name="ssh_access"></a>
<h3 class="underlined_5">Setting up SSH access</h3>
<p>
Start Cygwin/shell, then enter:
@@ -339,7 +339,7 @@ $ ssh-user-config
passphrase retaining.
</div>
</div>
-<a name="N100B3"></a><a name="Setting+up+passphrase+access"></a>
+<a name="Setting+up+passphrase+access"></a>
<h3 class="underlined_5">Setting up passphrase access</h3>
<p>
Perform the following:
@@ -380,7 +380,7 @@ $ ssh userxxx@cvs.apache.org
If now you are logged in to the to the CVS machine without entering the
password then everything's Ok.
</p>
-<a name="N100D7"></a><a name="Getting+the+project+from+CVS"></a>
+<a name="Getting+the+project+from+CVS"></a>
<h3 class="underlined_5">Getting the project from CVS</h3>
<p>
Now you are ready to get a project from CVS using SSH connection.
@@ -392,7 +392,7 @@ $ ssh userxxx@cvs.apache.org
$ export CVS_RSH=/bin/ssh
$ cvs -d :ext:userxxx@cvs.apache.org:/home/cvs co xml-cocoon2
</pre>
-<a name="N100E8"></a><a name="How+to+setup+WinCVS"></a>
+<a name="How+to+setup+WinCVS"></a>
<h3 class="underlined_5">How to setup WinCVS</h3>
<ul>
@@ -423,7 +423,7 @@ $ cvs -d :ext:userxxx@cvs.apache.org:/ho
<li>Click Ok</li>
</ul>
-<a name="N1011B"></a><a name="References"></a>
+<a name="References"></a>
<h3 class="underlined_5">References</h3>
<p>
You can find more on CVS, SSH and WinCVS here:
Modified: forrest/site/docs_0_80/howto/howto-asf-mirror.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-asf-mirror.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-asf-mirror.html (original)
+++ forrest/site/docs_0_80/howto/howto-asf-mirror.html Thu Jan 20 06:47:23 2011
@@ -353,7 +353,7 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10010"></a><a name="Intended-Audience"></a>
+<a name="Intended-Audience"></a>
<h2 class="underlined_10">Intended Audience</h2>
<div class="section">
<ul>
@@ -366,7 +366,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N1001E"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
@@ -380,7 +380,7 @@ document.write("Last Published: " + docu
from anywhere in the site. So we explain how to process additional files.
</p>
</div>
-<a name="N10029"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<ul>
@@ -398,10 +398,10 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10042"></a><a name="Steps"></a>
+<a name="Steps"></a>
<h2 class="underlined_10">Steps</h2>
<div class="section">
-<a name="N10047"></a><a name="cgi"></a>
+<a name="cgi"></a>
<h3 class="underlined_5">Add the mirrors.cgi as a raw file</h3>
<p>
As explained in the mirrors document, there will be a two-line CGI
@@ -415,7 +415,7 @@ document.write("Last Published: " + docu
project's
<a href="http://svn.apache.org/repos/asf/forrest/trunk/site-author/content/mirrors.cgi">mirrors.cgi</a>)
</p>
-<a name="N1005E"></a><a name="html"></a>
+<a name="html"></a>
<h3 class="underlined_5">Add the mirrors.html to xdocs directory</h3>
<p>
This file contains the html content of your mirror page, including the
@@ -433,7 +433,7 @@ document.write("Last Published: " + docu
Note that the special tokens (e.g. [if-any http] [for http]) need to be
encompassed by xml comments.
</p>
-<a name="N10075"></a><a name="menu"></a>
+<a name="menu"></a>
<h3 class="underlined_5">Add a menu entry for Download</h3>
<p>
Add an entry to your site.xml navigation. For example ...
@@ -447,7 +447,7 @@ document.write("Last Published: " + docu
<download_html href="mirrors.html"/><!-- so the page is part of a tab -->
...
</pre>
-<a name="N10083"></a><a name="link"></a>
+<a name="link"></a>
<h3 class="underlined_5">Cause the mirrors.html to be processed as an extra file</h3>
<p>
Forrest gathers the links that are to be crawled, by reading site.xml
@@ -470,7 +470,7 @@ document.write("Last Published: " + docu
<uri type="append" src="mirrors.html"/>
</uris>
</pre>
-<a name="N1009E"></a><a name="forrest"></a>
+<a name="forrest"></a>
<h3 class="underlined_5">Run 'forrest' to build your site</h3>
<p>
That is all that you need to do, Forrest will take care of it from
Modified: forrest/site/docs_0_80/howto/howto-buildPlugin.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-buildPlugin.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-buildPlugin.html (original)
+++ forrest/site/docs_0_80/howto/howto-buildPlugin.html Thu Jan 20 06:47:23 2011
@@ -431,7 +431,7 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10013"></a><a name="Intended-Audience"></a>
+<a name="Intended-Audience"></a>
<h2 class="underlined_10">Intended Audience</h2>
<div class="section">
<p>
@@ -446,7 +446,7 @@ document.write("Last Published: " + docu
</div>
</div>
</div>
-<a name="N1001E"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
@@ -454,7 +454,7 @@ document.write("Last Published: " + docu
configure a Forrest project to use their plugin.
</p>
</div>
-<a name="N10026"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<p>
@@ -475,20 +475,20 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10040"></a><a name="Steps"></a>
+<a name="Steps"></a>
<h2 class="underlined_10">Steps</h2>
<div class="section">
<p>
Here is how to proceed.
</p>
-<a name="N10048"></a><a name="typeOfPlugin"></a>
+<a name="typeOfPlugin"></a>
<h3 class="underlined_5">Type of Plugin</h3>
<p>
There are three types of plugin, each with a clear purpose, you must
first decide which <a href="../../pluginDocs/plugins_0_90/pluginInfrastructure.html">type of
plugin</a> you need to build.
</p>
-<a name="N10056"></a><a name="ant"></a>
+<a name="ant"></a>
<h3 class="underlined_5">Make ant available on the command-line</h3>
<p>
The following instructions rely heavily on
@@ -507,7 +507,7 @@ document.write("Last Published: " + docu
network to get the DTDs on every xml parse. Be aware that Forrest might
be relying on some Ant features in its version.
</p>
-<a name="N1006A"></a><a name="seed"></a>
+<a name="seed"></a>
<h3 class="underlined_5">Seed a New Plugin</h3>
<p>
Regardless of the type of plugin you are building, the directory
@@ -569,7 +569,7 @@ document.write("Last Published: " + docu
more information about the plugin directory structure and configuration
files.
</p>
-<a name="N100A8"></a><a name="edit-template"></a>
+<a name="edit-template"></a>
<h4>Edit the Plugin Template</h4>
<p>
You now have a skeleton plugin project. However, it doesn't do
@@ -579,7 +579,7 @@ document.write("Last Published: " + docu
<p>
Here are some general notes:
</p>
-<a name="N100B4"></a><a name="status"></a>
+<a name="status"></a>
<h5>status.xml</h5>
<p>
This file is used to track changes to the plugin project and to
@@ -593,14 +593,14 @@ document.write("Last Published: " + docu
this file so that it can then be used as a changelog for your
plugin.
</p>
-<a name="N100C4"></a><a name="forrest-properties"></a>
+<a name="forrest-properties"></a>
<h5>forrest.properties</h5>
<p>
This file defines many configuration parameters for Forrest. It does
not need to be customised in most cases. However, see for more
details.
</p>
-<a name="N100CE"></a><a name="skinconf"></a>
+<a name="skinconf"></a>
<h5>src/documentation/skinconf.xml</h5>
<p>
This configures the skin for your plugins documentation. There are
@@ -608,14 +608,14 @@ document.write("Last Published: " + docu
copyright information. The file is heavily commented so probably
best to read through it, changing what you need to.
</p>
-<a name="N100D8"></a><a name="doc"></a>
+<a name="doc"></a>
<h5>Documentation</h5>
<p>
It is also a good idea to start writing the documentation at this
stage. The above process created a very simple plugin documentation
site for you. All you have to do is add the content.
</p>
-<a name="N100E2"></a><a name="hosted"></a>
+<a name="hosted"></a>
<h5>Style notes for plugins hosted at forrest.apache.org</h5>
<p>
After seeding a new plugin, copy the configuration from an existing
@@ -623,7 +623,7 @@ document.write("Last Published: " + docu
src/documentation/skinconf.xml (and edit to suit) and
src/documentation/content/xdocs/images/project-logo.gif
</p>
-<a name="N100EE"></a><a name="edit-sitemap"></a>
+<a name="edit-sitemap"></a>
<h3 class="underlined_5">Edit the Plugin sitemap file(s)</h3>
<p>
The plugin <span class="codefrag">xmap</span> file is a Cocoon sitemap that is mounted at
@@ -653,7 +653,7 @@ document.write("Last Published: " + docu
<a href="../../mail-lists.html#forrest-dev">developer mailing list</a> a very
good resource (check the archives before posting, please).
</p>
-<a name="N1011B"></a><a name="components"></a>
+<a name="components"></a>
<h4>Components, Actions and Resources</h4>
<p>
If your plugin uses any components (i.e. generators, transformers or
@@ -674,7 +674,7 @@ document.write("Last Published: " + docu
<p>
See the examples below for more details.
</p>
-<a name="N10144"></a><a name="resources"></a>
+<a name="resources"></a>
<h3 class="underlined_5">Create the Necessary Resource Files</h3>
<div class="fixme">
<div class="label">Fixme (open)</div>
@@ -682,7 +682,7 @@ document.write("Last Published: " + docu
Discuss the XSL files and other such resources
</div>
</div>
-<a name="N1014E"></a><a name="dtd-catalog"></a>
+<a name="dtd-catalog"></a>
<h4>Entity catalog for DTDs and other resources</h4>
<p>
If the plugin uses non-core DTDs and other entities, then add them to
@@ -691,7 +691,7 @@ document.write("Last Published: " + docu
another plugin (e.g. "listLocations" has a simple example; "glossary"
has a more complex example) and edit it to suit.
</p>
-<a name="N1015C"></a><a name="samples"></a>
+<a name="samples"></a>
<h3 class="underlined_5">Create Samples in the Documentation</h3>
<p>
Plugin documentation should provide (as a minimum) an index page that
@@ -705,7 +705,7 @@ document.write("Last Published: " + docu
Try to provide a sample for all the major functions of your plugin and
document any configuration that is available.
</p>
-<a name="N10172"></a><a name="test"></a>
+<a name="test"></a>
<h3 class="underlined_5">Testing a Plugin</h3>
<p>
Since your documentation for the plugin illustrates all of its
@@ -742,7 +742,7 @@ document.write("Last Published: " + docu
Ensure that your sitemaps are robust and handle matches for files in
sub-directories, as well as those at the root level.
</p>
-<a name="N1019F"></a><a name="Testing+During+Development"></a>
+<a name="Testing+During+Development"></a>
<h4>Testing During Development</h4>
<p>
In the current plugin system plugins are not used from their src
@@ -769,9 +769,9 @@ document.write("Last Published: " + docu
files in the <span class="codefrag">conf</span> directory you will, most likely, have
to restart Forrest to see these changes.
</p>
-<a name="N101B9"></a><a name="release"></a>
+<a name="release"></a>
<h3 class="underlined_5">Releasing a Plugin</h3>
-<a name="N101BF"></a><a name="register"></a>
+<a name="register"></a>
<h4>Register the Plugin with Apache Forrest</h4>
<div class="fixme">
<div class="label">Fixme (rdg)</div>
@@ -779,7 +779,7 @@ document.write("Last Published: " + docu
Describe making a request of Forrest devs for inclusion
</div>
</div>
-<a name="N101CA"></a><a name="deploy"></a>
+<a name="deploy"></a>
<h4>Deploying the Plugin</h4>
<p>
To deploy the plugin so that others can use it, it must be made
@@ -817,7 +817,7 @@ document.write("Last Published: " + docu
cycle, but we feel the peace of mind is worth it.
</div>
</div>
-<a name="N101FC"></a><a name="descriptor"></a>
+<a name="descriptor"></a>
<h4>Managing the plugins descriptors</h4>
<p>
The files plugins/plugins.xml and whiteboard/plugins/plugins.xml are
@@ -876,7 +876,7 @@ document.write("Last Published: " + docu
Start adding changes notes.</li>
</ul>
-<a name="N1023B"></a><a name="experimental"></a>
+<a name="experimental"></a>
<h3 class="underlined_5">Experimental Functionality</h3>
<div class="warning">
<div class="label">Warning</div>
@@ -895,7 +895,7 @@ document.write("Last Published: " + docu
<span class="codefrag">org.apache.forrest.internal.NoteTaking</span> plugin.
</div>
</div>
-<a name="N1024A"></a><a name="Locationmap"></a>
+<a name="Locationmap"></a>
<h4>Locationmap</h4>
<p>
Plugins can use the Forrest locationmap to expose resources to your
@@ -907,7 +907,7 @@ document.write("Last Published: " + docu
<a href="http://issues.apache.org/jira/browse/FOR-200">issue</a> for
the status of locationmap development.
</p>
-<a name="N1025E"></a><a name="Dispatcher"></a>
+<a name="Dispatcher"></a>
<h4>Dispatcher</h4>
<p>
Dispatcher (previous codename Forrest Views) is the collective name
@@ -954,7 +954,7 @@ document.write("Last Published: " + docu
locationmap which is generated when you seed a new plugin, but for now
it must be done manually.
</p>
-<a name="N1027E"></a><a name="Plugin+Properties"></a>
+<a name="Plugin+Properties"></a>
<h4>Plugin Properties</h4>
<p>
Plugins can define properties that each project can over-ride. For
@@ -965,13 +965,13 @@ document.write("Last Published: " + docu
<a href="http://issues.apache.org/jira/browse/FOR-588">issue</a> for
the status of this new configuration system.
</p>
-<a name="N10290"></a><a name="examples"></a>
+<a name="examples"></a>
<h3 class="underlined_5">Examples</h3>
<p>
This section will provide some example plugins to help illustrate the
steps discussed above.
</p>
-<a name="N10299"></a><a name="input"></a>
+<a name="input"></a>
<h4>Input Plugin</h4>
<div class="fixme">
<div class="label">Fixme (RDG)</div>
@@ -979,7 +979,7 @@ document.write("Last Published: " + docu
Discuss OpenOffice.org plugin here
</div>
</div>
-<a name="N102A4"></a><a name="output"></a>
+<a name="output"></a>
<h4>Output Plugin</h4>
<div class="fixme">
<div class="label">Fixme (RDG)</div>
@@ -987,7 +987,7 @@ document.write("Last Published: " + docu
Discuss s5 plugin here
</div>
</div>
-<a name="N102AF"></a><a name="internal"></a>
+<a name="internal"></a>
<h4>Internal Plugin</h4>
<div class="fixme">
<div class="label">Fixme (RDG)</div>
@@ -995,7 +995,7 @@ document.write("Last Published: " + docu
Discuss IMSManifest plugin here
</div>
</div>
-<a name="N102BB"></a><a name="extension"></a>
+<a name="extension"></a>
<h3 class="underlined_5">Further Reading</h3>
<ul>
@@ -1006,7 +1006,7 @@ document.write("Last Published: " + docu
<a href="../../pluginDocs/plugins_0_90/">Plugins Documentation</a> for users</li>
</ul>
-<a name="N102D1"></a><a name="summarise"></a>
+<a name="summarise"></a>
<h3 class="underlined_5">Summarise the Entire Process</h3>
<div class="fixme">
<div class="label">Fixme (open)</div>
Modified: forrest/site/docs_0_80/howto/howto-corner-images.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-corner-images.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-corner-images.html (original)
+++ forrest/site/docs_0_80/howto/howto-corner-images.html Thu Jan 20 06:47:23 2011
@@ -349,7 +349,7 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10010"></a><a name="Intended-Audience"></a>
+<a name="Intended-Audience"></a>
<h2 class="underlined_10">Intended Audience</h2>
<div class="section">
<p>
@@ -361,7 +361,7 @@ document.write("Last Published: " + docu
corner image generation process.
</p>
</div>
-<a name="N1001B"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
@@ -371,7 +371,7 @@ document.write("Last Published: " + docu
for your own skin colors.
</p>
</div>
-<a name="N10027"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<ul>
@@ -385,7 +385,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N1003D"></a><a name="Steps"></a>
+<a name="Steps"></a>
<h2 class="underlined_10">Steps</h2>
<div class="section">
<p>
@@ -394,7 +394,7 @@ document.write("Last Published: " + docu
for these images by modifying the
<span class="codefrag">src/documentation/skinconf.xml</span> of a project.
</p>
-<a name="N10048"></a><a name="css-files"></a>
+<a name="css-files"></a>
<h3 class="underlined_5">Understand how corner images are named (the contract)</h3>
<p>
The corner images are referenced in some .css files of the above-named
@@ -561,7 +561,7 @@ images/{$name}-{$v-orientation}-{$h-orie
directly generating it.
</div>
</div>
-<a name="N10121"></a><a name="skinconfig"></a>
+<a name="skinconfig"></a>
<h3 class="underlined_5">Modifying the skinconf.xml of your project</h3>
<p>
modifying the <span class="codefrag">skinconf.xml</span> of your project (by default you
@@ -623,7 +623,7 @@ images/{$name}-{$v-orientation}-{$h-orie
color (<span class="codefrag">-3tab-selected</span>) are set to red (remember: we defined
<span class="codefrag">#FF0000</span> as the "color" value of <span class="codefrag">tab-selected</span>).
</p>
-<a name="N10178"></a><a name="css_modify"></a>
+<a name="css_modify"></a>
<h3 class="underlined_5">Modifying .css files</h3>
<p>
In addition to the modification of <span class="codefrag">skinconf.xml</span> you can
@@ -658,7 +658,7 @@ images/{$name}-{$v-orientation}-{$h-orie
Horrible, isn't it?
</p>
</div>
-<a name="N101A8"></a><a name="Feedback"></a>
+<a name="Feedback"></a>
<h2 class="underlined_10">Feedback</h2>
<div class="section">
<p>
Modified: forrest/site/docs_0_80/howto/howto-custom-html-source.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-custom-html-source.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-custom-html-source.html (original)
+++ forrest/site/docs_0_80/howto/howto-custom-html-source.html Thu Jan 20 06:47:23 2011
@@ -392,7 +392,7 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10010"></a><a name="Intended-Audience"></a>
+<a name="Intended-Audience"></a>
<h2 class="underlined_10">Intended Audience</h2>
<div class="section">
<p>
@@ -400,7 +400,7 @@ document.write("Last Published: " + docu
everybody who wants to learn more about Forrest's pipelines in general.
</p>
</div>
-<a name="N10018"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
@@ -410,7 +410,7 @@ document.write("Last Published: " + docu
does not suffice.
</p>
</div>
-<a name="N10020"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<p>
@@ -448,7 +448,7 @@ document.write("Last Published: " + docu
</ol>
</div>
-<a name="N10043"></a><a name="Understanding-the-HTML-Pipeline"></a>
+<a name="Understanding-the-HTML-Pipeline"></a>
<h2 class="underlined_10">Understanding the HTML-Pipeline</h2>
<div class="section">
<p>
@@ -457,7 +457,7 @@ document.write("Last Published: " + docu
documents. If you already know how pipelines work, then skip to the
section about <a href="#custom">Customizing the html pipeline</a>.
</p>
-<a name="N1004F"></a><a name="example"></a>
+<a name="example"></a>
<h3 class="underlined_5">Driven by Example</h3>
<p>
The best way to learn about Forrest pipelines is follow the processing
@@ -469,7 +469,7 @@ document.write("Last Published: " + docu
<br>
'http://my.domain.org/mytest/mybad.html'.
</p>
-<a name="N1005E"></a><a name="sitemap"></a>
+<a name="sitemap"></a>
<h3 class="underlined_5">Finding the Sitemap</h3>
<p>
Like all applications based on Apache Cocoon, each request for a given
@@ -498,7 +498,7 @@ map:sitemap
are other sitemaps (which we will see later on), we always start looking
for a matching pattern right here.
</p>
-<a name="N10079"></a><a name="pipelines"></a>
+<a name="pipelines"></a>
<h3 class="underlined_5">Find the Beginning of the Pipelines Section</h3>
<p>
Modular as everything else in Cocoon, Forrest's sitemap starts with a
@@ -522,7 +522,7 @@ map:pipelines
bottom until it encounters a Pipeline that will take care of our
request.
</p>
-<a name="N10090"></a><a name="matches"></a>
+<a name="matches"></a>
<h3 class="underlined_5">Looking for a Match</h3>
<p>
Like all Cocoon applications, Forrest knows which pipeline to use for
@@ -562,7 +562,7 @@ map:pipelines
*.something in Cocoon matches only files in the root directory.
</div>
</div>
-<a name="N100B4"></a><a name="html-pipeline"></a>
+<a name="html-pipeline"></a>
<h3 class="underlined_5">Processing in the '**/*.html' Pipeline</h3>
<p>
Let's take a quick look at this pipeline to understand what's happening
@@ -616,7 +616,7 @@ map:pipelines
comes from. To find out, we have to look at the sources of the
aggregation.
</p>
-<a name="N100D5"></a><a name="protocols"></a>
+<a name="protocols"></a>
<h3 class="underlined_5">Following the Pseudo-Protocols</h3>
<p>
To find out what goes into our aggregation, we'll need to look at the
@@ -680,7 +680,7 @@ map:pipelines
As you can easily tell, we are suddenly calling for a whole new
document. Let's see where that takes us:
</p>
-<a name="N10139"></a><a name="call"></a>
+<a name="call"></a>
<h3 class="underlined_5">Second Call for Content</h3>
<p>
Processing of cocoon-calls is not much different from normal requests by
@@ -699,7 +699,7 @@ map:pipelines
</span> from the beginning of the sitemap to see where we find our next
match.
</p>
-<a name="N10151"></a><a name="match-1"></a>
+<a name="match-1"></a>
<h3 class="underlined_5">First Match for '**body-*.html'</h3>
<p>
Our first match is different to the previous ones because there is a
@@ -721,7 +721,7 @@ map:pipelines
So we have a pipeline, but it doesn't do anything. In this case Forrest
will simply keep looking for the next match further down.
</p>
-<a name="N10167"></a><a name="match-2"></a>
+<a name="match-2"></a>
<h3 class="underlined_5">Second Match for '**body-*.html'</h3>
<p class="instruction">
Continue searching downwards for '**body-*.html' in the sitemap-file.
@@ -784,7 +784,7 @@ map:pipelines
<pre class="code">
<map:generate src="cocoon:/mytests/mybad.xml"/>
</pre>
-<a name="N101CF"></a><a name="match-3"></a>
+<a name="match-3"></a>
<h3 class="underlined_5">Third Call for Content</h3>
<p class="instruction">
So let's scan the main sitemap looking for a match for
@@ -844,7 +844,7 @@ map:pipelines
for the existence of the file with different extensions. '.html' is
third in this list and leads to the processing steps shown below:
</p>
-<a name="N1020A"></a><a name="process-html"></a>
+<a name="process-html"></a>
<h3 class="underlined_5">html-Default Processing</h3>
<p>
The default processing of html-files consists of three processing steps:
@@ -897,7 +897,7 @@ map:pipelines
that name).
</div>
</div>
-<a name="N1023E"></a><a name="body"></a>
+<a name="body"></a>
<h3 class="underlined_5">Returning to the '**body-*.html'-Pipeline</h3>
<p>
On returning into the '**body-*.html'-Pipeline (in sitemap.xmap),
@@ -944,7 +944,7 @@ map:pipelines
that name).
</div>
</div>
-<a name="N10266"></a><a name="aggregate"></a>
+<a name="aggregate"></a>
<h3 class="underlined_5">Returning to the '**/*.html'-Pipeline</h3>
<p>
At the end of this pipeline, processing returns the results into the
@@ -952,13 +952,13 @@ map:pipelines
Pipeline</a>, merges it with other data, skins and serializes for
presentation in the requesting client.
</p>
-<a name="N10274"></a><a name="custom"></a>
+<a name="custom"></a>
<h3 class="underlined_5">Customizing the html pipeline</h3>
<p>
In this last part of this document, we will show how to customize the
HTML-pipeline to add your additional steps to the default processing.
</p>
-<a name="N1027D"></a><a name="when"></a>
+<a name="when"></a>
<h4>When to customize?</h4>
<p>
The html-Pipeline in Forrest is designed to be able to also integrate
@@ -980,7 +980,7 @@ map:pipelines
will see the original page from your legacy website, menu and all,
embedded in your new Forrest site.
</p>
-<a name="N1028D"></a><a name="how"></a>
+<a name="how"></a>
<h4>How to customize?</h4>
<p>
To add your own custom processing for a group of pages, you will
@@ -1000,7 +1000,7 @@ map:pipelines
pipeline'), your pipeline intercepts practically all of Forrest's
standard pipelines.
</p>
-<a name="N1029D"></a><a name="what"></a>
+<a name="what"></a>
<h4>What to intercept?</h4>
<p>
Where to intercept standard processing is really a matter of your
@@ -1018,7 +1018,7 @@ map:pipelines
new pipeline that intercepts **.xml for our pages, copy the steps the
original processor is doing and add a transformation of our own to it.
</p>
-<a name="N102AD"></a><a name="intercept"></a>
+<a name="intercept"></a>
<h4>Intercept pattern</h4>
<p>
Take great care when intercepting very basic pipelines. Instead of
Modified: forrest/site/docs_0_80/howto/howto-editcss.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-editcss.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-editcss.html (original)
+++ forrest/site/docs_0_80/howto/howto-editcss.html Thu Jan 20 06:47:23 2011
@@ -354,7 +354,7 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10010"></a><a name="Intended-Audience"></a>
+<a name="Intended-Audience"></a>
<h2 class="underlined_10">Intended Audience</h2>
<div class="section">
<p>
@@ -362,7 +362,7 @@ document.write("Last Published: " + docu
with changing certain CSS-styles settings to see what happens.
</p>
</div>
-<a name="N10018"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
@@ -377,7 +377,7 @@ document.write("Last Published: " + docu
property will have on the look and feel of your Forrest.
</p>
</div>
-<a name="N10023"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<p>
@@ -426,10 +426,10 @@ document.write("Last Published: " + docu
</ol>
</div>
-<a name="N10049"></a><a name="Steps"></a>
+<a name="Steps"></a>
<h2 class="underlined_10">Steps</h2>
<div class="section">
-<a name="N1004E"></a><a name="openForrest"></a>
+<a name="openForrest"></a>
<h3 class="underlined_5">Open your Forrest</h3>
<p class="instruction">
Start your Firefox Browser and open the Forrest you'd like to work
@@ -438,7 +438,7 @@ document.write("Last Published: " + docu
<p>
The page you have pointed to will show up in Firefox's main window.
</p>
-<a name="N1005C"></a><a name="OpenEditCSS"></a>
+<a name="OpenEditCSS"></a>
<h3 class="underlined_5">Open the EditCSS-Sidebar</h3>
<p class="instruction">
Select View-Sidebar-EditCSS from Firefox's main menu to open the EditCSS
@@ -448,7 +448,7 @@ document.write("Last Published: " + docu
The EditCSS sidebar will show next to the main window and load all the
styles from the main page.
</p>
-<a name="N1006A"></a><a name="changeCSS"></a>
+<a name="changeCSS"></a>
<h3 class="underlined_5">Change any CSS</h3>
<p class="instruction">
Change any style you'd like to experiment with or add new settings and
@@ -466,7 +466,7 @@ document.write("Last Published: " + docu
windows for every character you type.
</div>
</div>
-<a name="N1007B"></a><a name="saveChanges"></a>
+<a name="saveChanges"></a>
<h3 class="underlined_5">How to save changes?</h3>
<p>
Since it takes a few explanations to apply the changes to your Forrest,
@@ -474,7 +474,7 @@ document.write("Last Published: " + docu
extend Forrest-CSS"
</p>
</div>
-<a name="N10085"></a><a name="Feedback-and-further-development-of-this-How-To"></a>
+<a name="Feedback-and-further-development-of-this-How-To"></a>
<h2 class="underlined_10">Feedback and further development of this How-To</h2>
<div class="section">
<p>
Modified: forrest/site/docs_0_80/howto/howto-forrest-from-maven.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-forrest-from-maven.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-forrest-from-maven.html (original)
+++ forrest/site/docs_0_80/howto/howto-forrest-from-maven.html Thu Jan 20 06:47:23 2011
@@ -352,14 +352,14 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10010"></a><a name="Intended-Audience"></a>
+<a name="Intended-Audience"></a>
<h2 class="underlined_10">Intended Audience</h2>
<div class="section">
<p>
Users who want to run Forrest from within Maven.
</p>
</div>
-<a name="N10018"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
@@ -367,7 +367,7 @@ document.write("Last Published: " + docu
using Forrest in lieu of Maven's site plugin.
</p>
</div>
-<a name="N10020"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<ul>
@@ -376,21 +376,21 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N1002F"></a><a name="Steps"></a>
+<a name="Steps"></a>
<h2 class="underlined_10">Steps</h2>
<div class="section">
<p>
The procedure outlined below describes how to add a goal to your project's
maven.xml that will invoke Forrest's <span class="codefrag">site</span> target.
</p>
-<a name="N1003A"></a><a name="set-maven-home"></a>
+<a name="set-maven-home"></a>
<h3 class="underlined_5">Set the FORREST_HOME environment variable</h3>
<p>
Make sure the FORREST_HOME environment variable points to your Forrest
home directory (i.e. the directory that contains
<span class="codefrag">forrest.build.xml</span>) (e.g. C:\opt\apache-forrest-0.7)
</p>
-<a name="N10047"></a><a name="define-ant-environment-prop"></a>
+<a name="define-ant-environment-prop"></a>
<h3 class="underlined_5">Initialize an Ant environment property at the top of
maven.xml</h3>
<p>
@@ -399,7 +399,7 @@ document.write("Last Published: " + docu
<pre class="code">
<property environment="env" />
</pre>
-<a name="N10055"></a><a name="add-forrest-goal-to-maven-xml"></a>
+<a name="add-forrest-goal-to-maven-xml"></a>
<h3 class="underlined_5">Add forrest goal to maven.xml</h3>
<p>
Paste the following goal into your project's maven.xml:
@@ -429,14 +429,14 @@ document.write("Last Published: " + docu
makes use of the copy of Ant 1.6 that is bundled with Forrest, so it's
not even necessary to have Ant 1.6 installed separately.
</p>
-<a name="N10066"></a><a name="Alternative+file"></a>
+<a name="Alternative+file"></a>
<h3 class="underlined_5">Alternative file</h3>
<p>
Under <span class="codefrag">$FORREST_HOME/tools/targets/maven.xml</span>
</p>
</div>
-<a name="N10073"></a><a name="Feedback"></a>
+<a name="Feedback"></a>
<h2 class="underlined_10">Feedback</h2>
<div class="section">
<p>
Modified: forrest/site/docs_0_80/howto/howto-pdf-tab.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/howto-pdf-tab.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-pdf-tab.html (original)
+++ forrest/site/docs_0_80/howto/howto-pdf-tab.html Thu Jan 20 06:47:23 2011
@@ -358,7 +358,7 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10010"></a><a name="Intended-Audience"></a>
+<a name="Intended-Audience"></a>
<h2 class="underlined_10">Intended Audience</h2>
<div class="section">
<p>
@@ -366,7 +366,7 @@ document.write("Last Published: " + docu
of documents.
</p>
</div>
-<a name="N10018"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
@@ -376,7 +376,7 @@ document.write("Last Published: " + docu
certain parts of the site.
</p>
</div>
-<a name="N10020"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<ul>
@@ -386,26 +386,26 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N1002F"></a><a name="Steps"></a>
+<a name="Steps"></a>
<h2 class="underlined_10">Steps</h2>
<div class="section">
<p>
The procedure outlined below will define a project
<span class="codefrag">sitemap.xmap</span> and create a new <span class="codefrag">pdf-tab.xmap</span>.
</p>
-<a name="N1003D"></a><a name="sitemap"></a>
+<a name="sitemap"></a>
<h3 class="underlined_5">Create your project's main sitemap.xmap</h3>
<p>
If you do not have already a sitemap then create a new empty one in your
<span class="codefrag">src/documentation</span> directory (or wherever
${project.sitemap-dir} points to).
</p>
-<a name="N1004A"></a><a name="aggregator"></a>
+<a name="aggregator"></a>
<h3 class="underlined_5">Create another sitemap: pdf-tab.xmap</h3>
<p>
Like before create an empty sitemap and name it pdf-tab.xmap.
</p>
-<a name="N10054"></a><a name="mount"></a>
+<a name="mount"></a>
<h3 class="underlined_5">Edit project sitemap.xmap to mount pdf-tab.xmap</h3>
<p>
Your sitemap should look something like this.
@@ -427,7 +427,7 @@ document.write("Last Published: " + docu
</map:pipelines>
</map:sitemap>
</pre>
-<a name="N10062"></a><a name="edit-aggregator"></a>
+<a name="edit-aggregator"></a>
<h3 class="underlined_5">Edit the file pdf-tab.xmap</h3>
<p>
The <span class="codefrag">
@@ -459,7 +459,7 @@ document.write("Last Published: " + docu
</map:pipelines>
</map:sitemap>
</pre>
-<a name="N10075"></a><a name="edit-site"></a>
+<a name="edit-site"></a>
<h3 class="underlined_5">Edit your site.xml</h3>
<div class="note">
<div class="label">Note</div>
@@ -516,7 +516,7 @@ document.write("Last Published: " + docu
do)!!!
</div>
</div>
-<a name="N100A9"></a><a name="explain"></a>
+<a name="explain"></a>
<h3 class="underlined_5">Explanation of the operation</h3>
<p>
Line 4 of our example
@@ -571,7 +571,7 @@ document.write("Last Published: " + docu
</p>
</div>
-<a name="N100E0"></a><a name="Feedback-and-further-development-of-this-How-To"></a>
+<a name="Feedback-and-further-development-of-this-How-To"></a>
<h2 class="underlined_10">Feedback and further development of this How-To</h2>
<div class="section">
<p>
Modified: forrest/site/docs_0_80/howto/index.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/index.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/index.html (original)
+++ forrest/site/docs_0_80/howto/index.html Thu Jan 20 06:47:23 2011
@@ -329,7 +329,7 @@ document.write("Last Published: " + docu
</div>
</div>
-<a name="N1000D"></a><a name="Forrest+Site+and+Documentation"></a>
+<a name="Forrest+Site+and+Documentation"></a>
<h2 class="underlined_10">Forrest Site and Documentation</h2>
<div class="section">
<ul>
@@ -352,7 +352,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10023"></a><a name="Using+and+developing+with+Forrest"></a>
+<a name="Using+and+developing+with+Forrest"></a>
<h2 class="underlined_10">Using and developing with Forrest</h2>
<div class="section">
<p>
@@ -395,7 +395,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N1004E"></a><a name="Extending+Forrest"></a>
+<a name="Extending+Forrest"></a>
<h2 class="underlined_10">Extending Forrest</h2>
<div class="section">
<ul>
Modified: forrest/site/docs_0_80/howto/multi/howto-multi.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/multi/howto-multi.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/multi/howto-multi.html (original)
+++ forrest/site/docs_0_80/howto/multi/howto-multi.html Thu Jan 20 06:47:23 2011
@@ -346,21 +346,21 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N10010"></a><a name="Intended-audience"></a>
+<a name="Intended-audience"></a>
<h2 class="underlined_10">Intended audience</h2>
<div class="section">
<p>
Describe the audience here.
</p>
</div>
-<a name="N10018"></a><a name="Purpose"></a>
+<a name="Purpose"></a>
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
Explain the purpose of the howto here.
</p>
</div>
-<a name="N10020"></a><a name="Prerequisites"></a>
+<a name="Prerequisites"></a>
<h2 class="underlined_10">Prerequisites</h2>
<div class="section">
<p>
@@ -384,7 +384,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N1003D"></a><a name="Various-Steps"></a>
+<a name="Various-Steps"></a>
<h2 class="underlined_10">Various Steps</h2>
<div class="section">
<p>
@@ -407,14 +407,14 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10057"></a><a name="Real-World-Extension"></a>
+<a name="Real-World-Extension"></a>
<h2 class="underlined_10">Real World Extension</h2>
<div class="section">
<p>
Briefly describe some relevant extensions that go beyond these basics.
</p>
</div>
-<a name="N1005F"></a><a name="Tips"></a>
+<a name="Tips"></a>
<h2 class="underlined_10">Tips</h2>
<div class="section">
<p>
@@ -429,7 +429,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10070"></a><a name="Related-Resources"></a>
+<a name="Related-Resources"></a>
<h2 class="underlined_10">Related Resources</h2>
<div class="section">
<p>
@@ -443,7 +443,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10082"></a><a name="Feedback"></a>
+<a name="Feedback"></a>
<h2 class="underlined_10">Feedback</h2>
<div class="section">
<p>
Modified: forrest/site/docs_0_80/howto/multi/step1.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/multi/step1.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/multi/step1.html (original)
+++ forrest/site/docs_0_80/howto/multi/step1.html Thu Jan 20 06:47:23 2011
@@ -330,15 +330,15 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N1000D"></a><a name="Step-1:-Do-foo"></a>
+<a name="Step-1:-Do-foo"></a>
<h2 class="underlined_10">Step 1: Do foo</h2>
<div class="section">
-<a name="N10012"></a><a name="First+section+of+this+step"></a>
+<a name="First+section+of+this+step"></a>
<h3 class="underlined_5">First section of this step</h3>
<p>
Description here.
</p>
-<a name="N1001C"></a><a name="Second+section+of+this+step"></a>
+<a name="Second+section+of+this+step"></a>
<h3 class="underlined_5">Second section of this step</h3>
<p>
Description here.
Modified: forrest/site/docs_0_80/howto/multi/step2.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/multi/step2.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/multi/step2.html (original)
+++ forrest/site/docs_0_80/howto/multi/step2.html Thu Jan 20 06:47:23 2011
@@ -330,15 +330,15 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N1000D"></a><a name="Step-2:-Do-foobar"></a>
+<a name="Step-2:-Do-foobar"></a>
<h2 class="underlined_10">Step 2: Do foobar</h2>
<div class="section">
-<a name="N10012"></a><a name="First+section+of+this+step"></a>
+<a name="First+section+of+this+step"></a>
<h3 class="underlined_5">First section of this step</h3>
<p>
Description here.
</p>
-<a name="N1001C"></a><a name="Second+section+of+this+step"></a>
+<a name="Second+section+of+this+step"></a>
<h3 class="underlined_5">Second section of this step</h3>
<p>
Description here.
Modified: forrest/site/docs_0_80/howto/multi/step3.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/howto/multi/step3.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/multi/step3.html (original)
+++ forrest/site/docs_0_80/howto/multi/step3.html Thu Jan 20 06:47:23 2011
@@ -330,15 +330,15 @@ document.write("Last Published: " + docu
</ul>
</div>
</div>
-<a name="N1000D"></a><a name="Step-3:-Finish-up"></a>
+<a name="Step-3:-Finish-up"></a>
<h2 class="underlined_10">Step 3: Finish up</h2>
<div class="section">
-<a name="N10012"></a><a name="First+section+of+this+step"></a>
+<a name="First+section+of+this+step"></a>
<h3 class="underlined_5">First section of this step</h3>
<p>
Description here.
</p>
-<a name="N1001C"></a><a name="Second+section+of+this+step"></a>
+<a name="Second+section+of+this+step"></a>
<h3 class="underlined_5">Second section of this step</h3>
<p>
Description here.
Modified: forrest/site/docs_0_80/libre-intro.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/libre-intro.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/libre-intro.html (original)
+++ forrest/site/docs_0_80/libre-intro.html Thu Jan 20 06:47:23 2011
@@ -403,7 +403,7 @@ document.write("Last Published: " + docu
</div>
</div>
-<a name="N10010"></a><a name="Intro"></a>
+<a name="Intro"></a>
<h2 class="underlined_10">Intro</h2>
<div class="section">
<div class="warning">
@@ -445,7 +445,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10029"></a><a name="Using+Libre+now+%280.0+alfa%29"></a>
+<a name="Using+Libre+now+%280.0+alfa%29"></a>
<h2 class="underlined_10">Using Libre now (0.0 alfa)</h2>
<div class="section">
<div class="warning">
@@ -459,7 +459,7 @@ document.write("Last Published: " + docu
this time)
</div>
</div>
-<a name="N10034"></a><a name="Generated+Output"></a>
+<a name="Generated+Output"></a>
<h3 class="underlined_5">Generated Output</h3>
<p>
The XML output that comes out of the generator largely follows this
@@ -507,7 +507,7 @@ document.write("Last Published: " + docu
The number and value (and its meaning) of the attributes on these
elements are specified in the libre.xml file.
</p>
-<a name="N1004E"></a><a name="Contents"></a>
+<a name="Contents"></a>
<h3 class="underlined_5">libre.xml Contents</h3>
<p>
That libre.xml file follows the
@@ -552,7 +552,7 @@ document.write("Last Published: " + docu
regex CDATA #IMPLIED
substitute CDATA #IMPLIED
></pre>
-<a name="N10060"></a><a name="Building+Blocks"></a>
+<a name="Building+Blocks"></a>
<h4>Building Blocks</h4>
<p>
The following elements get the following meaning when interpreted by
@@ -732,12 +732,12 @@ document.write("Last Published: " + docu
</ul>
</ul>
-<a name="N1016C"></a><a name="Important+Side+Effects"></a>
+<a name="Important+Side+Effects"></a>
<h3 class="underlined_5">Important Side Effects</h3>
<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>
+<a name="No+libre.xml"></a>
<h4>No libre.xml</h4>
<p>
When using an <span class="codefrag"><auto> </span>section, the filter will
@@ -745,7 +745,7 @@ document.write("Last Published: " + docu
output. You can however include a manual <span class="codefrag"><entry></span>
to point to the <span class="codefrag">libre.xml</span> file if needed.
</p>
-<a name="N1018B"></a><a name="No+Duplicates"></a>
+<a name="No+Duplicates"></a>
<h4>No Duplicates</h4>
<p>
You can combine multiple <span class="codefrag"><entry></span> and
@@ -756,7 +756,7 @@ document.write("Last Published: " + docu
<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>
+<a name="Example+Constructs"></a>
<h3 class="underlined_5">Example Constructs</h3>
<p>
Adding sorting and filtering to the filesystem with libre becomes a
@@ -768,7 +768,7 @@ document.write("Last Published: " + docu
that sets up the directories to store 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>
+<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 like
@@ -821,7 +821,7 @@ document.write("Last Published: " + docu
directory structures can all benefit from this same
filenaming/sorting strategy.
</p>
-<a name="N101E5"></a><a name="Naming+your+files+or+asking+them+their+name%3F"></a>
+<a name="Naming+your+files+or+asking+them+their+name%3F"></a>
<h4>Naming your files or asking them their name?</h4>
<p>
Given the poor expressiveness of the filesystem, the labels that
@@ -853,7 +853,7 @@ document.write("Last Published: " + docu
</libre></pre>
</div>
-<a name="N101F5"></a><a name="Next+Libre+%280.1%29"></a>
+<a name="Next+Libre+%280.1%29"></a>
<h2 class="underlined_10">Next Libre (0.1)</h2>
<div class="section">
<div class="note">
@@ -864,7 +864,7 @@ document.write("Last Published: " + docu
happens...
</div>
</div>
-<a name="N10202"></a><a name="Itches"></a>
+<a name="Itches"></a>
<h3 class="underlined_5">Itches</h3>
<p>
There is quite a number of fast code patches that can/need to happen
@@ -901,14 +901,14 @@ document.write("Last Published: " + docu
early optimizations :-P</li>
</ul>
-<a name="N1022A"></a><a name="Upcoming+Features"></a>
+<a name="Upcoming+Features"></a>
<h3 class="underlined_5">Upcoming Features</h3>
<p>
More importantly however there is a major set of new features that is
waiting to get in there. It all boils down in fact to having a more
expressive libre.xml file... some of the thoughts:
</p>
-<a name="N10233"></a><a name="Combinations+of+filter+logic"></a>
+<a name="Combinations+of+filter+logic"></a>
<h4>Combinations of filter logic</h4>
<p>
Some itching stuff:
@@ -943,7 +943,7 @@ document.write("Last Published: " + docu
</not>
</filter>
</pre>
-<a name="N10253"></a><a name="Separating+property-retrieval+from+formatting+and%0A++++++++++++testing"></a>
+<a name="Separating+property-retrieval+from+formatting+and%0A++++++++++++testing"></a>
<h4>Separating property-retrieval from formatting and
testing</h4>
<p>
@@ -990,7 +990,7 @@ document.write("Last Published: " + docu
And more logically introduce other tests like <span class="codefrag"><globtest
match="..."></span> or <span class="codefrag"><availabletest></span> or...
</p>
-<a name="N1028C"></a><a name="Replace+the+introspection+with+semantically+richer+named%0A++++++++++++properties+to+read."></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>
@@ -1043,7 +1043,7 @@ document.write("Last Published: " + docu
<p>
The DTD would then list the possible attributeValues.
</p>
-<a name="N102D0"></a><a name="Avalonising"></a>
+<a name="Avalonising"></a>
<h3 class="underlined_5">Avalonising</h3>
<p>
There are a number of perceived opportunities in taking up a stronger
@@ -1066,7 +1066,7 @@ document.write("Last Published: " + docu
HierarchyReader the (avalon) environment he needs.</li>
</ul>
-<a name="N102E6"></a><a name="Unresolved+Discussions"></a>
+<a name="Unresolved+Discussions"></a>
<h3 class="underlined_5">Unresolved Discussions</h3>
<ul>
@@ -1086,7 +1086,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10303"></a><a name="Libre+Design"></a>
+<a name="Libre+Design"></a>
<h2 class="underlined_10">Libre Design</h2>
<div class="section">
<p>
@@ -1128,7 +1128,7 @@ document.write("Last Published: " + docu
<p>
... hope this somewhat clarifies how things have been setup for now.
</p>
-<a name="N1032E"></a><a name="Dependencies"></a>
+<a name="Dependencies"></a>
<h3 class="underlined_5">Dependencies</h3>
<ul>
Modified: forrest/site/docs_0_80/linking.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/linking.html?rev=1061134&r1=1061133&r2=1061134&view=diff
==============================================================================
--- forrest/site/docs_0_80/linking.html (original)
+++ forrest/site/docs_0_80/linking.html Thu Jan 20 06:47:23 2011
@@ -388,7 +388,7 @@ document.write("Last Published: " + docu
</div>
</div>
-<a name="N1000D"></a><a name="intro"></a>
+<a name="intro"></a>
<h2 class="underlined_10">Introduction</h2>
<div class="section">
<p>
@@ -407,7 +407,7 @@ document.write("Last Published: " + docu
</p>
</div>
-<a name="N10025"></a><a name="site"></a>
+<a name="site"></a>
<h2 class="underlined_10">site.xml</h2>
<div class="section">
<p>
@@ -552,7 +552,7 @@ document.write("Last Published: " + docu
</p>
</div>
-<a name="N100B4"></a><a name="menu_generation"></a>
+<a name="menu_generation"></a>
<h2 class="underlined_10">Generating Menus</h2>
<div class="section">
<p>
@@ -595,7 +595,7 @@ document.write("Last Published: " + docu
<span class="codefrag">community/howto/index.html</span>
</p>
-<a name="N100FD"></a><a name="tabs-external"></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
@@ -614,7 +614,7 @@ document.write("Last Published: " + docu
root-relative and obviously specifies a directory (ends in '/'). In
which case /index.html will be added.
</p>
-<a name="N1011D"></a><a name="selecting-entries"></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
@@ -673,14 +673,14 @@ document.write("Last Published: " + docu
"<span class="codefrag">home</span>". Forrest will select <em>all nodes with
tab="home"</em> and put them in the menu.
</p>
-<a name="N10177"></a><a name="other-menu-selection"></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
entries is not the only one, although it is the most flexible. Here we
describe a few alternatives.
</p>
-<a name="N10183"></a><a name="dir-menu-selection"></a>
+<a name="dir-menu-selection"></a>
<h4>Directory-based selection</h4>
<p>
In this scheme, each tab corresponds to a directory within the site.
@@ -707,7 +707,7 @@ document.write("Last Published: " + docu
entries.</li>
</ul>
-<a name="N101B3"></a><a name="book-menu-selection"></a>
+<a name="book-menu-selection"></a>
<h4>Specifying menus with book.xml</h4>
<p>
Historically, menus in Forrest have been generated from a
@@ -719,7 +719,7 @@ document.write("Last Published: " + docu
files. In general, however, we recommend that users avoid
<span class="codefrag">book.xml</span> files.
</p>
-<a name="N101D0"></a><a name="tab-selection"></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
@@ -727,7 +727,7 @@ document.write("Last Published: " + docu
"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="N101E6"></a><a name="tab-site"></a>
+<a name="tab-site"></a>
<h3 class="underlined_5">Configuring the interaction between tabs.xml and site.xml</h3>
<p>
This is a collection of tips to assist with getting your menus and
@@ -797,7 +797,7 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N10239"></a><a name="toc-generation"></a>
+<a name="toc-generation"></a>
<h2 class="underlined_10">Table of Contents Generation</h2>
<div class="section">
<p>
@@ -845,10 +845,10 @@ document.write("Last Published: " + docu
</ul>
</div>
-<a name="N1026D"></a><a name="linking"></a>
+<a name="linking"></a>
<h2 class="underlined_10">Linking systems</h2>
<div class="section">
-<a name="N10273"></a><a name="direct-linking"></a>
+<a name="direct-linking"></a>
<h3 class="underlined_5">Direct linking</h3>
<p>
In earlier versions of Forrest (and in similar systems), there has
@@ -867,7 +867,7 @@ document.write("Last Published: " + docu
typically renders to multiple output formats (HTML and PDF), links in
one of them (here, the PDF) are likely to break.
</p>
-<a name="N10298"></a><a name="indirect-linking"></a>
+<a name="indirect-linking"></a>
<h3 class="underlined_5">Indirect linking</h3>
<p>
Forrest's solution is simple: instead of <a href="todo.html">,
@@ -895,7 +895,7 @@ document.write("Last Published: " + docu
"idea" of "the todo file". It doesn't matter where it physically
lives; that will be sorted out by Forrest.
</p>
-<a name="N102BF"></a><a name="resolve-site-uris"></a>
+<a name="resolve-site-uris"></a>
<h4>Resolving site: URIs</h4>
<p>
So how does "<span class="codefrag">site:todo</span>" get resolved? A full answer is
@@ -931,7 +931,7 @@ document.write("Last Published: " + docu
make "new_content_type" its own XML file, or a node in another file,
in another category.
</p>
-<a name="N102FD"></a><a name="resolve-ext-uris"></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
@@ -970,7 +970,7 @@ document.write("Last Published: " + docu
Specifically, the "@href" aggregation makes defining large numbers
of related URLs easy.
</p>
-<a name="N10330"></a><a name="source-uris"></a>
+<a name="source-uris"></a>
<h4>Theory: source URIs</h4>
<p>
The "<span class="codefrag">site:</span>" URIs like "<span class="codefrag">site:todo</span>" are
@@ -987,7 +987,7 @@ document.write("Last Published: " + docu
just like exotic XML source formats are translated into plain old
HTML in the output.
</p>
-<a name="N1034F"></a><a name="future-schemes"></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
@@ -1068,7 +1068,7 @@ document.write("Last Published: " + docu
</p>
</div>
-<a name="N103FB"></a><a name="concept"></a>
+<a name="concept"></a>
<h2 class="underlined_10">Concept</h2>
<div class="section">
<p>
@@ -1083,7 +1083,7 @@ document.write("Last Published: " + docu
</p>
</div>
-<a name="N10412"></a><a name="implementation"></a>
+<a name="implementation"></a>
<h2 class="underlined_10">Implementation</h2>
<div class="section">
<p>