REF: Discussion: Could we merge project/packages both MeCab.DotNet and LibNMeCab

[kekyo]

Refer:

komutan/NMeCab#32

[kekyo]

My first post translated in English by Google:

---

Hello, It was good to have continued to update the person's komutan. My MeCab.DotNet is also updating mainly on environmental issues, but I'm wondering what to do because I can't keep up with the changes of komutan. Better yet, I thought about integrating it with this project, so I first created an issue to hear my opinion. In the first place, MeCab.DotNet was ported because I wanted to use it in the .NET Core environment for a certain event, but after it was released, I found that it was also used by overseas people ( It is a situation where we are continuing to update with a sense of duty, mainly in terms of development environment (so that you do not have to worry about new versions of .NET Core, for example). (The event is a long sentence, but I have summarized it in my blog.) I use it in some private projects (mainly private), but I do not have knowledge of morphological analysis itself, so I mentioned above. I am worried that it has been updated within the range of. Probably, komutan is more advanced in improving the functions of the core part, so I think that there is a part where we can cooperate in terms of updating and enhancing the functions in the development environment as it is now. So, I thought about integrating the two projects, but if there is a reason that it is easier to develop if it is forked separately, it does not matter at all, so please say so. I think it's a project. I haven't really pondered the issues with integration yet: Source code integration: I'll do my best :) I think the biggest external interface issue is namespaces. In my proposal, I think it would be better to take a structure that can be referenced in either of the two namespaces for a while, add Obsolete, etc., and finally move to either one. NuGet package: Consider a method of distributing a library with a double interface definition as described above in separate packages (with the same contents), adding Obsolete, and finally unifying to either one. If there are some (non-cohabitable) incompatibilities of methods or properties, compromise them with breaking change. For the time being, I wrote down what I have come up with, but if you have any opinions, please.

[kekyo]

Processing: komutan/NMeCab#34

[kekyo]

Processing: komutan/NMeCab#35