SUMMARY Changing the spell check language from the status bar, does not change the real language for spell check. Still the one set as Default language in Kate options is taken into account. STEPS TO REPRODUCE 1. Load a document with a language different than the default one set in Kate options. 2. Set that language from the status bar language options. 3. Enable spell check from the status bar language options. OBSERVED RESULT The text is still underlined in red (incorrectly spelled) EXPECTED RESULT Remove red underlines for correctly spelled words SOFTWARE/OS VERSIONS Windows 10 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION
Kate 21.08.2: I cannot confirm this behaviour on Linux. I can change the language in the status bar, press, enable automatic spell checking and unknown words are underlined. If I change the language back, the red underlines are removed. Is it still a problem for you? I did notice, however, that enabling autodetection of language cause the spellcheck to not show any spelling mistakes.
I checked with the latest official windows release I have 21.04.0 (present in Microsoft Store), but the problem seems not solved. Since the official windows release is rather old one, I downloaded Kate 21.11.70 nightly (for win64), and the behavior is slightly different: I have mixed text in both Bulgarian and English languages, and Automatic Spell check enabled. It looks the spell check for both languages work simultaneously somehow. I mean, it does not matter which language is selected, the correct/known words in both languages are not red underlined, and incorrect/unknown words (also in both languages) are red underlined. I'm not sure if that is intended and if it should work that way. If yes, then the bug is fixed. However, if that is not intended and the spell checking should be performed only for one selected language, then this probably escalated into another issue. It would be good if someone could comment that behavior.
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!
I'm marking back the issue as REPORTED, since it is not clear if the big is solved or not. I mean, the behavior have changed, but it is not clear if it is correct. Please see my previous comment. Probably someone who works on that functionality could say more.