TIP: Click on subject to list as thread! ANSI
echo: 80xxx
to: SYLVAIN LAUZON
from: TOM TORFS
date: 1997-06-07 10:08:00
subject: huffman

* Reply to a message in personal_mail.
Sylvain Lauzon wrote in a message to Tom Torfs:
 SL> would you send me the C code for uuencode sheme please. or the
 SL> specification 
C code would be off-topic here; there's some asm code in the 1993 80XXX 
snippets.
I don't really have the specs either, but's here's what I know about the 
format:
The first line is always:
begin  
The attributes are usually 644. They stand for the file's privilege
rights, and are usually only of any importance on Unix systems.
Each encoded line begins with the line length (+32 to make it printable,
usually 'M' for the regular 64-char lines).
For the rest, the uuencoder reads 3 bytes (24 bits) and writes them out as
4 bytes, each containing 6 bits and with 32 added to them to make them
printable.
The last input bytes are padded with 0's if necessary to make it 3 input
bytes. In most modern uuencoders, output spaces (ASCII 32, 20H) are
converted to the '`' character.
The encoded data ends with the single line "end". More complicated encoders
might add checksums or CRC values at the end, or they might add the ability
to break up the output file into pages or separate x-byte long files, etc.
greetz,
Tom
tomtorfs@mail.dma.be
--- timEd/2 1.10+
---------------
* Origin: 80X86 BBS 32-15-24.62.32 V.34/V.FC (24h/24h) (2:292/516)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.