Current Bug List:
================

- Why does a 'clip' folowed by a 'stroke' also stoke the clip lines?
  Scaling should be done differently: 18/4 gives odd integers, so border
  lines and clipareas maybe off by one point...
  Try mpage -8 -H <file>

Current Wish List:
=================


- Should print a help string when invoked as "mpage".  However, like
cat(1), I chose to default to processing standard input when no files
are specified.  I will change this so that the file "-" refers to
standard input and hence you will have to type something like:
	ls -Rl | mpage -8 -
More thought is required here.  (you comments solicited)


- Add support for handeling ATT style spoolers.  Or any type spooler.
Shouldn't be that difficult.

 
- Support for reducing mpage output.  I.E. if I do:
		mpage -8P file.txt | mpage -8
I should get 64-up output.  Problems are that the PostScript code
produced is not "recursive".  The end-of-page macro in particular
suffers under re-definition, you get blank pages.  Another problems is
resolution of the printer.  See the next Wish item.

 
- Better handeling of PostScript input.  The current stuff works, but
it is not general enough.  I am currently learning more here, thanks
to the "Green Book" and will work on a cleaner parser for Version 3.
(Oh-my-goodness, a pre-announcement ;-)

Perhaps I should convert the whole PostScript processing routing to be
a "Finite Automata".  Each line will represent a "token" parsed by its
comment, output will be based upon transitions from state to state.
The automata should allow states and transitions to be added dynamicly
so that we can adapt to differening structure conventions, and
differing PostScript code generators (psdit, dvi2ps, etc ...)


- Add better timing information, possible adding command line
arguments to control the amount of timing information added to the
file.  (Eyuk, more arguments:-(


- Lots more, I'm sure.

