X-Recipient: archive-cygwin AT delorie DOT com 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:cc:from :message-id:date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=YtHJkTdyRQ6tZn8O LmGxHi4GuK0mSjz2Cucz6l70e+w5sT1M7k0Fzb8fbu7YN2zeMoaCJX+itlF96f3D lskpIWBxQzm8tudBUJHziejNSEBxKDkz2m37vq/BEgXA9YtQuBCbSJQKdBql9sHG kDiKuVA0hdOcl7UiOJ93p7uA4Og= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:reply-to:subject:to:references:cc:from :message-id:date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=caUkHT9t1Oy600XFZZye7M p/PJw=; b=bYSt+uWtEafH8J9JQShXeZx96/Ejx1DmRMaywV+9owJ32+1e5W1BdX YrTneI8kxejqHAGhaYGpjpyVeT8230gBcwmjZ94OEOq6H7z0TSPfEJZFAIzzk/sR gpzrK8zGBISSkmoAQ2HRbhMei6gvD6b67DylcBFVt8NG+DmODrBww= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,BODY_8BITS,GARBLED_BODY,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.1 spammy=fish, asian, japanese, Japanese X-HELO: smtp-out-so.shaw.ca Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Subject: Re: [ANNOUNCEMENT] xterm 348-1 To: cygwin AT cygwin DOT com References: <20191106211318 DOT 263462ceb47f01f6fd63c64e AT nifty DOT ne DOT jp> <420cec84-46a7-c55c-f723-dfd96d39d39b AT SystematicSw DOT ab DOT ca> <20191107004841 DOT 33764763bbb1ba364347c46c AT nifty DOT ne DOT jp> Cc: Takashi Yano From: Brian Inglis Openpgp: preference=signencrypt Message-ID: Date: Wed, 6 Nov 2019 10:24:29 -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: <20191107004841.33764763bbb1ba364347c46c@nifty.ne.jp> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Note-from-DJ: This may be spam On 2019-11-06 08:48, Takashi Yano wrote: > On Wed, 6 Nov 2019 07:11:14 -0700 Brian Inglis wrote: >> On 2019-11-06 05:13, Takashi Yano wrote: >>> On Fri, 01 Nov 2019 10:36:06 +0900 >>> Katsumi Yamaoka wrote: >>>> On Wed, 11 Sep 2019 18:24:37 -0400, Yaakov Selkowitz wrote: >>>>> The following packages have been uploaded to the Cygwin distribution: >>>>> * xterm-348-1 >>>> First of all, reverting it to XTerm(330) solved my problem. >>>> When copying non-ASCII text from another window to XTerm(348), it >>>> will be shown as a combination of ASCII and control characters, >>>> not the original human readable representation. >>>> I usually use Japanese text, これは日本語です for example. AFAICT, >>>> only the copy and paste is bad; `less' shows Japanese text and >>>> `ls' shows Japanese file names correctly. >>>> Is there a way to fix this problem? >>>> $ locale >>>> LANG=C >>>> LC_CTYPE="ja_JP.UTF-8" >>>> LC_NUMERIC="C" >>>> LC_TIME="C" >>>> LC_COLLATE="C" >>>> LC_MONETARY="C" >>>> LC_MESSAGES="C" >>>> LC_ALL= >>> I confirmed this occurs only if shell is tcsh. If shell is bash, zsh >>> or fish, pasting Japanese string works as expected. It works in cat, >>> od, etc as well. >>> The cause is unknown. >> Does it work properly if LANG="ja_JP.UTF-8" under tcsh? > No, it does not. Does tcsh input work properly under mintty instead of xterm? How does it work in cat, od, etc.? That can not include using input via tcsh? Presumably you are using IME(s) for Japanese input - which at what input layer(s)? 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. It sounds like an issue with either xterm or tcsh input locale handling, but both apparently handle locales well, so it may be a configuration issue caused by a recent change. It may be useful to read the FAQs (https://invisible-island.net/xterm/xterm.faq.html, https://www.tcsh.org/faq/), then open issues directly with xterm and/or tcsh upstream maintainers (https://invisible-island.net/personal/bug-reports.html, https://mailman.astron.com/mailman/listinfo/tcsh) to get more info. -- 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