On 05/10/2010 11:09, pankaj(_dot_)c(_at_)thomsondigital(_dot_)com wrote:
But what about keeping the DTD declaration along with Entity in resulting
output (required for roundtriping).
In XSLT you can read in the source file as text, using unparsed-text()
and then use string functions to cut off the input doctype declaration
and re-use.
In XSLT1 you may find system extension functions that may let you do
something similar.
Alternatively rather than trying to preserve the input declarations,
something closer to a pure xslt model of the transformation would be to
generate any declarations that you need.
Basically pass through the input file and for every attribute of type
ENTITY that you are going to copy to the output, extract the
unparsed-entity-uri() and generate a suitable ENTITY declartation which
you can output (using disable-output-escaping) as part of a local
doctype declaration.
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>
--~--