https://bugs.kde.org/show_bug.cgi?id=410008
michael <reeves...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CONFIRMED
--- Comment #3 from michael <reeves...@gmail.com> ---
The first case now fixed as this was an unintended regression. I am not going
to say that the second case will not be coming back. However I have concerns
over how kdiff3's current comparison code behaves in this case. Anything beyond
basic binary equality testing seems to assume its working with a text file of
some kind. As a result binary data can trigger odd corner cases that text files
don't hit. To avoid this kdiff3 currently does not run such code for binary
files. I'll have to look into this further to see just what would be needed for
binary comparison to come back.
--
You are receiving this mail because:
You are watching all bug changes.
