#Imagesetter output
16 messages in this thread
[ continuation ]
times if necessary. They will ask you what program was used to create the
file. Tell them that is irrelevant. They will probably insist on knowing
such information, since they are used to outputting native files from the
original application, NOT PostScript files.
Tell them to send it from their MAC using the program SendPS. If they do
not have SendPS, or don't know how to use it, or won't, go elsewhere. Adobe
supplies every imagesetter manufacturer with an extensive set of utilities
including this program. Every imagesetter owner gets a set of these
programs.
If your bureau is using a PC, they can send your file to their imagestter
using the DOS 'COPY' command. (COPY <filename> LPT1, asuming that the
imagesetter is connected to LPT1).
That's enough for now. Don't be dismayed if this is confusing.
Unfortunately, preparing output for an imagesetter, requires the user to
know a fair amount of graphic art concepts, as well as computer control.
Output to RC paper the first few times. You won't have to worry about
negative output. And its cheaper than film – $6 to $12 per 9 x 12 page of
output.
Don't hesitate to ask any questions about this process.
Good luck!
Rich
Rich,
Your instructions to me for Postscript printing are extremely
appreciative. One message taught me more than flipping thru magazines and
manuals for hours. I'm a heck of a lot more confident walking into the
printers shop now.
Thankyou very much for taking the time to help. I'm only using two fonts
and no graphics. The dimensions won't be a problem. RC paper and not an
EPS file, got it.
Thanks again….
I'll be back with the good news 🙂
Paul,
I'm glad that helped. It was just a start, though. Once you learn how to
properly use PostScript output, you realize there's more to learn. It seems
that each improvement of 10% reveals 100% more territory to conquer!
Also be prepared for problems. We have the imagesetter sitting right here
next to the computers. We have full control over everything, and I think we
understand things pretty well now and we still make mistakes.
Some of them the slap ourself on the forehead type, because we knew better
and did something dumb. Some of them, inexplicable, requiring lots of
thought to get things sorted out.
In the end, though it is always obvious that the computer (the imagesetter)
did exactly what we told it to. Whetther what we told it was what we
intended or not.
When we make a mistake, we can re-output a page right away. It's annoying,
but not a major problem. When you make a mistake, it will take a day or so
for you to see the incorrect (or non-existent) output. And it can get
expensive. It's easy, for instance to leave the output set to 70% because
you want to output to your own printer (laserprinter or dot matrix or
whatever) and then forget to reset back to 100% when outputting for the
imagesetter.
BTW, if you can _always_ output to a PostScript laser printer for proofing
purposes before sending your file for imagesetter output. If the file won't
output on the laser printer it absolutely will not output on the
imagesetter! If it _does_ output on the laser printer, chances are it will
also output on the imagesetter, although it is quite possible to produce a
file that will clear a 300 dpi printer and crash on a high resolution
device. Also, if you are like me, you will need the laser printer output to
check your work before high resolution output. I _cannot_ rely on the
screen image for anything but the most basic of issues such as page layout,
design, glaring typographic mistakes.
Rich
Richard… (and Paul), you have a good point about the imagesetter output
not aways being what you expect… when I drop something off at my service
bureau, I always ask them to ouput a laser printer proof and fax it to me
for final approval. If it is 'ok', that means they now have a guide sheet
with which they can check the imagesetter output… then, if their are
problems with the imagesetter output, they can recognize them, and FAX me
the imagesetter output so that I can make revisions.
Michael,
Get a copy of POST so that you can output your file to a dot matrix printer
(sounds like you don't have a PostScript laser printer available). Your
method of interacting with your service bureau works, but it sure can get
expensive (and time-consuming).
Rich
Richard, I have both POST and a postscript laser printer. It's amazing how
sometimes those files change from the time I take the disk out of my
computer and give it to the service bureau <g>
My Service Bureau charges only $1 for a 300 DPI laser proof, and they
REQUIRE a guide sheet prior to going to the imagesetter.
The minor expense has saved me the cost of paying for imagestter pages
that have to be reworked… and it keeps the folks at the service bureau
from laughing at me. 🙂
Michael,
Sounds like you have a good service bureau.
8)
Rich
Rich,
Would it be worthwhile to learn a little about the Postscript language or
would that be more for trouble shooting? The only way I could would be
from the bookstore.
Any thoughts?
Paul,
The only way I have survived in this field is to have learned PostScript.
The learning curve is steep (what else is new?). Hope you have a good
bookstore. Let me know if you need recomendations about books!
Rich
Knowing PostScript is really quite important if you want to know what's
going on, especially when things don't quite work as you expect them to.
But, if you are just intending to produce PostScript files and print them
once in a while, then it's probably not worth it.
I have about 20 different PostScript books, and they vary from very simple
and practical introductions to heady reference books … maybe I can offer
some ideas on a good book or two??
Mike (from the UK)
Do you know of a book that would touch on most of the language with good
examples?
Paul,
A basic arsenal of PostScript manuals should include:
PostScript Language Tutorial and Cookbook Adobe Systems, Inc.
Addison-Wesley Publishing Co., Inc
PostScript Language Design Adobe Systems, Inc. Glenn C. Reid Addison-Wesley
Real World PostScript Edited by Stephen F. Roth Addison-Wesley
Understanding PostScript Programming David A. Holzgang Sybex
PostScript Language Reference Manual Second Edition Adobe Systems Addison
Wesley
Mike probably has a few of his favorites to add. There are also some
PostScript periodicals, and Adobe from time to time offers seminars.
Rich
Paul
A very good introduction is `Learning PostScript, a Visual Approach' by
Ross Smith (Peachpit Press) … with this and the POST interpreter, you can
work through the many examples (although you will need to watch out for
specific fonts that the examples may call for) … it's very much a learn
by example sort of book and probably the most systematic introduction there
is, although it won't teach you the details of syntax and so on.
`Understanding PostScript Programming', by David A. Holzang (SYBEX) is much
more of a text-book, but is well written and fairly easy to follow.
The one book you really must have is the `Red Book', the `PostScript
Language Reference Manual', by Adobe (Addison-Wesley) … it's the
definitive guide to PostScript and, if you buy no other, you should buy
this. It isn't easy going, doesn't have many examples, but it is very
thorough.
The companion books from Adobe (`PostScript Language Tutorial & Cookbook'
[the Blue Book] and `PostScript Language Program Design' [the Green Book])
are also worth considering.
There are many others, but I don't think I could recommend any for a
beginner. They're either far too advanced, or far too bound up in specific
(and rather complex) example programs.
A one-book purchase would have to be the reference manual … and I'd
recommend either the visual approach book or the SYBEX book depending on
your personal learning style. The other Adobe books are okay, but they have
some limitations and I wouldn't recommend them as initial purchases … the
green book, for instance, is really only useful if you want to get into
writing complex PostScript applications.
If you've a decent bookshop nearby, you'd do well to have a browse around
the PostScript books they have.
Mike (from the UK)
Hi Mike,
I would be interested in your suggestions for a couple of entry level
books on PostScript. I would like to get an idea of what the language is
doing and be able to (maybe) debug a couple of minor problems if the need
arises.
By the way, I appreciate the messages you have been posting etc.. I am
just getting into DTP and the next step is to try and find a suitable
output shop for my 60 page catalogue for our company. Its all set up with
ProPage and just about ready to go.
Leonard. (from the land down under.)
Leonard
See my earlier reply for entry level books.
There's no doubt that the Adobe Reference Manual is the best book, and
really the most important since it's the main language reference. It's
quite heavy going in places, though.
For a very basic introduction to the language, the SYBEX book is pretty
good
… and if you're just interested in `playing' with the language, then the
Learning PostScript book is worth considering.
One thing that really does help in learning PostScript is the PD POST
interpreter that you'll find hereabouts … you can enter PostScript
commands and see what they do straight away.
Good luck!
Mike (from the UK)
Rich,
Your reply to Paul Toal was right on! Very good job, sounds like you do it
for a living. ;-), Gee, I miss that kind of daily talk. Right reading,
mirror, emulsion down. You wouldn't believe how many arguments I had about
that one with my ex-partner. I finally won, forcing the imager by
front-panel control or the Varityper software to change the settings, and
NOT using the program's settings to do it. But we got a lot of errors
before I got thru to her. B*!%@!
Chris