Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Unintended base64 encoding
Date: 09 Jul 1999 22:00:43 +0200	[thread overview]
Message-ID: <m3d7y1ioes.fsf@quimbies.gnus.org> (raw)
In-Reply-To: amu@MIT.EDU's message of "09 Jul 1999 15:43:14 -0400"

amu@MIT.EDU (Aaron M. Ucko) 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.

Okidoke; I've now made 0.1666 the limit.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen


      parent reply	other threads:[~1999-07-09 20:00 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
1999-07-09 20:01                 ` François Pinard
     [not found]               ` <udl4sjdbodp.fsf@tux.mit.edu>
1999-07-09 20:00                 ` Lars Magne Ingebrigtsen [this message]

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=m3d7y1ioes.fsf@quimbies.gnus.org \
    --to=larsi@ifi.uio.no \
    /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).