Is there a wholesale XSL way of getting rid of this problem
If (as is the case here) the input is not well formed, it won't get past
the XMl parser so XSLt can't fix it.
Most likely it's a badly labelled encoding (windows-1252 labeled as utf-8
fro example) in which case the fix is to make sure that the text is
labelled with the encoding that it's in, but that depends on where the
text is comming from, and how you are passing it to xslt rather than
anything you can actually solev within XSLT. (Unless you are using
xslt2's unparsed-text() function which allows you to specify the
encoding)
David
--~------------------------------------------------------------------
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>
--~--