tobold.org

correct • elegant • free

△ comp.mail.* △

◅ MIME faq ftp site

an algorithm(s) for encoding/decoding a a file. ▻

Content Transfer Encoding source

In article <1993Oct6.173815.1@ntuvax.ntu.ac.sg>, Joon Daroy
<asdaroy@ntuvax.ntu.ac.sg> wrote:
>For the Content-Transfer-Encoding techniques of base64 and quoted-printable,
>i just wonder where can i get a full description (or code whatever) of
>these encoding techniques.

They are defined in the MIME (draft) standard: RFC 1521, sections 5.2
and 5.1 respectively.

>Im trying to build my own reader for MIME messages. Any help would
>be appreciated.

You *must* read at least RFCs 1521 and 1522.

Tim.
--
Tim Goodwin | "I suspect that this lack of specificity is either insane or
PIPEX Ltd   | brilliant, but I could be wrong...." - Nathaniel Borenstein.

Original headers:

From: tim@pipex.net (Tim Goodwin)
Newsgroups: comp.mail.mime
Subject: Re: Content Transfer Encoding source
Date: 11 Oct 1993 15:03:23 +0100
Organization: PIPEX Ltd, Cambridge, UK
Message-ID: <29bp3b$op4@tank.pipex.net>
References: <1993Oct6.173815.1@ntuvax.ntu.ac.sg>

△ comp.mail.* △

◅ MIME faq ftp site

an algorithm(s) for encoding/decoding a a file. ▻