This is a beta release Windows NT file utility. 
 
The postscript interpreter is grafted onto a text/hex viewer.
I don't know whether it will stay on there for the final release
or not since the interpretation code was developed stricly
around the NT CD's.

Comments are welcome, preferably E-mail to CIS 73537,1203,
Jeff Lundblad.

Notes on viewing Postscript files:

1) LI only makes a first approximation attempt at processing
      a) text
      b) column positioning
      c) row positioning
      d) page ejects
   The 'interpretation' is based strictly on my examination of
   the files on the NT July, October and March CD's. There are 
   no guarantees that I'm doing it right. Positioning 'resolution' 
   is character width and line height based on the viewed font. 
   This doesn't work exceptionally well. Proportional fonts of 
   8-12pts seem to work best. Row positioning is relative, not 
   absolute. That is, I take the difference between the previous 
   'Y' coordinate and the current 'Y' coordinate & figure how many 
   blank lines that is. 'X' positioning is a little closer to absolute.

2) No character substitutions are performed.  Instead, where
   a character sub is found in the text, a binary 127 character
   is placed in the text. With an ANSI font, this looks like a
   box on the screen, with the 'terminal' font, it looks
   like a superscripted pyramid. Printed with a True-type font,
   it looks like a little bullet.  I have found that the .C00 
   language files use substitution characters for quote marks 
   and minus signs a lot.

3) The .C00 language doc's use a lot of subscripted 'opt's. These
   will show up in the line since I don't do subscripts. 
   So you'll see a lot of:

   describes-an-optional-feature opt of-the-language.


4) I do not do 'page processing'. Text comes out in the order
   it's found in the file.  The 'cursor' can only move down
   and to the right. You'll see some tables that look
   like:

   item 1
   item 2
   item 3
                 item 4
                 item 5
                 item 6

   where if the file was printed on a native postscript printer,
   item 1 and item 4 would be on the same line. You may also see
   page headers at the bottom of the page, and the dots between
   table of contents entries and their page numbers at the end
   of the line instead of between the text and number, and some
   special font'ed words in unusual places  - I don't try to go 
   back & put them where they belong. For example, you'll see

            This has a bold "Note" at the beginningNote

   where the 'Note' at the end would be in the blank at the front
   if printed on a postscript printer. 

5) If you want to print an 'interpreted' file, you will get best
   results with a true-type font and use 'match screen font' or a 
   printer font in the print dialog box with an 8-12pt font. Fixed 
   fonts tend to run off of the right edge of the paper. You may need to
   experiment with font size, depending on the file you're
   viewing. 

6) If you want to automatically switch to postscript interpretation
   when you open one of the NT doc's, set up the extents under
   Options|File Types, or copy the LI.INI file in this archive
   to your \Winnt directory.  If you're searching for text, or
   files containing specified text, it's best if you have the
   file types set up to be recognized as postscript. The View|Postscript
   menu item toggles between postscript interpretation and raw file
   output.


Notes on LI & NT

1) UNICODE support is un-tested, and will probably not work

2) HPFS support is un-tested, but will possibly work.

3) NTFS support is lightly tested and seems to work.

4) I don't know why the File|Save As and Options|File Types dialog
   boxes look so strange.

5) Only 32bits of file and disk sizes are processed (NT stores 64 bit
   sizes, but I only look at the bottom 32 bits).

6) Selections larger than 64K in edit windows will not work. There may 
   be some other remnants of 64K boundries that I haven't realized
   or found in my testing.