Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: forrest-dev@xml.apache.org
Date: Tue, 10 Dec 2002 03:44:16 +1100
From: Jeff Turner <jefft@apache.org>
To: forrest-dev@xml.apache.org
Subject: Re: Newbie question
Message-ID: <20021209164416.GC1638@expresso.localdomain>
Mail-Followup-To: forrest-dev@xml.apache.org
References: <3DF3DBE1.2070100@chalko.com>
 <006701c29f4d$9e1a0a00$7501a8c0@claudius>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <006701c29f4d$9e1a0a00$7501a8c0@claudius>
User-Agent: Mutt/1.4i

On Mon, Dec 09, 2002 at 02:38:33PM +0800, Hans E. Kristiansen wrote:
> I would like to publish a certificate using forrest. The problem is that the
> cert file always get the extension .html, rather than .crt. e.g. the file is
> called cacert.crt, but the generated file is always called cacert.crt.html
> (using "forrest site" command).
> 
> How do I ensure that the file extension is maintained during the publishing
> process.

It isn't really possible with the current Forrest.  See the mail I just
posted, "Adding protocols to links".  If I were you I'd wait to see what
happens on that thread.

The closest that can be achieved with today's Forrest is to stop Cocoon
adding the .html by filtering out the cacert.crt link, with a custom
sitemap:

http://cvs.apache.org/viewcvs/jakarta-avalon/src/documentation/sitemap.xmap?rev=1.20.2.4&content-type=text/vnd.viewcvs-markup

and stylesheet:

http://cvs.apache.org/viewcvs/jakarta-avalon/src/documentation/resources/stylesheets/Attic/avfilterlinks.xsl

Then cacert.crt would have to be copied manually.


--Jeff


> Thank you very much.
> 
> Regards,
> Hans E.
>