> Now the problem:  If in my <option> tags, I specify my keywords the
> way I did in the <meta> tags, like this:
> <option value="ir-cg">ir-cg
> <option value="ir-cg-a">ir-cg-a
> <option value="ir-cg-b">ir-cg-b
> <option value="ir-cg-b-x">ir-cg-b-x
> <option value="ir-cg-b-y">ir-cg-b-y
> (etc.)
>
> and then specify one of these in the search form's popup, and enter
> the same word in the text field as before, then htsearch finds NO
> matches.
>


Okay.

This is exactly what I had.

Keywords in the search form are handled differently to the words in the
search.

You can't have punctuation in the search from hidden keywords.

To quote from Gilles reply to my problems:

<snip>
> 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.

</snip>

Hope this helps.

In other words, you can't use the search form hidden keywords option for
anything other than plain words.

you could of course use:

> <option value="ir-cg">ir cg
> <option value="ir-cg-a">ir cg a
> <option value="ir-cg-b">ir cg b
> <option value="ir-cg-b-x">ir cg b x
> <option value="ir-cg-b-y">ir cg b y

but I suspect it will fail on the single character options.


HTH


(unless we campaign for a change!)

Best wishes

Tony


_______________________________________________
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

Reply via email to