I'm open to either option. If the separate nsxslt module was still dependent upon libxml2 then I'd say we might as well leave them in a single module.
If we got to the point of having a configure script (--with-xslt --without-xslt) it should be pretty simple for new people to compile. I did find that if I used straight html in my xslt template it crashed aolserver. I assume this has something to do with a lot of tags being opened and never being closed but I haven't looked into it any further than that. If few enough opened and not closed tags are used it generates a proper error and doesn't crash. On Saturday 01 June 2002 12:48 pm, Scott Goodwin wrote: > I've updated the nsxml module in AOLserver's SF CVS area with Jeremy > Collin's patch; this brings it up-to-date with Yon Derek's nsxml module > and adds XPath support. I've now removed the acs-misc version of nsxml. > > It compiles, and the server can load the module, but I haven't done any > real testing. > > I'd like comments as to whether the XSLT portion that was added by Yon > Derek should be pulled out and put into a new, separate nsxslt module, > or if it should stay inside of nsxml. > > > /s.
