MIME-Version: 1.0
In-Reply-To: <4B1E56D1.2090501@hones.org.uk>
References: <4B1E4D22.9020406@hones.org.uk> 	 <416096c60912080520l49cbf64bwa4a2c4510b13a9f0@mail.gmail.com> 	 <4B1E56D1.2090501@hones.org.uk>
Date: Tue, 8 Dec 2009 21:05:11 +0000
Message-ID: <416096c60912081305k3d386207q5d6fb6cdc77c47a@mail.gmail.com>
Subject: Re: UTF-8 in Cygwin console on 1.7
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

2009/12/8 Cliff Hones:
> Perhaps setup.exe should offer to generate a shortcut (as well as .bat
> and .ico) with, say, the Lucida font selected?

Or just do so without asking? We've had a number of questions on this
already, and there are likely to be many more. People can always
choose the raster font in the properties if they prefer that.


> 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...).

I don't know what the story behind that is, but a (trivial) fix is
attached. It also changes the handling of SI (0xF) in the same way.

I also noticed that the code for handling CAN (0x18) under 'case ERR:'
is unreachable, because CAN is classified as 'NOR' in the base_chars
table. Perhaps a separate 'CAN' class would be appropriate here?

Andy

--
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