From owner-freebsd-standards@FreeBSD.ORG Wed May 6 16:08:31 2009 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BBA1106567A for ; Wed, 6 May 2009 16:08:31 +0000 (UTC) (envelope-from wollman@khavrinen.csail.mit.edu) Received: from khavrinen.csail.mit.edu (khavrinen.csail.mit.edu [128.30.28.20]) by mx1.freebsd.org (Postfix) with ESMTP id DB21D8FC16 for ; Wed, 6 May 2009 16:08:30 +0000 (UTC) (envelope-from wollman@khavrinen.csail.mit.edu) Received: from khavrinen.csail.mit.edu (localhost [127.0.0.1]) by khavrinen.csail.mit.edu (8.14.3/8.14.3) with ESMTP id n46Fa943096394 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL CN=khavrinen.csail.mit.edu issuer=Client+20CA); Wed, 6 May 2009 11:36:10 -0400 (EDT) (envelope-from wollman@khavrinen.csail.mit.edu) Received: (from wollman@localhost) by khavrinen.csail.mit.edu (8.14.3/8.14.3/Submit) id n46Fa9Xg096391; Wed, 6 May 2009 11:36:09 -0400 (EDT) (envelope-from wollman) From: Garrett Wollman MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18945.44648.875780.605560@khavrinen.csail.mit.edu> Date: Wed, 6 May 2009 11:36:08 -0400 To: freebsd-standards@freebsd.org, juli@clockworksquid.com In-Reply-To: <200905060831.n468VcRE018431@lurza.secnetix.de> References: <200905060831.n468VcRE018431@lurza.secnetix.de> X-Mailer: VM 7.17 under 21.4 (patch 22) "Instant Classic" XEmacs Lucid X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (khavrinen.csail.mit.edu [127.0.0.1]); Wed, 06 May 2009 11:36:10 -0400 (EDT) Cc: Subject: Re: Shouldn't cat(1) use the C locale? X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 16:08:31 -0000 < said: > I think this is a bug in the manual page. When cat(1) is > using the current locale, that's perfectly correct behaviour > in a world that is clearly moving away from ASCII, towards > unicode. Maybe your part of the world.... > So I think the manual page should be fixed so it says that > the -v option handles non-printing characters in the current > locale, and cat needs to be fixed to handle multibyte chars > correctly if the -v option is used with a UTF locale. This is a Bad Idea. cat -v ought to work properly when the input does not consist of "characters" at all. -GAWollman