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.
Is it possible to add a flexible attribute system to the current HTML::Template design? I'm thinking of something like this:
<TMPL_INCLUDE NAME="file.txt" SEARCHABLE="no">
The additional attribute(s) could be ignored by HTML::Template, but hold meaning for external programs that need additional information on the template tag.
I'm sure it can be done with a filter, but frankly, I think that's a cop-out solution, being that the current filter mechanism does not have a way to hook into HTML::Template's parser.
------------------------------------------------------- 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
