Michel Schinz wrote:
> Michael Sperber <firstname.lastname@example.org> writes:
> > Since that port was pretty smooth to use, what you're saying doesn't
> > bode well ... :-(
> So, I checked the package found on your page, and it pretty much
> matches the package found on Sourceforge. So I think I need to clarify
> what I mean.
> So, first of all, to reassure you, loading packages.scm and then
> opening the various structures it contains works like a charm. In that
> sense your port is indeed very smooth, thanks.
I've used SSAX for one of my projects and I also found that I could
only use the files from the lib directory, after applying the patch
for the misnamed string->goodhtml.
[I've reported this misnaming a year or so ago, but there was no new
SSAX release in the meanwhile that fixed that. Actually, the CVS
version of sunet contains a patch for the misnaming in
I don't think the Scheme files in docs are necessary to be included in
the package. I think I remember a note somewhere that Oleg used this
files to create the documentation of SSAX. The result of that is
SXML.html in the docs directory, so you could just include that only.
In the benchmark directory, Oleg has put some files to show the
performance of SSAX. I think the files are for demonstration purposes
only anyway and not needed in a library.
I have similar arguments for the tests directory.
The files in the examples directory never worked for me (with scsh).
So, if you only include the lib directory along with SXML.html from
the docs directory, I think you are all set with the library.