Re: Preventing indexing HTML code in documents

"Joe R. Jah" <[email protected]>
Newsgroups gmane.comp.web.htdig.general
Message-ID <[email protected]>
On 25 Aug 2005, David Dyer-Bennet wrote:

> Date: 25 Aug 2005 18:46:09 -0500
> From: David Dyer-Bennet <[email protected]>
> To: [email protected]
> Subject: [htdig] Preventing indexing HTML code in documents
> 
> Except they're asking if there's a way to not index the HTML code in
> documents, just the text between tags.  The particular issue, I
> believe, is a list of keywords in a SELECT which appears as part of
> the navigation on every page, and hence makes every page a hit for
> those keywords.  I suspect there's no answer to this in current
> versions; if there is I haven't sniffed a trace of it in the FAQ or
> documentation.  But, is there?  As a possible long-term suggestion,
> what about some kind of meta tag that would tell htdig not to index
> things between them?  This would give people a lot of control on how
> site-specific local searches worked.

See http://www.htdig.org/attrs.html#noindex_start

Regards,

Joe
-- 
     _/   _/_/_/       _/              ____________    __o
     _/   _/   _/      _/         ______________     _-\<,_
 _/  _/   _/_/_/   _/  _/                     ......(_)/ (_)
  _/_/ oe _/   _/.  _/_/ ah        [email protected]



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.