Xref: utzoo comp.sys.mac:20870 comp.sys.mac.programmer:2556 comp.lang.postscript:1015
Path: utzoo!dciem!trigraph!john
From: john@trigraph.UUCP (John Chew)
Newsgroups: comp.sys.mac,comp.sys.mac.programmer,comp.lang.postscript
Subject: Re: PostScript run-length encoding (again)
Message-ID: <408@trigraph.UUCP>
Date: 28 Sep 88 12:33:05 GMT
Article-I.D.: trigraph.408
References: <271@rna.UUCP>
Reply-To: poslfit@gpu.utcs.toronto.edu
Followup-To: comp.sys.mac.programmer,comp.lang.postscript
Organization: Trigraph Inc., Toronto, Canada
Lines: 25

In article <271@rna.UUCP> marc@rna.UUCP (Marc Johnson) writes:
>Many thanks to those who responded to my query about compressing PostScript
>bitmaps output with the "image" operator.
>
>Alas, all the responses (and there were several good ones) gave various methods
>for compressing the original image data, and then decoding it either in 
>PostScript itself, or just prior to sending to PostScript printer.  My problem
>is not the original image files, but the amount of sheer data being sent to the
>printer.  I want to be able to cut down on the number of bits I actually have
>to send down the pipe at 9600 baud.  I gather that there really is no way to
>do this, since no one else seemed concerned with the transmission time.

Please take another look at what I posted and sent to you.  The reason
I wrote the code was to improve transmission time at 2400 baud.  It
works.  The data is compressed at some point before transmission, and
is transmitted in compressed form.  It does not get uncompressed until
it arrives at the PostScript printer, safely past the serial link.

John Chew

-- 
john j. chew, iii  poslfit@utorgpu.bitnet
    trigraph, inc. poslfit@gpu.utcs.toronto.edu
  toronto, canada  {uunet!mnetor!utzoo,utgpu,utcsri}!trigraph!john
  [it is my opinion that these are solely my opinions.]