Marco Maggi wrote: > how much is SSAX entangled in the Xitomatl libraries? > Would it be complex to extract it?
It's mostly self-contained and should be relatively easy to extract. It needs an includer. You could replace all imports of '(xitomatl include)' with whatever you want to provide 'include/resolve'. Or, more substantially change the including. There are very minor dependencies on '(xitomatl common)', '(xitomatl control)', and '(xitomatl conditions)' of stuff which is very easy to provide elsewise. Rename all '(xitomatl ssax ---)' to '(--- ssax ---)'. I'd also rename all "private-5-1" to "private", and change those library names to '(xitomatl private --- (5 1))', i.e. add the '(5 1)' version component, because that's how I should have done it. All the library-file names with "-5-1" should have that removed. It's only for PLT and not portable. You should review 'OS:file-length' in '(xitomatl ssax private-5-1 to-html-ext)'. I can't remember if the way I made it is OK, and there's a small dependency on '(xitomatl file-system base)'. I think I made a hack because I didn't have a way of getting file lengths, and I can't remember how important knowing the lengths is. '(xitomatl ssax multi-parser)' is not from the official SSAX 5.1. It's from PLaneT and depends on the SXML-Tools libraries. See revisions 82 through 89, to look at the commits for my work on this. Also, remember my port of the official tests in xitomatl/tests/ssax. I can't remember why I made two of the tests not 'include/resolve' the original code, but I must have had a reason, but it could probably be worked-around with tricks. Please use the files from the latest revision of Xitomatl, because I updated my copyright/license headers. Sorry if I've missed anything. -- : Derick ----------------------------------------------------------------
