Future PS extensions

Article View: comp.lang.postscript

Article #8874

Back to comp.lang.postscript Previous Next

#8874

From: Chris GUZAK
Date: Sun, 04 Feb 1990 05:23

21 lines
1345 bytes

I'd like to start a discussion about what people would like to see
added to PostScript.  Ideas have been thrown about in past postings
(sometimes hotly debated) but I would like more specific details.

Recent discussions of compression techniques (and code that I have
impelemented myself) point to an obvious extension, readencodedstring.
This would be just like readstring (or readhexstring) but would
support a standard encoding method, perhaps more than one (simple
RLE or LZ).  I would like to see Adobe (perhaps someone else?)
add this to future versions of postscript, as well as provide a 
tight, highly optimized version to support past versions where 
this is not available.

Even in environemnts where transimssion time is not an issue encoding
is useful (we all don't have infinte amounts of disk).

What about things like ROPS and bitblt? Are these things worth adding
or would they just spoil the flavor of the language?

Chris Guzak
disclaimer... sure.

Technical Details

Message-ID: <10447@microsoft.UUCP>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!microsoft!chrisg

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!microsoft!chrisg
From: chrisg@microsoft.UUCP (Chris GUZAK)
Newsgroups: comp.lang.postscript
Subject: Future PS extensions
Message-ID: <10447@microsoft.UUCP>
Date: 4 Feb 90 05:23:04 GMT
Reply-To: chrisg@microsoft.UUCP (Chris GUZAK)
Organization: Microsoft Corp., Redmond WA
Lines: 21