From: "François Pinard" <pinard@iro.umontreal.ca>
Subject: Re: Unintended base64 encoding
Date: 09 Jul 1999 14:44:38 -0400 [thread overview]
Message-ID: <oqyagpoe7d.fsf@titan.progiciels-bpi.ca> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "09 Jul 1999 20:09:09 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Toby Speight <Toby.Speight@streapadair.freeserve.co.uk> writes:
> > 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*.
> Seems nice. I've now written the function, but what is the switchover
> point between qp and base64? Math genius wanted!
The most efficient encoding might require creating more subparts to a part.
All QP or all 64 might not be the best way to go. Once away from two
extremes, which is all QP or all 64, recognising that more even subparts
is only an half-hearted solution, why not rather consider optional full
compression with later 64 only?
Unless readability considerations matter and favour QP? (Yes, I know! :-)
--
François Pinard http://www.iro.umontreal.ca/~pinard
next prev parent reply other threads:[~1999-07-09 18:44 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
1999-07-09 18:09 ` Lars Magne Ingebrigtsen
1999-07-09 18:44 ` François Pinard [this message]
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=oqyagpoe7d.fsf@titan.progiciels-bpi.ca \
--to=pinard@iro.umontreal.ca \
/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).