From: Toby Speight <Toby.Speight@streapadair.freeserve.co.uk>
Subject: Re: Unintended base64 encoding
Date: 09 Jul 1999 12:55:51 +0100 [thread overview]
Message-ID: <u1zeijauw.fsf@lanber.cam.citrix.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "Sat, 03 Jul 1999 09:22:12 GMT"
Lars> Lars Magne Ingebrigtsen <URL:mailto:larsi@gnus.org>
0> In <URL:news:m3908yrt15.fsf@quimbies.gnus.org>, Lars wrote:
Lars> Toby Speight <Toby.Speight@digitivity.com> writes:
>> Why does it do that, rather than inspecting the content to decide
>> the appropriate encoding?
Lars> What is the appropriate encoding? base64 is always appropriate.
Some time back (a couple of years, I think), I wrote code for TM which
inspected the message to determine the most space-efficient encoding
(if 8bit/binary weren't possible). So bodyparts containing mostly
US-ASCII printable characters got q-p encoding, and others got base64,
*irrespective of content-type*. AIUI, pgnus uses content-type or
disposition as the primary heuristic.
[For large parts, it may be a useful optimisation to only scan perhaps
the first 1K and the last 1K and assume they are representative of the
whole.]
next prev parent reply other threads:[~1999-07-09 11:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-11 18:36 X-face display patch Hrvoje Niksic
1999-06-11 18:40 ` Karl Kleinpaste
1999-06-11 18:46 ` Unintended base64 encoding Karl Kleinpaste
1999-06-13 1:17 ` Lars Magne Ingebrigtsen
1999-06-13 2:38 ` Karl Kleinpaste
1999-06-15 11:41 ` Toby Speight
1999-07-03 9:17 ` Lars Magne Ingebrigtsen
1999-07-09 11:55 ` Toby Speight [this message]
1999-07-09 18:09 ` Lars Magne Ingebrigtsen
1999-07-09 18:44 ` François Pinard
1999-07-09 19:18 ` Lars Magne Ingebrigtsen
1999-07-09 19:43 ` Aaron M. Ucko
1999-07-09 20:01 ` François Pinard
[not found] ` <udl4sjdbodp.fsf@tux.mit.edu>
1999-07-09 20:00 ` 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=u1zeijauw.fsf@lanber.cam.citrix.com \
--to=toby.speight@streapadair.freeserve.co.uk \
/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).