On Thu, 08 Mar 2001, Clint Gilders wrote:
> Jonathan Gardner wrote:
>
> > So basically, I would modify the template so it showed only the link, and maybe
> > the text. Then, in my serach results cgi script, I would call htsearch, get the
> > results, and parse out the link, and then process the link in the script.
> >
> > Sounds like this could work.
>
> Yeah, using my wrapper as an example, you could modify cgi_long.html:
>
> $(TITLE)||$(EXCERPT)||$(URL)
>
This doesn't account for if the excerpt has double pipes inside. That would
throw everyone for a loop.
I was thinking of using XML to put everything in its proper place, and then
using XML::Parser to parse it out after it is produced. 1) XML is basically
compatible with HTML (you can't use < or > unless you do < or >, so you
can't throw the parser for a loop), 2) XML is easy, and there are ten million
parsers out there, at least one for each language.
--
Jonathan Gardner
[EMAIL PROTECTED]
(425)820-2244 x123
_______________________________________________
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
