lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shad Storhaug (JIRA)" <>
Subject [jira] [Commented] (LUCENENET-566) Port Lucene.Net.Analysis.ICU
Date Tue, 25 Jul 2017 08:40:00 GMT


Shad Storhaug commented on LUCENENET-566:

Integrated the Collation functionality into Lucene.Net.ICU.

We can get 6 more classes from analysis icu by contributing the Normalizer2 class to the
project. And the remaining 2 from the Icu namespace by contributing the Transliterator, but
that would be a big project.

The stuff in the Segmentation namespace is more difficult. There is no concept of "script
inheritance" in .NET as far as I can tell, and porting the UScript class over and all its
dependencies might not be trivial. I haven't yet read the link from the documentation comments
that explains the what the goal is - maybe there is a way to do this in .NET by changing to
a different approach.

> Port Lucene.Net.Analysis.ICU
> ----------------------------
>                 Key: LUCENENET-566
>                 URL:
>             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

View raw message