This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: Re: callouts and admonitions
- From: fyl2xp1 <vnhu38f93 at subdimension dot com>
- To: Bob Stayton <bobs at caldera dot com>, docbook-apps at lists dot oasis-open dot org
- Date: Tue, 09 Jul 2002 08:17:19 +0100
- Subject: Re: DOCBOOK-APPS: Re: callouts and admonitions
- References: <20020705103017.A19560@caldera.com>
thanks. It was an accident posting to the wrong list, sorry. (typed the
wrong thing in)
----- Original Message -----
From: "Bob Stayton" <bobs@caldera.com>
To: <docbook-apps@lists.oasis-open.org>
Sent: Friday, July 05, 2002 6:30 PM
Subject: DOCBOOK-APPS: Re: callouts and admonitions
> [I moved this thread to docbook-apps where it is more
> appropriate. The docbook list is for DTD discussion].
>
> > From: fyl2xp1 <vnhu38f93@subdimension.com>
> >
> > If I want to use the callouts or admonitions in my files I am currently
placing a copy of the images directory (a customised copy containing the
files I need) in the directory that I am executing the command sequences
needed to generate the files.
> >
> > This does not feel like it is the correct way to do this as I would
assume that the
> > style-sheet programs should create these directories automatically and
place any
> > files needed in them?
>
>
> That would be a nice feature, but XSLT has no facilities
> of its own to create directories and copy binary files.
> It would require extension functions.
>
> I presume you are running into this for print output, since
> HTML output processing just writes a path in IMG src
> attributes but doesn't actually access the graphics files.
>
> For print output you can use the 'callout.graphics.path'
> and 'admon.graphics.path' parameters with the FO stylesheet
> to set paths to where the graphics files are installed.
> Relative paths work too. That way you don't have to copy
> them around. They will get pulled into the PDF output by
> the FO processor. Be sure to include a trailing slash on
> the paths.
>
> For HTML processing, those parameter values are written into
> the IMG src pathnames, so they should represent the
> location of the images relative to the HTML files
> in the output.
>
> Copying the image files to the HTML output directory would be
> a nice feature, if the processor knows the output
> directory. But if you are just directing unchunked HTML output
> to a file, then the XSL processor doesn't know where it is going.
>
> I generally use Makefiles so I don't forget details
> like copying the image files to the output area.
> --
>
> 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