From owner-freebsd-standards  Mon Feb 18 18:39:54 2002
Delivered-To: freebsd-standards@freebsd.org
Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87])
	by hub.freebsd.org (Postfix) with ESMTP id 1FDF937B47D
	for <freebsd-standards@FreeBSD.ORG>; Mon, 18 Feb 2002 18:39:01 -0800 (PST)
Received: from gateway.posi.net ([12.236.90.177]) by rwcrmhc54.attbi.com
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020219023900.RLTW1214.rwcrmhc54.attbi.com@gateway.posi.net>;
          Tue, 19 Feb 2002 02:39:00 +0000
Received: from localhost (kbyanc@localhost)
	by gateway.posi.net (8.11.6/8.11.6) with ESMTP id g1J2cwq67559;
	Mon, 18 Feb 2002 18:38:59 -0800 (PST)
	(envelope-from kbyanc@posi.net)
X-Authentication-Warning: gateway.posi.net: kbyanc owned process doing -bs
Date: Mon, 18 Feb 2002 18:38:58 -0800 (PST)
From: Kelly Yancey <kbyanc@posi.net>
To: Tim Robbins <tim@robbins.dropbear.id.au>
Cc: freebsd-standards@FreeBSD.ORG
Subject: Re: unexpand -t option
In-Reply-To: <20020218141415.A33138@descent.robbins.dropbear.id.au>
Message-ID: <20020218183522.D67464-100000@gateway.posi.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-standards@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-standards.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-standards>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-standards>
X-Loop: FreeBSD.ORG

On Mon, 18 Feb 2002, Tim Robbins wrote:

> This patch adds the -t option to unexpand, makes it use getopt instead of
> rolling its own option parser, and just generally cleans it up and simplifies
> it.
>
> Now that it no longer buffers output itself, it should be trivial to convert
> to support multibyte encoding: make `ch' in tabify() a rune_t, use
> fgetrune() and fputrune() instead of getchar()/putchar(). Should I make
> this change? (The standard suggests it should handle multibyte encodings
> when LC_CTYPE specifies one)
>
> Comments?
>

  I cannot comment on the patch, but please don't introduce BSD-specific rune
references.  David Cross and I are working on flushing out wide character
support which I would prefer to use as it is part of the C standard and the
Single Unix specification.  Thanks,

  Kelly
  kbyanc@{posi.net,FreeBSD.org}


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-standards" in the body of the message