There is a failure during spell checking, telling to “Change All”, not performs the function of correcting the Following words forgiveness by Google translation Versión: 4.4.3.2 Id. de compilación: 88805f81e9fe61362df02b9941de8e38a9b5fd16 Configuración regional: es_ES
Could not reproduce. Correct all changes all the instances of an erroneous word. Ubuntu 15.04 64-bit Version: 4.4.2.2 Build ID: 40m0(Build:2) Locale: en_US Version: 5.0.0.0.alpha1+ Build ID: 4c665178f49952138835fd318edef8978ac806e3 TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2015-05-12_06:15:42 Locale: en-US (en_US.UTF-8)
*** This bug has been marked as a duplicate of bug 46852 ***
Bug 46852 was about a different issue: using "Correct All" in combination with "Continue checking at beginning of document", the spellcheck process concluding prematurely. That was indeed fixed in LO 6.0. The issue described by Anaya is different: pressing "Correct all" does not correct all the same misspellings throughout the document (or at least, from the active word to the end of the document). And this is still the case in a recent daily build, as well as in OOo 3.3. Bug 75922 alludes to this, but was tracking many different issues with Correct All, so better keep that one as "resolved - works for me". This bug here can be reproduce with the default English dictionaries, and the following steps: 1. In a new Writer document, with document in any English variant, paste the following paragraphs (unformatted): dogg dogg catt dogg frogg frogg frogg catt dogg dogg catt frogg, dogg, catt 2. With cursor at beginning of document, start Tools > Spelling (F7) 3. Click "Correct All" for the suggestion "dogg -> dog" Result A: first two paragraphs are corrected, not the rest. 4. Click "Close" Result B: third paragraph is corrected, but not the rest. Expected result: all occurrences of "dogg" are replaced by "dog" throughout the document as soon as "Correct All" is pressed. This is the expectation according to the documentation[1]: "Replaces all occurrences of the unknown word with the current suggestion." I haven't seen any evidence that the command shouldn't apply to the whole document, and the feature should at least behave on par with the "Ignore All" command, which ignores all occurrences instantly and removes the red underline, before and after the current position. Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 5a75414d1772d1fd998f405e3b9bd80b1f10c51f CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Same results in OOo 3.3. Similar issue in Impress, see e.g. bugdoc[2] from AOO tracker[3]. [1]: https://help.libreoffice.org/24.8/en-US/text/shared/01/06010000.html [2]: https://bz.apache.org/ooo/attachment.cgi?id=68817 [3]: https://bz.apache.org/ooo/show_bug.cgi?id=110688
*** Bug 92545 has been marked as a duplicate of this bug. ***
*** Bug 126814 has been marked as a duplicate of this bug. ***
*** Bug 143231 has been marked as a duplicate of this bug. ***
*** Bug 161245 has been marked as a duplicate of this bug. ***
I submitted this bug and it was assigned bug number 161245, which was closed because it was a duplicate of this bug (91151). Unfortunately, this has not been resolved under either of the bug numbers and the bug continues to exist. Shantanu provided an incorrect and dismissive "solution" to 161245, with the implication that the bug was a user error and condescendingly chastising the user (me) for hitting the Close button before the Correct All function had a chance to finish making corrections. First, that is speculation, because I never hit the Close button when using the Spell function. Additionally, when clicking Correct All, a message is returned at the bottom right of my screen that shows how many instances of the misspelled word were FOUND, but there is no message stating how many instances were CORRECTED. Just to make sure I was seeing things correctly, I clicked Correct All to correct seven instances of a word in a document. Then I waited 30 minutes. Again, all I got was a message stating that seven instances of the incorrect spelling were FOUND, but no indication that there were seven actual corrections. In fact, only the first instance of the misspelling was corrected. Again, I did not hit the Close button for 30 minutes, thereby casting doubts on Shantanu's alleged "fix." As I stated in 161245 and will restate here, I have this same problem using Writer on my Ubuntu Linux machine, and on my Windows 11 machine. Maybe you cannot duplicate the condition, but I find it difficult (but not completely impossible) to believe that I am the only person in the universe who has this problem.
(In reply to Stéphane Guillou (stragu) from comment #4) > *** Bug 92545 has been marked as a duplicate of this bug. *** That was an excellent breakdown of the problem, thank you. I have been experiencing it for years and finally decided to inquire about it. Continuing on, using your example, I see that if I continue with the spellcheck operation, the "correct all" for "dogg" does work as I advance to the following paragraphs. So whereas my expected behavior is that clicking "correct all" immediately corrects all instances of the mistake, instead LO requires continuing the spellcheck through the ensuing data. Thus, "correct all" is not an automatic process, it is semi-automatic. Making the Correct All function automatic for the whole document would be much better and more in line with what people expect of the function, in my opinion. I'm on LO 25.2.0.0 on Linux Deb.
I've since discovered that the length of the document has a lot to do with how spellcheck / correct all works. For shorter documents, it does work. If you paste this into a new Writer document: misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx and do a "correct all", the whole paragraph is immediately corrected. Perfect. But if that paragraph is at the end of a long document, and you "correct all" one instance of "misspellingxxx" at the doc beginning, nothing happens to the last paragraph. It gets worse. As you progress with spellcheck, other instances of "misspellingxxx" along the way will not have been changed. You will have to manually correct each of them. So letting spellcheck advance to the end of the document (which may be impractical in one sitting with a large document with many spelling corrections) will still not make all the Correct All changes.
@Paul, I believe your assessment is incorrect. The length of the document is not a contributing factor to the issue. For example, consider the following case: misspellingxxx misspellingxxx admet misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx If you click "Close" immediately after the first "Correct All", the result will be: misspelling misspelling admet misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx Only the first two words are corrected, while the remaining errors after "admet" remain unchanged. misspelling misspelling admit misspelling misspelling misspelling misspelling misspelling misspelling misspelling misspelling misspelling misspelling misspelling misspelling misspelling If you require the correct output (mentioned above), you must also correct the word "admet." Exiting the spelling dialogue box prematurely is not an option, and this behavior constitutes a bug.
Shantanu, the behavior you describe is correct. At this point I'm not sure what's going on. Previously, the paragraph: Misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx in a new document containing only it, was completely corrected with the first and only Correct All. Now I have to do two Correct All's, and then the entire paragraph is corrected. I can't explain the difference. I'm on 25.8.0.0 at the moment. At any rate, there is a bug of some sort, and it makes the spellcheck useless on long documents with many spelling errors.
The spell check functions as expected as long as the "Close" button is not clicked prematurely. It has been used by millions of people for decades. To prevent the bug from occurring, ensure that all words are checked using options such as "Ignore", "Correct All" etc, and wait for the notification stating, "The spellcheck is complete."
I cannot confirm this. Text: misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxx misspellingxxxy misspellingxxx misspellingxxx misspellingxxx misspellingxxx Spellchek complains word "misspelling xxx", suggests "misslingen" Click on "correct all" makes visible replacements only in the first line, dialog stays open. No notification about completed operation. Upon closing the dialog, more replacements are visible Replaced text: misslingen misslingen misslingen misslingen misslingen misslingen misspellingxxxy misslingen misslingen misslingen misspellingxxx
I cannot confirm that either. I have done Correct All's, proceeded to other corrections, and then come upon further instances of words I had Correct All'd, all in one uninterrupted spellcheck session. That is why I finally pretty much gave up on trying to work with LO's spellcheck. I thought that document size might have something to do with it. I can see a spellcheck through to completion on a smaller document, but take one that's 400 pages, with British spellings, archaic spellings, and OCR errors that all need to be corrected, then being forced to ride the spellcheck through to the end for all the Correct All's to be effected becomes unworkable, in my view.
@birnbach, You've encountered yet another bug: "Correct All ignores the final word." Bug 92545 @Paul, you're absolutely right about "being forced to ride the spellcheck through to the end for all." But that's just the way it is — for now — until some kind soul takes pity on us and finally fixes this.