Chromium implementation

[wobu]

This isn't an issue, more a discussion for further improvements.

The native hunspell implemenation expects a patsh to physically existing dictionary files. This is quite annoying if u want distribute your software, cause you have to ensure the dictionaries are available there.

Today i crumbled accross the chromium hunspell implementation which is based on the original one with some documented changes.

The interesting part is:

Change the input params of the constructors to receive a BDICTReader instead of a file path.

I don't know the exact behavior or implementation but shipping your Java API with this implementation and with their provided .bdic files would be a great benefit in my opinion.