lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (LUCENE-6874) WhitespaceTokenizer should tokenize on NBSP
Date Sat, 14 Nov 2015 19:22:11 GMT


ASF subversion and git services commented on LUCENE-6874:

Commit 1714354 from [~thetaphi] in branch 'dev/trunk'
[ ]

LUCENE-6874: Add a new UnicodeWhitespaceTokenizer to analysis/common that uses Unicode character
properties extracted from ICU4J to tokenize text on whitespace

> WhitespaceTokenizer should tokenize on NBSP
> -------------------------------------------
>                 Key: LUCENE-6874
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/analysis
>            Reporter: David Smiley
>            Assignee: Uwe Schindler
>            Priority: Minor
>         Attachments: LUCENE-6874-chartokenizer.patch, LUCENE-6874-chartokenizer.patch,
LUCENE-6874-chartokenizer.patch, LUCENE-6874-jflex.patch, LUCENE-6874.patch, LUCENE_6874_jflex.patch,
icu-datasucker.patch, unicode-ws-tokenizer.patch, unicode-ws-tokenizer.patch, unicode-ws-tokenizer.patch
> WhitespaceTokenizer uses [Character.isWhitespace |]
to decide what is whitespace.  Here's a pertinent excerpt:
> bq. It is a Unicode space character (SPACE_SEPARATOR, LINE_SEPARATOR, or PARAGRAPH_SEPARATOR)
but is not also a non-breaking space ('\u00A0', '\u2007', '\u202F')
> Perhaps Character.isWhitespace should have been called isLineBreakableWhitespace?
> I think WhitespaceTokenizer should tokenize on this.  I am aware it's easy to work around
but why leave this trap in by default?

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message