HDTenEightyP/NetNews huggingface dataset:
From: zisk@adobe.com (Stephen Zisk)
Newsgroups: comp.lang.postscript
Subject: Re: Permanently hiding level 2 Postscript printers on LocalTalk
Date: 10 Nov 92 20:44:06 GMT
Article-I.D.: macne004.zisk-101192151023
Followup-To: comp.lang.postscript
Organization: Adobe Systems Incorporated

In article <root.721377167@psychvax>, johnh@psych.su.oz.au (John Holden)
wrote:
> 
> 	I have a LaserWriter IIg and a LaserWriter NTR that I wish to hide
> from direct access by Macintoshes by changing the LocalTalkType to
> something other than LaserWriter (ie LW Spooler). The following script works,
> but the printer reverts after a reset (ie power cycle).
> 
> true 0 startjob (%LocalTalk%) <</LocalTalkType (LW Spooler)>> setdevparams
> 
> Various permutations of %LocalTalk% like %LocalTalk_NV% will still fail
> across resets. Is there an incantation that works?

First of all, there are two passwords on a Level 2 machine: the startjob
password and the system parameters password. You are using the startjob
password by invoking startjob. Try adding the /Password key with a value of
the system parameters password to your setdevparams invokation.

Secondly, there is no guarantee that all settable device parameters will be
stored across power cycles. This depends on how much non-volatile ram is
available. Check your printer supplement for which values are persistent.

Finally, device parameters do not obey save/restore, so there is no need to
set them outside of the server loop. So your code could be:
  (%LocalTalk%) <</Password xxx /LocalTalkType (LW Spooler)>> setdevparams

Regards,
Steve Zisk

Stephen Zisk (zisk@adobe.com)   Disclaimer: These are my personal opinions
and
Adobe Systems Incorporated      do not represent the views of Adobe Systems
Eastern Regional Office         Incorporated.
24 New England Exec. Park
Burlington, MA 01803            They pay me but they don't muzzle me!
Newsgroups: comp.lang.postscript
From: henry@trilithon.mpk.ca.us (Henry McGilton)
Subject: Re: How to print a large ps file?.
Organization: Trilithon Software
Date: Thu, 12 Nov 1992 17:02:45 GMT


In article <1dn7brINNdjq@gap.caltech.edu> carl@SOL1.GPS.CALTECH.EDU writes:
>In article <1992Nov9.223322.27775@cs.wayne.edu>, nar@usha.cs.wayne.edu  
(Nagarajan Ramesh) writes:
	    **  I have a large ps file that is too large for my
	    **  Apple laser writer.  Even a symbollic link does
	    **  not work.  Can anybody tell me how I can print this
	    **  file?.

	*  Perhaps you'd tell us what you mean by "too large for my
	*  Apple laser writer"? What error messages do you get when
	*  you try to print it?  Why did you think a symbolic link
	*  would make the slightest difference?

    *  Well, the memory on my printer is limited to 300000 bytes.
    *  Therefore, when I send a postscript file from my workstation
    *  to my printer, there is not enough room to copy the whole
    *  file onto it. The error message I get is

	lpr: temp.ps: copy file is too large

    *  One could use a symbollic link (lpr with the -s option) on
    *  SUN OS, wherein instead of copying the file, a link is
    *  created and therefore the printer memory is not a limit -
    *  atleast in theory.  But again, apparently there is a limit
    *  even for this kind of operation. So, then my question is
    *  - how do I print the large postscript file?.

The message about  copy file too large  has nothing whatsoever to
do with the amount of memory or other resources available to your
printer.  This message comes from the print spooler, which can be
on a machine physically separate in both space and time from the
machine to which the printer is connected and from the time when
the job will be printed (sometimes days or weeks later if you're
using a UNIX spooler).

The message indicates that the print job is physically larger than
the defined number of bytes that the spooler is willing to copy
into the local spool area.

The  -s  option is of use in precisely one circumstance:  if you
are printing a real file (not the output of a pipe) to a printer
that is physically connected to the machine from which you are
performing the printing.  The  -s  option makes a symbolic link
instead of copying the print file to the spool directory.  In all
other cases, such as the printer being on a remote host, or the
print ``file'' being the result of something piped to lpr or lp,
the spooler makes a physical copy of the print job in the local
spool directory.

The default maximum file size is one megabyte.  You can change this
by changing the  /ect/printcap  file on the local machine so that
the mx field reads  mx#0  (0 means unlimited in this case).   This
of course refers to the BSD spooler.  I'm sure that SVR4 has a way
to make this even more complicated.

