From: Lachlan Andrew <lha@ee...> - 2002-10-18 12:00:58
On Mon, 14 Oct 2002 05:13, you wrote:
> KNOWN BUGS:
> * If exact isn't specified in the
> search_algorithms, $(WORDS) is not set correctly:
> PR#405294. (The documentation for 3.2.0b1 was updated,
> but can we fix this?)
> =A0(More importantly, do we ever want exact to /not/ be
I just had a look at this, and it seemed to me that=20
$(WORDS) is set correctly, but $(LOGICAL_WORDS) can be=20
missing some operands if there are no fuzzy matches. Was=20
that the original problem?
If so, would an acceptable fix be just to insert the exact=20
word whenever there are no fuzzy matches? It could be=20
given a very low weight so as not to disrupt the search.
That would be a two-line patch.
Lachlan Andrew Phone: +613 8344-3816 Fax: +613 8344-6678
Dept of Electrical and Electronic Engg CRICOS Provider Code
University of Melbourne, Victoria, 3010 AUSTRALIA 00116K