Hello Dev's at Lucene, I'm Roy.
Currently we are using the Java implementation, as well as the dotnet implementation of Lucene.
We've greatly enjoyed your works in our efforts to expand our app to accommodate and analyze multiple languages.
However, I've encountered a roadblock while working with the Korean analyzer.
There is a adequate implementation of the Korean (Nori) analyzer in Java, but not for dotnet.
Upon communicating and working with the developers at Lucene dotnet, there seem to be some changes to the dependencies which has made debugging almost impossible with the oldest versions of the Korean Analyzer.
The developers at Lucene dotnet are requesting that a backport of the Korean Analyzer to Java 4.8.0 to serve as a basis for porting the Java implementation to dotnet.
If this version could be provided in a dedicated branch, it'd be greatly appreciated so that this work can move forward, as many other developers are also anticipating for this feature to be made available in dotnet.
Thank you for your contributions!
Best regards,
Roy Hwang
Currently we are using the Java implementation, as well as the dotnet implementation of Lucene.
We've greatly enjoyed your works in our efforts to expand our app to accommodate and analyze multiple languages.
However, I've encountered a roadblock while working with the Korean analyzer.
There is a adequate implementation of the Korean (Nori) analyzer in Java, but not for dotnet.
Upon communicating and working with the developers at Lucene dotnet, there seem to be some changes to the dependencies which has made debugging almost impossible with the oldest versions of the Korean Analyzer.
The developers at Lucene dotnet are requesting that a backport of the Korean Analyzer to Java 4.8.0 to serve as a basis for porting the Java implementation to dotnet.
If this version could be provided in a dedicated branch, it'd be greatly appreciated so that this work can move forward, as many other developers are also anticipating for this feature to be made available in dotnet.
Thank you for your contributions!
Best regards,
Roy Hwang