Re: php, win32, xml bug?

"J Wynia" <letterj@phpgeek.com> schrieb im Newsbeitrag news:20020226024603.10825.qmail@pb1.pair.com... > The first thing I'd do is run your transformation through one of (or all of) > the rest of the XSL engines out there. There's a lot more variability out > there in XSL engines. Unfortunately, Sablotron isn't the most conformant of > the field. I haven't used Sablotron in a while for XSLT processing so am not > sure of your specific question. I left Sablotron behind for reasons like > this one. It fails on a great many transformations that run through Xalan, > Saxon and MSXML identically with no errors. My general rule is if it blows > up all XSLT engines, it's probably my XSLT. If Sablotron's the only one that > chokes, it's Sablotron. The new API for XSLT should allow for the other > engines, however, I haven't seen anything on putting the rest of them into > the equation, yet. > i tested it on MSXSL, no problem, all runs fine. but how to choose another xsl-engine? thanks alex