DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=h+wwsj9BM7Sh9ZOOn4lL+dEHaE1D0WQLoT20KQsqvCc
	Dx9T9yZiJIDn2Aoh2ltVYN3UIzAhJVq2NTWgcIjicjziahyHdXPmB7TW8M2JM8gF
	Bxyj7AQBjIGLWj4d5ckK//LmO2DQO2SdwGc8EByAqluKTw1VfVqG1Ds/rtsL2o8k
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <b5d35945-c41e-58b9-aa5f-b7f7eb7e241e@redhat.com>
References: <60db3460-a1c1-7cc2-0369-a7109d782ea0@redhat.com> <597b2988.4338ca0a.87fc4.4954@mx.google.com> <b5d35945-c41e-58b9-aa5f-b7f7eb7e241e@redhat.com>
From: Doug Henderson <djndnbvg@gmail.com>
Date: Fri, 28 Jul 2017 12:13:49 -0600
Message-ID: <CAJ1FpuMqd9_dKWNfvRn+B+V7W7cCKgkwoZOd9Q-3s1fX3Kc=eg@mail.gmail.com>
Subject: Re: [ANNOUNCEMENT] Updated: libreadline7-7.0.3-3
To: cygwin <cygwin@cygwin.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

On 28 July 2017 at 08:54, Eric Blake wrote:
> On 07/28/2017 07:09 AM, Steven Penny wrote:
>> On Fri, 28 Jul 2017 06:41:08, Eric Blake wrote:

>>    $ chcp.com 65001
>>    Active code page: 65001
>>
>>    $ ./cygwin.exe
>>    Ω
>>
>>    $ ./mingw32.exe
>>    Ω
>>

>>    $ chcp.com 437
>>    Active code page: 437
>>
>>    $ ./cygwin.exe
>>    Ω


IIRC, cygwin was changed some time ago (in the last year?) to always
emit unicode or UTF-8 to the console (i.e, it calls a different Win32
API function). Again, IIRC, it used to sometimes use one API call and
sometimes the other to write UTF-8 and unencoded bytes, depending on
something, perhaps the code page? I think it was written up in a
cygwin1.dll update announcement.

It looks like the mingw32 cross-compiler c runtime has not made that
change. That's the Microsoft supplied CRT, I believe.

In any case, this problem has nothing to do with libreadline of any
version, nor the current version of cygwin1.dll. It is possible that
this lies in the domain of mingw32, which suggests that it may be
off-topic here or at least needs a new subject line.

HTH
Doug


-- 
Doug Henderson, Calgary, Alberta, Canada - from gmail.com

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