Re: GIF/jpeg attached as quoted-printable in MIME?

["Johan Kullstam" <kullstam@ne.mediaone.net>]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Bjorn Halvor Solberg <bhso@pacbell.net> writes:
> 
> > The problem was really that software on the recipient side didn't know
> > what to do with the QP-encoded image, Gnus itself handled that just fine
> > as a recipient.
> 
> I'm thinking that perhaps it's a mistake to decide whether to QP or
> base64 things based on efficiency.

this is not the problem.  the choosing idea is perfectly fine.  the
implementation has let us down in the details.  the problem is/was a
buggy chooser function and a buggy quoted-printable encoder.

> Does all software know how to
> decode a QP-d picture?  I would kinda be surprised if that were the
> case... 

there's something wrong with the quoted-printable encoding for binary
files.  (this is how i discovered the buggy quoted-printable-or-base64
function.)  text with the odd weird char seem to work ok.  i think it
is something to do with very long text lines.  i think software knows
how to decode QP.  gnus/emacs just needs to fix its encoding.  

i have decoded quoted-printable (which gnus-0.96 emacs 20.4 sent) in
both emacs and netscape and get the same wrong answer (i.e., corrupt
file).  i suspect the encoder.  the corruption was a spurious bang
char (!) followed by a newline.

the qp-or-base64 choser function has been bogus in 0.9[56].  in 0.96
it would choose quoted-printable for all long attachments.  since the
chooser should now be fixed.  these kinds of image sent with
quoted-printable problems should go away.  however, this doesn't mean
we ought not fix quoted-printable in the first place.

-- 
J o h a n  K u l l s t a m
[kullstam@ne.mediaone.net]
Don't Fear the Penguin!