If the problem is with wrong character encodings, then the errors occur while reading XML not while
transforming with XSLT. Perhaps add a try-catch kind of clause around the reading and/or
transforming code?
Kind regards,
Geert
dan(_at_)streampad(_dot_)com wrote:
For my application, people have to upload an XML file (their iTunes Music
Library). After it uploads, I run a transformation on it in PHP5. Many
transformations are not working and showing errors because of weird
characters in the source XML. The source and result XML are set to UTF-8.
Is there a way to skip over a troubled node? I can't imagine that XLST
doesn't have a way to deal with this.
thanks,
Dan
--~------------------------------------------------------------------
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>
--~--
--
Drs. G.P.H. Josten
Consultant
Daidalos BV
Source of Innovation
Hoekeindsehof 1-4
2665 JZ Bleiswijk
Tel: +31 (0) 10 850 1200
Fax: +31 (0) 10 850 1199
www.daidalos.nl
De informatie - verzonden in of met dit emailbericht - is afkomstig van Daidalos BV en is
uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onbedoeld hebt ontvangen, verzoeken
wij u het te verwijderen. Aan dit bericht kunnen geen rechten worden ontleend.
--~------------------------------------------------------------------
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>
--~--