On Sat, 26 Jun 2004 05:21:27 -0600 (MDT), Jim <[EMAIL PROTECTED]> wrote:
> 
> On Sat, 19 Jun 2004, rand wrote:
> 
> > What i'm on to now is the cleaning up and making it all look good.
> > I'm wondering if there is a way to dig the site and not end up with
> > the top links as the first (and usually only) thing that is seen in a
> > search result.
> 
> See http://www.htdig.org/dev/htdig-3.2/FAQ.html#q4.15 for some options
> that allow you prevent certain content from being indexed.
> 
> Also, if you can afford the disk space, increasing the value of
> max_head_length should decrease the number of cases where htsearch
> resorts to using the top of the page as the excerpt.
> 
> > also, I seem to have made an error in the way I created the templates
> > for the top and bottom links, does this mean i have to recompile htdig
> > all over again or can i just modify the templates?  You can see what I
> 
> Changing the templates does not require that the package be recompiled.
> If you have already setup htsearch to use custom templates, then those
> templates are read each time a result page is generated.
> 
> Jim
> 
Sweet, Thanks Jim.
I haven't had time to go back and test yet, but that is exactly what I
was hoping for :)
I did increase the max_head_length, guess it was not enough, it's good
to know that is what will help keep the results of any search clean. I
was wondering why some searchs had clean results, but most around
those clean were the titles.

cheers

rand


-------------------------------------------------------
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 general mailing list: <[EMAIL PROTECTED]>
ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-general

Reply via email to