DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=WTT72BYp5vA1QiRH
	tOrIdd3WuXM/nxPtoleWPj8aK3ccdhuiAFVCzFwUbfZirKiikuNMCyaYKG5jrPFi
	euiib8OyWjO2QtqHBU10Xx32ya3Q7l6QPzNL3rEjwYxwdzAM0UY5ibG2ZzmtQwq3
	aIZnDrlATtsox3t64NXvVKMVLtc=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Reply-To: Brian.Inglis@SystematicSw.ab.ca
Subject: Re: [ANNOUNCEMENT] xterm 348-1
To: cygwin@cygwin.com
References: <announce.20190911182437.37466-1-yselkowitz@cygwin.com> <b4mtv7ogyyh.fsf@jpl.org> <20191106211318.263462ceb47f01f6fd63c64e@nifty.ne.jp> <420cec84-46a7-c55c-f723-dfd96d39d39b@SystematicSw.ab.ca> <20191107004841.33764763bbb1ba364347c46c@nifty.ne.jp> <e8821312-8750-48a1-e7f2-d7ce34f7d431@SystematicSw.ab.ca> <20191107113936.129b5b6f0c1879dbd5be7ed7@nifty.ne.jp>
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Openpgp: preference=signencrypt
Message-ID: <2e5a851b-43d7-bb5b-33b7-560215cf85c0@SystematicSw.ab.ca>
Date: Fri, 8 Nov 2019 06:13:24 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20191107113936.129b5b6f0c1879dbd5be7ed7@nifty.ne.jp>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 2019-11-06 19:39, Takashi Yano wrote:
> On Wed, 6 Nov 2019 10:24:29 -0700
> Brian Inglis wrote:
>> Does tcsh input work properly under mintty instead of xterm?
> 
> Yes, it works under mintty.
> 
>> How does it work in cat, od, etc.? That can not include using input via tcsh?
> 
> cat, od, etc. are works even if they are started from tcsh.
> 
>> Presumably you are using IME(s) for Japanese input - which at what input layer(s)?
> 
> I'm using Microsoft-made IME (MS-IME).
> 
>> I noticed that xterm was updated to Unicode 10 then 11, with changes to CJK/East
>> Asian character properties and handling; tcsh dropped libcatgets1 as a
>> dependency; those could affect input.
> 
> I confirmed the issue does not occur in the combination of:
> Debian/sid + xterm 349 + tcsh 6.21.00
> Debian/buster + xterm 344 + tcsh 6.20.00
> 
> Therefore, this may be a cygwin dedicated issue.
> 
> Wait. I have just found /etc/X11/app-defaults/XTerm has a entry
> *VT100*eightBitInput: false
> which is added from cygwin xterm 348-1.
> 
> Removing this line or changing the value to true solves this issue.
> 
> Katsumi, could you please check if this solves the issue?

Excellent catch! Great work!

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

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