After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 85986 - gnome-terminal doesn't handle 8-bit international characters
gnome-terminal doesn't handle 8-bit international characters
Status: RESOLVED DUPLICATE of bug 78007
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Havoc Pennington
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-06-19 22:15 UTC by dmoisset
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description dmoisset 2002-06-19 22:16:34 UTC
Package: gnome-terminal
Severity: normal
Version: 2.0.0
Synopsis: gnome-terminal doesn't handle 8-bit international characters
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general

Description:
Description of Problem:

When I type international characters on gnome-terminal, the key is
translated to some 7 bit character. My keyboard has keys for dead_acute,
ntilde, questiondown, etc. for writing spanish (but I use a C locale).
deadkeys are not dead (dead_acute writes a '4'), ntilde is converted to
'q'; questiondown and exclamdown are converted to '?' and '!' , and
compose is ignored.

Those keys still work on gnome-terminal 1.4.0.8, and in others gtk and
gtk2 applications. xev shows that they're sending the correct keysyms,
so it looks like a gnome-terminal (or zvt2? I don't know which one does
the keyboard handling) bug.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-06-19 18:16 -------

The original reporter (dmoisset@grulic.org.ar) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, hp@redhat.com.

Comment 1 Luis Villa 2002-06-26 03:10:54 UTC

*** This bug has been marked as a duplicate of 78007 ***