This I had with Kde 3.5.4 and now also with 3.5.5. Someone reported this to the kde bugs, but I think It could be gentoo specific thing.Anyway I have aspell -v @(#) International Ispell Version 3.1.20 (but really Aspell 0.60.4) aspell dump dicts en en-variant_0 en-variant_1 en-variant_2 en-w_accents en-wo_accents en_CA en_CA-w_accents en_CA-wo_accents en_GB en_GB-ise en_GB-ise-w_accents en_GB-ise-wo_accents en_GB-ize en_GB-ize-w_accents en_GB-ize-wo_accents en_GB-w_accents en_GB-wo_accents en_US en_US-w_accents en_US-wo_accents it But under Kword the spellcheking shows me just en_US and further it say's on start : kword: ERROR: No language dictionaries for the language : en_US The spellchecking engine works under kspell1 (under kcontrol and all other kde stuff) but kspell2 (which is used in kword) just won't.
The problem is that kword needs kspell2 and for some reason, that has been disabled in the ebuild for kdelibs: ie, # TODO - kspell2 Xspell plugins are automagically detected. # As nothing uses kspell2, don't install them. sed -i -e "s:plugins::" "${S}/kspell2/Makefile.am" || die "sed failed" and also, regardless of the spell useflag, the ebuild disables hspell and aspell, ie --without-hspell --without-aspell" A comment in an older ebuild said that hspell was disabled because it needs 0.90 or above, but 1.0 has been available since 03 Sep 2006 delete the sed hack and the --without lines from the ebuild, emerge the latest hspell and aspell, then reemerge kdelibs. kword spell checking will now work
Now *that* is amazingly stupid. Disabling kspell2??? Come on! Why do you think we ship code? Is this going to be fixed at the gentoo level?
kspell2 had more troubles than advantages last time (KWord still worked, btw), and solved the HSpell problem.
Ok bug is comfimed, I reemerged kdelibs with that changes and spell checking is working.. Closing this bug report, hopefully it will be integrated in next release of kdelibs.
Don't close bug reports if we didn't do anything.
Reply to #3: You don't get spellchecking in KOffice-1.5 or 1.6 if you don't have kspell2.
I'm on it now (sorry for being late, real life job required me not to handle this before). Please not that the affected versions are _unstable_ just for the sake of news. This will be fixed by bumping four times kdelibs: kdelibs-3.5.4-r3 and kdelibs-https://bugs.gentoo.org/show_bug.cgi?id=1524173.5.5-r4 will enable kspell2's aspell plugin with spell useflag enabled, ispell is no more an option in || (), as it will detected at runtime anyway, hspell will be disabled. kdelibs-3.5.4-r4 and kdelibs-3.5.5-r5 will enable kspell2's aspell plugin with spell useflag enabled, ispell still won't be an option in || (), and hspell will be enabled with linguas_he. I'll be asking for arch teams to re-keyword 3.5.4-r4 and 3.5.5-r5, the stable mark will happen on 3.5.4-r3.
And now bug is closed ... Opened: 2006-10-22 13:00 PST Closed: 2006-10-25 13:32 PST (about) this means 3 days and half an hour....
(In reply to comment #7) > ispell is no more an option > in || (), as it will detected at runtime anyway, It should be in || () so that it's possible to emerge kdelibs with USE=spell without also installing aspell. Could you please put that back in?
No. Please read the history of this bug and bug #152818. ispell support is _always_ built, and spell useflag _always bring aspell in. This because ispell is just runtime dependency. If you don't want aspell, don't enable spell useflag for kdelibs, it will still have ispell support.
(In reply to comment #10) > No. Please read the history of this bug and bug #152818. > If you don't want aspell, don't enable spell useflag for kdelibs, it will still > have ispell support. That wasn't clear from this bug report, and I had no reason to suspect it was explained in bug #152818. :) Thanks.
