Greetings Gilles,
Most of the forward ports that I feel confident to do are
now at
<http://www.ee.mu.oz.au/staff/lha/patch.forward-ports>
with the list of changes at
<http://www.ee.mu.oz.au/staff/lha/htdig-3.1.6-3.2-ports>.
Could you please apply them? The patches are relative to
the status at 2002-11-07.
Both defaults.cc and defaults.xml (in Brian White's
format) are up-to-date with respect to the new attributes.
The multimatch_factor has been cleaned up a bit compared
with 3.1.6. It now counts how many "OR" terms a document
matches. (For Boolean queries, the result of an "AND" is
taken to match the average of the two arguments.)
Currently, it simply multiplies by multimatch_factor if
there is more than one match, but the originally documented
functionality can be implemented by changing the line 822
parser.cc (in Parser::parse) from
dm->score *= multimatch_factor;
to
dm->score *= pow (multimatch_factor, orMatches - 1.0);
if you really want that exponential growth.
On Mon, 11 Nov 2002 15:57, Geoff Hutchison wrote:
> A few notes:
> * does rewrite at start of got_href suffice?
> No. Remember that you might want to rewrite the redirect.
My question was more about the placement within got_href.
3.2.0 rewrites *before* normalisation, while 3.1.6 rewrites
*after*. These are not equivalent, and we can't apply the
rules twice (or else "htm->html" would become "htm->htmll").
Which one do we break compatibility with?
--
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
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing
your web site with SSL, click here to get a FREE TRIAL of a Thawte
Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/htdig-dev