As to the questioning of Mister Ramesh's grasp of ``Computer
Science'' -- all this stuff about spooler limits, printcaps,
symbolic links -- none of this is ``computer science''.  It's
black magic and a miracle you ever get anything printed at all
on UNIX systems.

	........  Henry
Newsgroups: comp.lang.postscript
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.lang.postscript
Subject: Re: How do I recognize postscript from a file
Date: 9 Nov 1992 00:45:12 GMT
Organization: HST Wide Field/Planetary Camera
Distribution: world
Reply-To: carl@SOL1.GPS.CALTECH.EDU
NNTP-Posting-Host: sol1.gps.caltech.edu

In article <BxEy6H.KCs@chinet.chi.il.us>, les@chinet.chi.il.us (Leslie Mikesell) writes:
>In article <3944@ecicrl.ocunix.on.ca> clewis@ferret.ocunix.on.ca (Chris Lewis) writes:
>
>>>When printing from MS Windows to Postscript file, the file (if you don't
>>>make it not to) starts with characters ^D%! (i.e. control-D, %, !).

>>The correct way to handle this is for the application to *not*
>>append or prepend ^D's, and let the spooler handle it.

>Errr, since when does MS Windows *have* a print spooler?  Don't you
>think it would be pretty silly of the applications to generate output
>that wouldn't work under the most common conditions?

Why not have the application start the file with:

%!
^D
%!
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.
From: dundas@chip.Jpl.Nasa.Gov (John Dundas)
Newsgroups: comp.lang.postscript
Subject: PS fragment needed
Date: 4 Nov 92 23:45:01 GMT
Organization: Information Systems Engineering Grp, JPL

Could someone post code to perform the following:

	See if PhotoGrade is available (in a device & level independent manner)
		if so, set/get the resolution vs. grays setting for
			the current job

Thanks!

John Dundas
dundas@salt.jpl.nasa.gov
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.lang.postscript
Subject: Re: How do I recognize postscript from a file
Date: 8 Nov 92 19:59:05 GMT
Organization: Chinet - Public Access UNIX

In article <3944@ecicrl.ocunix.on.ca> clewis@ferret.ocunix.on.ca (Chris Lewis) writes:

>>When printing from MS Windows to Postscript file, the file (if you don't
>>make it not to) starts with characters ^D%! (i.e. control-D, %, !).

>The correct way to handle this is for the application to *not*
>append or prepend ^D's, and let the spooler handle it.

Errr, since when does MS Windows *have* a print spooler?  Don't you
think it would be pretty silly of the applications to generate output
that wouldn't work under the most common conditions?

>MS Windows use of ^D is a kludge workaround for somebody else's botch.
>A bad kludge.  Because the output of MS Windows ain't PostScript because
>of it.

Yes, having a single-tasking operating system is a botch I suppose, but
it happens a lot in the real world.  I say the botch is that postscript
printers require the ^D  to terminate a job over the serial/parallel
ports, yet it isn't a defined postscript command.  Personal computers
typically output directly to the printer generally do not provide
graceful termination when you cancel a print job or shut the machine
down. Thus applications cannot assume that the previous job was correctly
terminated and that the printer is in the correct state to start another
one without a ^D to flush it.  The same applies to printing to files
under DOS/windows since the most likely use of those files is to simply
copy them to the printer device.

If ^D or some other token (perhaps not in the control character range) had
been included in the postscript language definition to perform this needed
function the problem simply wouldn't exist.  In fact it could have been
documented like showpage as an operator that should be redefined during
EPS inclusion.  As things stand, I think the best approach is to teach
print spoolers to ignore leading ^D's on postscript documents.  Otherwise
it's impossible to get consistent behaviour when alternating between a
direct connection to a postscript printer and a network link that ends
up going through a print spooler.

Les Mikesell
  les@chinet.chi.il.us 
Newsgroups: comp.lang.postscript
From: jgm@cs.brown.edu (Jonathan Monsarrat)
Subject: PostScript vs. X as a graphics protocol
Organization: Brown University Department of Computer Science
Date: Mon, 9 Nov 1992 23:39:33 GMT

Newsgroups: comp.lang.postscript,
Subject: PostScript vs. X as a graphics protocol
Summary: 
Expires: 
Followup-To: 
Distribution: world
Organization: Brown University Department of Computer Science
Keywords: 

*******PROBLEM:

I've heard that some people prefer PostScript as a graphics protcol
over some other protocols like the X protocol for the following
reason:

1. PostScript is a program, which means that you can pack the data in 
   the best way possible, and include a tiny program to interpret it.

2. The X protocol is defined and static, so you can only do the things
   that the X protocol allows. Your data must be in one of the
   predefined forms.

