TC7.50pb4: Another font issue in Lister

[wanderer]

Using a unicode text file (i.e. a registry export), try the following:

1. View it in Lister as hex. Make sure you select the following settings:

Code: Select all

  - Options\ANSI
  - Encoding\As configured for current font

2. Now, close Lister and re-open it using the same file. You are now viewing the file using ANSI charset and also you are unable to alter the encoding.

3. Switch to hex mode and change the encoding to ASCII.
4. Close Lister
5. Re-open Lister. You are now viewing the file using ANSI charset, are unable to alter the encoding which is not "As configured for current font" but ASCII.

Since the file is a Unicode one, it seems like a bad idea to use an ASCII font to display it. IMO, there are two ways to deal with this situation. Either Encoding should have been automatically changed to "As configured for current font" the last time you opened Lister or the Encoding menu should not be disabled, allowing the user to change the font. I think the second solution might be the simpler/better one.

All tests performed under WinXP-SP3 (32bit).

[ghisler(Author)]

I don't see any problem here. TC uses the same font for Unicode independent from what is set in the encoding menu. So the menu is irrelevant for this display mode and can be disabled. The column is re-enabled when you switch to a view like Hex or Text view where the encoding is again relevant. The previous option is restored.

[wanderer]

In my PC, the font used for displaying the file as unicode in steps 2 and 5 depends on the encoding that had been chosen in steps 1 and 3. The font used in step 2 is different than the one used in step 5.

I don't see any problem here.

I'm not quite sure what you mean by this statement.

1. In your PC the same font is used in both cases or
2. In your PC different font is used in steps 2 and 5 (as in mine) but it doesn't matter because both fonts are actually unicode.

Which of the above is true?

[ghisler(Author)]

In my PC, the font used for displaying the file as unicode in steps 2 and 5 depends on the encoding that had been chosen in steps 1 and 3.

I cannot reproduce this here. What font do you use for ANSI and what font for Ascii?

[wanderer]

ANSI: Fixedsys
ASCII: Terminal
Variable: Arial

Take a look at this picture.

It looks like a case of font substitution. My questions is "is the font used in pics 3 and 4 actually unicode?". Please keep in mind that if TC is closed and reopened, it remembers the last used settings so it will use tihs font to display every file, even unicode ones.

[ghisler(Author)]

Hmm, very strange indeed - I will try to reproduce with fixedsys.

[wanderer]

Fixed in TC v.7.50b5. Tested under Win2K-SP4.

Now, Encoding always defaults to "As configured for current font" for unicode files probably because changing the Encoding has no meaning for unicode files, right?

[ghisler(Author)]

Yes, that's how it should have been from the beginning! Thanks for testing it and for confirming the fix.