diff options
author | Norbert Preining <norbert@preining.info> | 2019-09-02 13:46:59 +0900 |
---|---|---|
committer | Norbert Preining <norbert@preining.info> | 2019-09-02 13:46:59 +0900 |
commit | e0c6872cf40896c7be36b11dcc744620f10adf1d (patch) | |
tree | 60335e10d2f4354b0674ec22d7b53f0f8abee672 /dviware/dvgtk/doc/TODO |
Initial commit
Diffstat (limited to 'dviware/dvgtk/doc/TODO')
-rw-r--r-- | dviware/dvgtk/doc/TODO | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/dviware/dvgtk/doc/TODO b/dviware/dvgtk/doc/TODO new file mode 100644 index 0000000000..5b15511436 --- /dev/null +++ b/dviware/dvgtk/doc/TODO @@ -0,0 +1,36 @@ +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 |