[Dev] Using EXSLT for documentation generation

[Andi Vajda]

The repository was effectively switched over last Friday.
Once parcel loading has switched and our XSLT needs are met by libxml2 we have
no reason to keep the other XML packages in our build.

Andi..

On Wed, 17 Dec 2003, Morgen Sagen wrote:

>
> On Dec 17, 2003, at 7:19 AM, Jeffrey Harris wrote:
> > Happily, there's another option:  we could use the the cross-vendor
> > extensions to XSLT, EXSLT (<http://www.exslt.org>).  4Suite, the XSLT
> > processor we're currently using, has good EXSLT support.  If I can use
> > EXSLT's function element, the inheritance will be a lot simpler.
> >
> > So, my question is:  Does the Chandler community have any specific
> > investment in using only vanilla XSLT?  If not, I'll use EXSLT
> > liberally.
>
> Andi is in the process of switching Chandler's XML repository to use
> libxml2 (http://xmlsoft.org/), and I was hoping we could just
> standardize on that one XML implementation within Chandler (instead of
> the combination of expat/PyXML/4Suite that we have in there now).  It
> looks like there is an EXSLT-compatible library based on libxml2
> available (http://xmlsoft.org/XSLT/) with a command-line xslt processor
> we could use to generate the schema documents.  Hopefully this would
> meet everyone's needs.  I'm currently looking at moving our parcel
> loading code to using the libxml2 parser right now.
>
> ~morgen
>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/dev
>