Created attachment 116709 [details] Spellchecking a full sentence with nonsensical suggestions Two issues with spellchecker in writer. First, after mistyping a word I finished the sentence, then went back to correct the mistyped word (which I did by typing the missing letters where they belong). The squiggly red underline didn't go away immediately (the second issue,) instead, all the words from the mistyped to the end of the sentence were underlined in red. I can't recall when they got underlined (as I was typing or afterwards,) however when I right-clicked I got the suggestions in the attached screenshot. Clearly Writer thinks the whole sentence is a word, or something similar, as the suggestions are variations (some absurd) on the words and their endings. The second issue is one of UI responsiveness. I remember submitting a patch to lower the latency between changing the text and the spellchecking background thread kicking in (this was in 4.3/4.4 transition time). Whatever happened, the time Writer 4.4.3 is taking to refresh the spelling squiggles is the worst I've ever seen. This is very frustrating to users as they have to second guess the UI, especially after fixing a typo the red underline becomes a false alarm that is distracting rather than helpful.
Without reproducbile steps this may be difficult to confirm. Was there anything special about the paragraph, such as it being in a frame or section, or part of numbering? Did the paragraph wrap at any point? Were multiple languages involved? Was there scrolling through pages of images just before? Was the document just opened and still loading? The closest I could get to having the whole line with red squiggles was pasting a sentence to the end of a misspelled word (no space). The squiggles under the whole paragraph quickly disappeared to be replaced by squiggles under the orginial word and the first word from the paste. Perhaps there is an instance where it is possible to beat the clock and type in the correct characters and the squiggles stay. Windows Vista 64 Version: 4.4.4.3 Build ID: 2c39ebcf046445232b798108aa8a7e7d89552ea8 4.4.3.2
I realize this could be hard to reproduce, but wanted to make a note of it anyway. The document was in web-mode. It's a reasonably large document with multiple languages, but no sections or framing (a few tables here and there). The paragraph in question had nothing special about it to note. It was probably a few 100 words long. While I had seen extended squiggles as you describe, I hadn't been able to get incorrect spellcheck suggestions until this incident. It might be a timing issue, but I had plenty of time to check the suggestions multiple times (multiple right-clicking) and to capture it. Somewhere in the code the spellchecker isn't stopping at spaces to delimit words and thinks it's within the same word when it's actually dealing with multiple words. I might try digging in the code, but my time has been very scarce as of late.
what about upgrading to LibO 4.4.4.3 and resetting the user profile? https://wiki.documentfoundation.org/UserProfile
Created attachment 116978 [details] History is spelled correctly however is says its not. History is spelled correctly however is says its not.
I tested this out on Linux 4.4.3.2 with a normal .odt document. This maybe is a hack? Is this something specific to these words? (throught history) Error: History is spelled correctly however is says its not?
@Asher - I see "throught histroy" and not "throughout history" in your attachment. Which got me thinking... Check Tools -> Options -> Language Settings -> Writing Aids and edit the user-defined dictionaries to see if words in that sentence are in there. Maybe there are two or more words together and when you misspell part of it then it will come up with the whole of it underlined? If a paragraph was set to another language but you type in, say, English, then it will be underlined. Then at some point it got added to the dictionary but spaces should stop that from happening unless the language allows for that(?). Even then, it would be under a different language so when a paragraph is set to English that entry should not be available... There is also the bug with comments in the middle of a word causing underlining.
I wish I could stay up all night and help debug this. It seems to be a pretty serious issue.
I have had the same problem. I clear out collected words [actually fragments, mispellings, etc.] and disable autocorrect.
very strange issue... I make heavey use of the autocorrect feature (I have collected more than 350000 autocorrect replacements) and I've never experienced such a bug... are you guys able to reproduce that bug even with a clean new profile? https://wiki.documentfoundation.org/UserProfile
so, after 1 year with no replies I set status to NEEDINFO please retest with a recent LibO version (5.1.5 and 5.2.2 are available at the moment) and set status to RESOLVED WORKSFORME if bug is gone or set it back to NEW if issue persists.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20170502
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170531