Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 143361 - KWord language dictonary issues?
Summary: KWord language dictonary issues?
Status: VERIFIED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-09 09:40 UTC by Jaak Ristioja
Modified: 2009-02-05 23:54 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jaak Ristioja 2006-08-09 09:40:16 UTC
Every time I start app-office/kword-1.5.2 the following error pops up:

ERROR: No language dictionaries for the language : en_US
Comment 1 Carsten Lohrke (RETIRED) gentoo-dev 2006-08-15 14:24:47 UTC
Please look up, if the spell checker you have configured in controlcenter -> kde components -> spelling verification matches with what you have installed. Aside of the spell checker engine you need also the corresponding dictionary (one of app-dicts/*) installed.
Comment 2 Jaak Ristioja 2006-08-15 15:34:26 UTC
Control Center lists:

Dictionary: ISpell Default
Client: International Ispell

There are no other options listed.

Anyway... ispell isn't installed. Nor are any other app-dicts/*. No installed package on my system seems to depend on them either. Why doesn't koffice depend on a spell checker when it needs one?
Comment 3 Carsten Lohrke (RETIRED) gentoo-dev 2006-08-16 06:26:11 UTC
Well, the problem is not a missing dependency. While we could add the usual workaroud for missing use dependency support

if ! [[ build_with_use kdelibs spell ]] ; then ...

to the ebuild, this wouldn't cut it, since kspell2 (the KDE component) allows you to select spell checkers you don't have installed and KWord apparently allows you to select dictionaries you don't have installed. Moreso the supported spell checking engines are antiquated (no hunspell, no myspell) and the included enchant doesn't support current ispell dicionaries (bug 132433). In short: kspell2 needs an overhaul, if not a complete rewrite and if this happens, then soonest with KDE 4. The current status is anything else than pleasable, but we I don't see that we can do anything substantial about it.
Comment 4 Wulf Krueger (RETIRED) gentoo-dev 2007-04-15 22:14:53 UTC
(In reply to comment #3)
> In short: kspell2 needs an overhaul, if not a complete rewrite and if this
> happens, then soonest with KDE 4. The current status is anything else than
> pleasable, but we I don't see that we can do anything substantial about it.

As none of us seem to have a better solution, I'm closing this as an upstream issue.
Comment 5 Jaak Ristioja 2008-06-05 22:14:16 UTC
Even after installing aspell with some dictionaries, no matter how I configure the spell checking component in the KDE Control Center, KWord still displays the message "ERROR: No language dictionaries for the language : en_US". It always displays "en_US" no matter the language I chose in the Control Center. In KWord settings under "Spelling" the "Default language" combo box only has one option: "en_US"... Using KWord 1.6.3 and KDE 3.5.9.

So looking further into the matter, I managed to work around the problem. To keep it short, kdelibs needs to be built with USE=spell. Therefore I recommend adding "built_with_use kde-base/kdelibs spell" or something like that to the KWord ebuilds.
Comment 6 Jaak Ristioja 2008-06-05 22:46:35 UTC
See http://bugs.kde.org/show_bug.cgi?id=136044
Comment 7 Carsten Lohrke (RETIRED) gentoo-dev 2009-02-04 20:03:18 UTC
The fix is in the repository for a while now, see bug 202627.
Comment 8 Jaak Ristioja 2009-02-04 20:43:53 UTC
(In reply to comment #7)
> The fix is in the repository for a while now, see bug 202627.
> 

Well, at least that definately hides the real problem from the end-user quite well. :)
Comment 9 Carsten Lohrke (RETIRED) gentoo-dev 2009-02-05 23:54:39 UTC
(In reply to comment #8)
> Well, at least that definately hides the real problem from the end-user quite
> well. :)

I can't and won't deny that. ;)