Hi David Thinking Sphinx doesn't do anything special with the excerpt output - that's all down to Sphinx. That said, I'm surprised that it's cutting off what seems to be a 'match' span... I would expect Sphinx to be smarter about that.
As for HTML generally, though - I wouldn't recommend running excepts on text with HTML markup within them. It's a good way to get invalid HTML returned. Cheers -- Pat On 05/02/2011, at 12:02 PM, David Aronchick wrote: > We're doing a match against descriptions on objects - when I searched > for the term "green and yellow", I was returned the following as the > excerpt: > > <span class="clip_description">this <span class="match">yellow</span> > rose turns texans <span class="match">green</span>! a spastic parody, > this switched-on version yee-haws with wide-open filters, quirky > tuning, <span class="ma...</span> > > What happened, you can see, is that the excerpt function cut the last > span in half, and that proceeded to screw up the rest of the page > rendering. Any suggestions? > > -- > You received this message because you are subscribed to the Google Groups > "Thinking Sphinx" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/thinking-sphinx?hl=en. > -- You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/thinking-sphinx?hl=en.
