Re: questions on QP, non-text attachments and munpack

Jamie Zawinski <jwz@netscape.com> Fri, 09 February 1996 22:57 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa29271; 9 Feb 96 17:57 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa29267; 9 Feb 96 17:57 EST
Received: from list.cren.net by CNRI.Reston.VA.US id aa16036; 9 Feb 96 17:57 EST
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id RAA11261; Fri, 9 Feb 1996 17:33:58 -0500
Received: from urchin.netscape.com (unknown.netscape.com [198.95.250.59]) by list.cren.net (8.6.12/8.6.12) with ESMTP id RAA11227 for <ietf-822@list.cren.net>; Fri, 9 Feb 1996 17:32:24 -0500
Received: from gruntle (gruntle.mcom.com [205.217.230.10]) by urchin.netscape.com (8.6.12/8.6.9) with SMTP id OAA04701; Fri, 9 Feb 1996 14:29:26 -0800
Message-Id: <311BCAC4.20C98375@netscape.com>
Date: Fri, 09 Feb 1996 14:29:24 -0800
X-Orig-Sender: owner-ietf-822@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Jamie Zawinski <jwz@netscape.com>
To: "hansen@pegasus.att.com" <hansen@pegasus.attmail.com>
Cc: Ned Freed <ietf-822@list.cren.net>
Subject: Re: questions on QP, non-text attachments and munpack
References: <pegasus0402205380>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Sender: jwz@netscape.com
X-Mailer: Mozilla 2.1a0 (X11; U; Linux 1.2.13 i586)
X-Listprocessor-Version: 8.0(beta) -- ListProcessor by CREN

hansen@pegasus.att.com wrote:
> 
> From your statements above, you believe that munpack is incorrect.

If you're referring to me, that's not what I meant -- I thought that
munpack was doing the right thing, but that whoever had encoded binary
data in QP needed to use Base64 instead.

But now I agree with Ned -- you can use QP for binary data, but you just
need to be careful to make CR, LF, and CRLF explicit, and not to use
hard breaks (CRLF not preceeded by "=") since that's the part that has
"textual" semantics, and a decoder is allowed to translate those to the
local linebreak convention.

It still sounds, though, like the program that is encoding binary data
in QP is doing something wrong -- it's probably using hard breaks.

-- 
Jamie Zawinski    jwz@netscape.com   http://www.netscape.com/people/jwz/
``A signature isn't a return address, it is the ASCII equivalent of a
  black velvet clown painting; it's a rectangle of carets surrounding
  a quote from a literary giant of weeniedom like Heinlein or Dr. Who.''
                                                         -- Chris Maeda