Article View: comp.compression
Article #4035Re: Postscript level i compress for bitmaps
From: parker@shape.mps
Date: Wed, 16 Sep 1992 11:17
Date: Wed, 16 Sep 1992 11:17
48 lines
1375 bytes
1375 bytes
In article <geoffw.716076323@extro.ucc.su.OZ.AU> geoffw@extro.ucc.su.OZ.AU (Geoffrey Warren Hicks) writes: > >Posted on behalf of Craig Southeren who does not have access to >a net account: >------------------------------------------------------------------- > >On the subject of bitmap compression, I've got a small lex >program which will take an "standard" standalone Postscript >program and produce another Postcript program which produces >the same bit image. It also uses run length encoding. Being >written in "C", it runs fast (no exact timings, but basically >insignificant for files up several 100k on a Sparc 2). We >were getting compression ratios of up to 20:1. > >If anyone is interested, I'll dig it up or rewrite it when >I get to my new job next week. > >Be careful with compression systems implemented in Postcript. >By introducing a compression algorithm, you are swapping >communications times for decoding time. If you already have >a real fast communications port into your printer (say, parallel) >then compression won't get you a lot. If you have a slow >comms linke (we were using 38400 baud serial) it *IS* worth >doing for big files. > >Of course, you always save in disk storage terms. > >My $0.02 worth > > Craig OH SURE!!! Now tell me. Were were you a few months ago when I posted my orginal request? Of course I'm interested.
Message-ID:
<197j5dINNrin@shape.mps.ohio-state.edu>
Path:
rocksolid-us.pugleaf.net!archive.newsdeef.eu!mbox2nntp-comp.compression.mbox.zip!sparky!uunet!gumby!wupost!zaphod.mps.ohio-state.edu!not-for-mail
References:
<18j3vcINN8vu@shape.mps.ohio-state.edu> <geoffw.716076323@extro.ucc.su.OZ.AU>