From: Simon Strandgaard <neoneye@...>
Date: 2004-05-20T07:19:16+09:00
Subject: Re: [bug] irb or xterm crash with UTF-8

Thomas Dickey <dickey@saltmine.radix.net> wrote:
> Simon Strandgaard <neoneye@adslhome.dk> wrote:
> > Carlos <angus@quovadis.com.ar> wrote:
> >> [Simon Strandgaard <neoneye@adslhome.dk>, 2004-05-19 13.45 CEST]
> >> > server> irb
> >> > irb(main):001:0> $KCODE='U'
> >> > => "U"
> >> > irb(main):002:0> str = [0x70, 0x80, 0x90].pack('U*')
> >> > => "p詑
> >> > 
> >> > Then it just hangs forever.. 
> >> 
> >> $ irb
> >> irb(main):001:0> $KCODE='U'
> >> => "U"
> >> irb(main):002:0> str = [0x70, 0x80, 0x90].pack('U*').unpack("C*")
> >> => [112, 194, 128, 194, 144]
> >> 
> >> I guess the last character is interpreted as a control character by your
> >> xterm. Reading the xterm changelog, version 175 (one more than to have) has
> >> an option to treat characters between 128 and 159 as printable and not
> >> control.
> 
> but the thread seems to indicate it wasn't setup properly for UTF-8 anyway.
> 

yes.. I only wanted Ruby to use UTF-8.. but not output UTF-8.
I have one time long time ago made an attempt to switch xterm + the applications I
use to UTF-8.. but that didn't went out successfully. Im using iso8859-1 now,
but I am now considering making an attempt again.


> > That makes sense. Thanks.
> 
> > BTW: any suggestion for a better alternative than xterm? 
> > hopefully with antialiased font rendering.. (but not qt)
> 
> xterm does that...

yes, Carlos mailed me in private about this. 
xterm -fa 'Luxi Mono'.


> 
> xterm supports ANSI color, VT220 emulation and UTF-8
> There's an faq at
> 	http://invisible-island.net/xterm/xterm.faq.html
> 	ftp://invisible-island.net/xterm/

Thanks, lots of useful info.  I wasn't aware that so many
other terminals are derived from xterm.


BTW: Thomas, its nice to see you hanging out in comp.lang.ruby :-)

-- 
Simon Strandgaard