1/ From Larry W. Virden <lwv27%cas.BITNET@CUNYVM.CUNY.Edu>
   Is there any thought of adding support within mp's newsp program to
   print more of the news article header?  My dream would be to be able
   to tell newsp (via a .newsprc perhaps?) a set of headers to print using
   the same syntax as rn - or even having newsp USE my .rnrc file .

2/ From Michael J. Tuciarone <tooch@plan9.Sun.COM>
   The ability to better handle different page sizes depending perhaps on a
   command line options, or an environment variable, or a LOCALE setting or ...

3/ From Michael J. Tuciarone <tooch@plan9.Sun.COM>
   NeWS/OpenWindows does not implement the CharStrings dictionary.
   Therefore /backspacefont doesn't work correctly. Need to generate a
   NeWS/OW compatible version of CourierBack.

4/ From Andy Hall <andyh@ncduk.com>
   Running on a Sparcstation 1+ and with a Canon LBP8 mark 3 printer with
   PS-1 Scriptcard. This is a true version 51.4 Adobe Interpreter. If I print
   Unix manual pages using standard Nroff output and the mp.pro.ps v1.2
   prologue the job gets aborted after a few pages with a stackoverflow
   message on the serial output (I am using serial interface).  After a bit
   of investigation using a small C program to produce lines consisting only
   of a printed line number, a printable character, a backspace, an underscore
   and a newline, it appears that the job gets aborted on the page where the
   500th backspace is. I am not a PostScript expert but I am wondering whether
   the problem lies with the embedded piece of code backspacefont.ps or the way
   it is used. It is rather too convoluted for me to understand fully but my
   suspicions are aroused in that the default operand stack size mentioned by
   Adobe in their red book is 500.

5/ From Larry W. Virden <lwv27%cas.BITNET@CUNYVM.CUNY.Edu>
   Instead of having the lpr going to -Plw in the shell script, have it
   go to -P$(PRINTER:lw} ... so folks who use the PRINTER variable get it.

6/ From Lupe Christoph <lupe@alanya.Germany.Sun.COM>
   There are so many personal organisers all over the world that you need a
   more general scheme. What about a flag that takes the name of the personal
   organisers and sticks it in the mp.pro.%s.ps string ?

   Of course you need at least a short writeup on how to create these.
   Better, a short program that takes a general mp.pro.organiser.ps and
   substitutes a few variables. Or you can use short PostScript fragments,
   one for each personal organisers.
