Paul et al,
Regarding new versions of Swish[-e|++].. Is anyone planning to move
features of swish++ into the swish-e codebase. I'd like to have the
featureset of both programs, but since they use different index-file
formats, You have to choose one or the other. My problem is that I'm not
a coder, so I can't/won't write the web front-ed for swish++, and Swish-e
can't handle the size of my document tree without lots of RAM. It's speed
starts decreasing exponentially when it starts using swap space.
In other words, I'm saying what alot of people have said. I want to use
Swish++ with Autoswish. I'd be willing to help test it, but like I said,
I'm not a coder, so my ability to help in that area is very limited.
Paul J. Lucas
> The changes are attached from the 'Changes' file. This version
> includes the aforementioned feature whereby you can dump the
> words "around" the query words, e.g.:
> $ search -w7 electrical
> Above, '7' specifies the window size (at most). You can
> optionally specify the number of characters that must match,
> $ search -w7,4 electrical
> Above, "elapse" and "elevator" were not output because the
> first 4 characters of the words do not match "elec": the first
> 4 characters of "electrical".
> Creating a web interface using this new feature is left as an
> exercise for the reader. (My off-the-top-of-my-head suggestion
> would be to create one <SELECT SIZE=n> ... </SELECT> per query
> word and allow the user to refine their query from the words in
> the index. I would be interested in seeing your solutions.)
> - Paul
>* In "search," a "window" of words can be dumped around the query words.
>* In "search," the -d option to dump the index for a word now dumps all the
> query words instead of a single word. Additionally, a stop-word used to
> print "stop-word"; now it prints "# ignored: " followed by the word.
>* In "search," the -d option to dump the index for a word now prints the
> # not found: word
> if 'word' is not found in the index.
Received on Mon Nov 2 08:28:06 1998