https://bugs.documentfoundation.org/show_bug.cgi?id=91151

--- Comment #17 from Justin L <[email protected]> ---
Created attachment 201641
  --> https://bugs.documentfoundation.org/attachment.cgi?id=201641&action=edit
91151_correctAll.odt: example document

I started testing this bug using the Find/Replace dialog. In that case it
worked fine - in both OOo 3.3 and LO 26.2.

But this bug report is about the SPELL CHECKER, not find/replace. As reported
by various commenters, it seems to auto-correct the words until it reaches the
next misspelled word - which at first glance is very unexpected.

HOWEVER, as I continued to correct-all "catt", it then also auto-corrected the
next dogg, and when I continued to correct-all "frogg", it then auto-corrected
the remaining catts and doggs too. [Already worked like this in OOo 3.3.]

(Also note that in the preview line for correcting "catt" that dog has already
been shown as corrected.)

In other words, it is only when you stop the spell-check half-way through that
the correct-all doesn't occur. (Or if you make changes to the document itself -
bypassing the spell-check dialog.)

And from a technical perspective, that makes a lot of sense. When you make
corrections to words, you are changing the number of characters in a paragraph,
so stepping through it in a linear fashion allows the spell-checking-process to
only read the document once, instead of re-reading the entire thing after every
correction. It is a huge accuracy and performance concern.

So I'm not really sure there actually is a bug here.

Some possibilities for improvements:
-continue the correct-all process for the remainder of the document when the
close button is pressed (although that feels somewhat dangerous).
-keep the correct-all list active even though the user has made changes to the
document itself (although I expect that at the implementation level "resume"
has started the spell-check all over again - starting at the cursor position).

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to