This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Fixing <b>
- From: David Carlisle <davidc at nag dot co dot uk>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Thu, 28 Mar 2002 19:03:36 GMT
- Subject: Re: [xsl] Fixing &lt;b&gt;
- References: <000a01c1d636$4edf9c60$6501a8c0@pcukmka>
- Reply-to: xsl-list at lists dot mulberrytech dot com
> Conceptually, I want to parse the XML and copy the resulting
> nodes to the result tree. But if the result tree is being serialized to XML,
> I don't mind the processor being clever and bypassing the parse/serialize
> operations by copying the raw XML straight to the serial output file."
would you require the processor cleverness to include getting namespaces
right, if so probably parsing and re-serialising is probably about the
best you can do. In theory this is already available as
document('data:text/xml,<foo/>')
> That doesn't deal with the HTML variant of the problem, though ....
No, but you could do
document('data:text/html,<br>')
so long as you knew the html parser used on your text/html input streams
returned things as an "instance of the data model" to use xpath2
terminoligy:-)
the data:mime-type,string URI scheme is a standard scheme (and supported
by netscape since the beginning of time, I think)
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list