Ted,Thanks, but I'm afraid that isn't the problem. htseach generates the invalid XHTML code, it's not in the template files ... other than where you use $(VARIABLE) to tell htsearch where to put your results. The star config stuff doesn't help either, it only lets you determine things like what image to use NOT how to create the image tags. Unless of course I am seriously miss reading the documentation for this. As to using PHP .... same problem ... I'd still have to "mess" with the output which put's me at the mercy of other changes to the in-bult htsearch formatting ... so it's better if htsearch produces valid XHTML code (IMHO).
Thanks anyway though. On 7 Feb 2006, at 10:36, G. T. Stresen-Reuter wrote:
You can modify the templates and the "stars" attributes of the .conf file to be valid XHTML (or XML). The templates on my installation are in htdig/share/htdig. Just modify them as needed.You might also look at "wrappers" that have been written for PHP. They modify these same files and convert the results to PHP structures.Hope that helps. Ted Stresen-Reuter On Feb 2, 2006, at 7:34 PM, Dale Roberts wrote:Hi,Is there any wy to get the "internal" result generator (htsearch) to spew out valid XML / XHTML ... I would like to use Ajax to parse the return results slightly better than as text ... but the current version outputs "invalid" <IMG> tags ... as they are not closed <IMG ..... /> but <IMG .....> ... which causes XML parsers to have a fit.This would be REALLY nice when combined with the ability to set the content type to text/xml for use in things like my Ajax wrapped htdig install on my site.Dale Roberts http://daleroberts.info
Dale Roberts http://daleroberts.info
smime.p7s
Description: S/MIME cryptographic signature
