Re: DOCBOOK-APPS: Need help including c source

[Bob Stayton <bobs@caldera.com>]

> From: Yann Dirson <ydirson@alcove.fr>
> 
> On Thu, Oct 18, 2001 at 09:12:49AM -0700, Eric Richardson wrote:
> > I'm trying to include C source into docbook but I'm having problems with 
> > the #include <stdio.h>. I really would like to have the source compile 
> > as is and include as is into the document.
> 
> Instead of using an entity, you can use:
> 
> <imagedata fileref="foo.c" format="linespecific">
> 
> That roughly means, consider foo.c as an image encoded in the
> "linespecific" format - not a common way of looking at things, but
> semantically correct I think.
> 
> docbook-dsssl 1.73 should work out-of-the box with this construct, I
> don't know for sure about docbook-xsl, which I don't use.

Docbook-xsl should handle it if you are using Saxon or
Xalan processors, but not libxslt yet.  It requires
setting the params 'use.extensions' and
'textinsert.extension' to 1 so the text
insertion extensions in Saxon or Xalan will be utilized.

Without the extensions, the XSL output looks like this:

<div class="mediaobject"><a type="simple" show="embed"
  actuate="onLoad" href="foo.c"></a></div>

This is a bit of a hybrid between HTML and XLink,
since HTML doesn't have 'show' or 'actuate' attributes
for the <A> element. Since a browser won't 'show'
the link, and since the <A> element contains no
text, this is an invisible link.

bobs
Bob Stayton                                 400 Encinal Street
Publications Architect                      Santa Cruz, CA  95060
Technical Publications                      voice: (831) 427-7796
Caldera International, Inc.                 fax:   (831) 429-1887
                                            email: bobs@caldera.com