At 03:20 AM 09/16/00 -0700, you wrote:
>Agreed, one could index ALL stop words, but that would be extremely
Stop words are words that aren't indexed. So if you index stop words such
as "yes" and "no" then they are not stop words anymore.
>[Actually, commenting out IgnoreWords wouldn't work either. It would just
>cause Swish to spend an inordinate amount of time calculating the frequency
>of all of the potential stop words, as defined in config.h, and then
>deleting them from the index, ending up in essentially the same
Don't use IgnoreLimit
>It would be better to allow a few specified terms, like yes/no, etc. as
>"non" stop words. Then you could search within meta or xml tags like a
Sounds like you are confused about stop words. There are two kinds of
words: words in the index, and words that aren't in the index. You can't
say "yes" and "no" are stop words, but include them in the index. They are
no longer stop words if you do that.
Again, use IgnoreWords and specify your stop words:
IgnoreWords a an the and
Now you can search for "yes" and "no", but not "a" "an" "the" and "and".
>Suggested variable names: "SpecialWords" "Override_Stop_Words"
>At 02:34 PM 9/15/00, you wrote:
>>At 02:12 PM 09/15/00 -0700, Frank Heasley wrote:
>> >Although stop words are important, there is no provision (that I'm aware
>> >of) that can override them.
>># The IgnoreWords option allows you to specify words to ignore.
>># Comment out for no stopwords; the word "SwishDefault" will
>># include a list of default stopwords. Words should be separated by spaces
>># and may span multiple directives.
Received on Sat Sep 16 14:24:50 2000