Michael PG wrote:
> I don't think that's there'a an bug in msxml.
Personally, I wouldn't bet on that ;), but there must be a
bug somewhere,
I get the same result as Werner (with Saxon, Transformiix and MSXML3).
He wasn't running with MSXML3 or MSXML4. He was running the unnamed XSLT
processor included in the System.Xml.Xsl library in .NET
Michael Kay