Re: XSLT extension (fwd)

From: Date: Thu, 07 Sep 2000 18:22:24 +0000
Subject: Re: XSLT extension (fwd)
Groups: php.dev 
Request: Send a blank email to php-dev+get-32602@lists.php.net to get a copy of this message
Just thought some of the folks over on the php-xml list might have some input here. So far the general consensus appears to be: Sablotron is not 100% conformant, but there are equal concerns regarding the stability of Xalan. ---------- Forwarded message ---------- Date: Thu, 07 Sep 2000 17:08:27 +0300 From: Andi Gutmans <andi@zend.com> To: Martin Kong <mkong@interlog.com>, php-dev <php-dev@lists.php.net> Subject: Re: [PHP-DEV] XSLT extension It would be very interesting to hear from the XSLT experts how the Sablatron module vs. the Xalan module compare. I think it would be best for PHP to have one standard XSLT extension. Can we work on a way of deciding which one we should be using or merging both code bases into one extension? Let's hear the experts :) Andi At 03:16 PM 9/7/00 +0800, Martin Kong wrote: >We have developed a XSLT extension (based on Apache Xalan) and we would >like to add it to the PHP extension family. How do we go about doing >this? Is it documented anyway? > >As a starter, it's quite simple, it performs some simple XSLT >operation. We are also planning to add SAX and DOM parsing support. I >also like to get some input from the PHP community as to what functions >you think would be useful to have. > >Thanks and Regards, > >-- >PHP Development Mailing List <http://www.php.net/> >To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net >For additional commands, e-mail: php-dev-help@lists.php.net >To contact the list administrators, e-mail: php-list-admin@lists.php.net --- Andi Gutmans <andi@zend.com> http://www.zend.com/ -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net

« previous php.dev (#32602) next »