Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site uw-beaver
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!mtuxo!mtunh!mtx5d!hou5e!mtunf!ariel!vax135!cornell!uw-beaver!laser-lovers
From: laser-lovers@uw-beaver
Newsgroups: fa.laser-lovers
Subject: How using interpress
Message-ID: <1371@uw-beaver>
Date: Tue, 2-Jul-85 17:31:08 EDT
Article-I.D.: uw-beave.1371
Posted: Tue Jul  2 17:31:08 1985
Date-Received: Wed, 3-Jul-85 09:08:56 EDT
Sender: daemon@uw-beaver
Organization: U of Washington Computer Science
Lines: 13

From: mirror!rs@cca-unix (Rich Salz)


Before I left Xyvision three months ago, they were planning on
using interpress because they intended to drive the 9700 as an
output device.  It was going to be handled the same way any
other output device is:  an output driver program reads the
Xyvision Standard Format database, and translates their "generic"
data manipulation commands (e.g., MovHoriz, DrawRule:x:y, etc.)
into the specific commands required by the typesetter.  There
was some hassle because interpress isn't exactly the same
model as most CRT typesetters, but because XSF was a structured,
page-oriented data format, it didn't seem too unreasonable.