forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <>
Subject Re: Storing DTDs in zips (Re: [PATCH] Docbook 4.1.2 support)
Date Thu, 02 Oct 2003 11:36:40 GMT
Jeff Turner wrote:
> 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:
>>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.
>>  <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" />
>  </sourcetype>
>  ...
>  <map:when test="changes-v12">
>    <map:transform src="resources/stylesheets/changes2document.xsl" />
>  </map:when>

That's not what I had in mind. In the current case you need to specify 
the style in the sitemap, I had something like this in mind instead:

   <get-private-sourcetype property = "private-id"/>
   <map:transform src="resources/stylesheets/{private-id}.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.

Many have asked how to do a certain thing, and invariably the answer has 
been to touch the sitemap. I don't want users touching sitemaps if 
possible, as those are *not* our contracts with the world (also replying 
to the following point).

The DocumentDTD *is* our contract, and by doing this we ensure that 90% 
of the needed extra features can be done with 10% the hassle.

IT will also make it easier for us to maintain xsls and DTDs, as we 
don't need to touch the sitemaps ourselves.

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

We would not maintain ours externally, we would still keep thsm locally. 
What we would enable is for others to add theirs, exactly like the skins.

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

View raw message