From: amu@MIT.EDU (Aaron M. Ucko)
Cc: ding@gnus.org
Subject: Re: Unintended base64 encoding
Date: 09 Jul 1999 15:43:27 -0400 [thread overview]
Message-ID: <udl1zehbodc.fsf@tux.mit.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "09 Jul 1999 14:04:33 -0400"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Seems nice. I've now written the function, but what is the switchover
> point between qp and base64? Math genius wanted!
*raises hand* Ooh, ooh, call on me!
QP adds an overhead of roughly 2 characters per non-ASCII character.
("Roughly" because the line-wrapping stuff makes that number slightly
off.) On the other hand, base64 always adds an overhead of 1/3
character per character. The breakeven point occurs when these
overheads are equal; i.e., when about 1/6 of the characters are non-ASCII.
--
Aaron M. Ucko, KB1CJC <amu@mit.edu> (finger amu@monk.mit.edu)
next prev parent reply other threads:[~1999-07-09 19:43 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
1999-07-09 19:18 ` Lars Magne Ingebrigtsen
1999-07-09 19:43 ` Aaron M. Ucko [this message]
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=udl1zehbodc.fsf@tux.mit.edu \
--to=amu@mit.edu \
--cc=ding@gnus.org \
/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).