Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: forrest-dev@xml.apache.org
Message-ID: <3F1C350A.3010400@che-che.com>
Date: Mon, 21 Jul 2003 20:46:34 +0200
From: Juan Jose Pablos <cheche@che-che.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.2.1) Gecko/20030311 Debian/1.2.1-10
MIME-Version: 1.0
To: forrest-dev@xml.apache.org
Subject: Re: cvs commit: xml-forrest/src/resources/stylesheets
 text2document.xsl
References: <20030718001723.95409.qmail@icarus.apache.org>
 <3F173FE7.8090507@che-che.com>
 <1058529624.3f17e158bca52@secure.solidusdesign.com>
 <3F17E6BA.1070706@che-che.com>
 <1058533377.3f17f00190b31@secure.solidusdesign.com>
 <3F1B7A27.9000105@che-che.com>
 <1058793879.3f1be997bf162@secure.solidusdesign.com>
 <3F1BF4C5.1000807@apache.org> <3F1C13B3.4010700@che-che.com>
 <1058808958.3f1c247ec6691@secure.solidusdesign.com>
In-Reply-To: <1058808958.3f1c247ec6691@secure.solidusdesign.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Dave,

>>
>>As far as I am aware you only crawled files that are include on the 
>>book.xml / site.xml files.
> 
> 
> All links on a page are crawled, unless specified in filterlinks.xsl.
> 

The way the links got on a page is defined either on site.xml or a local 
  book.xml file.

> 
> I have seen a lot of different ideas and suggestions about Forrest's directories
> over just the few weeks I've been on the list.  I suggest we get a wiki set up,
> post all the different ideas and allow for comments.  After some time and
> perhaps IRC meetings, we could establish a firm vision of what the directories
> will look like in 0.5, 0.6, 1.0 or whatever.
> 

If there is a lot of ideas on this is because not many people like that 
set up.

Have you realize that no one talks about the use of "ant"?

I am not sure if the problem reside on the format we use to comunicate. 
But feel free to create a wiki to define this.

I do not think we are going to have any change on this release, but 
having a direction to follow would helps.


> 
> This would only be possible in a webapp, not a static generated website.  Even
> then, most browsers can handle most formats.  It is normally the end user who
> chooses if they want plain text (eg, to copy to a document), html (eg, to
> browse), pdf (eg, to print).
> 
> 

1) I can not see the technical reason of why "This would only be 
possible in a webapp". Please explain a bit futher.

2) I do not talks just on formats, It could be diferent language.

3) Not all the user agents are end users. A search engine bot who wants 
just the content in spanish.

It is not me who has these clever ideas (I wish!) , it is on the 
protocol stuff:  http://www.w3.org/Protocols/rfc2616/rfc2616-sec12.html


Cheers
Cheche