Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 38178 - Compare with ignore whitespace turned on does not recognise differences in strings containing whitespace
Summary: Compare with ignore whitespace turned on does not recognise differences in st...
Status: RESOLVED DUPLICATE of bug 257235
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-28 00:01 EDT by Shan Hooi CLA
Modified: 2009-05-21 04:22 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Shan Hooi CLA 2003-05-28 00:01:52 EDT 
Comparing two files, one containing:
String withWhitespace = "with whitespace";
and the other containing
String withWhitespace = "withwhitespace";
no differences are indicated in Java Source Compare.
Comment 1 Andre Weinand CLA 2003-06-03 05:39:31 EDT 
Works as designed: the text comparison does not know anything about 
Java.
However, I will investigate what it means to make it Java-aware.
(One problem is that the text comparison is strictly line oriented and this 
conflicts with Java-awareness).

Changed severity to "enhancement"
Comment 2 Yves-Marie Haussonne CLA 2003-12-09 05:22:00 EST 
This is not only a java related problem. I had the same kind of difficulty 
when merging a xml file.

You can do the test with a simple text file containing (for example) the text:

one word

Compare with :

oneword

With the the option "ignore whitespace" turned on, no differences are 
indicated.

A solution to this problem would to make to make the text comparison 
tool "word-aware" (via an option for example).
Comment 3 Dani Megert CLA 2009-05-21 04:22:45 EDT 

*** This bug has been marked as a duplicate of bug 257235 ***