From: Nic Ferrier <nferrier@tapsellferrier.co.uk>
Cc: rms@gnu.org, bugs@gnus.org, emacs-devel@gnu.org
Subject: Re: base64 behavior is not MIME compliant
Date: Wed, 06 Jul 2005 02:06:25 +0100 [thread overview]
Message-ID: <87slysivzi.fsf@kanga.tapsellferrier.co.uk> (raw)
In-Reply-To: <t53wto4byf6.fsf@central-air-conditioning.toybox.cambridge.ma.us> (Marc Horowitz's message of "Tue, 05 Jul 2005 19:55:41 -0400")
Marc Horowitz <marc@mit.edu> writes:
> Nic Ferrier <nferrier@tapsellferrier.co.uk> writes:
>
>>> Why can't you just pre-parse the data parsed to the base64 decoder? I
>>> believe that's the correct behaviour. A base64 decoder should decode
>>> base64, not "base64 but also it does this extra trick if you wave your
>>> hand in the air"
>
> You could do that, but then the pre-parser needs to know what base64
> character sets looks like, so it's not a very clean abstraction.
I disagree. Base64 is a well documented and understood
encoding. Particularly the acceptable characters.
A function base64-clean or clean-for-base64 would be better than
changing the base64 decoder to accept unstandard characters.
> decoder already knows everything it needs to know. It's also likely
> that other apps which want to do base64 decoding will want this same
> functionality, so repeating it makes little sense.
>
> But in the end, I don't care strongly if the code is in emacs or in
> gnus, as long as it's somewhere.
Can you go over again where you had the problem? Was it a particular
message from some particular MTA? Or was it something more general?
Nic
next prev parent reply other threads:[~2005-07-06 1:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <t53zmt4dce3.fsf@central-air-conditioning.toybox.cambridge.ma.us>
2005-07-03 20:43 ` base64 behavior is not MIME compliant Richard M. Stallman
2005-07-03 21:09 ` Nic Ferrier
2005-07-04 4:59 ` Marc Horowitz
2005-07-05 4:35 ` Richard M. Stallman
2005-07-05 21:35 ` Marc Horowitz
2005-07-05 22:10 ` Nic Ferrier
2005-07-05 23:55 ` Marc Horowitz
2005-07-06 1:06 ` Nic Ferrier [this message]
2005-07-06 1:15 ` Ken Raeburn
2005-07-06 1:48 ` Nic Ferrier
2005-07-05 22:52 ` Arne Jørgensen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87slysivzi.fsf@kanga.tapsellferrier.co.uk \
--to=nferrier@tapsellferrier.co.uk \
--cc=bugs@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).