forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <>
Subject Re: Storing DTDs in zips (Re: [PATCH] Docbook 4.1.2 support)
Date Thu, 02 Oct 2003 11:04:08 GMT
On Thu, Oct 02, 2003 at 11:44:03AM +0200, Nicola Ken Barozzi wrote:
> Jeff Turner wrote:
> >On Wed, Oct 01, 2003 at 02:11:57PM +0200, Nicola Ken Barozzi wrote:
> ...
> >>any case, the zip solution has other benefits too, so I favor it in
> >>any case (ie I don't see the size as an issue but like the idea 
> >>nevertheless).
> >
> >I'm having second-thoughts.. (sorry:), since DTD-aware editors want to be
> >pointed to the DTDs, not a .zip of them.
> I thought about it too, and have second-thought too, but of slightly 
> different nature ;-)
> What about doing (I propose myself for the job :-) a thing similar to 
> the one done with skins?
> I mean, we have skinpacks now, we can have DTD packs. Each DTD pack 
> contains the DTDs and the stylesheets that Forrest needs to transform 
> the source format to the documentDTD format (adaptor).
> How to make the Forrest sitemap use them? Simple, we make an action or 
> something that automatically maps DTDs to these adapter stylesheets.
> Example:
>   <public publicId="-//APACHE//DTD Changes V1.2//EN"
>           uri="dtd/changes-v12.dtd"/>
> Will use for this stylesheet:
>   blahblah/stylesheets/changes-v12.dtd.xsl

The SourceTypeAction does exactly that.

 <sourcetype name="changes-v12">
   <document-declaration public-id="-//APACHE//DTD Changes V1.2//EN" />
 <map:when test="changes-v12">
   <map:transform src="resources/stylesheets/changes2document.xsl" />

> As for the download and install I can use exactly the same scripts we 
> use for skins with some adjustments (to se what used DTDs are needed to 
> be downloaded).
> How does this sound?

We haven't exactly been swamped with requests for supporting obscure
DTDs, so I don't really see the need.

Also, DTDs we bundle are our contract with the world.  They are
fundamental to Forrest.  Why would we want to maintain them externally?


> -- 
> Nicola Ken Barozzi         
>             - verba volant, scripta manent -
>    (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------

View raw message