Maybe a new highlighter with no attempt at summarising could more
easily address phrase support for small pieces of content. It will
always be hard to faithfully represent all possible query match logic
- especially if there are NOTs, ANDs and ORs mixed in with all the
term proximity logic e.g. NotNear. Some compromise is required. I did
suggest that spans maybe a better basis for highlighting than terms
and pointed at some existing code to get you along this path - see
here http://marc.theaimsgroup.com/?l=lucene-user&m=112496111224218&w=2
Had not explored the link yet. That is the code I found and am using. It
will not extract spans in all cases then? I tried some basic tests and
it seemed to work great...I implemented a simple highlighter that does
not deal with highlighting overlap. I assume now that a complicated
query will not properly be extracted then? I guess I have some testing
to do.
- Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
