Re: [htdig] Parts of Words

[Douglas K. <kl...@he...>]

> On Fri, 9 Apr 2004, Douglas Kline wrote:
> 
> > > On Thu, 8 Apr 2004, Douglas Kline wrote:
> > > 
> > > > In order to test the substring attribute, I put the line
> > > > 
> > > > search_algorithm:  substring:.5
> > > 
> > > Did you change the existing search_algorithm line or add a new one? If yo
u
> > > added a new one, make sure that the old one is either removed or commente
d
> > > out. The default htdig.conf does explicitly specify this attribute.
> > 
> > 
> > I deleted the previous line and then tried combining its contents, "exact:1
> > synonyms:0.5 endings:0.1", with the substring factor, then tried just "exac
t:1"
> > and the substring factor, and then tried just the substring factor, all to 
no
> > avail.
> 
> I am not sure what else to suggest other than taking yet another look
> at the way you have things configured. You might want to try a cat -v
> on your config file to make sure that you don't have any non-printing
> characters fouling things up. Perhaps grab a clean copy of htdig.conf
> and redo your edits.
> 
> I just installed a fresh copy of 3.2.0b5, changed start_url to something
> appropriate, and replaced the default search_algorithm attribute with
> 
> search_algorithm:       substring:0.5
> 
> Without doing anything else (other than indexing of course), substring
> searching seems to be working fine. The list of displayed search terms
> clearly show that the terms are being expanded from the substring that
> I am providing.


You solved it.  I had construed the documentation to mean that it was the
htdig.conf for htsearch that was significant in enabling sub-string searching.
So I explicitly used a different htdig.conf for htsearch from the one I was
using for htdig.  When I ran htdig with that definition of search_algorithm and
then ran htsearch, also with that definition, it found strings other than
complete words.

Douglas

========
Douglas Kline
kl...@he...