Sorry if any of these are already known; I couldn't tell if the "bug
database" covered the beta, but I did quickly search thru the list archives
before posting.
I found a few bugs in testing & playing around with the beta 2 (which I'm
using for the alpha version of a rather odd document-retrieval system, which
still needs to be at least slightly presentable). See the AND operator
thread for the biggest bug (at least from my perspective), and my patch for
it. Unfortunately, I don't have specific repeatable examples for most of
these (been mucking with my config too often).
- some error conditions result in an error message followed by what seems to
be an attempt to output an excerpt (when there are obviously no documents).
This results in gibberish (sometimes fragments of htdig.conf, sometimes what
just looks like the contents of some random memory location, up to a few
lines long) inserted between '<blockquote><strong>' and
'</strong></blockquote>' in the resulting HTML.
- when using long.html and short.html (as opposed to the built-in formats or
a custom format) to display results, certain queries will say "results 1-x
shown" but not show any results. Which query produces this seems
unpredictable, but the same query will always either return a "blank list"
or return normally.
- a search for '"web and"' hangs htsearch when method=boolean (but not when
method=and or method=or. Yes, 'and' is in my bad_words, but doesn't seem to
be caught in this instance.)
- A search with multiple terms OR'd together (some of them strings) doesn't
seem to highlight _all_ of the terms present in an excerpt, only one of
them.
- a couple of really mangled query strings make $(SCORE) (for some
badly-matching documents) end up at 0 or -1. As an example of a mangled
query string, how about '("expert system" or "expert systems") or (("expert
system" or "expert systems") and ("decision support system" or "decision
support systems" or "decision support" or dss))'?
- This is more of a feature request... a search for '"phrase with prefix*"'
doesn't currently get expanded like 'prefix*' does. This might seem to go
against the whole idea of an exact phrase, but would be useful at least in
one thing I'm doing.
- Also, I've had some unreliable results with prefix searching in general.
However, I don't remember the specifics. Has anyone run into something
similar?
Thanks much for all your work!
(My internship's almost over, so responses to this address will soon bounce;
try <[EMAIL PROTECTED]>.)
Arthur.
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
