Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site kovacs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!mtuxo!mtunh!mtung!mtunf!ariel!vax135!cornell!uw-beaver!tektronix!hplabs!sdcrdcf!randvax!kovacs!rivero
From: rivero@kovacs.UUCP (Michael Foster Rivero)
Newsgroups: net.graphics
Subject: Re: run length encoding
Message-ID: <249@kovacs.UUCP>
Date: Wed, 10-Jul-85 14:39:50 EDT
Article-I.D.: kovacs.249
Posted: Wed Jul 10 14:39:50 1985
Date-Received: Wed, 17-Jul-85 07:21:18 EDT
References: <964@sdcsvax.UUCP>
Reply-To: rivero@kovacs.UUCP (Michael Foster Rivero)
Organization: Robt Abel & Assoc, Hollywood
Lines: 26
Summary: 

In article <964@sdcsvax.UUCP> brian@sdcsvax.UUCP (Brian Kantor) writes:
>I was recently given some image files that have a filename ending in ``.rle''.
>They appear to be encoded in some dense way.
>
>What is the format of this encoding?  I assume it is some sort of
>run-length-encoding, about which I would like to learn more, so some
>pointers to references on RLE would also be appreciated.
>
>	Brian Kantor	UC San Diego Computer Graphics Lab
>
>	decvax\ 	brian@ucsd.arpa
>	akgua  >---  sdcsvax  --- brian
>	ucbvax/		Kantor@Nosc 



	Run length encoding uses two  bytes  to  store  long  runs  of
	identical  pixels.  The  idea  is  "plot BYTE1 pixels of BYTE2
	color".  For very graphic images with  lots  of  white  space,
	black space, or large areas of the same color, the compression
	results in a lot of saved file space.  But, since there is  no
	standard  RLE  format,  the  best place to find out about your
	file is with the original programmer / system.


					Michael Rivero