On 8/2/2011 6:03:20 AM, Pauli Lindgren wrote:
>On 7/29/2011 8:13:44 PM, Ian Binnie
>> All the common fonts support both ANSI
>> and OEM (at least for Code Page 1252 and
>> Code Page 437) - although even there
>> there are some characters in a couple of
>> fonts with funny glyphs. The OS selects
>> glyphs based on Code Page.
>No. Only very few fonts support OEM.
>On my computer, the only ones are "VEDIT
>Oem" and "Terminal".
I should probably have said "All the common fixed pitch fonts".
>And I have never seen a font that
>supports both ANSI and OEM.
I can assure you all these fonts support OEM, although some are missing a few characters - Consolas has no box drawing characters.
I have worked extensively with fixed pitch fonts, and my findings are summarised in the following page:-
>At least not
>a fixed pitch font that can be used with
I see 12 fonts in vedit, but most of these aren't very good.
I am pretty sure Lucida Console is enabled by default in XP, although I can't be sure, and it may be necessary to modify the registry as described above.
As vedit is a native Windows application, not a Console application, the registry mods shouldn't be necessary.
I use Lucida Console extensively, including with vedit.
It is true that it is difficult to see the OEM in Lucida Console because vedit doesn't provide any way to select the OEM character set for TrueType fonts, although this can be done by editing vedit.ini (it wouldn't be difficult to change).
>> NOTE The newer fonts e.g. Consolas don't
>> have a lot of OEM glyphs.
>That is because Consolas does not
Microsoft has a free program "Font properties extension setup" (at least for XP) that enhances Character Map and shows all the supported codings. This shows the DOS support for Consolas.
>Of course it is possible to re-arrange
>the glyphs in a font (using a translate
>table) for example to view DOS (OEM)
>text files with Windows (ANSI) font.
>In Vedit, this can be done by setting
>the ANSI/OEM mode.
>But this only shows those characters
>that can be found in the ANSI font. For
>example the line drawing characters can
>not be seen.
I would not suggest this. Incidentally, it is easy to convert OEM to ANSI by translating OEM to Unicode, then to ANSI. This could probably be done reasonably simply with a macro, and I did something like this, but this does convert some characters and only shows those in the ANSI set. These days I use Unicode for most of my programs, even console programs, and can display characters from both sets.