Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (herse.apache.org: domain of wunderwood@netflix.com
 designates 216.35.131.152 as permitted sender)
User-Agent: Microsoft-Entourage/11.3.2.061213
Date: Wed, 03 Jan 2007 17:35:04 -0800
Subject: Re: Better highlighting fragmenter
From: Walter Underwood <wunderwood@netflix.com>
To: <solr-user@lucene.apache.org>
Message-ID: <C1C199C8.3E1C%wunderwood@netflix.com>
Thread-Topic: Better highlighting fragmenter
Thread-Index: AccvoI7GzR2kCpuTEdurJwAUUTF+rA==
In-Reply-To: <3d2ce8cb0701031713s9e19b88s144b985cef502b5f@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

On 1/3/07 5:13 PM, "Mike Klaas" <mike.klaas@gmail.com> wrote:

> Generally, we should strive for a high-quality out-of-the-box
> highlighting in Solr.  That might involve making things like better
> fragmenters and a few other tricks(*) the default setup, and providing
> a "quick & dirty" setting for speed demons.

I've implemented this before, once in Python and once in C, so I'd
be glad to take a look at it. I'm not sure I have time to do a lot
of implementation, but I'd sure be glad to help.

We tried several APIs and decided that the best was an array of
String with the odd elements containing the strings that needed
highlighting. That made it really easy to step through and wrap
highlighted stuff with the right markup, while properly escaping
any angle brackets in the source text.

I'm not sure how easy it is to handle that format in XSLT, but
it might be worth it. Embedded highlight markup just doesn't work.

wunder
-- 
Walter Underwood
Search Guru, Netflix