Article View: comp.lang.postscript
Article #7136Re: Run-length encoding for image data?
From: Ray Lubinsky
Date: Sat, 07 May 1988 03:37
Date: Sat, 07 May 1988 03:37
21 lines
1275 bytes
1275 bytes
In article <9440@sol.ARPA>, ken@cs.rochester.edu (Ken Yap) writes: > Have you tried byte level run-length encoding, i.e. > > 00 00 00 00 00 13 13 13 13 24 > > is encoded as > > 5 * 00, 4 * 13, 24 Yes (I'm sorry I didn't state that earlier -- I did the work last year and forgot to list all the things I tried). The lynch-pin in the whole process is the high cost of interpretively handling either character-at-a-time input (via read) or translating a string input via readhexstring/readstring into pixel data. -- | Ray Lubinsky, UUCP: ...!uunet!virginia!uvacs!rwl | | Department of BITNET: rwl8y@virginia | | Computer Science, CSNET: rwl@cs.virginia.edu -OR- | | University of Virginia rwl%uvacs@uvaarpa.virginia.edu |
Technical Details
Message-ID:
<2391@uvacs.CS.VIRGINIA.EDU>Path:
arc1-ca.pugleaf.net!utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ukma!uflorida!umd5!uvaarpa!virginia!uvacs!rwlReferences:
<2387@uvacs.CS.VIRGINIA.EDU> <9440@sol.ARPA>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ukma!uflorida!umd5!uvaarpa!virginia!uvacs!rwl From: rwl@uvacs.CS.VIRGINIA.EDU (Ray Lubinsky) Newsgroups: comp.lang.postscript Subject: Re: Run-length encoding for image data? Message-ID: <2391@uvacs.CS.VIRGINIA.EDU> Date: 7 May 88 03:37:24 GMT References: <2387@uvacs.CS.VIRGINIA.EDU> <9440@sol.ARPA> Organization: U.Va. CS in Charlottesville VA Lines: 21