Re: Is Adobe violating their own standards
- From: Allen Wessels <awessels@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 06 Mar 2007 04:04:10 GMT
In article <I01Hh.7641$8U4.2526@xxxxxxxxxxxxxxxxxxxxxxxxxx>,
"Steve/Aus" <adlab@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Postscript is the universal printer description language or is supposed
to be, or indeed it was. A postscript file created in practically any
application on any platform could be read and used in practically any app on
any platform.
It was amongst the first to succesfully cross-platform and yet this
standard which should, if anything, gotten better over the years seems to be
moving further away from being universal.
My experience with this comes from the fact I use CorelDraw as my
preferred vector drawing program. Without going into precise details why, it
has a lot to do with being able to have multiple page documents and running
the files to a reel-to-reel digital label printer (not a thermal printer, a
PS3 colour laser printer).
Back to postscript, since the release of the CS suite of programs by
Adobe, I can not import EPS files created in CS programs into CorelDraw
version 12 even though it does support level three postscript. Out the
window goes the standard. EPS files created in other apps and pre-CS are not
a problem. Therefore I must conclude that the code in EPS files created by
CS programs is different.
The work-around for this is to send the files to my bureau who opens
them in a CS program, usually Illustrator or InDesign back saves them and
then creates a new EPS file which opens into CorelDraw without a problem.
I could easily draw conclusions as what I think might be happening here
but I will refrain as there *could* well be a more logical answer. In any
case, 'why fix it if it ain't broke' certainly comes to mind.
Steve W (in Aus)
You've got a couple of problems here.
First, Corel*DRAW* (emphasis added) is a design program. You can do
page assembly in any program, but it's your problem if it can't import
files from another program, let alone another generation of programs.
Your second issue is complaining about forward compatibility of one
application with another of a newer generation. I've seen that sort of
problem even within the same application from the same vendor across
platforms.
I understand this is the application you're using, but its your burden
to make it work in a way not intended. Shoot, that's half of what keeps
the prespress guys employed.
The software companies aren't ever gonna fix this. In fact, there are
factors pushing them to do the opposite. If they make a program that
takes in everyone else's files but won't import into others, seems like
most everyone who needs that kind of flexibility will need their app, if
for example they already dominate the market :-)
- Allen
.
- References:
- Is Adobe violating their own standards
- From: Steve/Aus
- Is Adobe violating their own standards
- Prev by Date: Re: Is Adobe violating their own standards
- Next by Date: Re: Is Adobe violating their own standards
- Previous by thread: Re: Is Adobe violating their own standards
- Next by thread: Re: Is Adobe violating their own standards
- Index(es):
Relevant Pages
|
