Issue 57191 - Auotocorrect: "Ignore double spaces" - Wrong wording
Summary: Auotocorrect: "Ignore double spaces" - Wrong wording
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 2.0
Hardware: All All
: P3 Trivial with 1 vote (vote)
Target Milestone: AOO Later
Assignee: AOO issues mailing list
QA Contact:
Keywords: oooqa
Depends on:
Reported: 2005-11-02 12:12 UTC by pesala
Modified: 2013-02-07 22:02 UTC (History)
2 users (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description pesala 2005-11-02 12:12:35 UTC
This is a fault in the wording on the Autocorrect dialogue. 

It says "Ignore double spaces." 

So if the box is checked, one would be inclined to think that Autocorrect would 
ignore double spaces that the user types and leave them as double spaces. 

In fact, it does the opposite. If the box is checked, Open Office ignores any 
spaces typed after the first one. The box needs to be checked to replace double 
spaces with single spaces while typing. 

It would be better if the wording was: "Replace double spaces with single space.

I wonder why there is no [M] option to replace while modifying existing text? 
That would be a useful alternative to search and replace. Not important, just 
logical to have the option there too.
Comment 1 michael.ruess 2005-11-02 13:32:39 UTC
Reassigned to SBA.
Comment 2 ace_dent 2006-03-07 00:28:04 UTC
Confirmed with OOo 2.0.2RC3, WinXP, En-UK.

Under 'Tools'>'AutoCorrect...' in the 'Options' tab, the text entry reads
"Ignore double spaces". However, as reported this is not accurate.
Change text to: "Correct double spaces". This may need to be fixed in other locales.

It would a useful addition to provide an [M] option to fix existing text. This
should be handled by a seperate Enhancement request Issue.

Comment 3 stefan.baltzer 2006-04-05 10:33:27 UTC
SBA: Reassigned to FL.
Comment 4 pesala 2008-05-16 04:40:40 UTC
This still affects release version 2.4 and Development version Beta 3.0
Comment 5 Olaf Felka 2008-05-16 07:31:51 UTC
Don't change the version entry. It indicates in which version the issue has been
found. If it hasn't been fixed it it pretty logical that it will still occur.