Today konversation (KDE IRC client) got support for per-channel configurable spell-checking. This means that depending on the channel you write in, a different dictionary can be pre-selected. With the standard implementation I stumbled over a bug that when changing channels (which takes the focus from the KTextEdit box) the wrong dictionary is used for the highlighter (the spell checker itself seemed to use the correct one). According to one of the konversation developers: http://quickgit.kde.org/index.php?p=konversation.git&a=commit&h=e5203323f4ae68601749301941628f2adbadf782 "KTextEdit creates a new Sonnet::Highlighter on every FocusInEvent and then forgets to re-apply the previous set spell checking lan- guage, so let's "take over" highlighter creation by implementing the virtual and follow it up by reapplying the language setting ourselves." Reproducible: Always Steps to Reproduce: 1. Get a konversation build prior to e5203323f4ae68601749301941628f2adbadf782 2. Select two different languages for two different IRC channels 2a. if you need help for that: connect to an IRC network and join two random channels, e.g. ##1234testtest and ##xyztesttest on freenode. In the context menu of the input field in one channel set the language to e.g. french, and english in the other. 3. Switch between them Actual Results: Even though the correct language is selected in the context menu, the wrong dictionary is used. Expected Results: The correct dictionary is used
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!