forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [JIRA] Commented: (FOR-446) Dokumentation: HowTo Customize HTML Processing
Date Thu, 24 Mar 2005 07:38:18 GMT
The following comment has been added to this issue:

     Author: Ferdinand Soethe
    Created: Thu, 24 Mar 2005 1:38 AM
Thanks for the feedback.

Re splitting

The reason I did not split them after some consideration, is that you really need to understand
what happens to be able to customize the pipeline documents properly (in fact that's how I
learned all this because I found that Ross just telling me what to do will raise further questions
right away). I'd be interested to know why you changed that.


Thanks for doing the CDATA-stuff. I learned about this too late to apply it to this howto.

Re annotated sitemaps

I agree with your concerns. But I figured that you really need to follow and see those steps
in the sitemap to understand what is going on. I'd be happy to use a different mechanism if
it is practical.

For a start I could add more genereal comments to sections of the sitemap. And if we find
a way to add some stable markers (comments?) to the sitemap I could perhaps use xincludes
to quote the sitemap. Any suggestions on if and how this could be done? 

View this comment:

View the issue:

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

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Forrest
             Documentation and website
   Fix Fors:

   Assignee: David Crossley
   Reporter: Ferdinand Soethe

    Created: Wed, 23 Feb 2005 2:24 PM
    Updated: Thu, 24 Mar 2005 1:38 AM

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

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message