Article View: comp.lang.postscript
Article #3928Re: NeWSprint help
From: Berthold K.P. Horn
Date: Fri, 02 Oct 1992 11:23
Date: Fri, 02 Oct 1992 11:23
18 lines
1270 bytes
1270 bytes
In article <1acrjhINNdeh@network.ucsd.edu> dmb@lyapunov.ucsd.edu (Doug Brownell) writes: I have a dumb question. I have a number of Type 1 fonts which won't print on our Sparc-printers, generating the error message 'command "eexec" undefined'. The message is somewhat more complicated than that, but I'll refrain from posting more unless asked. Is this due to an older version of NeWS, or is it intrinsic to Openwin? The error page indicated I'm using NeWSprint 1.0 fcs, Openwin 2, NeWSprint interpreter version 2.1 . I'd really like to be able to use these fonts! Version 1.0 does not support T1 fonts. Get version 2.0. It does support T1, although it has a number of bugs (that apparently will be ironed out by the time version 2.1 rolls around). Berthold K.P. Horn Cambridge, Massachusetts, USA
Technical Details
Message-ID:
<28758@life.ai.mit.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!wupost!usc!snorkelwacker.mit.edu!ai-lab!kauai!bkphReferences:
<1acrjhINNdeh@network.ucsd.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!wupost!usc!snorkelwacker.mit.edu!ai-lab!kauai!bkph From: bkph@kauai.ai.mit.edu (Berthold K.P. Horn) Newsgroups: comp.lang.postscript Subject: Re: NeWSprint help Message-ID: <28758@life.ai.mit.edu> Date: 2 Oct 92 11:23:50 GMT References: <1acrjhINNdeh@network.ucsd.edu> Sender: news@ai.mit.edu Lines: 18 In-reply-to: dmb@lyapunov.ucsd.edu's message of 30 Sep 92 18:28:01 GMT