Subject: | |
From: | |
Reply To: | |
Date: | Thu, 3 Jul 1997 15:40:46 +0100 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
You might be best off using UUENCODE format. This is recognised by most
PC mailers automatically and decoded, and is a 100% text format. (Used
by the binary newsgroups).
the format is
begin xxxx filename.xxx
<data lines>
end
in the message.
UUencoding has the advantage that it doesn't need any special headers.
hope that helps,
James
(listowner FRIENDS at Dartmouth)
--
______________________________________________________________________
James Chamier, Application Developer, IBM UK Ltd
[log in to unmask] - IBMMAIL(GBDSLJCH) - Tel 01932 745072
Any views or opinions are mine and do not represent those of IBM
>----------
>From: Nicolas.GRANER[SMTP:[log in to unmask]]
>Sent: 03 July 1997 15:19
>To: [log in to unmask]
>Subject: binaries in the filelist
>
>I would like to put some PC software on my list archive that can be
>useful to my subscribers. The problem is that it must be encoded as
>text. I already have some Macintosh software in BinHex format, but I'm
>not aware of a similar "standard" encoding in the PC world. My
>questions are:
>
>1) [not listserv related] is there a way to encode a binary file as
>text such that most or all PC users can decode it?
>
>2) if not, how can I PUT binary file in a way that listserv will
>process correctly?
>
>3) what instructions should I give to my subscribers to retrieve said
>file?
>
>I suppose using a base64 MIME attachment is not an option; even if I
>put a base64 file in the archive, when it is retrieved listserv will
>not add the required headers and separators that would enable a
>MIME-aware MUA to decode it. Is this correct?
>
>Nicolas
>
|
|
|