> >It's often frustrating, like IE eating up the space text nodes, > >so the XML syntax highlighting I describe above doesn't work with > >IE, and needs to be done with a proper (standard compliant) XSL > >engine (Xalan, Saxon, FireFox's XSL engine, etc...), but it's > >rewarding work ;-) I like it's functional model. > > > >XSL 2.0 looks very promising has an improvement over 1.0, > >being even more functional, and having regexp and sequences, > >but that requires Saxon. I don't know how people feel about > >a Saxon 8.x dependency. > > > > > This should not be too much of a problem. It will be used > during the build phase (in the same way that junit is used), > and maybe using <libraries>, however it would be nicer > just to use xalan.
We have a more "non-standard" dependency than JUnit (which is nearly in every project :) : jakarta-site for generating the homepage from xdocs. If Saxon is only need during the build process of Ant and if its free, we could use that - if itīs really better that "our own" (ASF) xsl engine. Jan