*******EXAMPLE:

If I wanted to generate a picture made up of filled regions,
I could use the X protocol like this:

    line line line line fill line line line line fill line line line fill
    etc. etc.

Where the lines and fills belong to some predefined format. In
PostScript I can prepend a special program to let me do the lines and
filling more compactly, like this:

/p 4/f{{}forall moveto gsave{dup 32 mod dup 15 mul rotate sub p div 0 rlineto}
forall fill grestore}def 4 scale 1 def(``f`f`f)dup(  )f( i).3 setgray f/p 8 def
1 setgray/h(F!6! 2477!W)def h("4)h(,C)h(6O)h(LT)h(^O)h(tC)h(~6)(7!6!"7#$&6!7 #)
(9~)(""""""""""")(}~)(fTV``Vt)(9!)(e!FR"n&44ED-w@-7&&b)(C2)11{f}repeat showpage

********THINK-UMS:

Well, pros and cons that I can think of.

PostScript Con: the program passed in through the protocol
                could be a security problem.

PostScript Con: the program could be non-portable. When you port 
                X to a platform, it's done. With a PostScript protocol
                each protocol program needs porting.

PostScript Pro: Takes less space than X.

X Pro: No need to interpret and compile incoming program. Large common
       stuff can be handled directly.

PostScript Con: Unless you combined a little of the "static programs"
                of the X method, you'd never be able to interpret data
                at all unless there were a program sent with it!

PostScript Con: Is PostScript fast enough?

********DISCUSSION?

Now, I come from MIT where a lot of X stuff happened, but I also
like PostScript a lot. So I am undecided.

Any opinions on this choice and where/when one or the other is best?

What systems use PostScript as a protocol? The NeXT does this, right?

I'm not going to cross-post this to an X newsgroup because I'm just
kind of curious to hear some opinions. I'm not trying to start a
flame session between two newsgroups or anything!! :)

-Jon
%! Jon Monsarrat   jgm@cs.brown.edu   Brown University %! Obfuscated PostScript
0 0 moveto 15 setlinewidth(qlllll-??LHHL??llH?hH7t,7olCAHH@)1 setlinejoin{dup
10 mul rotate 80 lt{50 0 rlineto}{50 0 rmoveto}ifelse}forall stroke showpage
From: dok_mki@sovb23pki-nbg.philips.de (Manfred Kipp)
Newsgroups: comp.lang.postscript
Subject: Re: PS-program to extract font from printer?
Keywords: Font-Upload, PS-fonts, outline-fonts, Adobe
Date: 9 Nov 92 10:16:52 GMT
Reply-To: dok_mki@pki-nbg.philips.de
Organization: Philips Communication Systems, Nuremberg, Germany


In article <BwDGxK.3pv@bull.nl>, jos@bull.nl (Jos Vos) writes:
|> From: jos@bull.nl (Jos Vos)
|> Subject: Re: PS-program to extract font from printer?
|> 
|> simon@nada.kth.se (Simon Tardell) writes:
|> 
|> >I think the subject says it all. I want a ps-program that will extract
|> >any given font from the printer and send it back to the computer.
|> >Where do I find it?
|> 
|> In PostScript level 1, it is NOT possible to get information about Type 1
|> fonts. E.g., the operator giving you back the path of a letter produces an
|> "invalidaccess" error.
|> 
|> It was said that this restriction would be removed in PS level 2, but I
|> didn't actually try it. So, any solution will only work at PS level 2.
|> 
|> Hint: if you want the standard 13+22 type 1 fonts from your printer,
|> buy Adobe Type Manager (base 13 fonts) and/or the ATM Plus pack (22 fonts).
|> 
|> -- 
|> --    Jos Vos <jos@bull.nl>   (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos)
|> --    Bull Nederland NV, Product Support Unix, Amsterdam, The Netherlands

Hi all interested,
this seems not to be the whole truth,
it is possible to upload fonts from printer (maybe only AppleIINTX).

If you use MacIntosh and Altsys' application "Metamorphosis",
(including selected option: ... load fonts from printer) you can
extract Type 1 or Type 3 e.g. from printer and generate Fontographer Database-file.
Next step: try Altsys'"Fontographer" to generate bitmap and diff. outline-font-formats.
See Fontogr.-man-pages

How to convert to sun using FrameMaker e.g., see Frame's "Adding PostScript Fonts to FrameMaker".

P.S. "Metamorphosis" didn't work with an Emerald-RIP-included harddisk!
     Maybe this is one answer to a FAQ!

greetings
m.k.
From: brown@vidiot.UUCP (Vidiot)
Newsgroups: comp.lang.postscript
Subject: Re: How do I recognize postscript from a file
Date: 10 Nov 92 06:45:04 GMT
Reply-To: brown@vidiot.UUCP (Vidiot)
Organization: Vidiot's Hangout

In article <BxEy6H.KCs@chinet.chi.il.us> les@chinet.chi.il.us (Leslie Mikesell) writes:
<In article <3944@ecicrl.ocunix.on.ca> clewis@ferret.ocunix.on.ca (Chris Lewis) writes:
<
<>>When printing from MS Windows to Postscript file, the file (if you don't
<>>make it not to) starts with characters ^D%! (i.e. control-D, %, !).
<
<>The correct way to handle this is for the application to *not*
<>append or prepend ^D's, and let the spooler handle it.
<
<Errr, since when does MS Windows *have* a print spooler?  Don't you
<think it would be pretty silly of the applications to generate output
<that wouldn't work under the most common conditions?

Gee, I thought that MS Windows did have a print spooler.  Sure looked like it
when I used it.
-- 
      harvard\                          spool.cs.wisc.edu!astroatc!vidiot!brown
Vidiot  ucbvax!uwvax..........!astroatc!vidiot!brown
      rutgers/            INTERNET:vidiot!brown%astroatc.UUCP@spool.cs.wisc.edu
                                   brown@wi.extrel.com
Newsgroups: comp.lang.postscript
Subject: Help! ATM fonts
From: zong@huey.cs.huji.ac.il (Yaniv Azriel)
Date: 8 Nov 1992 07:43:14 GMT
Distribution: world
Organization: The Hebrew U. of Jerusalem, Computer Science Dep.
NNTP-Posting-Host: huey.cs.huji.ac.il

Hallo everyone,

  I have no experience in post script, but my boss is sitting on my neck for some
fonts we urgently need in the company. Can anyone please help me out here:

   I am looking for Adobe Type I fonts, on FTP,  for Russian and Arabic.
   WHere can i find any?
   I 'think' i need them in .pfa or .pfb format, though i am not sure... ;)

  Any help would be appreciated
  Thanks,

   Yaniv




------------------------------------------------------------
Yaniv Azriel		|	
Hebrew University	|	
Jerusalem		|	Users are irrelevant...
Israel			|
huey.cs.huji.ac.il 	|
------------------------------------------------------------
       __   ______   _____    ______   ______   __
      | |  |  ___|  |  __ \  |  __ |  |  ___|  | |
      | |  | |____  | |_| /  | |_| |  | |___   | |
      | |  |____ |  |  _ \   |  __ |  |  __|   | |
      | |   ___| |  | | \ \  | | | |  | |____  | |____
      |_|  |_____|  |_| |_|  |_| |_|  |_____|  |_____|

------------------------------------------------------------

         _|\_     And some day, when i am old and wise
        /_O_/     If they ask me if i knew you
         \/       I would smile and say you were a friend on mine
   |/     |
  >@--,   \       And some day, in the midth of time
  /\  \  \|/      If they ask you if you knew me
      /   \       Remember that you were a friend of mine.
 ^^^^^^^^^^^^^^             (Alan Parson Project, Old and Wise)

----------------------------------------------------------------
From: earley@modular.com (Joe Earley)
Newsgroups: comp.lang.postscript
Subject: Re: PostScript vs. X as a graphics protocol
Date: 11 Nov 92 15:42:58 GMT
Distribution: na
Organization: Modular Mining Systems, Tucson, AZ

But what about an input model for DPS?  What flavor of coordinates do I get
when I click a mouse button in a DPS canvas?  If I'm given the raw device
coordinates how do I get the coordinates from the current graphics state
without having to keep track of the graphics state myself?  Do I get
synchronous and asynchronous communications to the DPS interpreter?

Please don't believe that I'm bad mouthing DPS.  I'm facing the demise of
NeWS and am hoping that DPS will enable me to salvage a couple of applications
that I've got.  I'ld also like to continue using PostScript as my drawing
language and not have to face using some Xlib derivative.

Joe Earley, Modular Mining Systems
modular!earley@cs.arizona.edu
Newsgroups: comp.lang.postscript,comp.periphs.printers
From: mark.horton@ATT.COM (Mark Horton)
Subject: LaserJet I enhancements
Followup-To: poster
Reply-To: mark.horton@ATT.COM (Mark Horton)
Organization: AT&T Bell Labs
Date: Tue, 10 Nov 1992 18:58:57 GMT

I recently acquired an original HP LaserJet and I'm trying to make it
do something more useful than printing plain text.  I heard a rumor
that a company called PrinterWorks (possibly advertising in Computer
Shopper) offers an add-in board that will turn a LaserJet (or anything
with a Canon engine) into a PostScript printer.  Another rumor suggests
that Pacific Page has such a product as well.

Does anyone know anything about these products, or where the companies are
so I can contact them and find out?  I'm also wondering about the quality
of the result, since the LJ has only a serial port, line noise can mess up
the print quality.

I know about GhostScript - I have that working, but it's limited to 75dpi
due to the tiny memory of the laserjet.  It also looks like it's been FAXed
due to line noise from the serial port.

I'm also wondering about printing PostScript on the new HP color DeskJet
printers, such as the 550C.  Is there any way to do that?

Thanks,

	Mark.Horton@att.com
From: andrew@frip.WV.TEK.COM (Andrew Klossner)
Newsgroups: comp.lang.postscript
Subject: Re: How do I recognize postscript from a file
Date: 10 Nov 92 21:17:02 GMT
Reply-To: andrew@frip.wv.tek.com
Organization: Tektronix Color Printers, Wilsonville, Oregon

[]

	"The correct way ... would be to provide a defined and
	acceptable operator that an application could use to indicate
	that "this is the start of a new job" with the implicit effect
	of putting a printer in a sane state (i.e.  equivalent to after
	receiving ^D or EOF)."

The reason this isn't sufficient is that the PostScript lexer isn't
necessarily the agent reading from the job stream.  The previous job
might be stuck in a "currentfile readline" loop.  Or the previous job
might have encountered an error, and the system is "flushing until
end-of-file".

Ideally, PostScript jobs are transmitted through media which provide
for out-of-band notification of control information such as
end-of-file.  This is the case for AppleTalk and TCP/IP (and note that
you'd better not send a control-D through these networks!), but not for
serial and parallel, so these latter must use an in-band EOF indicator
which is not part of the language.

  -=- Andrew Klossner  (andrew@frip.wv.tek.com)
                       (uunet!tektronix!frip.WV.TEK!andrew)
From: dundas@chip.Jpl.Nasa.Gov (John Dundas)
Newsgroups: comp.lang.postscript
Subject: PS fragment needed
Date: 4 Nov 92 23:08:19 GMT
Organization: Information Systems Engineering Grp, JPL

Could someone post code to perform the following:

	See if PhotoGrade is available (in a device independent manner)
		if so, set/get the resolution vs. grays setting for
			the current job

Thanks!

John Dundas
dundas@salt.jpl.nasa.gov
From: brown@vidiot.UUCP (Vidiot)
Newsgroups: comp.lang.postscript
Subject: Re: How do I recognize postscript from a file
Date: 7 Nov 92 03:27:33 GMT
Reply-To: brown@vidiot.UUCP (Vidiot)
Organization: Vidiot's Hangout

In article <AV.92Nov4095431@kielo.uta.fi> av@uta.fi (Arto V. Viitanen) writes:
<>>>>> On 3 Nov 92 11:14:48 GMT, eweingar@loanshark.cs.indiana.edu (Peter Weingartner) said:
<
<Peter> In article <1992Nov3.083527.20756@ugle.unit.no> helgeaa@colargol (Helge O. Aarstein) writes:
<
<Peter>    We are trying to make a filter for the lp-command to reject 
<Peter>    non-postscript files. But, there is a problem: 
<Peter> 	   How can I be sure that the file contains postscript-
<Peter> 	   code?
<
<Peter> The simplest way is probably to check to see that the first two
<Peter> characters of the file are '%!'.  
<
<When printing from MS Windows to Postscript file, the file (if you don't
<make it not to) starts with characters ^D%! (i.e. control-D, %, !). In a way,
<this is right way, since ^D means end-of-job to a Postscript printer, so
<previous job is stopped. I only thought to say this, since lpr-filter on our
<department checks the %! -pair, and several times Postscript document has
<been run through Ascii-to-PS filter.

Starting with a ^D is wrong pure and simple.  DOS machines have been doing it
wrong for a long time.  Sending a ^D to the printer at the end of the job is
fine, but not before the job.

Makes it rough on printer spoolers looking for the correct %! and it also makes
it tough when trying to cat PostScript files together as one job.

I consider it wrong, plain and simple.
-- 
      harvard\                          spool.cs.wisc.edu!astroatc!vidiot!brown
Vidiot  ucbvax!uwvax..........!astroatc!vidiot!brown
      rutgers/            INTERNET:vidiot!brown%astroatc.UUCP@spool.cs.wisc.edu
                                   brown@wi.extrel.com