Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <419A0CAE.6010008@apache.org>
Date: Tue, 16 Nov 2004 14:20:30 +0000
From: Ross Gardler <rgardler@apache.org>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
MIME-Version: 1.0
To: dev@forrest.apache.org
Subject: Re: Selective PDF
References: <200411141149.20071.sean@inwords.co.za>
 <200411160751.58073.sean@inwords.co.za> <4199F223.70605@apache.org>
 <200411161559.47386.sean@inwords.co.za>
In-Reply-To: <200411161559.47386.sean@inwords.co.za>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sean Wheller wrote:
> On Tuesday 16 November 2004 14:27, Ross Gardler wrote:
> 
>>Sean Wheller wrote:
>>
>>>On Tuesday 16 November 2004 02:51, Ross Gardler wrote:
>>>
>>>>How about this:
>>>>
>>>>Say we have an output plugin for PDF. It will have to provide an fbit
>>>>for the pdf button.
>>>>
>>>>In forrest properties we can have:
>>>>
>>>>plugin.pdf.button.include.output=**.html, documentation/index.html
>>>>plugin.pdf.button.exclude.output=**/index.html
>>>>
>>>>This will result in the "button" fbit provided by the pdf plugin being
>>>>placed on all html pages, but not on the index pages (except the
>>>>documentation index).
> 
> 
> Ok, I get it !!!

:-))

It was your itch care to implement it? (I'll help where I can)

>>>>*problem* how do we filter on source doctype?
> 
> 
> Hmm. Do we have to? I mean, source format to target formats is the idea no?

I'm not sure if it is a valid use case, I'm just thinking ahead (quite 
possibly too far ahead):

Suppose we have two xml source formats (i.e. *.xml files). One includes 
a TOC and another doesn't. We will want out TOC fbit to generate the TOC 
for one doctype but not for the other.

Ross