This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: imagedata format="linespecific"
- From: Bob Stayton <bobs at caldera dot com>
- To: Jeff Beal <jeff dot beal at ansys dot com>,"DocBook Mailing List (E-mail)" <docbook-apps at lists dot oasis-open dot org>
- Date: Fri, 22 Nov 2002 14:31:23 -0800
- Subject: Re: DOCBOOK-APPS: imagedata format="linespecific"
- References: <E08C8F26F6901D42B1201763D125853815B358@ntdevexc.win.ansys.com>
On Fri, Nov 22, 2002 at 03:30:43PM -0500, Jeff Beal wrote:
> I have been testing the <imagedata/> tag with format="linespecific" for
> inserting text files into my docs. I am using Saxon + XSL 1.57.0 and
> properly including the extension function on my CLASSPATH. The text is
> properly inserted into the FO and HTML, but it is not inside a line-specific
> environment, so the white space is not preserved when rendered. Is this a
> bug in the stylesheets, or the intentional rendering?
It's not a bug. But the term 'linespecific' in this case
is a red herring. The use of imagedata like this was a
kludge that simply hacked an available attribute to make the
trick work. The text inclusion mechanism itself doesn't
preserve white space in the output. You have to wrap it
in a programlisting or literallayout to indicate
presentation.
If you are using DTD version 4.2, you can use textobject
instead, and it doesn't mention linespecific.
But you still have to put it in a container.
See:
http://www.sagehill.net/xml/docbookxsl/SolveProblems.html#ExternalCode
for more information on both ways of doing it.
--
Bob Stayton 400 Encinal Street
Publications Architect Santa Cruz, CA 95060
Technical Publications voice: (831) 427-7796
The SCO Group fax: (831) 429-1887
email: bobs@sco.com