On Mon, Apr 19, 2004 at 09:25:54PM +0200, Andreas Tille wrote: > On Mon, 19 Apr 2004, Thomas Dickey wrote: > > > To do this, you have to limit it to the vt100 window: > > > > http://invisible-island.net/xterm/xterm.faq.html#tiny_menus > OK, then this is not really important to me ... > > But the real Problem remains: Even > > XTerm*utf8: 2 > > does not fix the missing Umlauts (just blanks) but xterm -ut8 works > fine. "-u8" (but your earlier email did state that). However. The command-line options of xterm simply set specific resource patterns and can be overridden by other resource patterns that are more specific. The "XTerm*utf8" pattern would not be overridden in a case where the other would (if there were already a "*utf8" pattern lurking in your resources). Perhaps that's what is happening: if your locale is not de_DE.UTF-8, then forcing UTF-8 output could cause the output of umlauts to be lost. (My impression is that the euro locales are 8-bit encodings, while UTF-8 is multibyte - and codes in the range 128-255 are interpreted differently). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
Attachment:
pgpK72_2dPSvb.pgp
Description: PGP signature