Bill Moseley wrote:
At 01:41 AM 03/26/02 +0800, Stas Bekman wrote:
Another issue of the search I'd like to address is that the packet of
results that come back is a little problematic: the mixture of code
which cannot be formatted and text is a mess, and you're easily turned
off byt it. I suggest that we make it search through the code sections
(as it's still pretty important), but we don't show the code listing on
the results page.
I guess it would be helpful to know what you searched for to see what you
are seeing.
The bit of content returned with each search result is just to help decide
if that's the result one might be interested in. I never considered that
it had to be formatted correctly, and in fact for something like perl code
that would take up too much space.
that wasn't my question, but Per Einar's :)
I suggest the following solution: if you meet a <pre> tag and no closing
</pre> tag we add it.
Do you think this is possible Bill? Assuming that all the HTML is proper
(no text without enclosing <p>),
we can always tell which text is not HTML (i.e. <pre>) am I right?
It's not that easy. Swish is what is storing the content. It's being
parsed by libxml2 and it's just storing the text, not any of the tags.
It's also converting \n into white space, so any formatting would be lost
anyway.
For HTML in general, it's a fun task to add highlighting code around a
group of words -- and still keep the HTML valid.
Never mind then, it's still better to see what are the hits.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
