[comp.lang.postscript] Postscript

11TSTARK@GALLUA.BITNET (Timothy Stark) (01/30/88)

Hello,

  I get PostScript from someone (comp.sources.unix) but I don't have
X11-Windows. Later, I found a reference file at Sri-Nic node
(service@sri-nic.arpa). It called RFC1013 file. It have many information
about X11 windows protocols. Is RFC1013 compitable with UNIX X library???
If, not, Is it PD or Properitory?? If properitory, please know me that
where company sells it include address and price, etc... If PD, please
know me that who distribute it includes address.. Please reply me
directly. Thanks.

-- Tim Stark

+==============================================================================+
| Timothy Stark          | BitNet:   11TSTARK@GALLUA.BITNET                    |
| Gallaudet University   | Internet: 11TSTARK%GALLUA.BITNET@CUNYVM.CUNY.EDU    |
| P.O. Box 1453          | UUCP:     ...!psuvax1!gallua.bitnet!11tstark        |
| Washington, DC. 20002  | CSNET:    11TSTARK%GALLUA.BITNET@RELAY.CS.NET       |
| USA                    | QLink:    TimS18                                    |
+==============================================================================+
 slkjd fjdjlf ds fldsjlkj  fldjfdjs sd f jfjflkdk fjffioweer  fkfoe  fdjjfd
 dkj  sjnvngdi fddskmbb dkjrticks skfmvmff kfdigoulapsz f dskxi,e szki z???

nrh@buzz.bellcore.com (Nat Howard) (03/25/88)

Now that there are several PostScript clones around or about
to be around, we printer-buyers have a problem:  How do you know
if a clone measures up?

When I first thought of this, the only answer I could see was to 
try printing stuff on different printers to see what would happen, but this
has some difficulties: visual fatigue, human error, blah, blah...

It then occurred to me that one might be able to do better: the
"framedevice" operator is given a proc as argument that is called
""to cause the contents of the frame buffer to be transmitted to the 
physical output device" (PLRM pp. 162)

If we knew what this proc was expecting as arguments, we could maybe
arrange for it to send a representation of the raster frame buffer
back down the communications link, and then do something (heaven only
knows what) to verify that you get the same bits out when you
put the same bits in.  

Has anyone tried this approach, or come up with something else
in the way of validation?  I agree that the resultant bitmaps
(even at 300 DPI) need not *exactly* match between an Adobe Postscript
and a clone printer -- particularly if they use different
technology engines (so that one would want some difference).  On the
other hand, the relative darkness of different areas of the pages
should be alike, and one could go on from there.

ken@cs.rochester.edu (Ken Yap) (03/25/88)

|It then occurred to me that one might be able to do better: the
|"framedevice" operator is given a proc as argument that is called
|""to cause the contents of the frame buffer to be transmitted to the 
|physical output device" (PLRM pp. 162)

I can think of one reason why this might not be implemented. You could
grab all the fonts off the printer that way. Since fonts do not enjoy
copyright protection in the US, printer manufacturers have to protect
their fonts by encoding them in proprietary format in ROMs.

Also, you'd need a fast channel like AppleTalk or a Centronics
interface for this to be practical.

	Ken

gerb@brahms.udel.edu (Herbert G Silber) (06/01/91)

How do I print a Mac postscript file on a sun connected to a 
XEROX page printer.  Need help quick
-greg