[
https://issues.apache.org/jira/browse/LUCENE-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878354#action_12878354
]
Shai Erera commented on LUCENE-2498:
------------------------------------
FWIW, I've implemented sentence boundary support by returning a special token
(Type.EOF) from the Tokenizer and created a EOSFilter which increments the
posIncr attribute (set it to 100). I haven't been following UAX#29 issue, but
I'm sure it's a great thing :).
I've used the following
http://www.fileformat.info/info/unicode/category/Po/list.htm to detect EOS +
\u0085 (Next Line (NEL). I'm sure though that there are other markers as well.
> add sentence boundary charfilter
> --------------------------------
>
> Key: LUCENE-2498
> URL: https://issues.apache.org/jira/browse/LUCENE-2498
> Project: Lucene - Java
> Issue Type: New Feature
> Components: contrib/analyzers
> Reporter: Robert Muir
>
> From the discussion of LUCENE-2167:
> It would be nice to have a CharFilter? to mark sentence boundaries.
> Such functionality would be useful for:
> * prevent phrase queries with 0 slop from matching across sentences
> * inhibiting multiword synonyms, or shingles, etc.
> For sentence boundary detection we could use Jflex's support for the Unicode
> Sentence_Break property etc,
> and the UAX#29 definition as a default grammar.
> One idea is to just mark the boundaries with a user-provided String.
> As a simple use-case, a user could then add this string to a stopfilter, and
> it would introduce a position increment.
> This would inhibit phrase queries, etc.
> a user could use the sentence-markers to do more advanced processing
> downstream.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
