forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From scott hutinger <s-hutin...@wiu.edu>
Subject Re: plugin for DITA
Date Sun, 05 Dec 2004 12:06:15 GMT
Ross Gardler wrote:

> Dave Brondsema wrote:
>
>> Ross Gardler wrote:
>>
>>>
>>>
>>> Dave Brondsema wrote:
>>>
>>>> Ross Gardler wrote:
>>>>
>>>>> scott hutinger wrote:
>>>>>
>>>>>> It will take a bit to figure it all out, as it goes from a 
>>>>>> strange .dtd to other items.  Is this all going through the 
>>>>>> pipeline, or would it be multiple plugins.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> I couldn't be certain without knowing more about DITA, but I'll 
>>>>> give the generic answer:
>>>>>
>>>>> I have heard of DITA once before. In that thread it was mentioned 
>>>>> that there are a set of DITA to HTML XLST stylesheets. It would, 
>>>>> probably, be best to leverage those and not convert to Forrests 
>>>>> xdoc format.
>>>>>
>>>>> I would *guess* you need to:
>>>>>
>>>>> DITA --> HTML --> XDoc --> Forrest site
>>>>>      /\        /\       /\
>>>>>      1         2        3
>>>>>
>>>>> 1 would be the DITA XSLT's
>>>>>
>>>>> 2 would be the .xsl
>>>>>
>>>>> 3 is the normal Forrest stuff
>>>>>
>>>>> 1 & 2 would be your DITA input plugin.
>>>>>
>>>>
>>>> 2 is part of forrest core so the DITA input plugin should only do 
>>>> 1.  Right?
>>>
>>>
>
> ...
>
>> What I wanted to make clear is that the input plugin can produce an 
>> html document and that is enough.  It does not have to do the 
>> conversion to our current intermediate format (xdoc).
>
>
> +1
>
> Ross
>
If one were to completely control the output, then the transformation to 
html would be all one would need to do.  But to follow forrest, one 
could output to xdoc format.  Wouldn't it be better to transform to xdoc?

scott

Mime
View raw message