From rja7m@phil.cs.virginia.edu Thu Jun 13 17:13:49 1991
Received: from [128.143.2.7] by dkuug.dk via EUnet with SMTP (5.64+/8+bit/IDA-1.2.8)
	id AA25918; Thu, 13 Jun 91 17:13:49 +0200
Received: from uvacs.cs.Virginia.EDU by uvaarpa.Virginia.EDU id aa21323;
          13 Jun 91 11:13 EDT
Received: from phil.cs.Virginia.EDU by uvacs.cs.Virginia.EDU (4.1/5.1.UVA)
	id AA08751; Thu, 13 Jun 91 11:12:57 EDT
Posted-Date: Thu, 13 Jun 91 11:13:05 EDT
Return-Path: <rja7m@phil.cs.Virginia.EDU>
Received: by phil.cs.Virginia.EDU (4.1/SMI-2.0)
	id AA13448; Thu, 13 Jun 91 11:13:05 EDT
Date: Thu, 13 Jun 91 11:13:05 EDT
From: rja7m@phil.cs.Virginia.EDU
Message-Id: <9106131513.AA13448@phil.cs.Virginia.EDU>
In-Reply-To: Walt Daniels <dan@watson.ibm.com>
       "(i18n 97) Re: data announcement" (Jun 13,  9:14am)
X-Mailer: Mail User's Shell (7.2.0 10/31/90)
To: Walt Daniels <dan@watson.ibm.com>, iso10646@jhuvm,
        ietf-822@dimacs.rutgers.edu, unicode@sun.com
Subject: Re: (i18n 97) Re: data announcement
Cc: i18n@dkuug.dk
X-Charset: ASCII
X-Char-Esc: 29

On Jun 13,  9:14am, Walt Daniels wrote:
Subject: (i18n 97) Re: data announcement

% It is high time that Unix took one more step into the 20th century
% before the 21st arrives.  The fiction that all files are just byte
% streams is just that, fiction.  The user just has to know what files
% are binary and what files are text (line oriented) files.  Just try
% the split command on an arbitrary file.  If you are lucky it will find
% NLs sufficiently often to not abend due to overflowing a static
% buffer.
% 
% Just because this is a hard migration step for Unix does not mean that
% we should not spec it out and start pushing for its inclusion in the
% next POSIX release.
End of excerpt from Walt Daniels

  It would be highly inappropriate for this change proposal to be put
through POSIX because POSIX is chartered to standardise "existing
practice in historical UN*X systems" -- not CHANGE existing practice.

  It might or might not be a good idea, but POSIX is the *wrong* venue
to discuss it -- for that matter it isn't clear to me how any of this
relates to either ISO 10646 or UNICODE or SMTP Mail.  
Further discussion probably belongs elsewhere.

Randall Atkinson
randall@Virginia.EDU



