Ken Krugler wrote in message <[EMAIL PROTECTED]>... > >At 12:00am -0800 00-12-02, Palm Developer Forum digest wrote: >>Subject: Re: RLE compression >>From: "Richard M. Hartman" <[EMAIL PROTECTED]> >>Date: Fri, 1 Dec 2000 16:55:25 -0800 >>X-Message-Number: 73 >> >> >> >>Denis Faivre wrote in message <[EMAIL PROTECTED]>... >>... >> >I had seen your post and definition of RLE : "The RLE compression is a >> >simple sequence of <repeat count><byte of data>, where the repeat count >>byte >> >will be 1...255." >> > >> >However I wondered if Palm somehow confirmed that PalmOS implementation >> >follows this definition. >> > >> >>So for non-repeating byte sequences you double them in length, e.g. >>sequence: 0x01 0x02 0x03 0x04 >>result: 0x01 0x01 0x01 0x02 0x01 0x03 0x01 0x04 >>?? >> >>Most RLE schemes I am familiar with have a code that says "the next >>N bytes are to be read as-is", frequently the high-bit. Thererefore the >>result for my example could be: 0x84 0x01 0x02 0x03 0x04 >> >> Now ... which way does Palm do it? > >RLE doesn't have any special support for encoding non-repeating bytes >more efficiently (though it should).
So in the Palm scheme, every single non-repeating byte is preceeded by an additional repeat count byte of 0x01 ?? That could seriously increase the size of things! -- -Richard M. Hartman [EMAIL PROTECTED] 186,000 mi/sec: not just a good idea, it's the LAW! -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
