Compose key and xterm vs. UTF-8

[Parv]

Nothing of susbtance here ...

in message <20100314114524.GB25702 at slackbox.erewhon.net>,
wrote Roland Smith thusly...
>
> On Sun, Mar 14, 2010 at 12:16:45AM +0000, Christian Weisgerber wrote:
> > Short:
> > ------
> > Why do compose key sequences fail to work in a UTF-8 xterm?
> 
> The port x11/rxvt-unicode is lighter on resources then xterm, and
> works fine with utf-8. (with LANG=en_US.UTF-8 and
> LC_ALL=en_US.UTF-8 set)

I tried to open a genunine xterm window but a kterm-like window was
opened.  Tried it again; got another non-xterm window.  The
experience was rather annoying.  After waking up I realized what had
happened, and life went on as it was before.


  - parv

--