Thanks Geoff But, that didn't work.
I was using noindex_start/end to ignore <script> content, but then I replaced them with various tags of my own device (one at a time), as well as using the default ones, but no luck. Is there some instance where noindex_start/end does not work? Max number of lines perhaps? The funny thing is that it DID work for the <script> tags. The reason I know this is that I found that the script tags were breaking htdig, so the solution was either to comment them out (like for older browsers), or tell htdig to ignore <script> content. Take care, Antun > -----Original Message----- > > Yes, of course. You can put in comment tags that will tell ht://Dig to > ignore everything between them. > > By default, the strings are <!--htdig_noindex--> <!--/htdig_noindex--> ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Gadgets, caffeine, t-shirts, fun stuff. http://thinkgeek.com/sf _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
