> According to Douglas Kline: > > Apart from possible miscommunication in e-mail, I found a reason why I thou ght > > that the search_algorithm applied only to htsearch and not to htdig: The > > Attributes Web page says that search_algorithm is "used by: > > htsearch". > > The documentation is correct, and can be confirmed by searching through > the source code for places that use the search_algorithm attribute. > It is used only by htsearch, and has no effect on htdig. If reindexing > solved your problem with getting substring matching to work, it's likely > because there was a problem with your db.words.db database beforehand, > and reindexing rebuilt it.
A scan of the source code in the htdig and htsearch directories confirms that the string "search_algorithm" is found only in the latter directory (and there only in the file htsearch.cc and in that file in only one command line). That doesn't prove that the htdig command isn't affected by the definition of that attribute. A repetition of the tests I ran before confirms that a database created by "rundig -a" with an htdig.conf file with the line search_algorithm: substring:0.5 can be searched for strings other than whole words by htsearch using the same htdig.conf file while a database created by "rundig -a" with an htdig.conf file with the line search_algorithm: exact:1 synonyms:0.5 endings:0.1 cannot be searched for such strings. The files in the database created by rundig with these two htdig.conf files are the same size. However I ran cksum on them and got different results. So their content is different. rundig calls htdig, htpurge, htnotify, and htfuzzy. Might one of the others be relevant? htnotify does not affect the database. If I understand correctly, htfuzzy doesn't either and when I ran it the files in the database weren't changed. In trying to pin down whether htdig or htpurge or both had to be run with the htdig.conf file with the search_algorithm: line, I found that specifying the alternate htdig.conf file with "-c <file name>" didn't have the same effect as naming the alternate htdig.conf file "htdig.conf", i.e. bin/ rundig -a -c conf/htdig-substring.conf while conf/htdig.conf is a different file from conf/htdig-substring.conf produces a database which cannot be searched for non-word strings and ln conf/htdig-substring.conf conf/htdig.conf followed by bin/rundig -a does. What's going on here? Is the "-c" flag not being interpreted correctly? TIA. Douglas ======== Douglas Kline [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ ht://Dig general mailing list: <[EMAIL PROTECTED]> ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-general
