New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spellcheck doesn't see dictionaries on macOS after upgrading to Geany 1.38 #30
Comments
I'm going to slide this to the Geany-osx repository since (AFAICT) that bundle includes enchant, but no backends. This may be deliberate and you have to install them yourself, but the OSX packager will know. |
I haven't tried it but at least from this code https://github.com/AbiWord/enchant/blob/ff5e31d0535ba93f27010a6b1ac50e87252bd759/src/lib.c#L116 it seems that enchant gets the config files from |
Unfortunately, moving dictionaries to ~/.config/enchant doesn't seem to help. |
There was indeed a problem where the enchant library didn't correctly find the corresponding spelling module. I created a new build here, would you give it a try? |
It seems like in this build, the plugin shows language names from the
|
OK, one more attempt - hunspell is now compiled and enchant_hunspell.so module is also added to the bundle. The download link is the same as before. Does it work now? |
It seems to work now. I have Russian.dic and en_US.dic files; Russian is now in the list, but since the languages from AppleSpell.config are still there, I'm not sure whether en_US is my dictionary file or the one from AppleSpell. Thanks! |
You can rename the |
Closing as I believe it's fixed now. |
I've updated Geany to 1.38 (geany-1.38_osx-2.dmg) and found that it no longer sees the dictionaries. In debug messages I found that Enchant is now 2.2.15 (was 1.x in Geany 1.37), so, as README suggests, I moved the dictionaries to the "hunspell" subdirectory while leaving the path in the configuration dialog untouched (parent directory of "hunspell"). Unfortunately, this didn't help, and the plugin still gives error "The Enchant library couldn't be initialized (unknown error (maybe the chosen language is not available))".
The text was updated successfully, but these errors were encountered: