Re: Re: Re: Creating a XSL to return the input
> > Everybody can and will make their own conclusion about the real > > level of testing of an XSLT processor that does not implement > > correctly something so basic as the child::node() node test. > > <xsl:template match="@*|node()"> > > is not child::node() node test. node() is an abbreviation for child::node(), as per spec: http://www.w3.org/TR/xpath#path-abbrev Because node() will match different kinds of nodes depending on with which axis it is used, it is better to show the axis in order to avoid any possible confusion. And the problem of correctly matching node() is what started this thread. > You tend to jump very hastilly on > conclusions... which often happens when people didn't go down to > actually implementing the stuff :-) There are great people, who are actually implementing the stuff and implementing it *correctly*. > I still don't know what aim you're aiming at but this looks less > and less trying to be useful the community on this specific thread. Right. Usually such threads are not created at all, because the developers are grateful to the people, who have found some bug and thus contributed to making their product better. Dimitre Novatchev. http://fxsl.sourceforge.net/ -- the home of FXSL __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format