>As Neal suggested, check out the xmlsearch code, which is also bundled
>in the contrib directory of 3.1.6. You can avoid any HTML code in
>the excerpts by turning off the add_anchors_to_excerpt attribute, and
>changing start_ellipses, end_ellipses, start_highlight, and end_highlight.
>I suppose these attribute definitions should be added to xml.conf in
>contrib/xmlsearch. I think there will also be a problem with the 3.2
>betas, not just with excerpts but with all $&(var) expansions, in that
>all accented characters are mapped back to ISO-8850-1 character entities,
>which, if I understand correctly, are invalid in XML.
Ciao Gilles and Neal.
Thanks for your postings. I tried with the XML output, but I found also
another way for managing the output with PHP. Indeed, creating a wrapper
PHP script which handles the XML output generated by htsearch is kinda slow.
Basically this is my idea. I tried it and it works pretty fast and it
is very flexible. I make htsearch write PHP code itself, by generating code
to be evaluated inside the wrapper script. It's needless to say to we have
to be extremely careful about checking the code.
I am testing it. If you are interested I can share it with you guys and
discuss about it. Waiting for your opinion, especially as far as the
security is concerned.
Ciao and thanks
-Gabriele
--
Gabriele Bartolini - Computer Programmer
U.O. Rete Civica - Comune di Prato - Prato - Italia - Europa
[EMAIL PROTECTED] | http://www.po-net.prato.it/
The nice thing about Windows is - It does not just crash,
it displays a dialog box and lets you press 'OK' first.
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/htdig-dev
