Bug 192298 - red underline words disappears
Summary: red underline words disappears
Status: RESOLVED DUPLICATE of bug 87035
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kspell (show other bugs)
Version: 4.2
Platform: Mandriva RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Zack Rusin
URL:
Keywords:
: 206365 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-05-11 09:23 UTC by Dimitrios Glentadakis
Modified: 2010-01-31 06:45 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Dimitrios Glentadakis 2009-05-11 09:23:12 UTC 
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Mandriva RPMs

The underliner of wrong spell words does nt work properly
In the beggining of typing it underline in red the wrong words but after a while the underline disappears. I use two applications very often , konqueror and lokalize, and the underline of wrong spelling almost does nt work at all. after the first spellcheck the underline is almost disabled
Comment 1 Dario Andres 2009-06-29 21:22:24 UTC 
- Are you still experiencing this bug ?
From what I saw in the Sonnet/highlight code, it suspends drawing the underline after an ammount of bad written words (I'm not sure *why*, performance reasons?)

-Do you think this is the case?
Thanks
Comment 2 Dimitrios Glentadakis 2009-06-30 21:18:45 UTC 
yes i think that it hapens something like that. But in the first time and for the first translation string it is working fine. After the word is nt underlined when the spelling is wrong but sometimes i see the underlines activated by them selves if i add the point at the end of the phrase "." or when i corrige the spelling of one word. 
The sure is that spelling doesnt works properly.
Comment 3 Dario Andres 2009-10-11 17:56:39 UTC 
*** Bug 206365 has been marked as a duplicate of this bug. ***
Comment 4 Christoph Feck 2010-01-31 06:45:44 UTC 

*** This bug has been marked as a duplicate of bug 87035 ***