From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: GIF/jpeg attached as quoted-printable in MIME?
Date: 25 Sep 1999 12:23:04 +0200 [thread overview]
Message-ID: <vaf670z2stz.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "25 Sep 1999 10:40:37 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> I'm thinking that perhaps it's a mistake to decide whether to QP or
> base64 things based on efficiency. Does all software know how to
> decode a QP-d picture? I would kinda be surprised if that were the
> case...
Maybe all attachments should be base64 encoded whereas you do the
normal (efficiency) check for inline parts. Would that be a suitable
heuristic?
kai
--
I like BOTH kinds of music.
next prev parent reply other threads:[~1999-09-25 10:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-08 21:24 Bjorn Halvor Solberg
1999-09-09 0:14 ` Bjorn Halvor Solberg
1999-09-25 8:40 ` Lars Magne Ingebrigtsen
1999-09-25 10:23 ` Kai Großjohann [this message]
1999-09-25 10:38 ` Lars Magne Ingebrigtsen
1999-09-26 21:46 ` Johan Kullstam
1999-09-27 14:03 ` Toby Speight
1999-09-27 17:59 ` Lars Magne Ingebrigtsen
1999-09-27 18:26 ` Toby Speight
1999-09-27 18:43 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vaf670z2stz.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).