Received: by ATHENA-PO-2.MIT.EDU (5.45/4.7) id AA11846; Wed, 9 Aug 89 14:22:14 EDT
From: <amgreene@ATHENA.MIT.EDU>
Received: by ATHENA.MIT.EDU (5.45/4.7) id AA19777; Wed, 9 Aug 89 14:20:11 EDT
Received: by GEVALT.MIT.EDU (5.61/4.7) id AA14519; Wed, 9 Aug 89 14:19:30 -0400
Date: Wed, 9 Aug 89 14:19:30 -0400
Message-Id: <8908091819.AA14519@GEVALT.MIT.EDU>
To: ilham@ATHENA.MIT.EDU
Cc: staff@ATHENA.MIT.EDU
In-Reply-To: Ilham's announcement of Palladium
Subject: Questions about Palladium


Being interested in the options that pdpr will give us (most interested
in continuing to use -h), I came across these questions based on the
man page:

>     -b banner-type
>          Specifies the type of banner to use: "full" for a com-
>          plete banner containing information about the job or
>          "breif" for a banner containing only the job name and
>          user name.

Will "brief" save the extra piece of paper?  And does pdpr want
"breif" or is that a manpage typo?

>     -d doc-type
>          Specifies the type of document being printed: "Ascii"
>          or "Postscript", the default is Ascii.

Does Palladium do any magic-number tests, or will we have to explicitly
declare our PostScript files?  If the latter, I suggest that the default
is wrong, since an Ascii file interpreted as PS generates 0 or 1 pages of
output, while a PS file printed as Ascii will generate gobs (which is, I
believe, the technical term :-).

>     -e event-list
>          The user will be notified when the events listed occur.
>          If more than one event is listed they should be sur-
>          rounded by "'s and separated by commas.

What events are these?  They weren't enumerated on the man page, unless
I missed them...

It may be that these are silly questions; I'm not in E40 right now so I
can't test to find the answers, but they're things that raise exception
flags in my mind....

- Andrew
