You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by cr...@apache.org on 2004/10/29 08:24:08 UTC
svn commit: rev 55946 - in forrest/site: . howto
Author: crossley
Date: Thu Oct 28 23:24:07 2004
New Revision: 55946
Modified:
forrest/site/changes.html
forrest/site/changes.pdf
forrest/site/changes.rss
forrest/site/changes.xml
forrest/site/forrest-issues.html
forrest/site/forrest-issues.pdf
forrest/site/howto/howto-pdf-tab.html
forrest/site/howto/howto-pdf-tab.pdf
Log:
Publish the recent changes to "howto-pdf-tab".
Modified: forrest/site/changes.html
==============================================================================
--- forrest/site/changes.html (original)
+++ forrest/site/changes.html Thu Oct 28 23:24:07 2004
@@ -240,10 +240,16 @@
This fixes the issue building the apache fop site.
Replace libraries from the cocoon 2.2.0-dev version.
(JJP)</li>
+<li>
+<img class="icon" alt="update" src="images/update.jpg">
+ Updated How-To:
+ <a href="howto/howto-pdf-tab.html">How to create a PDF document for each
+ tab</a> to create subject-specific aggregated documents.
+ (TS)</li>
</ul>
</div>
-<a name="N1003D"></a><a name="version_0.6"></a>
+<a name="N10046"></a><a name="version_0.6"></a>
<h2 class="underlined_10">Version 0.6 (2004-10-15)</h2>
<div class="section">
<ul>
@@ -1077,7 +1083,7 @@
</div>
-<a name="N10491"></a><a name="version_0.5.1"></a>
+<a name="N1049A"></a><a name="version_0.5.1"></a>
<h2 class="underlined_10">Version 0.5.1 (2003-10-06)</h2>
<div class="section">
<ul>
@@ -1122,7 +1128,7 @@
</div>
-<a name="N104D7"></a><a name="version_0.5"></a>
+<a name="N104E0"></a><a name="version_0.5"></a>
<h2 class="underlined_10">Version 0.5 (2003-09-13)</h2>
<div class="section">
<ul>
@@ -1508,7 +1514,7 @@
</ul>
</div>
-<a name="N106E2"></a><a name="version_0.4"></a>
+<a name="N106EB"></a><a name="version_0.4"></a>
<h2 class="underlined_10">Version 0.4 (2003-02-12)</h2>
<div class="section">
<ul>
@@ -1594,7 +1600,7 @@
</div>
-<a name="N1074F"></a><a name="version_0.3"></a>
+<a name="N10758"></a><a name="version_0.3"></a>
<h2 class="underlined_10">Version 0.3 (2003-01-30)</h2>
<div class="section">
<ul>
@@ -1856,7 +1862,7 @@
</ul>
</div>
-<a name="N1088A"></a><a name="version_0.2"></a>
+<a name="N10893"></a><a name="version_0.2"></a>
<h2 class="underlined_10">Version 0.2 (2002-11-16)</h2>
<div class="section">
<ul>
@@ -1878,7 +1884,7 @@
</ul>
</div>
-<a name="N108A2"></a><a name="version_0.2rc1"></a>
+<a name="N108AB"></a><a name="version_0.2rc1"></a>
<h2 class="underlined_10">Version 0.2rc1 (2002-11-13)</h2>
<div class="section">
<ul>
Modified: forrest/site/changes.pdf
==============================================================================
Binary files. No diff available.
Modified: forrest/site/changes.rss
==============================================================================
--- forrest/site/changes.rss (original)
+++ forrest/site/changes.rss Thu Oct 28 23:24:07 2004
@@ -1,18 +1,18 @@
<?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE rss PUBLIC "-//Netscape Communications//DTD RSS 0.91//EN" "http://my.netscape.com/publish/formats/rss-0.91.dtd">
-<rss version="0.91"><channel><title>Forrest Changes</title><link>http://forrest.apache.org/changes.html</link><description>Forrest Changes</description><language>en-us</language><item><title>core add</title><link>http://forrest.apache.org/changes.html</link><description>core add
+<rss version="0.91"><channel><title> Changes</title><link>changes.html</link><description> Changes</description><language>en-us</language><item><title>core add</title><link>changes.html</link><description>core add
by
DC
:
Added to the document-v20 DTD to support usemap attribute in img tag.
Also added demonstration of client-side imagemap to the "seed site".
- Thanks to Tamara Harpster.</description></item><item><title>docs update</title><link>http://forrest.apache.org/changes.html</link><description>docs update
+ Thanks to Tamara Harpster.</description></item><item><title>docs update</title><link>changes.html</link><description>docs update
by
JJP
:
Added FAQ to explain character encoding for certain languages.
- Thanks to Joao Ferreira.</description></item><item><title>core add</title><link>http://forrest.apache.org/changes.html</link><description>core add
+ Thanks to Joao Ferreira.</description></item><item><title>core add</title><link>changes.html</link><description>core add
by
RDG
:
@@ -21,7 +21,7 @@
added through the addition of small code blocks (plugins). Plugins
are downloaded automatically when a site that requries them is built.
See Extending Forrest with Plugins.
- </description></item><item><title>core update</title><link>http://forrest.apache.org/changes.html</link><description>core update
+ </description></item><item><title>core update</title><link>changes.html</link><description>core update
by
JJP
:
@@ -29,7 +29,7 @@
Update fop0.20.5 just with optional jimi support.
This fixes the issue building the apache fop site.
Replace libraries from the cocoon 2.2.0-dev version.
- </description></item><item><title>core add</title><link>http://forrest.apache.org/changes.html</link><description>core add
+ </description></item><item><title>core add</title><link>changes.html</link><description>core add
by
DC
:
@@ -37,4 +37,12 @@
The brokenlinks file now contains referer information.
Upgraded lib/core/cocoon.jar and added attribute "show-referrers"
to the Cocoon cli.xconf
- Thanks to Upayavira.</description></item></channel></rss>
\ No newline at end of file
+ Thanks to Upayavira.</description></item><item><title>docs update</title><link>changes.html</link><description>docs update
+ by
+ TS
+ :
+
+ Updated How-To:
+ How to create a PDF document for each
+ tab to create subject-specific aggregated documents.
+ </description></item></channel></rss>
\ No newline at end of file
Modified: forrest/site/changes.xml
==============================================================================
--- forrest/site/changes.xml (original)
+++ forrest/site/changes.xml Thu Oct 28 23:24:07 2004
@@ -18,7 +18,11 @@
Update fop0.20.5 just with optional jimi support.
This fixes the issue building the apache fop site.
Replace libraries from the cocoon 2.2.0-dev version.
- (JJP)</li></ul></section>
+ (JJP)</li><li><icon alt="update" src="images/update.jpg"/>
+ Updated How-To:
+ <link href="site:pdf-tab">How to create a PDF document for each
+ tab</link> to create subject-specific aggregated documents.
+ (TS)</li></ul></section>
<section id="version_0.6"><title>Version 0.6 (2004-10-15)</title><ul><li><icon alt="add" src="images/add.jpg"/>
<!-- Please keep this action at the top -->
Added new document to facilitate
Modified: forrest/site/forrest-issues.html
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Thu Oct 28 23:24:07 2004
@@ -164,6 +164,12 @@
<div id="minitoc-area">
<ul class="minitoc">
<li>
+<a href="#%5BFOR-337%5D+Only+enable+plugins+required+by+a+site">[FOR-337] Only enable plugins required by a site</a>
+</li>
+<li>
+<a href="#%5BFOR-335%5D+Generate+Plugins+documentation">[FOR-335] Generate Plugins documentation</a>
+</li>
+<li>
<a href="#%5BFOR-310%5D+Support+embedded+open+office+images+%28and+Impress+files%29">[FOR-310] Support embedded open office images (and Impress files)</a>
</li>
<li>
@@ -232,12 +238,6 @@
<li>
<a href="#%5BFOR-197%5D+Link+for+whole-site+docs">[FOR-197] Link for whole-site docs</a>
</li>
-<li>
-<a href="#%5BFOR-187%5D+Redefine+project+documentation+dirs">[FOR-187] Redefine project documentation dirs</a>
-</li>
-<li>
-<a href="#%5BFOR-186%5D+Add+a+%22svg+on%22+button+for+seeing+all+svgs+natively">[FOR-186] Add a "svg on" button for seeing all svgs natively</a>
-</li>
</ul>
</div>
<div class="frame note">
@@ -248,7 +248,41 @@
<a class="external" href="http://issues.cocoondev.org/secure/IssueNavigator.jspa?pid=10000&resolutionIds=-1&tempMax=1000&reset=true">all</a> open issues).
The listing below is regenerated on each Forrest run.</div>
</div>
-<a name="N10011"></a><a name="%5BFOR-310%5D+Support+embedded+open+office+images+%28and+Impress+files%29"></a>
+<a name="N10011"></a><a name="%5BFOR-337%5D+Only+enable+plugins+required+by+a+site"></a>
+<h2 class="underlined_10">[FOR-337] Only enable plugins required by a site</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-337">http://issues.cocoondev.org//browse/FOR-337</a>
+</p>
+<p>At present when a plugin is requried by any site it is installed and used to build any subsequent site. This causes two problems:
+<br>
+
+<br>
+1) Performance is impacted by having unused mounts
+<br>
+2) any conflicts between plugins (e.g. simplified-docbook and docbook-full) may result in incorrect processing of a site
+<br>
+
+<br>
+What we need to do is have Forrest build the plugins/sitemap.xmap file before starting to build the site. This will result in only the plugins required by that site to be mounted for that particular run of Forrest.</p>
+</div>
+<a name="N1001F"></a><a name="%5BFOR-335%5D+Generate+Plugins+documentation"></a>
+<h2 class="underlined_10">[FOR-335] Generate Plugins documentation</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-335">http://issues.cocoondev.org//browse/FOR-335</a>
+</p>
+<p>When functionality is removed from Forrest core and placed in plugins the samples in the documentation and fresh-site should also be removed. However, this leaves us in the position where new Users cannot see the potential of Forrest + plugins.
+<br>
+
+<br>
+We need to include the documentation and samples within plugins in the Forrest website and also include a list of plugins and their funcitionality in fresh-site.
+<br>
+
+<br>
+</p>
+</div>
+<a name="N1002D"></a><a name="%5BFOR-310%5D+Support+embedded+open+office+images+%28and+Impress+files%29"></a>
<h2 class="underlined_10">[FOR-310] Support embedded open office images (and Impress files)</h2>
<div class="section">
<p>
@@ -268,7 +302,7 @@
<br>
It is recomended that this be done as part of the excercise to create an Open Office plugin so as to not to cause any disruption in trunk.</p>
</div>
-<a name="N1001F"></a><a name="%5BFOR-298%5D+Revise+the+build+system+to+remove+relics+which+were+prior+to+copyless+method"></a>
+<a name="N1003B"></a><a name="%5BFOR-298%5D+Revise+the+build+system+to+remove+relics+which+were+prior+to+copyless+method"></a>
<h2 class="underlined_10">[FOR-298] Revise the build system to remove relics which were prior to copyless method</h2>
<div class="section">
<p>
@@ -276,7 +310,7 @@
</p>
<p>There are some old targets in the build system that can be removed following the move to being "copyless". Some targets such as "copy-sitemap" have already had such parts removed, leaving them with a different purpose which doesn't match their name.</p>
</div>
-<a name="N1002D"></a><a name="%5BFOR-284%5D+%27error%3A%27+prepending+problems"></a>
+<a name="N10049"></a><a name="%5BFOR-284%5D+%27error%3A%27+prepending+problems"></a>
<h2 class="underlined_10">[FOR-284] 'error:' prepending problems</h2>
<div class="section">
<p>
@@ -292,7 +326,7 @@
<br>
@see declare-broken-site-links.xsl in teh core templates for more info.</p>
</div>
-<a name="N1003B"></a><a name="%5BFOR-278%5D+Extend+the+forrest+webapp+with+%22lenya%22+functionality+or+vice+versa"></a>
+<a name="N10057"></a><a name="%5BFOR-278%5D+Extend+the+forrest+webapp+with+%22lenya%22+functionality+or+vice+versa"></a>
<h2 class="underlined_10">[FOR-278] Extend the forrest webapp with "lenya" functionality or vice versa</h2>
<div class="section">
<p>
@@ -304,7 +338,7 @@
<br>
+-lenya should be integrated into forrest or vice versa. That makes it possible to edit the content in a WYSWYG editor! Again writing in tags can not be our aim! Lenya should take care of creating new, editing and archiving existing content. Namly site.xml, tab.xml and all other xdocs. With lenya we have as well workflow!</p>
</div>
-<a name="N10049"></a><a name="%5BFOR-277%5D+investigate+use+of+forrest-0.6-dev+as+webapp+with+Tomcat+5"></a>
+<a name="N10065"></a><a name="%5BFOR-277%5D+investigate+use+of+forrest-0.6-dev+as+webapp+with+Tomcat+5"></a>
<h2 class="underlined_10">[FOR-277] investigate use of forrest-0.6-dev as webapp with Tomcat 5</h2>
<div class="section">
<p>
@@ -322,7 +356,7 @@
<br>
Wed, 4 Aug 2004 10:18:34 -0500</p>
</div>
-<a name="N10057"></a><a name="%5BFOR-259%5D+openoffice+files+can+skip+sections"></a>
+<a name="N10073"></a><a name="%5BFOR-259%5D+openoffice+files+can+skip+sections"></a>
<h2 class="underlined_10">[FOR-259] openoffice files can skip sections</h2>
<div class="section">
<p>
@@ -346,7 +380,7 @@
<br>
The last two lines are not translated into sections.</p>
</div>
-<a name="N10065"></a><a name="%5BFOR-247%5D+Tigris+*.css+need+cleanup+to+remove+our+local+changes"></a>
+<a name="N10081"></a><a name="%5BFOR-247%5D+Tigris+*.css+need+cleanup+to+remove+our+local+changes"></a>
<h2 class="underlined_10">[FOR-247] Tigris *.css need cleanup to remove our local changes</h2>
<div class="section">
<p>
@@ -356,7 +390,7 @@
<br>
<a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=109169132601758">http://marc.theaimsgroup.com/?l=forrest-dev&m=109169132601758</a></p>
</div>
-<a name="N10073"></a><a name="%5BFOR-241%5D+forrest+undoes+entity+resolution"></a>
+<a name="N1008F"></a><a name="%5BFOR-241%5D+forrest+undoes+entity+resolution"></a>
<h2 class="underlined_10">[FOR-241] forrest undoes entity resolution</h2>
<div class="section">
<p>
@@ -402,7 +436,7 @@
<br>
the ampersand in the link href attribute is not.</p>
</div>
-<a name="N10081"></a><a name="%5BFOR-237%5D+xml+stylesheets+unnecessary+copied+to+deployed+site"></a>
+<a name="N1009D"></a><a name="%5BFOR-237%5D+xml+stylesheets+unnecessary+copied+to+deployed+site"></a>
<h2 class="underlined_10">[FOR-237] xml stylesheets unnecessary copied to deployed site</h2>
<div class="section">
<p>
@@ -410,7 +444,7 @@
</p>
<p>Why are forrest.css.xslt and skinconf.xsl copied over to the deployment location? They're not required there, and therefore should not be copied.</p>
</div>
-<a name="N1008F"></a><a name="%5BFOR-233%5D+sub-project+seperation"></a>
+<a name="N100AB"></a><a name="%5BFOR-233%5D+sub-project+seperation"></a>
<h2 class="underlined_10">[FOR-233] sub-project seperation</h2>
<div class="section">
<p>
@@ -418,7 +452,7 @@
</p>
<p>Subprojects that are not directly dependant on Forrest should be seperate modules (directories in SVN). This will allow SoC (seperation of concerns), separate releases, and per-subproject access control in SVN.</p>
</div>
-<a name="N1009D"></a><a name="%5BFOR-232%5D+skin+fetching+cleanup"></a>
+<a name="N100B9"></a><a name="%5BFOR-232%5D+skin+fetching+cleanup"></a>
<h2 class="underlined_10">[FOR-232] skin fetching cleanup</h2>
<div class="section">
<p>
@@ -426,7 +460,7 @@
</p>
<p>Fix skin fetching. It's an ugly combination of XSL and unusual ant tasks. It's also broken in at least one way: you get a malformed URL exception if you try to use a skin that doesn't exist. It should instead just say it doesn't exist.</p>
</div>
-<a name="N100AB"></a><a name="%5BFOR-230%5D+forrestbot+log+workstages"></a>
+<a name="N100C7"></a><a name="%5BFOR-230%5D+forrestbot+log+workstages"></a>
<h2 class="underlined_10">[FOR-230] forrestbot log workstages</h2>
<div class="section">
<p>
@@ -434,7 +468,7 @@
</p>
<p>forrestbot should log all workstages, not just the site build. it should also notify properly if a failure occurs in any workstage (e.g. cannot get source)</p>
</div>
-<a name="N100B9"></a><a name="%5BFOR-229%5D+SVG+not+converted+to+PNG"></a>
+<a name="N100D5"></a><a name="%5BFOR-229%5D+SVG+not+converted+to+PNG"></a>
<h2 class="underlined_10">[FOR-229] SVG not converted to PNG</h2>
<div class="section">
<p>
@@ -442,7 +476,7 @@
</p>
<p>See <a href="http://nagoya.apache.org/eyebrowse/BrowseList?listName=dev@forrest.apache.org&by=thread&from=828955">http://nagoya.apache.org/eyebrowse/BrowseList?listName=dev@forrest.apache.org&by=thread&from=828955</a></p>
</div>
-<a name="N100C7"></a><a name="%5BFOR-224%5D+All+documentation+needs+review%2C+to+be+up-to-date+with+copyless+procedure"></a>
+<a name="N100E3"></a><a name="%5BFOR-224%5D+All+documentation+needs+review%2C+to+be+up-to-date+with+copyless+procedure"></a>
<h2 class="underlined_10">[FOR-224] All documentation needs review, to be up-to-date with copyless procedure</h2>
<div class="section">
<p>
@@ -450,7 +484,7 @@
</p>
<p>Since the change to copyless there is stacks of documentation that needs to be modified.</p>
</div>
-<a name="N100D5"></a><a name="%5BFOR-220%5D+Include+the+pdf-tab.xmap+as+standard+feature"></a>
+<a name="N100F1"></a><a name="%5BFOR-220%5D+Include+the+pdf-tab.xmap+as+standard+feature"></a>
<h2 class="underlined_10">[FOR-220] Include the pdf-tab.xmap as standard feature</h2>
<div class="section">
<p>
@@ -462,7 +496,7 @@
<br>
The basic idea is to include the sitemaps described in the howto (src/documentation/content/xdocs/howto/howto-pdf-tab.xml) to the *.xmap folder. This way it will be possible to define aggregation parts with the attribute "wholesite='true'".</p>
</div>
-<a name="N100E3"></a><a name="%5BFOR-218%5D+HowTo+about+tab+specific+PDF"></a>
+<a name="N100FF"></a><a name="%5BFOR-218%5D+HowTo+about+tab+specific+PDF"></a>
<h2 class="underlined_10">[FOR-218] HowTo about tab specific PDF</h2>
<div class="section">
<p>
@@ -504,7 +538,7 @@
<br>
</p>
</div>
-<a name="N100F1"></a><a name="%5BFOR-217%5D+Certain+patterns+are+claimed+by+the+default+sitemaps"></a>
+<a name="N1010D"></a><a name="%5BFOR-217%5D+Certain+patterns+are+claimed+by+the+default+sitemaps"></a>
<h2 class="underlined_10">[FOR-217] Certain patterns are claimed by the default sitemaps</h2>
<div class="section">
<p>
@@ -514,7 +548,7 @@
<br>
</p>
</div>
-<a name="N100FF"></a><a name="%5BFOR-215%5D+site.lucene+name+colaps+with+site.html+request"></a>
+<a name="N1011B"></a><a name="%5BFOR-215%5D+site.lucene+name+colaps+with+site.html+request"></a>
<h2 class="underlined_10">[FOR-215] site.lucene name colaps with site.html request</h2>
<div class="section">
<p>
@@ -536,7 +570,7 @@
<br>
</p>
</div>
-<a name="N1010D"></a><a name="%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links"></a>
+<a name="N10129"></a><a name="%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links"></a>
<h2 class="underlined_10">[FOR-211] whole-site html and pdf: broken ext links</h2>
<div class="section">
<p>
@@ -544,7 +578,7 @@
</p>
<p>In the the generated site.html all of the external links are broken (i.e. the href attributes are like ... error:#ext:forrest).</p>
</div>
-<a name="N1011B"></a><a name="%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links"></a>
+<a name="N10137"></a><a name="%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links"></a>
<h2 class="underlined_10">[FOR-210] whole-site html and pdf: broken link faq, broken image links</h2>
<div class="section">
<p>
@@ -556,7 +590,7 @@
<br>
</p>
</div>
-<a name="N10129"></a><a name="%5BFOR-201%5D+Common+template+to+add+alternate+views+in+docs"></a>
+<a name="N10145"></a><a name="%5BFOR-201%5D+Common+template+to+add+alternate+views+in+docs"></a>
<h2 class="underlined_10">[FOR-201] Common template to add alternate views in docs</h2>
<div class="section">
<p>
@@ -564,7 +598,7 @@
</p>
<p>The pdf, xml, etc links should be in the document itself for all skins, and be removed when printing. A common template would make all skins look consistent in this regard.</p>
</div>
-<a name="N10137"></a><a name="%5BFOR-200%5D+Locationmap+for+Forrest+and+Users"></a>
+<a name="N10153"></a><a name="%5BFOR-200%5D+Locationmap+for+Forrest+and+Users"></a>
<h2 class="underlined_10">[FOR-200] Locationmap for Forrest and Users</h2>
<div class="section">
<p>
@@ -576,7 +610,7 @@
<br>
Beware that it will not work for raw files that are not linked, as this "feature" currently uses a fixed dir being being copied by Ant.</p>
</div>
-<a name="N10145"></a><a name="%5BFOR-197%5D+Link+for+whole-site+docs"></a>
+<a name="N10161"></a><a name="%5BFOR-197%5D+Link+for+whole-site+docs"></a>
<h2 class="underlined_10">[FOR-197] Link for whole-site docs</h2>
<div class="section">
<p>
@@ -585,26 +619,6 @@
<p>It's difficult for our users to find out how to make a whole-site pdf.
<br>
We should add an icon on the skins to download the whole-site pdf after accessing a page that explains that it's the *whole* site, and not just the page.</p>
-</div>
-<a name="N10153"></a><a name="%5BFOR-187%5D+Redefine+project+documentation+dirs"></a>
-<h2 class="underlined_10">[FOR-187] Redefine project documentation dirs</h2>
-<div class="section">
-<p>
-<a class="external" href="http://issues.cocoondev.org//browse/FOR-187">http://issues.cocoondev.org//browse/FOR-187</a>
-</p>
-<p>We should finalize all discussions about where to put sources and extensions in the projects.</p>
-</div>
-<a name="N10161"></a><a name="%5BFOR-186%5D+Add+a+%22svg+on%22+button+for+seeing+all+svgs+natively"></a>
-<h2 class="underlined_10">[FOR-186] Add a "svg on" button for seeing all svgs natively</h2>
-<div class="section">
-<p>
-<a class="external" href="http://issues.cocoondev.org//browse/FOR-186">http://issues.cocoondev.org//browse/FOR-186</a>
-</p>
-<p>Users that have an svg renderer installed can't get the svgs served nativaly in pages. It would be nice to have a button that can set the option on, so that I can see all svg images using that renderer.
-<br>
-
-<br>
-Note that discovering it automatically with javascript is very limited and buggy, so it's not a real option.</p>
</div>
</div>
<!--+
Modified: forrest/site/forrest-issues.pdf
==============================================================================
Binary files. No diff available.
Modified: forrest/site/howto/howto-pdf-tab.html
==============================================================================
--- forrest/site/howto/howto-pdf-tab.html (original)
+++ forrest/site/howto/howto-pdf-tab.html Thu Oct 28 23:24:07 2004
@@ -167,10 +167,7 @@
<a href="#sitemap">Create your project's main sitemap.xmap</a>
</li>
<li>
-<a href="#aggregator">Create the aggregator sitemap pdf-tab.xmap</a>
-</li>
-<li>
-<a href="#workaround-202">Edit project sitemap.xmap</a>
+<a href="#aggregator">Create another sitemap: pdf-tab.xmap</a>
</li>
<li>
<a href="#mount">Edit project sitemap.xmap to mount pdf-tab.xmap</a>
@@ -249,85 +246,72 @@
<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> based on the <span class="codefrag">aggregate.xmap</span>
-
-</p>
-<a name="N10054"></a><a name="sitemap"></a>
+ <span class="codefrag">pdf-tab.xmap</span>.
+ </p>
+<a name="N10051"></a><a name="sitemap"></a>
<h3 class="underlined_5">Create your project's main sitemap.xmap</h3>
<p>
- Simply copy the sitemap.xmap from the Forrest sitemaps at
- <span class="codefrag">${FORREST_HOME}/context/sitemap.xmap</span> into your
+ 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="N10064"></a><a name="aggregator"></a>
-<h3 class="underlined_5">Create the aggregator sitemap pdf-tab.xmap</h3>
+<a name="N1005E"></a><a name="aggregator"></a>
+<h3 class="underlined_5">Create another sitemap: pdf-tab.xmap</h3>
<p>
- Copy the aggregate.xmap from Forrest sitemaps into your
- ${project.sitemap-dir} and rename it to pdf-tab.xmap
+ Like before create an empty sitemap and name it pdf-tab.xmap.
</p>
-<a name="N1006E"></a><a name="workaround-202"></a>
-<h3 class="underlined_5">Edit project sitemap.xmap</h3>
-<div class="frame note">
-<div class="label">Note</div>
-<div class="content">
- This is a workaround for Issue FOR-202
- </div>
-</div>
-<p>
- Edit the project <span class="codefrag">sitemap.xmap</span> to comment-out the match
- for the sitemap like this:
- </p>
-<pre class="code">
-<!--
-<map:pipeline internal-only="false">
-<map:select type="exists">
- <map:when test="{project:sitemap}">
- <map:mount uri-prefix="" src="{project:sitemap}" check-reload="yes" />
- </map:when>
-</map:select>
-</map:pipeline
--->
- </pre>
-<a name="N10082"></a><a name="mount"></a>
+<a name="N10068"></a><a name="mount"></a>
<h3 class="underlined_5">Edit project sitemap.xmap to mount pdf-tab.xmap</h3>
<p>
- Insert the following lines after the
- <span class="codefrag"><map:match pattern="site.xml"></span>
- pipeline in the section called "SOURCE FORMATS".
+ Your sitemap should look something like this.
</p>
<pre class="code">
-...
-<map:match pattern="pdf-tab.xml">
- <map:mount uri-prefix="" src="pdf-tab.xmap" check-reload="yes" />
-</map:match>
-...
+<map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
+ <map:pipelines>
+ <map:pipeline internal-only="false">
+ <map:match pattern="**.xml">
+ <!-- pdf-tab definitions -->
+ <map:match pattern="pdf-tab.xml">
+ <map:mount uri-prefix="" src="pdf-tab.xmap"
+ check-reload="yes" />
+ </map:match>
+ <!-- end of pdf-tab definitions -->
+ </map:match>
+ </map:pipeline>
+ </map:pipelines>
+</map:sitemap>
</pre>
-<a name="N10093"></a><a name="edit-aggregator"></a>
+<a name="N10076"></a><a name="edit-aggregator"></a>
<h3 class="underlined_5">Edit the file pdf-tab.xmap</h3>
<p>
The <span class="codefrag"><map:match pattern="*.xml"></span> element
should look like the following:
</p>
<pre class="code">
-<map:match pattern="*.xml">
- <map:generate src="cocoon://abs-linkmap"/>
- <map:transform type="xpath">
- <map:parameter name="include" value="//*[@wholesite='true']"/>
- <map:parameter name="exclude" value="//*[@wholesite='false']"/>
- </map:transform>
- <map:transform src="resources/stylesheets/site2book.xsl" />
- <map:transform src="resources/stylesheets/aggregates/book2cinclude.xsl">
- <map:parameter name="title"
- value="{conf:project-name}: Still My Foo Site"/>
- </map:transform>
- <map:transform type="cinclude"/>
- <map:transform src="resources/stylesheets/aggregates/doc2doc-uniqueids.xsl"/>
- <map:transform src="resources/stylesheets/aggregates/docs2document.xsl"/>
- <map:serialize type="xml"/>
-</map:match>
+<map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
+ <map:pipelines>
+ <map:pipeline internal-only="false">
+ <map:match pattern="*.xml">
+ <map:generate src="cocoon://abs-linkmap"/>
+ <map:transform type="xpath">
+ <map:parameter name="include" value="//*[@wholesite='true']"/>
+ <map:parameter name="exclude" value="//*[@wholesite='false']"/>
+ </map:transform>
+ <map:transform src="resources/stylesheets/site2book.xsl" />
+ <map:transform src="resources/stylesheets/aggregates/book2cinclude.xsl">
+ <map:parameter name="title"
+ value="{conf:project-name}: Still My Foo Site"/>
+ </map:transform>
+ <map:transform type="cinclude"/>
+ <map:transform src="resources/stylesheets/aggregates/doc2doc-uniqueids.xsl"/>
+ <map:transform src="resources/stylesheets/aggregates/docs2document.xsl"/>
+ <map:serialize type="xml"/>
+ </map:match>
+ </map:pipeline>
+ </map:pipelines>
+</map:sitemap>
</pre>
-<a name="N100A6"></a><a name="edit-site"></a>
+<a name="N10089"></a><a name="edit-site"></a>
<h3 class="underlined_5">Edit your site.xml</h3>
<p>Add the following entry to your site.xml in the
<span class="codefrag"><about></span> element
@@ -368,7 +352,7 @@
as the child (will cause a <span class="codefrag">stack overflow</span> if you do)!!!
</div>
</div>
-<a name="N100D6"></a><a name="explain"></a>
+<a name="N100B9"></a><a name="explain"></a>
<h3 class="underlined_5">Explanation of the operation</h3>
<p>
Line 4 of our example
@@ -416,27 +400,10 @@
<span class="codefrag"><map:parameter name="title" value="{conf:project-name}: Still My Foo Site"/></span>
</p>
-<div class="frame note">
-<div class="label">Note</div>
-<div class="content">
- In the original <span class="codefrag">aggregate.xmap</span> there is the line
- <br>
-
-<span class="codefrag"><map:parameter name="ignore" value="{1}"/></span>
-
-<br>
- just before the title definition
- (<span class="codefrag"><map:parameter name="title" value=".../></span>).
- Be sure to delete it or comment it out if you like to generate a
- pdf-file for specific sites. You only need it for the generation of
- one pdf-file for the whole project (this is what
- <span class="codefrag">aggregate.xmap</span> usually does).
- </div>
-</div>
</div>
-<a name="N10121"></a><a name="Feedback and further development of this How-To"></a>
+<a name="N100F1"></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>
@@ -447,12 +414,6 @@
In the future, this ability will probably be incorporated into the
main Forrest process.
</p>
-<div class="frame fixme">
-<div class="label">Fixme (open)</div>
-<div class="content">
- This document will need to be modified when Issue FOR-202 is solved.
- </div>
-</div>
</div>
</div>
Modified: forrest/site/howto/howto-pdf-tab.pdf
==============================================================================
Binary files. No diff available.