Thanks for your answer. Finally, the error was the inclusion of the character '*' in the conf variable <valid_punctuation>. I think this made htsearch to automatically remove the character '*' from the search string before processing it.
The FAQ http://www.htdig.org/FAQ.html#q5.31 you suggested induced me to compare the old conf file we were using with the default new one included in 3.1.6 release. Thaks again. Regards. At 17:15 15/08/2002, you wrote: >According to Emilio: > > Hi, I'm trying to perform prefix searches in our site but I can't make it > > work correctly. > > > > I have read all the documentation at htdig.org and in the related messages > > of the list and all appear to be correct. > > > > My htdig (version 3.1.6) configuration file has the following lines: > > > > search_algorithm: exact:1 prefix:0.5 accents:0.5 endings:0.3 speling:0.2 > > prefix_match_character: * > > > > (I also have tried prefix_match_character:*) > > > > Parameters max_prefix_matches and minimum_prefix_length are not specified, > > that is, leave to default. > > > > If I search separately for the words esencia, esencial, esencialmente in > > the site, all of them appear correctly. > > But if I search for the word esenci* none of them appear in the results (0 > > matches). > > > > If I leave the prefix_match_character blank, that is: > > > > prefix_match_character: > > > > then the prefix search is always made inconditionally. That is, if I > search > > the word esenci (without the *) I get the matches for esencial, esencia y > > esencialmente. Since I need to supply exact searching, this solution is > not > > satisfactory. > > > > Am I missing something? > >Well, I can't reproduce the problem at my end. Actually, I inadvertently >did when I first tried to, but that was because I had two definitions of >prefix_match_character in my test config file. If you just have the one >definition of prefix_match_character, and it's set to "*" (which is the >default if you have no prefix_match_character definition in your config), >then it should work fine. See also http://www.htdig.org/FAQ.html#q5.31 > >Note that there's no "speling" fuzzy algorithm in 3.1.6, though, it's >only in 3.2 betas. > >The one difference I encountered between 3.1.5 and 3.1.6, as far as >the handling of prefix_match_character is concerned, is that if you >set prefix_match_character to an empty string, then the "*" is stripped >out of a word in 3.1.5 but not in 3.1.6. So, if prefix_match_character >is empty, htsearch 3.1.5 would still handle a search for "esenci*" as >though prefix_match_character were set to "*" - in reality as though >you had typed "esenci". Not so for 3.1.6, though, because the "*" >isn't stripped out (because it's the default wildcard for the "match >all documents" facility when prefix_match_character is empty). > >-- >Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> >Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ >Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) > > >------------------------------------------------------- >This sf.net email is sponsored by: OSDN - Tired of that same old >cell phone? Get a new here for FREE! >https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 >_______________________________________________ >htdig-general mailing list <[EMAIL PROTECTED]> >To unsubscribe, send a message to ><[EMAIL PROTECTED]> with a subject of unsubscribe >FAQ: http://htdig.sourceforge.net/FAQ.html ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
