Good to see someone else working with the .net platform, but apparently we had the same idea and the same project. Unfortunately, we did not talk before... probably would have saved a lot of time on both sides.
I successfully ported the whole library to c# a few weeks ago, I had to change quite a bit to make everything compatible (also to keep the library extensible) with the OpenNLP. If you want to take a look at how I solved the problems of to port the link of my project is: https://github.com/knuppe/SharpNL Or even better If you want to work in partnership would be great, since I’m starting to add some features/tools to the library. Best regards, Gustavo K. 2014-11-16 17:41 GMT-02:00 Mark Johnston <[email protected]>: > Hello, > > just a quick email, I've recently started a port of Open NLP to the .NET > framework, and have just created the first commit on github, in case anyone > is interested. > > From the Readme: > > "opennlp4net is a port of OpenNLP to the .NET framework. The code is > written in C#, and is very much a work-in-progress. The code in this > library should not even be considered alpha, and only exists because there > are no other open source natural language tools available for .NET. > > The code was initially ported using an automated tool for the mechanical > conversion, then attempts were made to fix functionality piece by piece, > function by function, by replacing JAVA-isms with .NET equivalents. The > result is not pretty, but a number of the tools work via the API: > > the sentence detector > > the tokenizer > > the namefinder > > the chunker > > the postagger > > The parser does not work currently, neither does any functionality relating > to training the models." > > The repository is at: https://github.com/quicquam/opennlp4net. > > If anyone wants to help me to get this port up to speed, please contact me > via this forum. The solution includes models (which the port uses > unconverted), and test projects which have an absolute minimal test set for > the tools listed above. > > I am currently trying to get the parser tool working, but having issues I > think related to the fact that the model file is nested, and the code that > I have written can't cope with that yet. > > Cheers, > > Mark >
