Issue 62136 - "Find and replace" must treat non-breaking characters (i.e. spaces, hyphens) as their normal equivalents
Summary: "Find and replace" must treat non-breaking characters (i.e. spaces, hyphens) ...
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: OOo 2.0.3
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: oooqa
Depends on:
Reported: 2006-02-16 11:19 UTC by timi_openoffice
Modified: 2013-08-07 14:38 UTC (History)
3 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 timi_openoffice 2006-02-16 11:19:38 UTC
When you use non-breakting characters like strg+space or strg+minus in your 
document, you can't word combinations with "find and replace" when you enter 
normal space or minus sign as search string. It would be very practical if 
that would be possible.
Comment 1 michael.ruess 2006-02-16 11:39:52 UTC
Reassigned to SBA.
Comment 2 lars 2006-02-16 13:33:08 UTC
OOo 2.0.2 RC1 finds tri<ctrl+->angle when searching for tri-angle
Comment 3 timi_openoffice 2006-02-16 14:39:14 UTC
With 2.0.2rc1 I don't get this to work. Only when I activate "similarity 
search", this is possible.
Comment 4 lars 2006-02-16 15:39:28 UTC
you are right; this is only possible with Similarity Search enabled, which is 
the default
Comment 5 timi_openoffice 2006-02-16 18:44:26 UTC
Sorry for commenting another time, but at my system (linux) Similarity Search 
is not the default.
Comment 6 stefan.baltzer 2006-04-18 10:51:59 UTC
SBA: Looks a lot like issue 62135.
Reassigned to requirements.
Comment 7 timi_openoffice 2006-09-25 13:00:30 UTC
> SBA: Looks a lot like issue 62135.

Okay. 62135 is a duplicate of 15616 and yet solved for 2.1.

Maybe it is possible to easily fix this issue with the same code?
Comment 8 stefan.baltzer 2006-10-17 17:06:37 UTC
SBA->timi_openoffice: The "treat equally as normal spaces" can not be "the same
code" as "ignore".

SBA->FME: I regard this one as a defect, too (=> changes issue type type).
Similar to the discussion of custom hyphens, the non-breaking spaces need some
attention. A non-breaking space must be treated like a normal space because...
(A) MS Word treats them equally to normal spaces in Find&Replace (=> expectation
of "refined" users :-)
(B) In normal document view or in a printout they can not be distinguished by
the user.

SBA->FME: Once we're at this, we must take the Complex Text formatting aid signs
into account, too. (To see them all in the Insert-Formatting Mark sub menu,
enable CTL support in Tools-Options-Language setting-Languages first)

In total, there is...
(1) Non-breaking space
(2) Non-breaking hyphen
(3) Optional hyphen
(4) No-width optional break
(5) No-width no break
(6) Right-to-left mark
(7) Left-to-right mark 

So far, (3) is solved. 

I am aware that we can not handle all this without a specification.
Nevertheless, this is a defect.

Comment 9 Unknown 2010-10-23 06:46:06 UTC
Created attachment 72347