Ok, I haven't achieved my goal, which is causing docbook2.css to be
copied into the target directory. The xhtml references the
docbook2.css file though.
Ok, Dave are you saying that I need to preprocess the xsl
customization layer in order to expand the xinclude and drop the css
stuff inside? Then, after I have done this, I will have to process it
again? (something akin to two pass processing).
How would I do this with Saxon (if it's possible)? Would I need to do
two-pass processing (where I process it into an intermediary file?
***************************************
The problem is that I don't know what's going on with these
parameters, and what Bob's answer means. Am I including a css file or
an xml file which contains css information?
Dave Pawson replied:
The 'text' bit
<xi:include href="docbook2.css" parse="text"
says that it is plain text, i.e. not XML.
Hence as the extension says, you're pulling in css.
--
Robert Nagle
6121 Winsome Ln #56C, Houston TX 77057-5581
(H) 713 893 3424/ (W) 832-251-7522 Carbon Neutral Since Jan 2010
http://www.robertnagle.info
