File comparison, edit mode: CR gets corrupted

[StatusQuo]

When comparing binary files which are containing different forms of Carriage Return, the CR-characters get corrupted:

- 0Ah (Carriage Return in *NIX-Format) automatically gets changed
to 0Dh (Carriage Return in Mac-Format),

- 0A 0Dh (Carriage Return in Wind*ws-Format) automatically gets changed
to 0Dh (Carriage Return in Mac-Format),

both without a warning or question to the user.

[Flint]

StatusQuo
Please, read help:

<...> When saving, the type of line end (Windows, Unix, Mac) is determined by the majority of line ends of the original file, e.g. if the original contained Windows line ends with a few Unix line ends, the saved file will contain only Windows line ends.

[StatusQuo]

StatusQuo
Please, read help:

<...> When saving, the type of line end (Windows, Unix, Mac) is determined by the majority of line ends of the original file, e.g. if the original contained Windows line ends with a few Unix line ends, the saved file will contain only Windows line ends.

Tested and found the problem (probably a user fault): binary files can't be edited/changed in the File-Compare-Editmode, so the "binary" checkbox had to be turned off to make changes possible at all. Unfortunately this also makes the file content be interpreted as "text in lines" - including the above behaviour.

So I learned: binary files can't be changed (yet) with TC's File-Compare Editmode.
Thanks for the hint.

[ghisler(Author)]

So I learned: binary files can't be changed (yet) with TC's File-Compare Editmode

That's correct. Don't edit binary files in text mode, because this will convert them to a text file on saving it.