From: Chris Wong Date: 2002-10-22T06:21:04+09:00 Subject: Re: XML/XSLT processors - XSLT4R not working? Is there any known memory leak issues with libxml2, libxslt, salblotron and expat (which salblotron uses to parse xml)? I'm curious why there isn't a strong need to create a pure Ruby xslt processor based on maybe rexml? Is it because of performance issue? BTW, ruby-libxml won't link. I'll notify the owner or submit a patch later when I have time. Chris JamesBritt wrote: > > >>-----Original Message----- >>From: Chris Wong [mailto:chris_wong@mac.com] >>Sent: Monday, October 21, 2002 7:48 AM >>To: ruby-talk ML >>Subject: XML/XSLT processors - XSLT4R not working? >> >> >>I'm looking for a pure Ruby XSLT processor. Stumbled across XSLT4R. >>It looks promising, but it doesn't seem to work even for the test.xslt >>in its test directory. I'd appreciate some recommendations in XSLT >>processor for Ruby. Is there anything in Ruby similar to JAXP in Java? >> >> > >Here are some choices for XSLT in Ruby, though they do not fit a "pure Rby" >requirement. >The descriptions are taken from the either the RAA entry or the owner's web >site. > > >sablot http://www.rubycolor.org/sablot/ > This is a Ruby interface to Sablotron, the XSLT processor developed by > Ginger Alliance. Requires Sablotron binary or compiled source > > >ruby-libxslt http://www.rubynet.org/modules/xml/ruby-libxslt/ > A working, fully compliant, XSLT engine for Ruby. This module is still under > heavy development and requires libxml, however it is very functional and is > feature complete for the XSLT spec. Requires libxml (binary or compiled from >source) > > >James > > > > > >>Thanks >>Chris "the XSLT newbie who would rather program in Ruby" >> >> >> >> >> > > > >