Altova Mailing List Archives


RE: [xsl] A list of useful functions that aren't in the core of xsl.

From: "bryan" <bry@---------->
To:
Date: 3/26/2003 4:58:00 AM
This is actually a problem I've had for a while, which is that a lot of
xml documents out there use escaped html at various nodes. 
This is a common community practice in various flavors of RSS, in
blogger xml files, and I just saw an example on Sam Ruby's weblog where
he was sending SOAP with RDF/XML in the soap:body and escaped html
nested in some other element. The way I have been handling this in RSS
is that I wrote an extension function using Tidy to strip out the html,
for msxml, with a fallback using regex if Tidy failed. I don't want to
have to write the same extension for Saxon, Xalan etc when I need to use
those. 

Does anyone have suggestions on how to handle this admittedly bad usage
but unfortunately too common problem? What about with xslt 2.0, can
anyone think of ways it helps solve this problem, other than the support
of regex? 





 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.