Re: XSLT extension

Well if that is so it sounds as if having two extensions is the right way to go then. I just wanted to make sure as I don't have any experience with XSL Translators. Andi At 06:56 PM 9/7/00 +0200, Stefan Livieratos wrote:

Hi Andi, those XSLT extensions are mostly wrappers for the corresponding C++ libraries, as I understand it, so I can't see how one could merge them into one super extension. You could of course try and build an abstraction layer but I don't think this is feasible. So, if we were to make a decision which library/implementation to use for PHP right now, I would say it is too early to decide. Sablotron for example isn't 100% conformant to the XSLT spec and I am not sure how stable Xalan-C++ is. Regards, Stefan Andi Gutmans wrote: As I said I'm not an XSLT expert and if there is a good reason to have two (each one is strong in its own area like databases differ) than it makes sense. However, in general our goal is to unify things and make it easier for people to share and exchange code. Also by making the group effort concentrate on one extension instead of on two usually means that the final result will be better. I think that having one super XSLT extension is better than having two mediocre ones. Let's try and aim for this goal. If there are good and valid reasons not to do this, then we should go for two. Andi At 06:18 PM 9/7/00 +0200, Stefan Livieratos wrote:

Hi Andi, what would be so bad about having more than one XSLT extension? Let the users decide which one they want to use just like with the PDF (PDFlin and CPDF) extensions. Regards Stefan Andi Gutmans wrote:

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 --- 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

--- Andi Gutmans <andi@zend.com> http://www.zend.com/