Hi Peter:

PF> Once I get this damn Inf2QuickHelp converted working 
PF> the way I want,  I am toying with the idea of writing 
PF> Inf2Printer program that will paginate (and put the 
PF> page numbers next to each hyper-link),  print a table 
PF> of contents (with page number) and an index (with page 
PF> numbers). It sounds so handy I might even try to sell it.
 
PF> I was thinking of doing it to raw postscript,  but 
PF> could use just plain ascii or the PM spooler (the last 
PF> would take a LOT of disk space and time,  but you'd get 
PF> the prettiest looking document).   Whichever, I think 
PF> I'll only do it one way.  I'm leaning towards PS right 
PF> now,  since I've got a PS printer :-).

Raw postscript does not fair well with the device independance.  This
would limit your potential client base.

What if you were to create the output one page at a time.  Each page
would be a print job in the spooler.  You could monitor available disk
space and halt the output when the space drops below a given
threshold.  This threashold would be user configurable of course.

Advantages:

    - device independance
    - nice output
    - easy color support for color printers

Disadvantages:

    - In cases where multiple printers are connected to a single
queue, the output would be split between two printers.  For this case,
perhaps an option to keep the whole thing as one job.  If they have
the disk space on their spool drive, they won't have to colate the
output.

     - for network queues, other jobs could/will slip between jobs in
this output.  Again, the single job option would fix this for those who
can handle it.

     - for queues that have a seperator page between jobs, seperate
jobs would be totally inappropriate, as it would double the amount of
paper used and be a general pain.


I hope this is of some use to you.  Now that you mention it, I could
use an Inf2print utility. :)


Best wishes,

Tom

 * KWQ/2 1.2g * In the .EXEs of Life, he had more NOPs than most.
--- Maximus/2 2.02