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/18 04:47:07 UTC
svn commit: rev 54985 - in forrest/site: . docs
Author: crossley
Date: Sun Oct 17 19:47:07 2004
New Revision: 54985
Modified:
forrest/site/docs/upgrading_06.html
forrest/site/docs/upgrading_06.pdf
forrest/site/docs/your-project.html
forrest/site/docs/your-project.pdf
forrest/site/forrest-issues.html
forrest/site/forrest-issues.pdf
Log:
Open issues for 0.7
Note about catalog entity resolver when integrating forrest with a project build.
Modified: forrest/site/docs/upgrading_06.html
==============================================================================
--- forrest/site/docs/upgrading_06.html (original)
+++ forrest/site/docs/upgrading_06.html Sun Oct 17 19:47:07 2004
@@ -489,12 +489,12 @@
<h2 class="underlined_10">forrest.antproxy.xml is obsolete in favor of Ant's <import> task</h2>
<div class="section">
<p>
- Projects that use <span class="codefrag">forrest.antproxy.xml</span> via and Ant build
+ Projects that use <span class="codefrag">forrest.antproxy.xml</span> via an Ant build
task to invoke Forrest, will receive
an error message directing them to this document.
Please see the <a href="../docs/your-project.html#invoking_from_ant">Invoking
Forrest from Ant</a> documentation for instructions on how to use
- the <import> task.
+ the <import> task to integrate Forrest with your build system.
</p>
</div>
Modified: forrest/site/docs/upgrading_06.pdf
==============================================================================
Binary files. No diff available.
Modified: forrest/site/docs/your-project.html
==============================================================================
--- forrest/site/docs/your-project.html (original)
+++ forrest/site/docs/your-project.html Sun Oct 17 19:47:07 2004
@@ -1418,12 +1418,18 @@
</target>
</project>
</pre>
-<p>(Note: That technique requires Ant 1.6+ otherwise the <import>
+<p>Because you are using your own version
+ of Ant to do Forrest's work, you will need to provide the
+ supporting catalog entity resolver:
+ '<span class="codefrag">cp forrest/lib/xml-commons-resolver-1.1.jar $ANT_HOME/lib</span>'
+ </p>
+<p>Note: The technique described above requires Ant 1.6+ otherwise
+ the <import>
task will not be available for you to use. Forrest
bundles the latest version of Ant, so you can invoke your project
- like this: <span class="codefrag">forrest -f myproject.xml</span>.
- This will not run forrest; it will just use Forrest's Ant to execute
- your buildfile.)
+ like this: '<span class="codefrag">forrest -f myproject.xml</span>'.
+ This will not run the '<span class="codefrag">forrest</span>' command. It will just
+ use Forrest's Ant and resolver to execute your buildfile.
</p>
<p>
Another option is to use the Forrest Antlet from the Krysalis Project's <a class="external" href="http://antworks.sourceforge.net/importer/">Antworks Importer</a>.
Modified: forrest/site/docs/your-project.pdf
==============================================================================
Binary files. No diff available.
Modified: forrest/site/forrest-issues.html
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Sun Oct 17 19:47:07 2004
@@ -152,6 +152,85 @@
<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
</div>
<h1>Open issues for the upcoming release</h1>
+<div id="minitoc-area">
+<ul class="minitoc">
+<li>
+<a href="#%5BFOR-305%5D+Need+FAQ+to+explain+character+encoding+for+certain+languages">[FOR-305] Need FAQ to explain character encoding for certain languages</a>
+</li>
+<li>
+<a href="#%5BFOR-298%5D+Revise+the+build+system+to+remove+relics+which+were+prior+to+copyless+method">[FOR-298] Revise the build system to remove relics which were prior to copyless method</a>
+</li>
+<li>
+<a href="#%5BFOR-284%5D+%27error%3A%27+prepending+problems">[FOR-284] 'error:' prepending problems</a>
+</li>
+<li>
+<a href="#%5BFOR-278%5D+Extend+the+forrest+webapp+with+%22lenya%22+functionality+or+vice+versa">[FOR-278] Extend the forrest webapp with "lenya" functionality or vice versa</a>
+</li>
+<li>
+<a href="#%5BFOR-277%5D+investigate+use+of+forrest-0.6-dev+as+webapp+with+Tomcat+5">[FOR-277] investigate use of forrest-0.6-dev as webapp with Tomcat 5</a>
+</li>
+<li>
+<a href="#%5BFOR-259%5D+openoffice+files+can+skip+sections">[FOR-259] openoffice files can skip sections</a>
+</li>
+<li>
+<a href="#%5BFOR-247%5D+Tigris+*.css+need+cleanup+to+remove+our+local+changes">[FOR-247] Tigris *.css need cleanup to remove our local changes</a>
+</li>
+<li>
+<a href="#%5BFOR-241%5D+forrest+undoes+entity+resolution">[FOR-241] forrest undoes entity resolution</a>
+</li>
+<li>
+<a href="#%5BFOR-237%5D+xml+stylesheets+unnecessary+copied+to+deployed+site">[FOR-237] xml stylesheets unnecessary copied to deployed site</a>
+</li>
+<li>
+<a href="#%5BFOR-235%5D+Cannot+use+Ctrl-C+to+shutdown+demo+forrest+run+with+jdk1.3">[FOR-235] Cannot use Ctrl-C to shutdown demo forrest run with jdk1.3</a>
+</li>
+<li>
+<a href="#%5BFOR-233%5D+sub-project+seperation">[FOR-233] sub-project seperation</a>
+</li>
+<li>
+<a href="#%5BFOR-232%5D+skin+fetching+cleanup">[FOR-232] skin fetching cleanup</a>
+</li>
+<li>
+<a href="#%5BFOR-230%5D+forrestbot+log+workstages">[FOR-230] forrestbot log workstages</a>
+</li>
+<li>
+<a href="#%5BFOR-229%5D+SVG+not+converted+to+PNG">[FOR-229] SVG not converted to PNG</a>
+</li>
+<li>
+<a href="#%5BFOR-224%5D+All+documentation+needs+review%2C+to+be+up-to-date+with+copyless+procedure">[FOR-224] All documentation needs review, to be up-to-date with copyless procedure</a>
+</li>
+<li>
+<a href="#%5BFOR-220%5D+Include+the+pdf-tab.xmap+as+standard+feature">[FOR-220] Include the pdf-tab.xmap as standard feature</a>
+</li>
+<li>
+<a href="#%5BFOR-218%5D+HowTo+about+tab+specific+PDF">[FOR-218] HowTo about tab specific PDF</a>
+</li>
+<li>
+<a href="#%5BFOR-217%5D+Certain+patterns+are+claimed+by+the+default+sitemaps">[FOR-217] Certain patterns are claimed by the default sitemaps</a>
+</li>
+<li>
+<a href="#%5BFOR-215%5D+site.lucene+name+colaps+with+site.html+request">[FOR-215] site.lucene name colaps with site.html request</a>
+</li>
+<li>
+<a href="#%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links">[FOR-211] whole-site html and pdf: broken ext links</a>
+</li>
+<li>
+<a href="#%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links">[FOR-210] whole-site html and pdf: broken link faq, broken image links</a>
+</li>
+<li>
+<a href="#%5BFOR-204%5D+Broken+link+summary+include+the+referencing+URLs">[FOR-204] Broken link summary include the referencing URLs</a>
+</li>
+<li>
+<a href="#%5BFOR-201%5D+Common+template+to+add+alternate+views+in+docs">[FOR-201] Common template to add alternate views in docs</a>
+</li>
+<li>
+<a href="#%5BFOR-200%5D+Locationmap+for+Forrest+and+Users">[FOR-200] Locationmap for Forrest and Users</a>
+</li>
+<li>
+<a href="#%5BFOR-197%5D+Link+for+whole-site+docs">[FOR-197] Link for whole-site docs</a>
+</li>
+</ul>
+</div>
<div class="frame note">
<div class="label">Note</div>
<div class="content">These are the open issues for our upcoming release listed in our
@@ -159,6 +238,366 @@
(see
<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-305%5D+Need+FAQ+to+explain+character+encoding+for+certain+languages"></a>
+<h2 class="underlined_10">[FOR-305] Need FAQ to explain character encoding for certain languages</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-305">http://issues.cocoondev.org//browse/FOR-305</a>
+</p>
+<p>imediatlly after a fresh "forrest seed", if I run "forrest validate" it stops saying "BUILD FAILLED" in any .xml file that contains characters with accents, which are very common in portuguese, german, french and other languages...</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>
+<h2 class="underlined_10">[FOR-298] Revise the build system to remove relics which were prior to copyless method</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-298">http://issues.cocoondev.org//browse/FOR-298</a>
+</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>
+<h2 class="underlined_10">[FOR-284] 'error:' prepending problems</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-284">http://issues.cocoondev.org//browse/FOR-284</a>
+</p>
+<p>'error:' prepending, for site: and ext: links that were not found, causes problems.
+<br>
+
+<br>
+For example, if in xdocs/samples I have ext:dtd-docs, Cocoon will search for samples/ext:dtd-docs, which of course does not exist.
+<br>
+
+<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>
+<h2 class="underlined_10">[FOR-278] Extend the forrest webapp with "lenya" functionality or vice versa</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-278">http://issues.cocoondev.org//browse/FOR-278</a>
+</p>
+<p>Link: <a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=109411643128812&w=2">http://marc.theaimsgroup.com/?l=forrest-dev&m=109411643128812&w=2</a>
+<br>
+
+<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>
+<h2 class="underlined_10">[FOR-277] investigate use of forrest-0.6-dev as webapp with Tomcat 5</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-277">http://issues.cocoondev.org//browse/FOR-277</a>
+</p>
+<p>Some people report having troubles running Forrest as a webapp under Tomcat. Needs investigation before 0.6 release.
+<br>
+
+<br>
+This is the background email to forrest-users:
+<br>
+ <a href="http://mail-archives.apache.org/eyebrowse/ReadMsg?listId=260&msgNo=282">http://mail-archives.apache.org/eyebrowse/ReadMsg?listId=260&msgNo=282</a>
+<br>
+ Forrest 0.6 Interaction with Tomcat 5.0.27
+<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>
+<h2 class="underlined_10">[FOR-259] openoffice files can skip sections</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-259">http://issues.cocoondev.org//browse/FOR-259</a>
+</p>
+<p>Create an openoffice file with lines like this:
+<br>
+
+<br>
+Heading 2
+<br>
+Heading 3
+<br>
+Heading 4
+<br>
+Heading 9
+<br>
+Heading 2
+<br>
+
+<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>
+<h2 class="underlined_10">[FOR-247] Tigris *.css need cleanup to remove our local changes</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-247">http://issues.cocoondev.org//browse/FOR-247</a>
+</p>
+<p>We have made some local changes to our copies of the tigris *.css which actually need to go into an over-riding css. Also remove our license notice which was added by accident.
+<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>
+<h2 class="underlined_10">[FOR-241] forrest undoes entity resolution</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-241">http://issues.cocoondev.org//browse/FOR-241</a>
+</p>
+<p>If I have a url like this inside the XML source:
+<br>
+
+<br>
+<a href="http://sourceforge.net/sflogo.php?group_id=comics-grabber&type=1">http://sourceforge.net/sflogo.php?group_id=comics-grabber&type=1</a>
+<br>
+
+<br>
+validate-xdocs fails because it wants the literal & to be typed out as
+<br>
+&amp; instead. So I correct it to become:
+<br>
+
+<br>
+<a href="http://sourceforge.net/sflogo.php?group_id=comics-grabber&type=1">http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;type=1</a>
+<br>
+
+<br>
+However, the generated HTML has the entity resolution UNDONE!:
+<br>
+
+<br>
+<a href="http://sourceforge.net/sflogo.php?group_id=comics-grabber&type=1">http://sourceforge.net/sflogo.php?group_id=comics-grabber&type=1</a>
+<br>
+
+<br>
+This HTML fails validation as 4.01 transitional.
+<br>
+
+<br>
+David Crossley adds:
+<br>
+There is a demonstration of the problem in the document
+<br>
+src/documentation/content/xdocs/docs/dreams.xml
+<br>
+The ampersand in the link element text is properly handled but
+<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>
+<h2 class="underlined_10">[FOR-237] xml stylesheets unnecessary copied to deployed site</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-237">http://issues.cocoondev.org//browse/FOR-237</a>
+</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-235%5D+Cannot+use+Ctrl-C+to+shutdown+demo+forrest+run+with+jdk1.3"></a>
+<h2 class="underlined_10">[FOR-235] Cannot use Ctrl-C to shutdown demo forrest run with jdk1.3</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-235">http://issues.cocoondev.org//browse/FOR-235</a>
+</p>
+<p>After doing 'forrest run' cannot shutdown the demo with Ctrl-C when running on jdk-1.3 (all is okay with jdk-1.4).</p>
+</div>
+<a name="N1009D"></a><a name="%5BFOR-233%5D+sub-project+seperation"></a>
+<h2 class="underlined_10">[FOR-233] sub-project seperation</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-233">http://issues.cocoondev.org//browse/FOR-233</a>
+</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="N100AB"></a><a name="%5BFOR-232%5D+skin+fetching+cleanup"></a>
+<h2 class="underlined_10">[FOR-232] skin fetching cleanup</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-232">http://issues.cocoondev.org//browse/FOR-232</a>
+</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="N100B9"></a><a name="%5BFOR-230%5D+forrestbot+log+workstages"></a>
+<h2 class="underlined_10">[FOR-230] forrestbot log workstages</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-230">http://issues.cocoondev.org//browse/FOR-230</a>
+</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="N100C7"></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>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-229">http://issues.cocoondev.org//browse/FOR-229</a>
+</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="N100D5"></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>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-224">http://issues.cocoondev.org//browse/FOR-224</a>
+</p>
+<p>Since the change to copyless there is stacks of documentation that needs to be modified.</p>
+</div>
+<a name="N100E3"></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>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-220">http://issues.cocoondev.org//browse/FOR-220</a>
+</p>
+<p>This feature will allow aggregate parts of the site.xml like described in the howto that was added because of FOR-218.
+<br>
+
+<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="N100F1"></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>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-218">http://issues.cocoondev.org//browse/FOR-218</a>
+</p>
+<p>>Hello devs,
+<br>
+>> Stephan Schlierf posted me a HowTo about tab specific PDF as a XML-doc.12.
+<br>
+>>
+<br>
+>> Now my question is where should I put it into the documentation?
+<br>
+>> So far I could not find any place in our site for HowTos.
+<br>
+
+<br>
+
+<br>
+We used to have a section called Community with HowTos
+<br>
+but that was deliberately hidden in the re-organisation
+<br>
+to /docs/ ... most of those were demonstration docs.
+<br>
+
+<br>
+Now that we have a real one we can bring them back.
+<br>
+
+<br>
+Adding them to the Documentation tab will get cumbersome
+<br>
+when we have more of them. So how about adding another
+<br>
+tab called HowTo which lists the stuff that is in /docs/howto/
+<br>
+
+<br>
+</p>
+</div>
+<a name="N100FF"></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>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-217">http://issues.cocoondev.org//browse/FOR-217</a>
+</p>
+<p>Users are prevented from using certain filenames because those patterns are claimed by the default sitemaps for special processing. These include: site, changes, todo, faq, images, my-images, skinconf,
+<br>
+</p>
+</div>
+<a name="N1010D"></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>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-215">http://issues.cocoondev.org//browse/FOR-215</a>
+</p>
+<p>Any link called site.html or site.pdf produce a loop on the search funcionality.
+<br>
+
+<br>
+The reason is an internal request called <a href="cocoon://site.lucene">cocoon://site.lucene</a> a work around would be to choose another name for this internal request.
+<br>
+
+<br>
+But this means that a request called /index-creation.html would have the same problem.
+<br>
+
+<br>
+
+<br>
+</p>
+</div>
+<a name="N1011B"></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>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-211">http://issues.cocoondev.org//browse/FOR-211</a>
+</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="N10129"></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>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-210">http://issues.cocoondev.org//browse/FOR-210</a>
+</p>
+<p>The "fresh-site" build from 'forrest seed site' reports some failures for faq.html and various missing images. Wonder if sitemap issue?
+<br>
+
+<br>
+</p>
+</div>
+<a name="N10137"></a><a name="%5BFOR-204%5D+Broken+link+summary+include+the+referencing+URLs"></a>
+<h2 class="underlined_10">[FOR-204] Broken link summary include the referencing URLs</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-204">http://issues.cocoondev.org//browse/FOR-204</a>
+</p>
+<p>It would be helpful if the brokenlinks.xml file contained for each broken link a summary of files where the broken link occured.
+<br>
+
+<br>
+Example: test1.xml, test2.xml and test3.xml have a link to linkeddoc.xml. Now the linkeddoc.xml is moved to another directory but the test?.xml files are not updated. The brokenlinks.xml should contain something like:
+<br>
+
+<br>
+<link message="/old-file-path/linkeddoc.xml (No such file or directory)">
+<br>
+ <name>linkdeddoc.html</name>
+<br>
+ <document>/file-path/test1.xml</document>
+<br>
+ <document>/file-path/test2.xml</document>
+<br>
+ <document>/file-path/test3.xml</document>
+<br>
+</link></p>
+</div>
+<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>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-201">http://issues.cocoondev.org//browse/FOR-201</a>
+</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="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>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-200">http://issues.cocoondev.org//browse/FOR-200</a>
+</p>
+<p>The locationmap gives us the ability to specify where sources are, both for Forrest and for the users.
+<br>
+
+<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="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>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-197">http://issues.cocoondev.org//browse/FOR-197</a>
+</p>
+<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>
</div>
<!--+
Modified: forrest/site/forrest-issues.pdf
==============================================================================
Binary files. No diff available.