This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
Re: DOCBOOK-APPS: Including C source code in a document
- To: Jorge Godoy <godoy at conectiva dot com>
- Subject: DOCBOOK: Re: DOCBOOK-APPS: Including C source code in a document
- From: Camille Bégnis <camille at mandrakesoft dot com>
- Date: Fri, 21 Jul 2000 16:36:53 +0200
- Cc: DocBookList <docbook at lists dot oasis-open dot org>
- Organization: MandrakeSoft
- References: <kpittzbngv.fsf@dagon.conectiva> <397857C4.58200183@detewe.de><kpaefbblup.fsf@dagon.conectiva>
Jorge Godoy a écrit :
>
> >>>>> "Michael" == Michael Wiedmann <michael.wiedmann@detewe.de> writes:
>
> > <programlisting> <![CDATA[ This is a programlisting so
> > white space and line breaks are significant. But it is
> > also a CDATA section so <emphasis>tags</emphasis> and
> > &entities; are not recognized. The only markup that is
> > recognized is the end-of-section marker, which is two
> > "]"'s in a row followed by a >. ]]> </programlisting>
>
> Thanks!
>
> This solution would require me to actually put the source in the
> document. Isn't there any solution that allow me to get the C file as
> an entity? This would be much more interesting since I'd always have
> the last version of the file without having to worry with modifying my
> document.
A long time ago Norman wrote:
-----------------------------------------
Personally, I use the following "hack"
<inlinegraphic fileref="fr/snippet.txt" format="linespecific">
My DSSSL stylesheets support this and the XSL stylesheets support it
with a little post-processing.
The long-term general solution to this problem is XLink.
-----------------------------------------
Jorge, does that solves your problem?
Norman, What about XLink now?
Camille.
--
Get your head off the keyboard and look behind the screen.