Simply, I have an XSLT transformation which, when called on a DocBook
file from the command line (`xsltproc
~/.xxe2/config/docbook/xsl/change.xsl docbook-file.xml`) produces the
expected value, but when used from an XXE configuration, adds a tiny bit
of data in an unexpected way. In particular, the fileref attributes of
imagedata elements have the text "./" added at the beginning. I just
wanted to know where this data comes from. Of course, this fileref does
specify a URL location, but I don't know that there is any way for XXE
to know that a priori (as it is not specified anywhere in my
configuration).
Does this have anything to do with the cfg:documentResources element of
the parent configuration? How does this element affect transformations?
How can such potential behavior be controlled?
I have attached the zip file of the user configuration (as if it were to
be unzipped directly into ~/.xxe2/config/) for your perusal if needed.
My initial test document is proprietary; I can generate a generic test
document if necessary.
Take care,
John L. Clark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: docbook.zip
Type: application/octet-stream
Size: 5517 bytes
Desc: not available
Url :
http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20040421/752398eb/attachment.dll
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20040421/752398eb/attachment.sig
