DTP gone bad!
21-Jan-90 23:32:17
Sb: #5876-DTP gone bad!
Fm: David Vereschagin 75645,1752
To: David Vereschagin 75645,1752
[continued]
think that's to their credit. And if a historical face has to be adjusted
to turn out well at 300 dpi, I think that's acceptable. Now, I think more
properly your argument is that because type is being designed for use at
300 dpi, it is being ruined for higher resolution. And that I might be able
to agree with you on. But I think those people who have a need for truly
fine type at high resolution will go to the bother of finding the right
vendor to fill their needs. Now, finding a service bureau to match that is
another question. As Kathleen pointed out in (I think) a different thread,
many bureaus will use fonts supplied by clients for particular jobs, and
remove them from their systems when the job is complete. And although this
may not follow the exact letter of the licensing agreement, it seems to be
how it is working out in practice. Has anybody been sued yet for doing
this? (This is an honest query, I'd like to know.)
Most people buy Adobe because Adobe is all they know. They know Adobe put
the "35 resident fonts" into their LaserWriters, so when they go looking
for more, they naturally turn in that direction. Plus, they are almost
universally available. This is Adobe's advantage from having been in at the
beginning of dtp. Again, as the field matures things will change. Adobe is
facing a lot of challenges these days. From Royal, from other vendors, from
PostScript clones. Things are still very volatile in this field, and it's a
field which, until recently, was not used to such rapid change. And we're
still not used to it. Most of us are complaining mightily about Royal and
bemoaning the thought of having to start our type libraries all over from
scratch.
I, too, work almost exclusively with dtp now, and I don't want to go
back, either. And it pleases me no end when I hear that my work on my Mac
can pass as the "real" stuff among typographic snobs who sneer at dtp.