Author: crossley
Date: Thu Nov 17 00:05:53 2005
New Revision: 345208
URL: http://svn.apache.org/viewcvs?rev=345208&view=rev
Log:
Automatic publish from forrestbot
Modified:
forrest/site/forrest-friday.html
forrest/site/forrest-friday.pdf
forrest/site/forrest-issues.html
forrest/site/forrest-issues.pdf
Modified: forrest/site/forrest-friday.html
URL:
http://svn.apache.org/viewcvs/forrest/site/forrest-friday.html?rev=345208&r1=345207&r2=345208&view=diff
==============================================================================
--- forrest/site/forrest-friday.html (original)
+++ forrest/site/forrest-friday.html Thu Nov 17 00:05:53 2005
@@ -302,6 +302,12 @@
</li>
<li>
+ See the irchelp.org
+ <a href="http://www.irchelp.org/irchelp/changuide.html";>guide</a>
+ for channel operators.
+ </li>
+
+<li>
Make sure that your irc client is creating a logfile.
</li>
Modified: forrest/site/forrest-friday.pdf
URL:
http://svn.apache.org/viewcvs/forrest/site/forrest-friday.pdf?rev=345208&r1=345207&r2=345208&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/forrest-issues.html
URL:
http://svn.apache.org/viewcvs/forrest/site/forrest-issues.html?rev=345208&r1=345207&r2=345208&view=diff
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Thu Nov 17 00:05:53 2005
@@ -201,9 +201,6 @@
<a
href="#%5BFOR-572%5D+run+a+memory+profiler+while+forrest+is+operating">[FOR-572]
run a memory profiler while forrest is operating</a>
</li>
<li>
-<a href="#%5BFOR-427%5D+Need+licensing+element+in+plugins.xml">[FOR-427] Need
licensing element in plugins.xml</a>
-</li>
-<li>
<a href="#%5BFOR-701%5D+Missing+locationmap+entry+gives+poor+error">[FOR-701]
Missing locationmap entry gives poor error</a>
</li>
<li>
@@ -231,9 +228,6 @@
<a href="#%5BFOR-343%5D+Upgrading+Plugins">[FOR-343] Upgrading Plugins</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-284%5D+link+rewriting+broken+when+linking+to+xml+source+views+which+contain+site%3A+links">[FOR-284]
link rewriting broken when linking to xml source views which contain site:
links</a>
</li>
<li>
@@ -260,6 +254,12 @@
<li>
<a href="#%5BFOR-187%5D+Redefine+project+documentation+dirs">[FOR-187]
Redefine project documentation dirs</a>
</li>
+<li>
+<a href="#%5BFOR-157%5D+skin-descriptors+comma+separated+list+fails">[FOR-157]
skin-descriptors comma separated list fails</a>
+</li>
+<li>
+<a
href="#%5BFOR-143%5D+Encoding+of+HTML+files+should+be+configurable">[FOR-143]
Encoding of HTML files should be configurable</a>
+</li>
</ul>
</div>
<div class="note">
@@ -340,16 +340,7 @@
</p>
<p>We need to run a memory profiler while forrest is operating.</p>
</div>
-<a name="N10057"></a><a
name="%5BFOR-427%5D+Need+licensing+element+in+plugins.xml"></a>
-<h2 class="underlined_10">[FOR-427] Need licensing element in plugins.xml</h2>
-<div class="section">
-<p>
-<a
href="http://issues.apache.org/jira/browse/FOR-427";>http://issues.apache.org/jira/browse/FOR-427</a>
-</p>
-<p>Since plugins can be hosted on different sites they can be released under
licenses other than the Apache one. We need an element in plugins.xml that
records the type of license a plugin is released under. This element should be
used by the plugin install process to verify that the user agrees to the terms
of that license before download and installation is started.<br>
-</p>
-</div>
-<a name="N10065"></a><a
name="%5BFOR-701%5D+Missing+locationmap+entry+gives+poor+error"></a>
+<a name="N10057"></a><a
name="%5BFOR-701%5D+Missing+locationmap+entry+gives+poor+error"></a>
<h2 class="underlined_10">[FOR-701] Missing locationmap entry gives poor
error</h2>
<div class="section">
<p>
@@ -361,7 +352,7 @@
<br>
We need to throw a meaningful error when when a resource cannot be found.</p>
</div>
-<a name="N10073"></a><a
name="%5BFOR-654%5D+Create+Schema+for+XHTML2+subset"></a>
+<a name="N10065"></a><a
name="%5BFOR-654%5D+Create+Schema+for+XHTML2+subset"></a>
<h2 class="underlined_10">[FOR-654] Create Schema for XHTML2 subset</h2>
<div class="section">
<p>
@@ -371,7 +362,7 @@
<br>
<a
href="http://marc.theaimsgroup.com/?l=forrest-dev&m=112489488330888&w=2">http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=112489488330888&amp;w=2</a></p>
</div>
-<a name="N10081"></a><a
name="%5BFOR-707%5D+Document+i18n+features+of+Forrest"></a>
+<a name="N10073"></a><a
name="%5BFOR-707%5D+Document+i18n+features+of+Forrest"></a>
<h2 class="underlined_10">[FOR-707] Document i18n features of Forrest</h2>
<div class="section">
<p>
@@ -391,7 +382,7 @@
<br>
We could, at the very least use the locationmap to pull this content into our
site [OT: I wonder if this could be a way to generate more documentation?)</p>
</div>
-<a name="N1008F"></a><a
name="%5BFOR-630%5D+Forrest+strategy+and+direction"></a>
+<a name="N10081"></a><a
name="%5BFOR-630%5D+Forrest+strategy+and+direction"></a>
<h2 class="underlined_10">[FOR-630] Forrest strategy and direction</h2>
<div class="section">
<p>
@@ -561,7 +552,7 @@
<br>
* [C] Content directory.</p>
</div>
-<a name="N1009D"></a><a
name="%5BFOR-388%5D+Use+plugins+in-place+if+src+available"></a>
+<a name="N1008F"></a><a
name="%5BFOR-388%5D+Use+plugins+in-place+if+src+available"></a>
<h2 class="underlined_10">[FOR-388] Use plugins in-place if src available</h2>
<div class="section">
<p>
@@ -577,7 +568,7 @@
<br>
</p>
</div>
-<a name="N100AB"></a><a
name="%5BFOR-675%5D+upgrading+to+commons-jxpath-1.2.jar+causes+failures+with+linkrewriter+protocols+site%3A+etc."></a>
+<a name="N1009D"></a><a
name="%5BFOR-675%5D+upgrading+to+commons-jxpath-1.2.jar+causes+failures+with+linkrewriter+protocols+site%3A+etc."></a>
<h2 class="underlined_10">[FOR-675] upgrading to commons-jxpath-1.2.jar causes
failures with linkrewriter protocols site: etc.</h2>
<div class="section">
<p>
@@ -585,7 +576,7 @@
</p>
<p>upgrading from commons-jxpath-20030909.jar to commons-jxpath-1.2.jar causes
failures with linkrewriter protocols site: etc. This happens in both modes:
'forret run' and 'forrest'.</p>
</div>
-<a name="N100B9"></a><a
name="%5BFOR-711%5D+Cache+results+from+the+Locationmap"></a>
+<a name="N100AB"></a><a
name="%5BFOR-711%5D+Cache+results+from+the+Locationmap"></a>
<h2 class="underlined_10">[FOR-711] Cache results from the Locationmap</h2>
<div class="section">
<p>
@@ -601,7 +592,7 @@
<br>
If we test all locationmaps and find no result we should record that tere is
no result in this hashmap. This will also be a good place to throw an exception
so that Cocoon can better report such errors (see FOR-701)</p>
</div>
-<a name="N100C7"></a><a
name="%5BFOR-490%5D+serve+multiple+sites+on+a+single+Forrest+instance"></a>
+<a name="N100B9"></a><a
name="%5BFOR-490%5D+serve+multiple+sites+on+a+single+Forrest+instance"></a>
<h2 class="underlined_10">[FOR-490] serve multiple sites on a single Forrest
instance</h2>
<div class="section">
<p>
@@ -624,7 +615,7 @@
(From Thread &quot;[RT] Serving Apache Forrest site from live
Forrest&quot;<br>
on dev-list. Will add link later.)</p>
</div>
-<a name="N100D5"></a><a name="%5BFOR-343%5D+Upgrading+Plugins"></a>
+<a name="N100C7"></a><a name="%5BFOR-343%5D+Upgrading+Plugins"></a>
<h2 class="underlined_10">[FOR-343] Upgrading Plugins</h2>
<div class="section">
<p>
@@ -634,20 +625,7 @@
<br>
We need a traget in the buildfile that will upgrade an indicated plugin when
possible. This can then (optionally) be used when running Forrest to
automatically upgrade plugins.</p>
</div>
-<a name="N100E3"></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
href="http://issues.apache.org/jira/browse/FOR-277";>http://issues.apache.org/jira/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>
-&nbsp;<a
href="http://mail-archives.apache.org/eyebrowse/ReadMsg?listId=260&msgNo=282">http://mail-archives.apache.org/eyebrowse/ReadMsg?listId=260&amp;msgNo=282</a><br>
-&nbsp;Forrest 0.6 Interaction with Tomcat 5.0.27<br>
-&nbsp;Wed, 4 Aug 2004 10:18:34 -0500</p>
-</div>
-<a name="N100F1"></a><a
name="%5BFOR-284%5D+link+rewriting+broken+when+linking+to+xml+source+views+which+contain+site%3A+links"></a>
+<a name="N100D5"></a><a
name="%5BFOR-284%5D+link+rewriting+broken+when+linking+to+xml+source+views+which+contain+site%3A+links"></a>
<h2 class="underlined_10">[FOR-284] link rewriting broken when linking to xml
source views which contain site: links</h2>
<div class="section">
<p>
@@ -655,7 +633,7 @@
</p>
<p>When linking to *.xml files (e.g. to demonstrate a source file) then if
that file contains &quot;site:&quot; or &quot;ext:&quot; links,
then they are reported as broken, e.g. docs/site:dtd-docs</p>
</div>
-<a name="N100FF"></a><a
name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
+<a name="N100E3"></a><a
name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
<h2 class="underlined_10">[FOR-241] character entities (e.g. ampersand) are
expanded again for href or src attributes</h2>
<div class="section">
<p>
@@ -701,7 +679,7 @@
<br>
the ampersand in the link href attribute is not.</p>
</div>
-<a name="N1010D"></a><a
name="%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links"></a>
+<a name="N100F1"></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>
@@ -711,7 +689,7 @@
<br>
</p>
</div>
-<a name="N1011B"></a><a
name="%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs"></a>
+<a name="N100FF"></a><a
name="%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs"></a>
<h2 class="underlined_10">[FOR-209] First level selected tab is not
highlighted when containing 2nd level tabs</h2>
<div class="section">
<p>
@@ -725,7 +703,7 @@
<br>
</p>
</div>
-<a name="N10129"></a><a
name="%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links"></a>
+<a name="N1010D"></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>
@@ -733,7 +711,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="N10137"></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>
@@ -748,7 +726,7 @@
<br>
</p>
</div>
-<a name="N10145"></a><a
name="%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately"></a>
+<a name="N10129"></a><a
name="%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately"></a>
<h2 class="underlined_10">[FOR-203] 2nd level tabs are not selected
appropriately</h2>
<div class="section">
<p>
@@ -770,7 +748,7 @@
<br>
&nbsp;&nbsp;Lorenz Froihofer.</p>
</div>
-<a name="N10153"></a><a name="%5BFOR-184%5D+Switch+to+XHTML2"></a>
+<a name="N10137"></a><a name="%5BFOR-184%5D+Switch+to+XHTML2"></a>
<h2 class="underlined_10">[FOR-184] Switch to XHTML2</h2>
<div class="section">
<p>
@@ -778,13 +756,72 @@
</p>
<p>Switch to using XHTML2 as a base and intermediate format. This means also
using RelaxNG validations, new sitemap pipelines, new stylesheets, new
input/output for &quot;views&quot;. See the steps in thread: <a
href="http://marc.theaimsgroup.com/?t=112512735800002">http://marc.theaimsgroup.com/?t=112512735800002</a></p>
</div>
-<a name="N10161"></a><a
name="%5BFOR-187%5D+Redefine+project+documentation+dirs"></a>
+<a name="N10145"></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
href="http://issues.apache.org/jira/browse/FOR-187";>http://issues.apache.org/jira/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="N10153"></a><a
name="%5BFOR-157%5D+skin-descriptors+comma+separated+list+fails"></a>
+<h2 class="underlined_10">[FOR-157] skin-descriptors comma separated list
fails</h2>
+<div class="section">
+<p>
+<a
href="http://issues.apache.org/jira/browse/FOR-157";>http://issues.apache.org/jira/browse/FOR-157</a>
+</p>
+<p>The second link does *not* read the url of the skin correctly.<br>
+<br>
+I repeated today the steps with a second skin:<br>
+1) create the skin<br>
+2) forrest package-skin<br>
+3) defined it in my descriptor <br>
+4) checked with &quot;forrest available-skins&quot;<br>
+5) forrest<br>
+<br>
+and it worked :)<br>
+<br>
+... dunno why it have not yesterday.<br>
+<br>
+Yes I do! I just changed:<br>
+forrest.skins.descriptors=<a
href="http://www.apache.org/~thorsten/whiteboard/forrestskins/skins.xml">http://www.apache.org/~thorsten/whiteboard/forrestskins/skins.xml</a><br>
+to<br>
+forrest.skins.descriptors=<a
href="http://xml.apache.org/forrest/skins/skins.xml,http://www.apache.org/~thorsten/whiteboard/forrestskins/skins.xml">http://xml.apache.org/forrest/skins/skins.xml,http://www.apache.org/~thorsten/whiteboard/forrestskins/skins.xml</a><br>
+<br>
+Trying to say something wrong with the &quot;comma seperated
list,&quot;. The second link do *not* work. In detail the url of the skin.
<br>
+<br>
+I just double checked as well the <a
href="file:///d:/get/skins.xml">file:///d:/get/skins.xml</a> and it
worked. When it stands alone but not in the comma seperated list.<br>
+</p>
+</div>
+<a name="N10161"></a><a
name="%5BFOR-143%5D+Encoding+of+HTML+files+should+be+configurable"></a>
+<h2 class="underlined_10">[FOR-143] Encoding of HTML files should be
configurable</h2>
+<div class="section">
+<p>
+<a
href="http://issues.apache.org/jira/browse/FOR-143";>http://issues.apache.org/jira/browse/FOR-143</a>
+</p>
+<p>From: Fabrice Bacchella <br>
+<br>
+<br>
+By default, HTML files are encoded in ISO-8859-1 because of the way the
Cocoon's HTML serialiser is declared in sitemap.xmap :<br>
+<br>
+&lt;map:serializer name=&quot;html&quot;
mime-type=&quot;text/html&quot;<br>
+src=&quot;org.apache.cocoon.serialization.HTMLSerializer&quot;&gt;<br>
+&nbsp;&nbsp;&lt;doctype-public&gt;-//W3C//DTD HTML 4.01
Transitional//EN&lt;/doctype-public&gt;<br>
+<br>
+&lt;doctype-system&gt;<a
href="http://www.w3.org/TR/html4/loose.dtd&lt;/doctype-system">http://www.w3.org/TR/html4/loose.dtd&amp;lt;/doctype-system</a>&gt;<br>
+&lt;/map:serializer&gt;<br>
+<br>
+The default one is such a case is ISO-8859-1. And it even add a META inthe
HTML result. But here in French, ISO-8859-15 is better because of the =AB e
dans l'o =BB character : =9C. In Russian or Asia, the <br>
+situation is even worse.<br>
+<br>
+Is that possible to add a properties in forrest.properties saying for example
:<br>
+project.encoding=UTF-8<br>
+<br>
+and adding a
&lt;encoding&gt;@project.encoding@&lt;/encoding&gt; element in
the<br>
+HTML serializer ?<br>
+<br>
+And in a more general way, where can I find a document about the way
properties are used by forrest ? Which files use them ? How to add a<br>
+new one ?</p>
</div>
</div>
<!--+
Modified: forrest/site/forrest-issues.pdf
URL:
http://svn.apache.org/viewcvs/forrest/site/forrest-issues.pdf?rev=345208&r1=345207&r2=345208&view=diff
==============================================================================
Binary files - no diff available.
