The following comment has been added to this issue:

     Author: Ross Gardler
    Created: Wed, 23 Feb 2005 4:50 PM
       Body:
Excellent contribution to our docs. There are a few spelling/grammatical 
errors, but I've ignored them for the moment. Here are the more important 
points:

---

"In doing the research for this How To, Ross Gardler taucht me so many 
interesting facts" 

- much as I appreciate the acknowledgement we don't directly reference 
developers in the docs. This is because over time many people will typically 
contribute to documents such as this.

---

"A basic understanding of coocons pipelines and their compontents." 
- perhaps a link to relevant Cocoon docs would be helpful, there are some links 
on http://forrest.apache.org/docs/your-project.html#sitemap.xmap

---

"If you plan on creating your own custom processing for
                                HTML-pages, you'll also need write access to 
Forrest's
                                project directory.
"

---

"Follow this link to the <a 
href="sitemap.xmap.html#%3C%21--Start+of+Sitemap--%3E">start of the 
Sitemap.</a>" 

- why a .html file?

---

"'*.xlex' that would match if our file ended with '.xlex'" 

- it's the request that needs to end with .xlex rather than the file.

---

"<source>
&lt;map:match pattern="**/*.html"&gt;
    &lt;map:aggregate element="site"&gt;
      &lt;map:part" 

- if you use "<source><![CDATA[ ... ]]></source>" 
there is no need to escape the '<' and '>' symbols. 

----

"<tr>
                                        <td>%1</td>
                                        <td>mybad</td>
                                        <td>the second match</td>
                                </tr>
"

- {2} matches the second match :-)

---

"At the output of this transformer we will have some rough kind of XHTML."

- probably better to say that we get a valid XML document.

---

"<fixme>I'm unclear about the calling of skinit here. Why is it called twice 
(in processing the body here and the final page later on), what is the 
difference?.</fixme>"

- the first call skins the body, whilst the second skins the whole page 
(including layount of menus and tabs) Note the value of the type parameter in 
each call.

---

<fixme>
I'm unclear about the translation from the property project.stylesheets-dir to 
the variable {forrest:stylesheets}. How and where does it take place and why 
are the names different? That seems very confusing!                             
    
</fixme>

- There is no such translation. The two values are not connected

---

" <strong>&lt;map:transform 
src="{forrest:stylesheets}/fixMyBadHTML.xsl"/&gt;</strong>"

- should be src="project:stylesheets-dir/fixMyBadHTML.xsl" 

---

A complete example, with the stylesheet and the source document would be great. 
But the document stands up as a good document even as it is.

Great work!
---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-446?page=comments#action_12086

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-446

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-446
    Summary: Dokumentation: HowTo Customize HTML Processing
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Forrest
 Components: 
             Documentation and website
   Versions:
             0.7

   Assignee: 
   Reporter: Ferdinand Soethe

    Created: Wed, 23 Feb 2005 2:24 PM
    Updated: Wed, 23 Feb 2005 4:50 PM

Description:
A long HowTo with lots of info on how Forrest processes requests for html 
document. Requires checking for facts, language and a few fixmes.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Reply via email to