RE: [none] (Wendy's question)
I had previously thought of using entity references for this purpose, but it turns out not be a viable solution. It would have been nice to be able to say: <xsl:for-each select='@attribute=&search.for;'> Before performing transformNode(), I would have used the DOM to access the entity table of the DTD (probably an internal DTD) and modified the entity value. Unfortunately this is not allowed, per the XML 1.0 spec. It would have been very nice, on a server, to keep the DOM of the stylesheet in memory and modify these entity values for each transaction, and let the transform take place. Multi-threading issues might have required a different DOM per thread, or it might have required access to the entity table to be based upon the current thread. Alas, entities are not allowed to be modified after a document is parsed. A DOM will have no entity reference nodes. Oh well. It looks like the search and replace functionality has to be hand coded by each application developer. Mike XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
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