1 Current Bug List:
  2 ================
  3 
  4 - Processing Framemaker input (request from: delorme@panda.ceng.cea.fr)
  5 
  6 - When a input PS file contains NULL characters, mpage will go nuts...
  7   but you'll only see it when you try to print/gs its output.
  8 
  9 - Scaling should be done differently: 18/4 gives odd integers, so border
 10   lines and clipareas maybe off by one point...
 11   Try mpage -8 -H <file>
 12 
 13 - When resizing with -W and -L, the header may become a mesh.
 14   Probably should not scale header with this...
 15 
 16 - CTRL-D characters at the beginning of a file are removed.
 17 
 18 
 19 Current Wish List:
 20 =================
 21 
 22 -  I18N support
 23 
 24 - Option to print line numbers before each line of text
 25 
 26 - It would be nice if the Makefile used sed on the man page to insert
 27   the user's PREFIX/share directory into the man page, rather than having
 28   /usr/local/share/mpage hard coded.
 29 
 30 - Build Configure script...
 31 
 32 
 33 - Build RPM package for mpage
 34 
 35 
 36 - Check out th -j option. Does not seem to work properly.
 37   maybe it is  fixed with the multiple -j patches...
 38 
 39 
 40 - Add support to select paper trays.
 41 
 42 
 43 - Tidy up the manual page. Option description could be much better...
 44 
 45 
 46 - Allow printing of header for postscript-input also. 
 47   Sort of request by Tobias Buchal <buch@ifh.bau-verm.uni-karlsruhe.de>
 48 
 49 
 50 - Better control of how pages are positioned on the page 
 51   (David B. Peterson (dave@Spacestar.COM,
 52    Ted Stern <stern@amath.washington.edu>
 53    Dave Lopez <lopez@chdasic.sps.mot.com>)
 54   found a need for again a different layout. Guess we need something like:
 55 
 56   -<someoption><#c><#r>[[<portrait/landscape><normal/upsidedown>]<page#>]+
 57 
 58   and pages are printed viewing as portrait from left to right from
 59   bottom to top, eg (proposing option -e):
 60 
 61    -e2c3rpu14l23n56 
 62 
 63   would print logical pages in 2 (short side) by 3 long side) rows: 
 64       1 and 4 in portrait, upside down
 65       2 and 3 in landscape, upside down
 66       5 and 6 in landscape, normal
 67   with logical page 1 in the lower left corner, page 4 in the lower right
 68   corner, page 2 in the middle row left, page 3 in the middle row right,
 69   page 5 in the top row left, page 6 in the top row right.
 70 
 71 
 72 - Definition of page location, landscape/portrait etc becomes spagetti.
 73   Need to redefine the way this is setup...
 74 
 75 
 76 - Define an option to leave some space between logical pages. 
 77   suggested by: Jeremie PETIT petit@aurora.unice.fr
 78 
 79 
 80 - More flexible header definitions (size, fontname, which items where
 81   greying ...):,e.g.:
 82 
 83   mpage ... -H="grey=20% user=left filename=center pagenumber=right" ...
 84 
 85   suggested by: Jeremie PETIT petit@aurora.unice.fr
 86 
 87 
 88 - Define a (optional) physical page header with optionally a
 89   physical pagenumber. Also dates etc.
 90   Currently partly implemented: -X option. Could use some work
 91   on proper font (bold/not bold...)
 92 
 93 
 94 - Also might want a general pageframe around the logical pages. On top
 95   of this frame we can put the -X option output.
 96 
 97 
 98 - The postscript character encoding support is sort of a hack. I guess
 99   things could be a bit cleaner.
100 
101 
102 - Support for reducing mpage output.  I.E. if I do:
103 
104                 mpage -8P file.txt | mpage -8
105 
106   I should get 64-up output.  Problems are that the PostScript code
107   produced is not "recursive".  The end-of-page macro in particular
108   suffers under re-definition, you get blank pages.  Another problems is
109   resolution of the printer.  See the next Wish item.
110 
111  
112 - Better handeling of PostScript input.  The current stuff works, but
113   it is not general enough.  I am currently learning more here, thanks
114   to the "Green Book" and will work on a cleaner parser for Version 3.
115   (Oh-my-goodness, a pre-announcement ;-)
116 
117   Perhaps I should convert the whole PostScript processing routing to be
118   a "Finite Automata".  Each line will represent a "token" parsed by its
119   comment, output will be based upon transitions from state to state.
120   The automata should allow states and transitions to be added dynamicly
121   so that we can adapt to differening structure conventions, and
122   differing PostScript code generators (psdit, dvi2ps, etc ...)
123 
124 
125 - From: zachary brown <zbrown@lynx.dac.neu.edu>
126 
127   When I use mpage on
128   postscript files, the document's preexisting margins cause mpage to leave a
129   lot of blank space in between each mini-page, thus causing it to shrink the
130   pages more than necessary. My suggestion is this: allow the user to specify
131   how much a mini-page can break out of the boundary mpage sets for it and
132   overwrite what is on a neighboring mini-page. Also allow the user to specify
133   how far along either end of the imaginary line connecting the upper left
134   corner and the lower right corner of each minipage, the mini-page will be
135   magnified. This way, since there would only be those extra margins poking
136   into other space, nothing would in fact be overwritten, and mpage would
137   magnify the tiny-pages to their optimal size, and (since the user would
138   specify the edges to be magnified), there would be no problem with part of
139   the mini-page being off the physical page. I came to be aware of this
140   problem by trying to print out the gnu libc manual, and finding no way to
141   avoid huge gaps between the mini-pages.
142 
143 
144 - Add better timing information, possible adding command line
145   arguments to control the amount of timing information added to the
146   file.  (Eyuk, more arguments:-(
147 
148 
149 - Recognise things like c^Hc^Hc to be displayed in bold font...
150   (underline works fine currently)
151 
152 
153 - Lots more, I'm sure.
154