This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
Re: Inserting external code into docbook
- From: Bob Stayton <bobs at caldera dot com>
- To: Joachim Ziegler <ziegler at algorilla dot de>,DocBook <docbook at lists dot oasis-open dot org>
- Date: Thu, 24 Oct 2002 09:32:53 -0700
- Subject: Re: DOCBOOK: Inserting external code into docbook
- References: <200210231742.46136.ziegler@algorilla.de><20021023092609.A16330@caldera.com> <200210241506.55430.ziegler@algorilla.de>
On Thu, Oct 24, 2002 at 03:06:55PM +0200, Joachim Ziegler wrote:
> Am Mittwoch, 23. Oktober 2002 18:26 schrieb Bob Stayton:
> > Looking back in the archives, it seems that this is how you
> > do it with 4.1.2:
> >
> > <programlisting>
> > <inlinemediaobject>
> > <imageobject>
> > <imagedata fileref="myfunc.c" format="linespecific"/>
> > </imageobject>
> > </inlinemediaobject>
> > <programlisting>
>
> Yes, this is valid with 4.1.2
>
> But why isn't there an easier mechanism/markup for verbatim inclusion of text
> files? I suppose that this is something which occurs frequently. (?)
There is an easier way, and it was adopted in the 4.2 DTD:
<programlisting><textobject><textdata fileref="mycode.c" /></textobject>
</programlisting>
I can't explain why something like it was not added earlier.
--
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