#287 Built-in diff shows unicode as binary data

[Alexander Kogtenkov]

The built-in diff command (neither TCL nor
Python are installed) shows differences for
Unicode files (i.e. those with "-ku" option set)
as raw UTF-8 bytes, i.e. without using the Unicode
characters. E.g. Russian unicode characters in the
file are not displayed as Russian glyphs on the
screen, but look like a garbage.

[Jerzy Kaczorowski]

Logged In: YES
user_id=119527

Does it work from the command line?

[Alexander Kogtenkov]

Logged In: YES
user_id=254563

In the command line it works in the same way:
the output is raw UTF-8.

[Jerzy Kaczorowski]

Logged In: YES
user_id=119527

It appears that the behaviour is by design and it's on CVSNT
side. Nothing much can be done here short of using the -kb for
the files in question instead of Unicode.

[Alexander Kogtenkov]

Logged In: YES
user_id=254563

I used to think that WinCvs is a GUI wrapper on top of CVSNT.
And as such, it is free to do anything that makes the life
easier. E.g., it can take UFT-8 output of CVSNT and write
to the output subwindow the same text, but in the readable
form. Of course, if WinCvs is not Unicode-capable, nothing can
be done.

BTW, what is the reason to have Unicode (-ku) files if one can
always use binary (-kb) files instead? The only reason, I can
see, is to support user-friendly diffs. Otherwise, "Unicode
support" becomes just words without any meaning behind.