From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Nic Ferrier Newsgroups: gmane.emacs.devel Subject: Re: base64 behavior is not MIME compliant Date: Wed, 06 Jul 2005 02:06:25 +0100 Message-ID: <87slysivzi.fsf@kanga.tapsellferrier.co.uk> References: <87wto4j44m.fsf@kanga.tapsellferrier.co.uk> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1120614070 9462 80.91.229.2 (6 Jul 2005 01:41:10 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 6 Jul 2005 01:41:10 +0000 (UTC) Cc: rms@gnu.org, bugs@gnus.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 06 03:41:08 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DpyuM-0004ai-Nn for ged-emacs-devel@m.gmane.org; Wed, 06 Jul 2005 03:41:03 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dpyve-00011M-Gk for ged-emacs-devel@m.gmane.org; Tue, 05 Jul 2005 21:42:22 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DpyrV-0006aa-18 for emacs-devel@gnu.org; Tue, 05 Jul 2005 21:38:05 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DpyrT-0006Zu-DQ for emacs-devel@gnu.org; Tue, 05 Jul 2005 21:38:04 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dpyls-0005FW-Py for emacs-devel@gnu.org; Tue, 05 Jul 2005 21:32:16 -0400 Original-Received: from [80.168.156.78] (helo=owls-tree.tapsellferrier.co.uk) by monty-python.gnu.org with esmtp (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.34) id 1DpyUy-0007Ux-LK; Tue, 05 Jul 2005 21:14:49 -0400 Original-Received: from [80.168.156.68] (helo=kanga) by owls-tree.tapsellferrier.co.uk with esmtp (Exim 4.50 #1 (Debian)) id 1DpyMU-0006lm-Mw; Wed, 06 Jul 2005 02:06:02 +0100 Original-Received: from nferrier by kanga with local (Exim 4.50) id 1DpyMs-0002P8-Mz; Wed, 06 Jul 2005 02:06:26 +0100 Original-To: Marc Horowitz In-Reply-To: (Marc Horowitz's message of "Tue, 05 Jul 2005 19:55:41 -0400") X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:40482 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:40482 Marc Horowitz writes: > Nic Ferrier 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