Version: 0.12.3 (using KDE KDE 3.5.5) Installed from: Debian testing/unstable Packages OS: Linux I have MSN, Yahoo, ICQ, MSN and two Jabber accounts configured in Kopete. I have Enable Automatic Spell Checking enabled in the Settings. Auto-spell check is ticked when I initiate a chat/message with all contacts _except_ Jabber accounts. If I right click and select Auto Spell Check for the Jabber contact, the setting is forgotten for subsequent conversations after I close the message Window. Thanks, Neil
Slight typo above, I don't have two MSN accounts, but one MSN and one AIM. I have confirmed that Auto-Spell check does not get enabled on the AIM account either in the same way as for Jabber. Thanks. Neil
This is a limitation in Qt that can't be fixed until KDE 4. It'll be fixed there.
On Thu, Nov 30, 2006 at 12:57:42AM -0000, Matt Rogers a ecrit: [bugs.kde.org quoted mail] Was this limitation introduced recently as I did not have this problem 2 version back?
Yes, it's because our Jabber protocol supports using rich text now. Rich text and automatic spell checking don't mix, since the highlighting done when there are spelling errors is sent with the message.
This is related to this bug reported some time ago: http://bugs.kde.org/show_bug.cgi?id=136193 Also reported at Kubuntu's bugzilla: https://launchpad.net/bugs/70773 The strange thing is that you have spell checking enabled in an ICQ account. As I see it, the problem is: Those accounts that allow rich text (Jabber or Yahoo) can have spell checking enabled by default if you disable rich text. But those accounts that don't allow rich text (MSN or ICQ) can't have spell checking enabled by default, and you have to enable it right clicking in each window each time. So there are 2 different problems. The one of not being able to use auto spell check on rich text can't be solved until QT4. But the one of not having auto spell check in non_rich_text_accounts doesn't require QT4 to solve it (AFAIK).
On Sat, Dec 02, 2006 at 03:56:41PM -0000, Alberto Gonzalez a ecrit: > ------- Additional Comments From luis6674 yahoo com 2006-12-02 16:56 ------- > This is related to this bug reported some time ago: > > http://bugs.kde.org/show_bug.cgi?id=136193 > > Also reported at Kubuntu's bugzilla: > > https://launchpad.net/bugs/70773 > > The strange thing is that you have spell checking enabled in an ICQ account. As I see it, the problem is: > > Those accounts that allow rich text (Jabber or Yahoo) can have spell checking enabled by default if you disable rich text. But those accounts that don't allow rich text (MSN or ICQ) can't have spell checking enabled by default, and you have to enable it right clicking in each window each time. > > So there are 2 different problems. The one of not being able to use auto spell check on rich text can't be solved until QT4. But the one of not having auto spell check in non_rich_text_accounts doesn't require QT4 to solve it (AFAIK). Slightly different problem: the Setting option is _NOT_ greyed out as with these other bug reports. The option is always selectable, just has no effect. N
Is there a way to say you'd rather have spell checking and NO rich text as I personally don't want rich text anyway and definitely need spell checking.
On Mon, Jan 08, 2007 at 06:48:21PM -0000, Jerry Kilpatrick a ecrit: [bugs.kde.org quoted mail] Not the bug owner, just the reporter... But in answer to the question, I think the answer is no, you can't turn rich text off.. At least I can't see a way of doing so.
I reversed the way this works by default by changing the following function: kopete/chatwindow/chatview.cpp: void ChatView::loadChatSettings() Change the following two lines: bool enableRichText = config->readBoolEntry( "EnableRichText", false ); ... bool enableAutoSpell = config->readBoolEntry( "EnableAutoSpellCheck", true ); This isn't a fix for the issue but if you are desperate to the get the spell checking working it will at least give you a temporary work around. Hope this helps someone!
this is not a good thing to do! Don't do it! If the auto spell checker thinks you'll misspelt a word, you will send out red text to the other client. Turn off rich text instead. For KDE 3, this is the only thing we can do. We should have a proper fix for KDE 4 (hence the reason it's marked LATER)