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

[Andreas Tille <tillea@rki.de>]

On Tue, 20 Apr 2004, Thomas Dickey wrote:

> > ~> grep -i utf /etc/X11/Xresources/*
> > /etc/X11/Xresources/uxterm:UXTerm*utf8: on
>
> that would be ignored.
It is not:  uxterm works - at least on the local box if I ignore all other stuff.

> > /etc/X11/Xresources/xterm:XTerm*utf8: 2
>
> that might be used (depending on the script).  I don't use xrdb.
>
> The manpage isn't explicit (does not state the value is an integer).
> It quotes the default value, which shows its type:
>
>      utf8 (class Utf8)
>              This specifies whether xterm will run in UTF-8 mode.
>              If  you  set  this  resource,  xterm  also  sets the
>              wideChars resource as a side-effect.  When set via a
>              resource,  xterm  cannot  be  switched  via  control
>              sequences out of UTF-8 mode.  The default  is  ``0''
>              (off).  Any other value will turn on UTF-8 mode.
Because you seem to know it exactly: Could you please file a bug against
this man page?

> > 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.
>
> no - I stated
>
> "on" wouldn't work, since this resource happens to be an integer.
Sorry, for quoting you wrong: I ment uxterm is set wrong according to
your opinion, but it works.  (Just try it.)

> > 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.
>
> so far it sounds like a documentation issue.
Not really.  At least I do not have a working xterm since the last GDM
upgrade and if we do not find a solution for this (which should be documented,
sure) than it is more than a documentation issue.

Kind regards

         Andreas.