Kile ⇒ Spell Check fails for long Words

[basak]

Hi,

I'm using Kile on Windows, and I haven't had any trouble except spell checking tool.

The problem is that my spell checker doesn't recognize very long words. For example, if i write "specification", it somehow assumes that it is spelled wrong. When I click on the word, I can see the word itself on the suggested words list. However, even if I choose the same word from the list, the red underline remains.

When I select "Add Word", then it corrects the word and remembers it in further uses.

Windows version; Vista and 7
KDE version: 4.5.4
Kile version: 2.0.86

[oscarlevin]

I too have this problem and would love to see a resolution. I might add that this is not purely a Kile problem - I also use Kate for windows (the editor is the same) and the problem appears there. Maybe a problem with aspell? Anyway, if you or anyone else figures this out, I would love to hear about it.

[SaarDaniel]

Hi!

I am suffering exactly the same problem as the two of you! I am working with KDE for Windows and Kile for several months now, and I am really satisfied with this editor, but the problem with wrong spell-checking of long words is still bugging me (and the reason why I encountered this thread roughly the fourth time now during a internet search for a solution, so I wanted to reply finally. )

If you found a solution for this or anybody else can tell me, how this problem can be solved, I would be very grateful! Permanently having to apply the "Add Word" quickfix is not a viable option anymore for me, especially for longer texts.

[localghost]

I doubt that the responsible developers will read such reports in a forum like this. Otherwise this thread wouldn't be orphaned. Hence write your reports to the corresponding developers either of KDE or Kile directly.

[SaarDaniel]

Yes, that should have probably been the first place to go, I will do that, thanks for your advice!
Nevertheless, if somebody knows this problem on this forum, I would be glad about sharing the solution.

[SaarDaniel]

Since this thread is still the top search result on the problem, I want to point out that I recently found a workaround which I documented in the KDE bugtracker.