lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From NightOwl888 <>
Subject [GitHub] lucenenet issue #191: Migrating Lucene.Net to .NET Core
Date Tue, 13 Dec 2016 22:13:04 GMT
Github user NightOwl888 commented on the issue:
    I have nearly finished Highlighter on this branch
    There is still 1 failing test (that doesn't appear to be related to BreakIterator). I
was able to make [hacky solutions for the first 3 issues](
I mentioned [above](,
but after the link you provided I am convinced that none of them will suffice for production,
and we will need a `RuleBasedBreakIterator` to be sure we have all of the breaking rules setup
correctly for international support.
    You can pull this now if you wish - let me know if you need me to work on that failing
    Some classes that I have already ported that you may wish to migrate into icu-dotnet:
    - [BreakIterator](
- Note that is one change from the original  - the Text property returns string instead of
CharacterIterator. In hindsight, this change may not have been necessary.
    - [CharacterIterator](
- a GetTextAsString() method was added primarily so we can get the text to pass on to icu-dotnet,
and the documentation hasn't yet been migrated from Java.
    - [StringCharacterIterator](
- Exactly like Java (but documentation not yet migrated).
    - [IcuBreakIterator](
- If you remove the hacks I put in to emulate the RuleBasedBreakIterator, it would probably
be a useful addition to icu-dotnet.
    - [TestBreakIterator](
- A partial set of tests that verify the sentence and word breaking RuleBasedBreakIterator
    Note that CharacterIterator is a dependency of [CharArrayIterator](,
but since that is in Analysis.Common (which already depends on icu-dotnet), we can completely
remove all of these classes from Lucene.Net once the functionality is available in icu-dotnet.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message