[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#341686: solved



On Mon, Dec 05, 2005 at 11:21:30AM +0100, Jan Willem Stumpel wrote:
> Following your suggestion I did xrdb -q; the result was
...
> xterm*VT100*utf8:
> 
> Apart from the first line, this is what I put in my ~/.Xresources file 
> ages ago. Notice there is a line xterm*VT100*utf8. I had put this in 
> because I thought it was necessary (and maybe it used to be in the 
> past). Anyway it did not hurt with xterm 200.

It does look odd since it is a blank value.  I would have expected the
X library to ignore that line, but it probably just uses atoi() on the
resource value.
 
> But then I commented it out, installed xterm 204, and restarted X.
> And now lo and behold! xterm is 'hard-wired' to UTF-8 mode (with 
> right-clicking you cannot switch it off), and creating a new xterm with 
> xterm +u8 produces an xterm which displays Latin-1, and which can be 
> switched to UTF-8 manually. This is what Thomas Wolff wanted, I assume.

yes - that sounds like the behavior that I expect (thanks).

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Attachment: pgpxvTY_26wGJ.pgp
Description: PGP signature


Reply to: