lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From NightOwl888 <>
Subject [GitHub] lucenenet issue #181: Analysis work
Date Mon, 22 Aug 2016 16:54:20 GMT
Github user NightOwl888 commented on the issue:
    Sure. I am currently working on,
which I plan to merge into #179 (probably within the next few hours).
    About the only thing left to port is the [collation namespace](,
a few missing tests and some obsolete functionality (I wasn't planning on doing these, so
you are welcome to them). You might want to also check to make sure I didn't miss anything
    There are also currently 45 failing tests out of about 1400. Most of the failing tests
are in the Synonym and Th namespaces if you want to have a go at them.
    Additionally, I haven't gone through the API to ensure the accessibility of fields and
members is the same as it was in Java. Certain functionality, such as the Pattern namespace
could use some more overloads to make them more .NET friendly (for example, passing regex's
in as strings/regex options in addition to passing in pre-made Regex objects). I am sure there
must be other tweaks to the API that need to be done, I was just giving this as an example.
    FYI - I am currently working on the Hunspell namespace - the rest is fair game. Just make
your intentions clear so we don't duplicate work.

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