Based on a quick look, I think it is an easy fix. However you would need to touch the source and rebuild at least htsearch. My assumption is that if you replace the 100 with 100.0 at line 314 of htsearch/Display.cc (for ht://Dig 3.1.6), then you will avoid the overflow and correct the problem you are encountering. I haven't actually tested this. If you are able to test this and it solves the problem, please let us know. You might also consider submitting a bug report if you get a chance just to make sure this issue doesn't get lost in the shuffle.
Hey, whaddya know :) It works.
Thanks ... amazing what the float/int difference can make.
Should I still file a bug report on this to get it 'officially fixed'? (3.1.7 anyone?)
I'm just surprised that noone else had run into this yet. Would seem to quickly happen on any decent sized website, if you search on a word that occurs, as a link, on many/all pages (such as nav text)
Thanks again! Eli
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
ht://Dig Developer mailing list:
[EMAIL PROTECTED]
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-dev
