Spooling a PostScript file
Dave Higton
a file, a PostScript file is generated.
If you then drag that file to the printer manager connected to a
real PostScript printer, does it invoke an application to process
the PostScript?
Should you change the file type to Printout so that it is sent
directly to the printer?
Dave
Jeremy Nicoll - news posts
> If you print something to a PostScript printer driver, saving to
> a file, a PostScript file is generated.
>
> If you then drag that file to the printer manager connected to a
> real PostScript printer, does it invoke an application to process
> the PostScript?
No; only the printer processes the PS (which is just plain text anyway).
> Should you change the file type to Printout so that it is sent
> directly to the printer?
It's so long since I did this I can't remember... Maybe a PS file gets
treated the same way? If it comes to that a straightforward *copy to the
device is probably enough.
--
Jeremy C B Nicoll - my opinions are my own.
Email sent to my from-address will be deleted. Instead, please reply
to newsre...@wingsandbeaks.org.uk replacing "nnn" by "284".
Martin Wuerthner
Dave Higton <daveh...@dsl.pipex.com> wrote:
> If you print something to a PostScript printer driver, saving to
> a file, a PostScript file is generated.
> If you then drag that file to the printer manager connected to a
> real PostScript printer, does it invoke an application to process
> the PostScript?
No, it spools the file to the printer. Unfortunately, in an extremely
sluggish way.
> Should you change the file type to Printout so that it is sent
> directly to the printer?
No, you should leave it as PostScript so that it is sent directly to
the printer.
Non-PostScript printer icons send Printout files directly to the
printer. PostScript printer icons send PostScript files directly to
the printer.
Martin
--
---------------------------------------------------------------------
Martin Wuerthner MW Software http://www.mw-software.com/
ArtWorks 2 -- Designing stunning graphics has never been easier
spam...@mw-software.com [replace "spamtrap" by "info" to reply]
davehigton
> In message <445e24a550.davehig...@dsl.pipex.com>
> Dave Higton <davehig...@dsl.pipex.com> wrote:
>
> > If you print something to a PostScript printer driver, saving to
> > a file, a PostScript file is generated.
> > If you then drag that file to the printer manager connected to a
> > real PostScript printer, does it invoke an application to process
> > the PostScript?
>
> No, it spools the file to the printer. Unfortunately, in an extremely
> sluggish way.
That's the symptom of the problem! But /why/ is it sent
sluggishly? Why is it treated any differently from sending a
Printout file to a non-PS printer?
> > Should you change the file type to Printout so that it is sent
> > directly to the printer?
>
> No, you should leave it as PostScript so that it is sent directly to
> the printer.
>
> Non-PostScript printer icons send Printout files directly to the
> printer. PostScript printer icons send PostScript files directly to
> the printer.
What would happen if its file type were set to Printout?
Btw I'm trying to diagnose the problem on behalf of Jim
Nagel, who described this to me at the show on Saturday.
Dave
Ian Hamilton
<455b69f6-df2a-4c8c...@z34g2000vbl.googlegroups.com>,
davehigton <daveh...@dsl.pipex.com> wrote:
> On 5 Oct, 00:26, Martin Wuerthner <spamt...@mw-software.com> wrote:
> > In message <445e24a550.davehig...@dsl.pipex.com>
> > Dave Higton <davehig...@dsl.pipex.com> wrote:
> >
> > > If you print something to a PostScript printer driver, saving to
> > > a file, a PostScript file is generated.
> > No, it spools the file to the printer. Unfortunately, in an extremely
> > sluggish way.
> That's the symptom of the problem! But /why/ is it sent
> sluggishly? Why is it treated any differently from sending a
> Printout file to a non-PS printer?
> > > Should you change the file type to Printout so that it is sent
> > > directly to the printer?
> >
> > No, you should leave it as PostScript so that it is sent directly to
> > the printer.
[Snip]
> What would happen if its file type were set to Printout?
> Btw I'm trying to diagnose the problem on behalf of Jim
> Nagel, who described this to me at the show on Saturday.
Jim runs PrintSpool, has he tried the above when it isn't running?
Ian
--
Ian Hamilton (Iyonix RO5) http://www.hamiltoni.pwp.blueyonder.co.uk/
Martin Wuerthner
ups.com>
davehigton <daveh...@dsl.pipex.com> wrote:
> On 5 Oct, 00:26, Martin Wuerthner <spamt...@mw-software.com> wrote:
>> In message <445e24a550.davehig...@dsl.pipex.com>
>> � � � � � Dave Higton <davehig...@dsl.pipex.com> wrote:
>>
>>> If you print something to a PostScript printer driver, saving to
>>> a file, a PostScript file is generated.
>>> If you then drag that file to the printer manager connected to a
>>> real PostScript printer, does it invoke an application to process
>>> the PostScript?
>>
>> No, it spools the file to the printer. Unfortunately, in an extremely
>> sluggish way.
> That's the symptom of the problem! But /why/ is it sent sluggishly?
Because !Printers feeds the file in incredibly tiny morsels to the
printer in a completely exaggerated attempt to multi-task nicely.
> Why is it treated any differently from sending a Printout file to a
> non-PS printer?
It is not. All files are spooled sluggishly by !Printers.
davehigton
> In article
> <455b69f6-df2a-4c8c-9564-38a17d6be...@z34g2000vbl.googlegroups.com>,
> davehigton <davehig...@dsl.pipex.com> wrote:
>
>
>
> > On 5 Oct, 00:26, Martin Wuerthner <spamt...@mw-software.com> wrote:
> > > In message <445e24a550.davehig...@dsl.pipex.com>
> > > Dave Higton <davehig...@dsl.pipex.com> wrote:
>
> > > > If you print something to a PostScript printer driver, saving to
> > > > a file, a PostScript file is generated.
> > > No, it spools the file to the printer. Unfortunately, in an extremely
> > > sluggish way.
> > That's the symptom of the problem! But /why/ is it sent
> > sluggishly? Why is it treated any differently from sending a
> > Printout file to a non-PS printer?
> > > > Should you change the file type to Printout so that it is sent
> > > > directly to the printer?
>
> > > No, you should leave it as PostScript so that it is sent directly to
> > > the printer.
>
> [Snip]
>
> > What would happen if its file type were set to Printout?
> > Btw I'm trying to diagnose the problem on behalf of Jim
> > Nagel, who described this to me at the show on Saturday.
>
> Jim runs PrintSpool, has he tried the above when it isn't running?
Sorry, I have no idea. This was just something he did on
Saturday morning.
I'll see if I can get him to join in this thread.
Dave
Jonathan Graham Harston
> It's so long since I did this I can't remember... Maybe a PS file gets
> treated the same way? If it comes to that a straightforward *copy to the
> device is probably enough.
Printer: ~CF~V. I usually use a grubby task on the icon bar with
the drag action set to "Copy %1 Printer: ~CF~V"
--
J.G.Harston - j...@arcade.demon.co.uk - mdfs.net/User/JGH
BBC BASIC for Windows and Internationalisation
See http://mdfs.net/Software/BBCBasic/Windows/ProgTips
Mr John FO Evans
I normally set my printers to print either to the printer directly
or to a file with a defined name in a scrap directory
I can then have any obey file in the same directory similar to the
following:-
*set Copyprint$Dir <Obey$dir>
*copy <Copyprint$dir>.printout lpr#192.168.123.2/: ~C F
This has the advantage that it can be extended to send multiple files - this
can be useful if your printer understands HP's PJL (Printer Job Language)
which can add extra functionality to the printer driver.
Multiple files could enable the printing printing of multiple collated Duplex
Booklets with a different paper tray for the cover and a centefold insert on
an HP8100:-
NOTE For multiple files a parallel connection must be used unless the files
are concatenated prior to printing. This is because the LAN seems to send an
end-of-job after each file.
*set Copyprint$Dir <Obey$dir>
*copy <Copyprint$dir>.pjl.preamble devices#buffers3:$.parallel ~C F
*copy <Copyprint$dir>.magcover devices#buffers3:$.parallel ~C F
*copy <Copyprint$dir>.magbody devices#buffers3:$.parallel ~C F
*copy <Copyprint$dir>.pjl.intermediate devices#buffers3:$.parallel ~C F
*copy <Copyprint$dir>.focus devices#buffers3:$.parallel ~C F
*copy <Copyprint$dir>.pjl.endjob devices#buffers3:$.parallel ~C F
magcover,magbody and focus are postscript2 (or PCL) files of separate parts
of the document. They can be generated seperately from the same or different
DTP packages.
Preamble sets the number of copies and DUPLEX/SIMPLEX. Intermediate and endjob
are simple control files. These files cannot be printed here and since binary
attachments are VERBOTEN here, you would need to ask me for them!!
John