You could also try the -en (encoding) option:
$ xterm -en UTF-8
Also, what are your locale settings?
xterm's command line options u8, wc, lc, en and its X resources utf8, locale, wideChars are interdependent in various ways, and some combinations depend on the locale settings (see the xterm man page for details), so it might well be that -u8 doesn't have the expected effect in your specific environment...
P.S. I can reproduce your problem with xterm v236 (SUSE 11.1 system) when I run it without any options. Virtually all other sensible combinations of the above mentioned options, however, either work fine (i.e. proper glyph is being displayed), or show the Latin-1 replacement 'x', but without aborting further output.
Interestingly, I cannot replicate your problem when I use xterm v235 (the debian lenny build) on my SUSE system (I currently don't have a debian system within reach). In some cases it says "Warning: couldn't find charset checkfont; using ISO 8859-1", in which case I get the 'x' replacement, but if I specify -en UTF-8 everything works fine.
BTW, see also luit.
In reply to Re: Printing the first letter of the Hebrew alphabet (U05D0) kills script?
by Eliya
in thread Printing the first letter of the Hebrew alphabet (U05D0) kills script?
by ELISHEVA
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |