[ 
https://issues.apache.org/jira/browse/LUCENE-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859989#action_12859989
 ] 

Robert Muir commented on LUCENE-2413:
-------------------------------------

Does consolidation include contrib/icu, too?

Otherwise we still suffer from similar problems, such as you need this filter 
in contrib/icu to standardize your width differences in CJK text, 
GreekLowerCaseFilter and such that are not really necessary and can be 
satisfied with case folding, etc.
(and really NFKC_Casefold in my opinion should just replace LowerCaseFilter in 
every single last one of these analyzers)


> Consolidate all (Solr's & Lucene's) analyzers into contrib/analzyers
> --------------------------------------------------------------------
>
>                 Key: LUCENE-2413
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2413
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Analysis
>            Reporter: Michael McCandless
>             Fix For: 3.1
>
>
> We've been wanting to do this for quite some time now...  I think, now that 
> Solr/Lucene are merged, and we're looking at opening an unstable line of 
> development for Solr/Lucene, now is the right time to do it.
> A standalone module for all analyzers also empowers apps to separately 
> version the analyzers from which version of Solr/Lucene they use, possibly 
> enabling us to remove Version entirely from the analyzers.
> We should also do LUCENE-2309 (decouple, as much as possible, indexer from 
> the analysis API), but I don't think that issue needs to block this 
> consolidation.
> Once we do this, there is one place where our users can find all the 
> analyzers that Solr/Lucene provide.

-- 
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]

Reply via email to