Re: [ANNOUNCEMENT] xterm 348-1

[Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>]

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