X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_SUB_ENC_UTF8
X-Spam-Check-By:	sourceware.org
Message-ID:	<4B1E56D1.2090501@hones.org.uk>
Date:	Tue, 08 Dec 2009 13:38:25 +0000
From:	Cliff Hones <cliff AT hones DOT org DOT uk>
User-Agent:	Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: UTF-8 in Cygwin console on 1.7
References:	<4B1E4D22 DOT 9020406 AT hones DOT org DOT uk> <416096c60912080520l49cbf64bwa4a2c4510b13a9f0 AT mail DOT gmail DOT com>
In-Reply-To:	<416096c60912080520l49cbf64bwa4a2c4510b13a9f0@mail.gmail.com>
X-Spam-Score:	-2.6 (--) (knockando.watchfront.net.uk)
X-Spam-Report:	knockando.watchfront.net.uk has scanned this email for spam. Results:- BAYES_00=-2.599 (total -2.6, current threshold 4.0)
X-IsSubscribed:	yes
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

Andy Koppe wrote:
> 2009/12/8 Cliff Hones:
>> Is UTF-8 character output fully supported in the standard Cygwin
>> console ($TERM=cygwin) under Cygwin 1.7?
> 
> Yes (except it's limited to the Basic Multilingual Plane). You need to
> select a Unicode-capable font in the console properties though.
> Basically, anything but the default "Raster Font".

Ah - yes, I should have thought to look at the console window font!  Lucida
and Consolas both display euro correctly.  However, font selection does not
affect the incorrect handling of NUL.

Perhaps setup.exe should offer to generate a shortcut (as well as .bat
and .ico) with, say, the Lucida font selected?

I have just checked Cygwin 1.5 and this aslo mishandles NUL, so I guess
it is a long-standing problem (or Microsoft oddity, or workaround for
something else...).  It is showing up as an error when I use telnet
in a cygwin console window - it seems telnet must run in binary mode
for UTF-8 to be passed successfully, but then telnet passes on the
NUL in the "\r NUL" sequence and you get a space at the start of each
line.  [This could be considered a telnet bug - but independent of
Cygwin NUL handling.]


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -