Try using Fixedsys instead of Terminal.
Thanks but no. Believe me I tried
Reasons being:
1. Fixedsys is ugly compared to Terminal. And it lacks some (lots!) in comparison (chars 0x7F-0x9F, except 0x91 and 0x92 all looks the same!)
2. Fixedsys already defaulted in Lister ANSI mode (A) but to dump binary/hex, one should use OEM/ASCII mode (S).
Reason behind this: I've been using NC/VC in DOS for 10+ years, F3/Hex shows most of the 255 chars. Under Linux, UNIX or OSX terminals, there's no OEM/ASCII mode available (or I'm lazy/don't know how) so I have to live with ANSI unicode characters, and that sucks -- a lot of same-looking chars. Sometimes I even dumped those OS binaries in Windows to view using TC (WINE works fine anyway, Windows 2000/XP emulation perhaps?)
3. Explained above, Terminal font does display differect OEM/ASCII bytes as unique chars, while none of ANSI fonts does AFAIK. 00-FF was, is 256 chars and will never grow beyond that, unless humanity discovered a new kind of Mathematics (00-ZZ or something). OEM/ASCII symbols was perfect and complete work while ANSI/Unicode never was (still being developed, eg. Right-to-Left; Arabic-Aramaic-Hebrew, Far-east languages, certain Cyrillic, Sanskrit etc). And there's just too many variations in Unicode inviting more unexpected results or bugs. Hence my choice, OEM/ASCII font, no bugs (supposed to be).
4. I see no point for viewing Hexadecimal in some Unicode font. Double-byte chars or unicode (on file/disk) still consists of two bytes, not one. While applicable OS/GUI/Application will show one char, in fact it is two. For hex viewing/comparing, unicode is not required. Filecompare or hexdump is no Desktop Publishing requiring complex, proportioned, compatible and pretty fonts.
5. Still doesn't explain why:
- Immediately after Windows login it's being displayed ok (a.k.a. The font is not being substituted, so it does what it does)
- But not after subsequent Windows logins, until reboot (a.k.a. The font is now being substituted -- with-God-knows-what -- for no apparent reason)
I understand that maybe some double-byte OS users (or not, me too sometimes) will want to compare some Unicode or UTF-8/16 text files, and that requires an ANSI/Unicode capable font. The fonts button is already there, but a more flexible choices of mode changing is a welcomed addition, I think (see my suggestion below)
My suggestion/workaround:
Enable two (or more) modes as in Lister in the Compare window. I'm expecting that this might or might not require a lot of work, so I'll understand if I'm not seeing this being implemented soon or never will.
I myself honestly can't figure out whether the fault being by Windows (Vista and above) or TC. The mystery might still remain unknown for some time. So no pressure to your side, I'm just explaining further.
As for me (or anyone else affected):
Try to avoid logging out of local workstation. As I work with servers through remote logins, this seems unavoidable...
Thanks. And sorry if I talked much.
Select a file in left pane, different file exists in right pane (say, a patched or modified file). Select Synchronize. Choose Select by content. Compare file. Press Ctrl+F3 (Binary ticked). Default Terminal 9px font will become *very tiny*, still readable though.
