TODO - for dvgt 3.5 - 21:22 GMT +10:00 Fri 20 August 1993 - Geoffrey Tobin.

1.  Subdirectory searching?

2.  Scale substitute PK and TFM files (like zoom, but restricted to
    one font), to match the scaled size of the missing font.

3.  More VDU drivers.

4.  Allow an output character recoding file?
    That might be useful where the glyph encoding differs from ascii,
    or, more generally, from the encoding of the display.
    One way would be pairs of (hexadecimal?) integers.
    Might allow "D" for decimal, "C" for ascii character,
    "X" for hexadecimal, and "O" for octal, as in Knuth's TFM files.
    Default would be which `number system'?

    To Terse mode, add a user-definable glyph encoding?
    (Currently uses an encoding based on cmr10.)
    Employ a character recoding file, which the user could alter?

    Virtual Fonts?
    A fanciful dream, that one.

5.  Macros?

6.  String Search in the DVI file.

7.  Conform dvgt to TUG's DVI Driver Standard, Level 0, at least more
    nearly.

8.  Choose different DVI files interactively?

9.  Make TFM, PK path and file spec. strings dynamic.

Geoffrey Tobin
