lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shad Storhaug (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENENET-566) Port Lucene.Net.Analysis.ICU
Date Thu, 20 Jul 2017 22:01:00 GMT

    [ https://issues.apache.org/jira/browse/LUCENENET-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095456#comment-16095456
] 

Shad Storhaug commented on LUCENENET-566:
-----------------------------------------

I ported the Collation classes and have 17/20 tests passing.

I also took a shot at porting the rest of the classes. But, it is looking like they are wrappers
around functionality that is not available (or at least not ported over) in icu.net. The only
thing other than collation that seems useful is the Normalization filter and its factory.

I am debating whether to even have a separate Lucene.Net.Analysis.ICU NuGet package for this,
or just put all of this functionality into the shared Lucene.Net.ICU package, since that is
where the collation stuff from Analysis.Common would ordinarily go (if it worked) anyway.

> Port Lucene.Net.Analysis.ICU
> ----------------------------
>
>                 Key: LUCENENET-566
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-566
>             Project: Lucene.Net
>          Issue Type: Task
>          Components: Lucene.Net.Analysis.ICU
>    Affects Versions: Lucene.Net 4.8.0
>            Reporter: Shad Storhaug
>            Assignee: Shad Storhaug
>            Priority: Minor
>              Labels: features
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> The Analysis.ICU component is a better option for Collation than Collation namespace
in Analysis.Common because in Java it uses icu4j, which is a close match to icu-dotnet.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message