> > > Inevitably, there will be certain pages using TMPL_INCLUDE tags. I imagine > > > that most of these will contain data that will not want to be searched for, > > > such as footers, and therefore my filter program can simply ignore > > > them. However, I don't feel safe in making the blanket assumption that > > > /all/ included files don't need to be searchable. > > > >Now you've lost me. There's lots of stuff in an HTML page that > >shouldn't be searched for. Stuff like headers and footers in includes > >is just the tip of the ice-berg. Why obsess over this? > > I want to give content authors more control over what portions of a > document are searched for.
This is a common mistake that information creators think 'is a good thing'... The web got popular for a number of reasons - one of them being "full text indexing of all content" (including headers/footers/etc). The point is that, it is the user of the system that wants to find the information - not the author telling you what you can and cant search for. Classic example -> books used to have (and still do) an index in the last couple of pages of the book, yet the user could never find what they were looking for; until the book made it onto CDROM at which point full-text-searching was possible. -> Full text searching is a _much better_ solution to search problems than indexing on what YOU think is the information they want. Mathew PS. This means, use a spider.. or even better use google via a "site:..." search. ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Html-template-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/html-template-users
