Diff engine highlightes bad parts of line

Logged In: YES
user_id=1996845
Originator: YES

File Added: File2.cs

Logged In: YES
user_id=1996845
Originator: YES

When comparing these two files (file1.cs and file2.cs) the result seen in Diff Pane was:
(characters ## - the highlighted part)

get{return #(#m_bIsLoaded);}
get{return (m_bIsLoaded);}#// end get#

This is wrong.

File Added: winmerge.ini

Logged In: YES
user_id=298505
Originator: NO

I got some similar behavior. See my attachment (winmerge_diff_highlighting.jpg)

HKR,"Interrupt #Management\MessageSignaledInterruptProperties",MSISupported,0x00010001,0#
HKR,"Interrupt #Management\MessageSignaledInterruptProperties",MSISupported,0x00010001,1#

Instead of:
HKR,"Interrupt Management\MessageSignaledInterruptProperties",MSISupported,0x00010001,#0#
HKR,"Interrupt Management\MessageSignaledInterruptProperties",MSISupported,0x00010001,#1#

Logged In: YES
user_id=1236935
Originator: NO

These issues are different.

tomers: It is a option you can set. See the issue you created in the tracker, I answered there.

xpokor13: The only way I was able to reproduce this problem is with the following steps.

- "Automatic rescan" option must be OFF.
- Put the "Line differencing coloring" option to "Word-level: Break at whitespace"
- Open the two files to compare
- Change the "Line differencing coloring" option to "Character level"

Was that your case?

Logged In: YES
user_id=1996845
Originator: YES

marcelgosselin: I tried this with version 2.6.14.0

I put the "Line differencing coloring" option to "Word-level: Character level"
and result was like this:

(characters ## - the highlighted part)

I atteched my winmerge_2.6.14.1.ini

get{return #(#m_bIsLoaded);}
get{return (m_bIsLoaded);}#// end get#

Logged In: YES
user_id=1996845
Originator: YES

marcelgosselin: Sorry :
I put the "Line differencing coloring" option to "Character-level"

New ini file

Logged In: YES
user_id=1996845
Originator: YES

File Added: winmerge_2.6.14.1.ini

Logged In: YES
user_id=1236935
Originator: NO

I've added a patch that fixes this issue at https://sourceforge.net/tracker/index.php?func=detail&aid=1962816&group_id=13216&atid=313216

Oops. Forgot to close this bug report. It was fixed for 2.8 branch and for 2.10 stable releases.

Closing now, thanks for Matthias for notifying me.