Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 UW 5/3/83; site uw-beaver Path: utzoo!linus!decvax!tektronix!uw-beaver!laser-lovers From: laser-lovers@uw-beaver (laser-lovers) Newsgroups: fa.laser-lovers Subject: Re: Scribe and the LN01 Message-ID: <2183@uw-beaver> Date: Sun, 11-Nov-84 02:24:27 EST Article-I.D.: uw-beave.2183 Posted: Sun Nov 11 02:24:27 1984 Date-Received: Tue, 13-Nov-84 00:44:33 EST Sender: yenbut@uw-beave Organization: U of Washington Computer Science Lines: 36 From: ss%wang-inst.csnet@csnet-relay.arpa > > [This is in response to a recent message from Sid Shapiro at Wang > concerning Scribe support for the DEC LN01.] > > Wang has stated that we do not correctly support the default fonts supplied > with the LN01 by DEC. This is not the case. What I said (or at least meant) was the default configuration of Scribe (for the LN01) did not reflect the default condition of the printer. In retrospect this is, of course, quite understandable, since how is UniLogic to know which printer I intend to use scribe with. However, there is no documentation with that describes how I tell scribe which of the LN01's fonts I DO have. > The second problem raised is that Scribe output files destined for the > LN01 cannot be spooled by means of the VMS PRINT command or even the COPY > command. This is clearly a deficiency in DEC's support for its own output > device, a fact which DEC freely admits and is taking steps to correct. True enough, however if UniLogic knows that there is a problem, I would have thought that they would be nice enough to warn people of this problem rather than letting us all find out on our own. If they must use a non-standard spooler to get things printed, then I would have expected at least a pointer to somwhere that I might obtain it also. Again in retrospect, I flamed a bit too much. However, I am disappointed in the level of warnings/support/and documentation that UniLogic provides. Which is too bad, since generally Scribe is great product. / Sid /