Win32 binaries of Lout 3.20 now available

[Valeriy E. Ushakov]

ftp://ftp.ptc.spbu.ru/pub/textproc/lout/binaries/win32/3.20/

    lt320w32.zip        - all you need to run lout on Win32
    lt320dps.zip        - preformatted (A4) PostScript docs
    lt320dlt.zip        - sources for the above

Init run was already done (with -l option).

Note that contents of the archives as packed lives under "lout/3.20".
This reflects my own setup, since I have previous versions of lout
installed as well for reference purposes.  But you don't have to
follow this convention.

lout.exe binary in the distribution will use the directory that it
lives in (as returned by GetModuleFileName) as default library
directory, unless explicitely overriden with LOUTLIB environment
variable, so you can put the contents of the archives in any place
convenient to you.  In the unlikely case that lout.exe can't determine
its full pathname, it will fall back to C:\lout\3.20 as the last
resort default.

Separate loutdbg.exe binary with -d debugging enabled.

zlib-1.1.3 compiled in statically.

There are also few cosmetic changes:

. prg2lout is much smaller as it uses smaller arrays in token_rec

. -V will tell if PDF compression and -d debugging is compiled in

. error messages about object size are in points and have two decimal
  places (1 lout internal unit is 0.05pt) - so infamous "too high"
  message for user's guide will now tell that 668.45p object is too
  high for 668.40p space (that is FP rounding caused 1 unit detla).

The last one is, perhaps, controversial.  This change was in my
sources and I was too lazy to back it out before compiling for the
binary release.  I've grown up in metric culture, but I still find
points to be more handy units when reasoning about typography.  (Gee,
I'm a retrograde ;).  Let me know if this is a problem.

SY, Uwe
-- 
address@hidden                         |       Zu Grunde kommen
http://www.ptc.spbu.ru/~uwe/            |       Ist zu Grunde gehen