Re: Indexing HTML comments - FOLLOW UP

On Tue, 28 Nov 2006, Steven Bonisteel wrote:

> 
> For anyone interested ...
> 
> It occurred to me that I was using the same 'custom' noindex definition in 3.2.0b6 that I was using without problems in 3.1.6:
> 
>  noindex_start:  <!-- citysearch_noindex -->
>  noindex_end:    <!-- /citysearch_noindex --> 
> 
> On a hunch that this was somehow making htdig brain dead on comments in general, I removed that from the .conf file and re-indexed.
> 
> Seems to be fine now.

I think the original problem was most likely due to the spaces in your
noindex_start and _end definitions. The value type for these attributes
changed from string to string list between 3.1.x and 3.2.x. With the
spaces, three separate markers were being defined for each attribute. I
would expect this to create any number of problems for the parser.

Jim

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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