You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by ma...@koodiorja.com on 2003/02/18 10:05:25 UTC

Docbook instead of document-v11?

Hi,

is there an easy way to use Docbook XML as the documentation type
instead of the new document-v11? We have started documenting our
Cocoon project in docbook but would definitely want to take the
advantage of the possibilities the Forrest project offers (without
having to stop using the authoring environments we have managed to
build for docbook).

Perhaps a XSL style sheet that would transform docbook to document-v11
could do the trick? However, implementing a XSL stylesheet that would
support even most of the docbook DTD and document-v11 DTD would be
quite huge task so we're not able to allocate resources for such
tasks. Instead, we are looking for something more complete (or
faster/easier to implement).


Sincerely,
Keijo Lehto

Re: Docbook instead of document-v11?

Posted by Jeff Turner <je...@apache.org>.
On Wed, Feb 19, 2003 at 12:35:10AM -0800, Nick Chalko wrote:
> I tried this to get docbook to use the standard docbook stylesheets but 
> no luck

Try adding:

> <!-- if the file is present as dbk, use the docbook stylesheets... -->
>            <map:act type="resource-exists">
>               <map:parameter name="url" value="content/xdocs/{1}.dbk" />
>               <map:generate src="content/xdocs/{../1}.dbk" />

                <map:serialize type="xml"/>

>               <map:transform 
> src="file://P:/xml/docbook-xsl-1.60.1/docbook-xsl-1.60.1/xhtml/docbook.xsl" 
> />
>               <map:transform src="library/xslt/html2htmlbody.xsl" />
>               <map:transform type="linkrewriter" src="cocoon:/linkmap" />
>               <map:serialize type="xml" />
>            </map:act>


And then request http://localhost:8080/forrest/body-index.xml and see
what the intermediate XML output is.  If it looks good, move the
serializer down one.  I suspect that path is wrong..

Or talk Nicola into committing his Docbook stuff into into a branch.

--Jeff

 
> Any Ideas?
> 
> I don't really know what I am doing. but I am trying.
> 
> R,
> Nick
> 

Re: Docbook instead of document-v11?

Posted by Nick Chalko <ni...@chalko.com>.
I tried this to get docbook to use the standard docbook stylesheets but 
no luck
<!-- if the file is present as dbk, use the docbook stylesheets... -->
            <map:act type="resource-exists">
               <map:parameter name="url" value="content/xdocs/{1}.dbk" />
               <map:generate src="content/xdocs/{../1}.dbk" />
               <map:transform 
src="file://P:/xml/docbook-xsl-1.60.1/docbook-xsl-1.60.1/xhtml/docbook.xsl" 
/>
               <map:transform src="library/xslt/html2htmlbody.xsl" />
               <map:transform type="linkrewriter" src="cocoon:/linkmap" />
               <map:serialize type="xml" />
            </map:act>


Any Ideas?

I don't really know what I am doing. but I am trying.

R,
Nick


Re: Docbook instead of document-v11?

Posted by David Crossley <cr...@indexgeo.com.au>.
Jeff Turner wrote:
> mailarch@koodiorja.com wrote:
> > Hi,
> > 
> > is there an easy way to use Docbook XML as the documentation type
> > instead of the new document-v11? We have started documenting our
> > Cocoon project in docbook but would definitely want to take the
> > advantage of the possibilities the Forrest project offers (without
> > having to stop using the authoring environments we have managed to
> > build for docbook).
> > 
> > Perhaps a XSL style sheet that would transform docbook to document-v11
> > could do the trick? However, implementing a XSL stylesheet that would
> > support even most of the docbook DTD and document-v11 DTD would be
> > quite huge task so we're not able to allocate resources for such
> > tasks. Instead, we are looking for something more complete (or
> > faster/easier to implement).
> 
> There is already a library/xslt/docbook2document.xsl stylesheet that
> attempts a conversion.  Right now, out intermediate format (doc-v11)
> needs loosening up before it can accommodate full Docbook.
> 
> If you don't mind losing PDFs, it would be fairly easy to generate HTML
> directly from the Docbook using the docbook.sf.net stylesheets, and then
> merging it with the Forrest header and menus.  It would be only one step
> beyond Forrest's existing *.ehtml handling (raw HTML + headers + menus).

To get you started, if you are happy with plain content
with no headers or menus, then this previous email will
help. The only catch is that we needed to put a hard-coded
file:// url in the project sitemap.xmap to point to
the local docbook stylesheets.
http://marc.theaimsgroup.com/?l=forrest-dev&m=104449613910273

--David




Re: Docbook instead of document-v11?

Posted by Jeff Turner <je...@apache.org>.
On Tue, Feb 18, 2003 at 11:05:25AM +0200, mailarch@koodiorja.com wrote:
> Hi,
> 
> is there an easy way to use Docbook XML as the documentation type
> instead of the new document-v11? We have started documenting our
> Cocoon project in docbook but would definitely want to take the
> advantage of the possibilities the Forrest project offers (without
> having to stop using the authoring environments we have managed to
> build for docbook).
> 
> Perhaps a XSL style sheet that would transform docbook to document-v11
> could do the trick? However, implementing a XSL stylesheet that would
> support even most of the docbook DTD and document-v11 DTD would be
> quite huge task so we're not able to allocate resources for such
> tasks. Instead, we are looking for something more complete (or
> faster/easier to implement).

There is already a library/xslt/docbook2document.xsl stylesheet that
attempts a conversion.  Right now, out intermediate format (doc-v11)
needs loosening up before it can accommodate full Docbook.

If you don't mind losing PDFs, it would be fairly easy to generate HTML
directly from the Docbook using the docbook.sf.net stylesheets, and then
merging it with the Forrest header and menus.  It would be only one step
beyond Forrest's existing *.ehtml handling (raw HTML + headers + menus).


--Jeff


> Sincerely,
> Keijo Lehto