#Postscript Problem
5 messages in this thread
OK, let's see if I can clarify somewhat. I talked to the guy again and he
says they do the following:
1. copy my file off of the BBS onto a MAC disk, put it in a MAC.
2. Launch Posertworks and place the file.
3. Print file to a Postscript level 2 file, which then goes directly to
Smart Color, which rasterizes it.
4. From here he should be able to a preview of the image, but it is always
blank.
So yes, it is still blank after they rip it. They do use true Adobe
Posctscrip as well.
No, I didn't print to disk with the EPS option. I didn't know there was
one.
I did, however, find that when I tried to print a scaled-down version of
the document onto an 8.5 x 11 page, it wouldn't print on my postscript
printer either. I turned on the "print errors" feature and found that
there is an "invalid font." It says the offending command is "show." So, I
changed the font the printer didn't like to one that it does (don't
understand this, since the bad font was an Adobe font to start with), and
now the small scale version prints okay. I don't know if this has anything
to do with the larger problem, but it's one thing out of the way at least.
In these situations it would help to know ahead of time which PS driver
version to use, whether I need to put "color" in the text gadget, and
which selection to make: Separable, Mechanical or no sep. The doc does use
spot color, but I don't know in this instance what format their machines
need. The guy can't tell me because it's not a MAC application. Again, I
have no trouble getting the settings right when outputting to my regular
service bureau to Rainbow or Lino printers. The last color job I did came
out gorgeous.
Hopefully you now have a clearer picture of what my immediate problem is.
Thanks,
CarsonT
They are not doing it correctly. They should not be importing the file into
PosterWorks. They should be sending it directly to Smart Color, which I assume
is some software-based PostScript interpreter. Importing the PS file into
PosterWorks will definitely cause problems.
You cannot import a PostScript file that has been printed to disk into another
DTP program for printing. EPS files are meant for that, but I don't recommend
that option for what you're doing. He should just be sending the PostScript
file to his PostScript interpreter directly. I recommend him reading his Smart
Color manual and finding out how to deal with PostScript files, which should be
a very basic function.
I'll need to know which version of PageStream you are using and the exact model
of the printer before I can recommend which driver options you should use.
PageStream2 and 3 work very differently in this regard, and I don't know
anything about his printer.
Cheers,
Michael – Soft-Logik Publishing
In a previous message I mentioned that his printer is a Versi Tech 8900.
My version of PageStream is 2.2.
I'll pass along your information, but it seems to me that this guy knows
exactly how to work his gear. OCB Reprographics is the biggest repro/cad
house in Orange County. It may be that my non-MAC application is what he
doesn't understand. You know what would be really helpful, is if you could
talk to this guy directly. I know it's a lot to ask, but it would
definitely save time and factor me out as the unknowledgeable go-between.
Should you feel so inspired, his name is:
Bill Southworth
CAD Division,
OCB Reprographics
(714) 660-1150
Reference: Carson Tyler's CONCEN.PS# uploads. He knows my name and is
familiar with the problems.
I'm sorry, he does _not_ know how to 'work his gear' if he is importing a
PostScript file into another program for printing. It's already printed and
just needs to be sent to the printer. This is one of the most common mistakes
made by service bureaus, and I normally recommend customers to avoid bureaus
like this. If a service bureau doesn't understand what a PostScript file is,
and how to print it, they don't deserve your business.
A service bureau doesn't have to know anything about your PostScript file to
print it. It is completely irrelevant that it was created on an Amiga.
PostScript is a device independent language and there is nothing wrong with
PageStream 2.2's output. This may sound pretty strong, but the problem is with
your service bureau.
If a service bureau chooses to use something like a software-based PostScript
interpreter (and this decision is almost always made to save money), they had
better know what they are doing. It doesn't sound like this service bureau
does.
Once again:
– tell him your file is a PostScript file. It does not need to be imported into
another program for printing. It should be sent directly to the
printer/imagesetter/interpreter.
If, upon doing that (and he hasn't done that yet according to what you have
told me), it doesn't work, then it is the fault of his PostScript clone. Our
PostScript files _will_ work on any PostScript printer or interpreter, but we
cannot guarantee compatibility with clones.
Michael – Soft-Logik Publishing
OK. I'll tell him.
Thanks,
CT