MIME-Version: 1.0
In-Reply-To: <4B1F8BA3.3070302@towo.net>
References: <4B1E4D22.9020406@hones.org.uk> 	 <416096c60912080520l49cbf64bwa4a2c4510b13a9f0@mail.gmail.com> 	 <4B1E56D1.2090501@hones.org.uk> 	 <416096c60912081305k3d386207q5d6fb6cdc77c47a@mail.gmail.com> 	 <4B1F29F0.7020701@hones.org.uk> 	 <416096c60912082136x316686b3gab4275c9ac5736de@mail.gmail.com> 	 <4B1F8BA3.3070302@towo.net>
Date: Wed, 9 Dec 2009 11:48:35 +0000
Message-ID: <416096c60912090348u4a2180e6w4d613346cbbf92bd@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/9 Thomas Wolff:
> So the #define IGN should go as well...

Yep.

> Actually, I don't really understand this code part:
> * What is the purpose of the lookup table for the switch rather than just
> switching on a few special control characters?

Good question.

> * What is the idea of (randomly?) assigning ERR to some control characters
> and NOR to others?

I wondered about that too.

> * How does the case NOR *work* actually?

Due to the code around line 1530 for dealing with multibyte chars.
Further deepens the mystery regarding the ERR/NOR distinction though.
Do only certain control chars (if any) appear in doublebyte encodings?

> Maybe after clarifying this, the whole snipplet should be cleaned up a
> little bit.

Sounds like a good addition to your console patch.

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