Bug#179407: xterm: not only bold fonts do not work with widechars

[Andreas Tille <tillea@rki.de>]

On Mon, 19 Apr 2004, Thomas Dickey wrote:
> > 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).
Sure - this was a typo.

> 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).

~> grep -i utf /etc/X11/Xresources/*
/etc/X11/Xresources/uxterm:UXTerm*utf8: on
/etc/X11/Xresources/xterm:XTerm*utf8: 2

I did not changed this uxterm but I regard this uxterm as a really
bad missconception.  For instance if you log in anywhere you have
to define a new TERM variable and whatever.  Moreover, regarding to
your mail before it is set to 'on' instead to an integer.  What's
wrong here.

> 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).
When I had no characters at the places of Umlauts I was using

    LANG=de_DE@euro
    LC_ALL=de_DE@euro

I now switched to

    LANG=de_DE.UTF-8@euro
    LC_ALL=de_DE.UTF-8@euro

The result is different but not better: �€ instead of À (a-Umlaut),
etc - just two charcters.

Note: All this happens with plain resource settings (see above).  An
       xterm -u8
works fine.

If you ask me I would like to change the severity of this bug to important,
because ist really smells like a missinterpretation of resources settings.

Kind regards

           Andreas.