Greetings, all, I'm working with Geany 1.23.1, and am hoping to make Geany my only editor/ide. However, I can't do that, unless/until it provides spellcheck functionality. Currently, I'm forced to open one of my other editors, in order to accomplish that. That siad; I'm on a FreeBSD/amd64 box. Source for it is current (3 days old). Geany version 1.23.1, I don't know if the spellcheck has a version, but the version of Enchant is: 1.6.02. I see there were some problems with it on Windows, but I see no reason to think that applies here. I have gone to great lengths to make the plugin work. I installed every single engine into Enchant that Enchant supports; ASPELL,HSPELL,HUNSPELL,ISPELL,ZEMBEREK. They are ALL currently installed. But Geany emits:
The Enchant library couldn't be initialized (unknown error (maybe the chosen language is not available)).
and provides no option to choose the desired engine. FWIW, my choice would be Ispell, and en/us. Any thoughts on how I might overcome this problem?
Thank you for all your time, and consideration.
--Chris
On 02/03/14 08:33, Development wrote:
Greetings, all, I'm working with Geany 1.23.1, and am hoping to make Geany my only editor/ide. However, I can't do that, unless/until it provides spellcheck functionality. Currently, I'm forced to open one of my other editors, in order to accomplish that. That siad; I'm on a FreeBSD/amd64 box. Source for it is current (3 days old). Geany version 1.23.1, I don't know if the spellcheck has a version, but the version of Enchant is: 1.6.02. I see there were some problems with it on Windows, but I
I'm using 1.6.0 on Linux without problems.
see no reason to think that applies here. I have gone to great lengths to make the plugin work. I installed every single engine into Enchant that Enchant supports; ASPELL,HSPELL,HUNSPELL,ISPELL,ZEMBEREK. They are ALL currently installed. But Geany emits:
The Enchant library couldn't be initialized (unknown error (maybe the chosen language is not available)).
and provides no option to choose the desired engine. FWIW, my choice would be Ispell, and en/us. Any thoughts on how I might overcome this problem?
Could you try on the command line the following command:
# enchant-lsmod
to check if Enchant knows its engines? This command should output a few engines installed on the system (e.g. "hspell (Hspell Provider)").
And please try:
# echo "hllo" | enchant -a -d en_US
that should output a list of alternative spellings for "hllo".
And could you check what is configured as "language" in the config file ~/.config/geany/plugins/spellcheck/spellcheck.conf
Regards, Enrico
Greetings, and thank you for your reply.
On 02/03/14 08:33, Development wrote:
Greetings, all, I'm working with Geany 1.23.1, and am hoping to make Geany my only editor/ide. However, I can't do that, unless/until it provides spellcheck functionality. Currently, I'm forced to open one of my other editors, in order to accomplish that. That siad; I'm on a FreeBSD/amd64 box. Source for it is current (3 days old). Geany version 1.23.1, I don't know if the spellcheck has a version, but the version of Enchant is: 1.6.02. I see there were some problems with it on Windows, but I
I'm using 1.6.0 on Linux without problems.
see no reason to think that applies here. I have gone to great lengths to make the plugin work. I installed every single engine into Enchant that Enchant supports; ASPELL,HSPELL,HUNSPELL,ISPELL,ZEMBEREK. They are ALL currently installed. But Geany emits:
The Enchant library couldn't be initialized (unknown error (maybe the chosen language is not available)).
and provides no option to choose the desired engine. FWIW, my choice would be Ispell, and en/us. Any thoughts on how I might overcome this problem?
Could you try on the command line the following command:
# enchant-lsmod
Here's the output:
# enchant-lsmod aspell (Aspell Provider) ispell (Ispell Provider) myspell (Myspell Provider)
to check if Enchant knows its engines? This command should output a few engines installed on the system (e.g. "hspell (Hspell Provider)").
And please try:
# echo "hllo" | enchant -a -d en_US
that should output a list of alternative spellings for "hllo".
# echo "hllo" | enchant -a -d en_US @(#) International Ispell Version 3.1.20 (but really Enchant 1.6.0) Couldn't create a dictionary for en_US
This was interesting to me. Because when I chose /usr/share/dict in the dictionary field for the plugin, the plugin still complained about no enchant lib.
And could you check what is configured as "language" in the config file ~/.config/geany/plugins/spellcheck/spellcheck.conf
# cat ~/.config/geany/plugins/spellcheck/spellcheck.conf
[spellcheck] check_while_typing=false use_msgwin=false show_toolbar_item=true show_editor_menu_item=true dictionary_dir=
Regards, Enrico
Hope this helps, and thank you very much for your thoughtful reply.
--Chris
-- Get my GPG key from http://www.uvena.de/pub.asc
Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Hi,
Any thoughts on how I might overcome this problem?
Could you try on the command line the following command:
# enchant-lsmod
Here's the output:
# enchant-lsmod aspell (Aspell Provider) ispell (Ispell Provider) myspell (Myspell Provider)
that's fine.
to check if Enchant knows its engines? This command should output a few engines installed on the system (e.g. "hspell (Hspell Provider)").
And please try:
# echo "hllo" | enchant -a -d en_US
that should output a list of alternative spellings for "hllo".
# echo "hllo" | enchant -a -d en_US @(#) International Ispell Version 3.1.20 (but really Enchant 1.6.0) Couldn't create a dictionary for en_US
This was interesting to me. Because when I chose /usr/share/dict in the dictionary field for the plugin, the plugin still complained about no enchant lib.
Hmm, to be honest I'm not sure whether the dictionary path setting works at all on Unix-like systems. IIRC only one engine (myspell) implemented this feature at all and is mostly important on Windows. On Unix-like systems enchant usually finds its dictionaries in common or compiled in paths (things like FHS are a great thing).
Anyway, the above error "Couldn't create a dictionary for en_US" is the key. Your dictionaries are installed in /usr/share/dict? It seems for some reason, the engines (ispell, aspell, myspell) don't search in this path or they don't find usable dictionaries in this path.
Could you maybe strace the above enchant command to get an idea where it does look for the dictionary files? I suspect a simple path problem here.
Is there anything special in your setup? I can't imagine enchant/*spell doesn't work out-of-the-box on a FreeBSD system.
Regards, Enrico
Hi,
Any thoughts on how I might overcome this problem?
Could you try on the command line the following command:
# enchant-lsmod
Here's the output:
# enchant-lsmod aspell (Aspell Provider) ispell (Ispell Provider) myspell (Myspell Provider)
that's fine.
to check if Enchant knows its engines? This command should output a few engines installed on the system (e.g. "hspell (Hspell Provider)").
And please try:
# echo "hllo" | enchant -a -d en_US
that should output a list of alternative spellings for "hllo".
# echo "hllo" | enchant -a -d en_US @(#) International Ispell Version 3.1.20 (but really Enchant 1.6.0) Couldn't create a dictionary for en_US
This was interesting to me. Because when I chose /usr/share/dict in the dictionary field for the plugin, the plugin still complained about no enchant lib.
Hmm, to be honest I'm not sure whether the dictionary path setting works at all on Unix-like systems. IIRC only one engine (myspell) implemented this feature at all and is mostly important on Windows. On Unix-like systems enchant usually finds its dictionaries in common or compiled in paths (things like FHS are a great thing).
OK. Had another chance to have a go at resolving this. Here's the output:
# echo "hllo" | enchant -a -d en_US @(#) International Ispell Version 3.1.20 (but really Enchant 1.6.0) & hllo 91 0: hello, halo, halloo, hallow, hollow, Hall, Hill, Hull, hall, hell, hill, hull, hellos, Gallo, jello, lilo, Holly, hilly, holly, Ho, LL, ho, ll, lo, Hal, Halon, halls, halon, halos, helot, help, hills, hulls, allow, alloy, Flo, HBO, HMO, Ill, Lao, Leo, PLO, all, ell, ill, loo, Hale, hale, hole, holy, hula, cello, Hals, Holt, half, halt, held, helm, hilt, hold, hols, hulk, Cleo, Clio, Colo, Ella, Hugo, Milo, Mlle, Polo, ally, filo, hero, hobo, homo, hypo, kilo, oleo, polo, silo, solo, he'll, hello's, Hull's, hall's, hell's, hill's, hull's, halo's, Hal's, I'll
Anyway, the above error "Couldn't create a dictionary for en_US" is the key. Your dictionaries are installed in /usr/share/dict? It seems for some reason, the engines (ispell, aspell, myspell) don't search in this path or they don't find usable dictionaries in this path.
Could you maybe strace the above enchant command to get an idea where it does look for the dictionary files? I suspect a simple path problem here.
Is there anything special in your setup? I can't imagine enchant/*spell doesn't work out-of-the-box on a FreeBSD system.
No special setup per-se'. But FreeBSD provides aspell(1) out-of-the-box "part of System". So I /assumed/, because the dictionary was present, as well as aspell, that all would be good. Not so. Enchant knows nothing about that version. So I had to install a "User" version of my chosen language dictionary (en/US). Having now done so. Everything works as expected/anticipated.
Thank you very much, for taking the time, and trouble to assist me, Enrico.
--Chris
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.asc
Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Hi Chris,
Is there anything special in your setup? I can't imagine enchant/*spell doesn't work out-of-the-box on a FreeBSD system.
No special setup per-se'. But FreeBSD provides aspell(1) out-of-the-box "part of System". So I /assumed/, because the dictionary was present, as well as aspell, that all would be good. Not so. Enchant knows nothing about that version. So I had to install a "User" version of my chosen language dictionary (en/US). Having now done so. Everything works as expected/anticipated.
Thank you very much, for taking the time, and trouble to assist me, Enrico.
You're welcome. Glad to hear it works now.
Regards, Enrico