Hello David:
I am sorry I forgot to mention one piece of information here. These
input files were originally SGML and were then converted to well
formed XML files. The input shown below are well-formed XML. But I
want to do some preprocessing before I apply xslt and that is what I
am trying to do in the new xslt.
So when I do the <xsl:copy> the entities are not copied over.
Is this a wrong approach? Please advise.
On Tue, Dec 15, 2009 at 5:17 PM, David Carlisle
<davidc(_at_)nag(_dot_)co(_dot_)uk> wrote:
<!ENTITY spoon.jpg SYSTEM "spoon.jpg">
That looks very wrong, if that entity were used the jpg file would be
parsed as XML, don't you mean an NDATA entity here?
XSLT has no record of parsed external entities, if you use NDATA
entities then the entity definitions are passed to XSLT and may be
accessed using the unparsed-entity-uri and similar function, although
entity declarations can not be generated you can (perhaps) specify a
doctype in xsl:output that contains the entities you need in the output.
David
________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs.
________________________________________________________________________
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--