Issue 59692 - Spelling checker - "Change All" problem
Summary: Spelling checker - "Change All" problem
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 2.0.1
Hardware: All Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-23 05:31 UTC by shmuelh
Modified: 2017-05-20 11:18 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description shmuelh 2005-12-23 05:31:19 UTC
When running the spelling checker, if I hit a word whose spelling I want to
change - and I want to make this change for all other references in this
document (e.g., a proper name which was misspelled), I go into the box which
shows the questioned word in red and make the appropriate change. I have tried
to press "Change All" after that, but this doesn't "take," and I keep getting
the same word highlighted. I think that if a person makes any change in the
spelling of a word within the spelling box, either the "Change All" should work
or (less preferable) the "Change All" button should be grayed out.
Comment 1 michael.ruess 2005-12-23 09:16:22 UTC
Reassigned to SBA.
Comment 2 jack.warchold 2005-12-23 16:59:22 UTC
confirmed in src680_145 
reassigend to os
set target OOo 2.0.2
Comment 3 Mathias_Bauer 2006-01-23 13:08:38 UTC
We will not finish this task in the 2.0.2 time frame -> retargetted to 3.0
Comment 4 Oliver Specht 2006-06-20 14:02:49 UTC
Target adjusted
Comment 5 Martin Hollmichel 2007-09-10 13:36:36 UTC
move target to 3.x according http://wiki.services.openoffice.org/wiki/Target_3x
Comment 6 foxcole 2007-11-10 14:24:05 UTC
I tried this dummy text in a new document:
The qick brown fox jumps over the lazy dog many times.

I inserted that maybe forty or fifty times, without typing a space before the
next shortcut text, so the resulting sentences did not have a space between the
period and the beginning of the next sentence: "times.The". The spellchecker of
course marked each occurrence of this and of the misspelled word "qick". What I
discovered is that the Change All seems to build strings of changes before it
will overwrite them all!

Here's what I saw.

I of course applied Change All to the first occurrence of "qick" and it changed
only that instance, stopping at the first occurrence of "times.The". So I
selected a suggested spelling for "times.The" which happened to be "timeshare",
chose Change All, and voom! The entire text was corrected for both changes (and
I watched it do multiple passes, because little black boxes that looked like
single-character highlights seemed to run through the text as it ran).

I tried the same test again but instead of allowing "timeshare" for the
replacement text, I manually corrected it to place a space between the period
and the next sentence. Change All this time did not cause the full -text
overwrite. This time it stopped at each instance of "times.The" so I had to make
the change again. I noticed that the "qick" wasn't corrected in that sentence
until I clicked Change All for the end-of-sentence correction.

So, it wasn't stopping on the "qick" but it was stopping at each end-of-sentence
error... unless I chose a suggested spelling from the list, which did not
include a suggestion to add the space. So, I thought, add the correction to the
dictionary. That worked; the next Change All triggered the overwrite.

Writer required me to add the correct word to the dictionary, and to make each
required correction before it would run through and change all the text. 
Comment 7 thuerrschmidt 2009-12-22 12:42:45 UTC
I wouldn't consider the imminent fourth birthday of this ticket as something to
celebrate, but it's certainly a good opportunity to remind the developers about
the issue. It's such a small bug, but it can get really annoying when one does a
lot of spell-checking in Writer.

I simply can't imagine why it should be so hard to fix this, considering that
there's an excellent, simple, and reproducible test case in foxcole's comment
above. Please, please do something about this and make OpenOffice.org an even
more enjoyable product! Thank you.

  

Comment 8 Unknown 2010-10-23 06:22:09 UTC
Created attachment 72315
Comment 9 Marcus 2017-05-20 11:18:10 UTC
Reset assigne to the default "issues@openoffice.apache.org".