[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::document_ft

Title:DOCUMENT T1.0
Notice:**New notesfile (DOCUMENT.NOTE) now available (see note 897)**
Moderator:CLOSET::ADLER
Created:Mon Feb 09 1987
Last Modified:Thu Oct 31 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:897
Total number of notes:4397

34.0. "Typesetter output?" by CASV07::JDEADERICK (Joan E. Deaderick) Fri Feb 27 1987 10:25

What has become of the TYPESETTER and BITBLASTER destinations in T1.0?

Not that we were able to use them, actually, but we were thinking about
using that kind of output for future applications.

Joan Deaderick
CAS RIS ISS

T.RTitleUserPersonal
Name
DateLines
34.1Consider PostScript devicesDECWET::KOSAKFri Feb 27 1987 11:4919
    If you're thinking about phototype output for the future, consider
    using a PostScript machine.  Now that DOCUMENT supports PostScript
    we can include graphics created on a wide range of systems that
    output PostScript files (like GRED), and use our LPS40s as proofing
    printers.  Right now, Linotype is the only company that makes a
    PostScript phototypesetter, but Compugraphic may be coming out with
    one soon.  There are also some high resolution PostScript laser
    printers coming out, like the Compugraphic CG 400-PS at 400 dpi.
    Later this spring Lintotype is supposed to announce a similar product
    (with perhaps higher resolution?).
    
    Another thing, for the price of an APS Micro-5G and a Bit Blaster,
    you could buy *two* Linotype L300 typesetters, an LPS40, a top of
    the line phototype paper processor, all the associated goodies,
    and still have $30,000 left over.
    
    Worth thinking about.
    
    -- Craig
34.2CLOSET::ADLERFri Feb 27 1987 17:319
Support for those destinations is not part of the general internal 
kit (and never was). The reason for that is that we don't own the
rights to the DVI driver for the APS micro-5 typesetter. Also, hooking
one of those  typesetters up to a VAX and getting it to work is a royal pain,
and we didn't want to encourage customers to do so (that's why we didn't
buy the software and include it in the product.


--Brian