RE: converting encoded characters <, > etc
I see what you mean :) yes, indeed that would work. No, I did not know about loadXML() before this. The methods available to me via MS' XMLDOM was not known to me before this and I could only try each relevant method I could find in the W3C DOM specs and see if it worked in MS' implementation. Color me frustrated... Well, I finally found a good library on the MS XMLDOM implementation: http://www.devguru.com/Technologies/xmldom/quickref/xmldom_intro.html yes!!! Thanks, Geert!! Wong -----Original Message----- From: Geert Josten [mailto:Geert.Josten@xxxxxxxxxxx] Sent: Wednesday, December 01, 2004 9:51 PM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: converting encoded characters <, > etc > Set newNode = objNode.createNode(1, "OutField1", "") > newNode.Text = "<p>Hello World</p>" Here is the cause of > and < appearing in your result. You pass < and > as literal text. They are escaped before being inserted in the DOM tree.. > Why did I not parse through "<p>Hello World</p>" and derive some nodes from > there? Well, 'cos it can be any HTML tag and I'm not confident I'll be able > to create a template for all the tags that might appear. I'm not sure we understand each other. What I meant is that you should try to do something like: Set tempDoc = New DOMDocument40 (or some object like that) tempDoc.loadXML("<p>Hello World</p>"); objNode.addChild(tempDoc.firstChild); It shouldn't matter whether the <p> contains <a> elements or not, as long as the string you pass contains well-formed XML... Good luck. Geert
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format