X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.9 required=5.0	tests=AWL,BAYES_50,SARE_SUB_ENC_UTF8,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArQDAOmlHU7QB6CdkWdsb2JhbABThEaTe44IcxQBAQEBFBIUJbs9kQSBK4QAMF8Eh1GQGBSLTg
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;	charset="UTF-8"
Subject: man UTF-8 rendering problem
Date: Wed, 13 Jul 2011 09:07:04 -0500
Message-ID: <2BF01EB27B56CC478AD6E5A0A28931F202DE9FEA@A1DAL1SWPES19MB.ams.acs-inc.net>
From: "Nellis, Kenneth" <Kenneth DOT Nellis AT acs-inc DOT com>
To: <cygwin AT cygwin DOT com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id p6DE7UEL029056

I wrote back in January about a UTF-8 rendering error with
"man size", but got no satisfaction.

http://cygwin.com/ml/cygwin/2011-01/msg00057.html

I encountered the same issue today with "man addr2line". 

Running mintty with the Lucinda Console font and configured
for the UTF-8 character set and LANG set to C.UTF-8, these 
two man commands render an undefined box symbol where a 
vertical bar would appear. It appears that man is
attempting to display U+23AA (CURLY BRACKET EXTENSION)
where it would display "|" (0x7C) were I configured
for ISO8859-1.

In a separate issue regarding hyphens and dashes, I recall 
that mintty added exception logic to work around an issue 
where Lucinda Console did not support the Unicode HYPHEN 
character as man presented, and so mintty instead rendered 
an Ascii HYPHEN-MINUS (0x2D) instead (or something like that...
I forget the details).

I wonder in this case whether mintty would be an appropriate 
place for a similar workaround.

Or what would the proper fix be? It seems CURLY BRACKET 
EXTENSION to be an odd choice for this character, but where 
is this choice being made?

--Ken Nellis