> According to Tony Crockford:
> > Am I right in thinking that keywords added in this way
> follow different
> > rules to words entered directly into a search box, if so how do I
> > configure htdig to ignore punctuation and bad words and
> allow the search
> > to proceed normally?
>
> Yes, the parsing of the keywords input parameter is much more
> simple-minded than the parsing of the words input parameter. It only
> allows white space (space, tab, newline) as separators, as
> well as Ctrl-A
> which is the separator used for multiple input parameter definitions,
> e.g. if you use checkboxes for building keywords input parameters.
>
> There's no configuration option to change this. You need either to
> clean up the keywords list you give to htsearch, or you need to modify
> htsearch to do better parsing of this parameter. Right now,
> this is at
> line 179 in 3.1.5's htsearch/htsearch.cc:
>
> requiredWords.Create(config["keywords"], " \t\r\n\001");
>
> You'd either need to add all punctuation characters you're likely
> to encounter to the list at the right, or you'd need to build up the
> StringList some other way.
>
>
Thanks for this,
I've taken the *easy* way out and cleaned up the list of generated
keywords.
Maybe when I've got more time I'll investigate the other options.
Thanks
(also to Geoff)
_______________________________________________
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
