From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] xterm 348-1
Date: Wed, 06 Nov 2019 14:11:00 -0000 [thread overview]
Message-ID: <420cec84-46a7-c55c-f723-dfd96d39d39b@SystematicSw.ab.ca> (raw)
In-Reply-To: <20191106211318.263462ceb47f01f6fd63c64e@nifty.ne.jp>
On 2019-11-06 05:13, Takashi Yano wrote:
>
>
> On Fri, 01 Nov 2019 10:36:06 +0900
> Katsumi Yamaoka wrote:
>> Hi,
>>
>> 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?
--
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
next prev parent reply other threads:[~2019-11-06 14:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 22:43 Yaakov Selkowitz
2019-11-01 1:36 ` Katsumi Yamaoka
2019-11-06 12:13 ` Takashi Yano
2019-11-06 14:11 ` Brian Inglis [this message]
2019-11-06 15:48 ` Takashi Yano
2019-11-06 17:24 ` Brian Inglis
2019-11-07 2:40 ` Takashi Yano
2019-11-07 8:31 ` Thomas Wolff
2019-11-07 10:16 ` Takashi Yano
2019-11-07 15:52 ` Brian Inglis
2019-11-07 15:50 ` Brian Inglis
2019-11-07 17:03 ` Brian Inglis
2019-11-08 4:19 ` Katsumi Yamaoka
2019-11-08 13:13 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=420cec84-46a7-c55c-f723-dfd96d39d39b@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).