From owner-freebsd-current  Tue Mar 25 05:38:24 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA12329
          for current-outgoing; Tue, 25 Mar 1997 05:38:24 -0800 (PST)
Received: from silvia.HIP.Berkeley.EDU (ala-ca8-54.ix.netcom.com [207.93.141.182])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA12311;
          Tue, 25 Mar 1997 05:38:10 -0800 (PST)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id FAA00884; Tue, 25 Mar 1997 05:37:42 -0800 (PST)
Date: Tue, 25 Mar 1997 05:37:42 -0800 (PST)
Message-Id: <199703251337.FAA00884@silvia.HIP.Berkeley.EDU>
To: wosch@apfel.de
CC: wosch@freebsd.org, current@freebsd.org, mita@jp.FreeBSD.org
In-reply-to: <199703251154.MAA00909@campa.panke.de> (message from Wolfram Schneider on Tue, 25 Mar 1997 12:54:03 +0100)
Subject: Re: -current uudecode can't grok one of japanese/vfxdvi's distfiles
From: asami@vader.cs.berkeley.edu (Satoshi Asami)
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * >Is this check really necessary?  
 * 
 * Yes. All characters outside the range are garbage/bitrot and
 * you get undefined results. 

(see (1) below)

 * >This file used to decode fine with
 * >the old decoder.  Besides, I can't figure out for the life of myself
 * >which character it's barfing on.
 * 
 * It use spaces (ASCII 32) in body.

Aah, I see.  Am I stupid or what, I was converting everything to space 
to check! ;(

 * 				     Spaces are bad because
 * some mailers delete blank lines. Our uuencode never create
 * spaces. See 'The UNIX-HATERS Handbook', page 82-83

Ok, I agree that it's not a good idea for *uuencode* to use space (I've
heard about that too), but if files with spaces decode correctly, I
see no reason why we want to disable it in *uudecode*. ...(1)

 * I can add character 32 to the valid range for compatibility with old
 * uuencode programs.

Yes, please!

Satoshi