Binary Compare Files by Content: RED dots for values 0D, 0A

[norfie²]

If comparing two totalcmd-log files (UTF8 format) and switch to binary compare then all (identical) new line characters i.e. 0D 0A are shown on the right text view with RED dots . instead of black dots . .

[ghisler(Author)]

Maybe I misunderstand you, but I can't reproduce the problem. Here is what I tried:
1. Make a copy of totalcmd_log file
2. Do some operation which changes the original file
3. Compare the teo - UTF-8 is enabled for both sides
4. Switch to binary and recompare

Result: Only the newly added lines are shown in red.

[norfie²]

2ghisler(Author)
You 're right in all - misunderstanding and your description.
Result is yours AND additional in the text view on the right side of both sides all identical characters with 0D 0A are shown with dots. This dot is red . but it should be a black . one. Please have a look at the screenshot from this post
http://www.ghisler.ch/board/viewtopic.php?p=326327#326327
There are the 0D 0A marked in binary view side and on the text view side the dots are red.

[ghisler(Author)]

If you have different line breaks from Windows and Linux, then you will of course see a difference here. Just use text mode for download to conver the Linux line breaks to Windows line breaks.

[norfie²]

What does it matter? It has nothing to do with the differences between Windows and Linux. What do you think was my reason that I used the totalcmd.log example? It's a problem with UTF8 (pure ASCII files are ok) that the wrong color is shown. I'm outta here.

[milo1012]

2norfie²
I'm trying to reproduce it with sample XML files, but it doesn't show up for me, no matter what I try.
TC 9.0a final, both 32- and 64-bit, Win7 x64.

Could you upload two sample files which trigger this behavior? And does it work back in TC 8.5 or older versions?

[petermad]

2norfie² & 2milo1012

I can confirm it: http://madsenworld.dk/tcmd/binaryutf8comp.png

TC 8.52a behaves the same way.

Sample files: http://madsenworld.dk/tcmd/binaryutf8comp.zip

[Dalai]

I can't reproduce this on XP. Instead of the dots I get the "regular" squares which are typical when some character is missing from the used font. I guess this has something to do with fonts. On Win7 I get the dots, but they're normal black... [ADD] unless I use a fresh wincmd.ini [/ADD]

[ADD2]
Since I use some dark blue for differences it looked like the dots were black, but they're not. Setting the color back to a lighter one (green or the default red) makes it easier to detect - they indeed use the diff color. So I can confirm the issue on Win7 with the test files provided by petermad.
[/ADD2]

Regards
Dalai

[milo1012]

I can confirm it: http://madsenworld.dk/tcmd/binaryutf8comp.png
...

Thx, now I can confirm this as well.

But I tried to reproduce the exact highlighting as in the OP linked image
http://mikdoe.lima-city.de/binaervergleich.png
but this is still not working for me, and is really strange anyway, as there are only the newline chars highlighted.


And BTW, concerning that confirmed behavior: I don't think that you can call this a bug, as it's just a different line content. You need to take the newline character(s) before the line's content into account, and so TC does the right thing:
- highlight the last two line's content in grain (including the prefixed newline char) on both sides for the text part, as these are the lines that are different
- highlight just the added bytes for the hex part
So in conclusion: TC assumes the prefixed newline char(s) belonging to a line. The same happens if you copy a single highlighted line from the CBC tool into a text editor: you'll get a prefixed empty line, due to TC copying it to clipboard with the prefixed newline char(s).

[ghisler(Author)]

This should be fixed in TC 9.10 beta, please test it!

[petermad]

I can confirm the fix in TC 9.10b1 - at least with the previous sample files: http://madsenworld.dk/tcmd/binaryutf8comp.zip