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] [Resolved] (LUCENENET-566) Port Lucene.Net.Analysis.ICU
Date Tue, 13 Aug 2019 05:42:00 GMT

     [ https://issues.apache.org/jira/browse/LUCENENET-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shad Storhaug resolved LUCENENET-566.
-------------------------------------
       Resolution: Implemented
    Fix Version/s: Lucene.Net 4.8.0

This was resolved by porting a large portion of ICU4J to .NET ([ICU4N|https://github.com/NightOwl888/ICU4N]).
From there, it was all down hill. 100% implemented and passing.

> 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
>             Fix For: Lucene.Net 4.8.0
>
>   Original Estimate: 120h
>          Time Spent: 12h
>  Remaining Estimate: 108h
>
> 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
(v7.6.14#76016)

Mime
View raw message