Dumbstruck by Quark 4 asking something about EPS
Robert Stralka
pictures, Quark will ask me:
"Page could contain EPS pictures which include Binary data. OK to
continue?"
I continued and passed the pdf distilled from the file I printed into
to my printer (meaning the company that is printing for us, not the
laser on my desk). The final result looked as expected, nobody
complained.
The pictures are saved from Photoshop into EPS. When asked for EPS
options, I chose TIFF (8-Bit/Pixel) and ASCII Coded - w/o knowing what
I am doing...
Would somebody be so kind to enlighten me? What is the professionel
way to bring pictures into a Quark file anyway?
TIA Robert
RSD99
many PostScript printers did not understand binary data.
Usually safe to ignore ...
- - - -
"Robert Stralka" <r...@aperion.de> wrote in message
news:95f027a2.0202...@posting.google.com...
Jono Moore
systems, I believe.
...Jono
Del Tree
Stralka <r...@aperion.de> wrote
It occurs because Quirk's default is "Clean 8 bit" - a binary bodge
invented in 1896. As others have pointed out Quirk are about 300 years
behind the times in this as in a so many other areas. Ignore it, or if
you never wish to see it again set up Print Styles for all your regular
installed and virtual printers and make sure the Data type in the
Options tab is set to "Binary".
Best,
--
Del Tree
Lee Blevins
> It is a 'very old' error message, one that was quite appropriate fifteen
> years ago when many PostScript printers did not understand binary data.
>
> Usually safe to ignore ...
Wasn't that message created because PC's had issues with sending binary
data?
Mac's never had issues with binary postscript.
Del Tree
Blevins <le...@digitalgraphics.net> wrote
>Wasn't that message created because PC's had issues with sending binary
>data?
Yes, in 1990 :-)
>Mac's never had issues with binary postscript.
Correct 10/10.
--
Del Tree
Neil Gould
Lee Blevins <le...@digitalgraphics.net> wrote:
> RSD99 <rsdwla...@gte.net> wrote:
>
> > It is a 'very old' error message, one that was quite appropriate
fifteen
> > years ago when many PostScript printers did not understand binary
data.
> >
> > Usually safe to ignore ...
>
> Wasn't that message created because PC's had issues with sending
binary
> data?
>
To pick nits, it was Microsoft's PostScript driver that choked on binary
data. Throughout the '80s, I created many binary PostScript files
without problems from apps that created their own PostScript, and that
was under DOS. PostScript is PostScript, but Microsoft seems to always
make something their own. Too bad they screwed it up in the process.
> Mac's never had issues with binary postscript.
>
Yes, Adobe's PostScript driver works well on PC's, too. It just took a
while to get it! 8-)
--
Neil Gould
----------------------------------------------------------------
Terra Tu AV http://www.terratu.com
Technical Graphics & Media
Derek Tree
<ne...@terratu.com> wrote
>Yes, Adobe's PostScript driver works well on PC's, too. It just took a
>while to get it! 8-)
I think Bill's finally got it. The native 5.00.2195.3305 driver that
ships with NT 5.0 and 5.1 works very well indeed.
--
Derek Tree
Dennis Gordon
causes a job to dump. ASCII seems to give a little more tolerance, although
I imagine it spools a larger file. If that doesn't work then I export a PDF,
something Quark does very well....
Dennis
RSD99
. PostScript is PostScript, but Microsoft seems to always
make something their own.
YES!
And they (almost always) SCREW IT UP in the process.
- - - - -
"Neil Gould" <ne...@terratu.com> wrote in message
news:a4lnkq$t73$1...@slb1.atl.mindspring.net...
RSD99
I think Bill's finally got it. The native 5.00.2195.3305 driver that
ships with NT 5.0 and 5.1 works very well indeed.
I believe that driver was actually written by ADOBE!
- - - - -
"Derek Tree" <nos...@sanspam.freeuk.com> wrote in message
news:w0XzGILM...@lvlhc27lwvtr.easily.co.uk...
Derek Tree
<rsdwla...@gte.net> wrote
>I believe that driver was actually written by ADOBE!
Dear me..
Thank you for stating the obvious. They _all_ were - including the one's
that didn't work, or to be really pedantic, the were written _jointly_
by Adobe and MS. That is, apart from the ones that were not written
jointly by Adobe and M$ - which did (mostly) work.
--
Derek Tree
Lee Blevins
> To pick nits, it was Microsoft's PostScript driver that choked on binary
> data. Throughout the '80s, I created many binary PostScript files
> without problems from apps that created their own PostScript, and that
> was under DOS. PostScript is PostScript, but Microsoft seems to always
> make something their own. Too bad they screwed it up in the process.
I thought the issue had something to do with flow control through pc
ports.
Like a cntl-D stopped transmission so they had to send assci.
Neil Gould
The Ctrl-D issue affected both binary and ASCII PostScript output. That
was a problem that the Microsoft driver created by putting the Ctrl-D at
the _beginning_ of the PostScript stream, which, of course, ended the
process before it began in printers that didn't strip this out. In the
'80s, I wrote a short applet that stripped out any Ctrl-Ds from
PostScript files to address this issue. Newer PostScript drivers have a
checkbox to eliminate this behavior.