i'm using following keyboard layout: Option "XkbLayout" "us,cz_qwerty" When using cz_qwerty the usual behaviour in all aplications (eg xterm) is that subsequent typing of two keys 'a results into the char
i'm using following keyboard layout: Option "XkbLayout" "us,cz_qwerty" When using cz_qwerty the usual behaviour in all aplications (eg xterm) is that subsequent typing of two keys 'a results into the char á. however Eterm outputs two chars 'a without any change. the situation is analogous with ˇ key. using Eterm 0.9.3-r4. Portage 2.0.53 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.5-r1, 2.6.15-suspend2 i686) ================================================================= System uname: 2.6.15-suspend2 i686 Intel(R) Pentium(R) M processor 1.86GHz Gentoo Base System version 1.6.14 dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -mcpu=i686 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://ftp.uni-erlangen.de/pub/mirrors/gentoo " LANG="cs_CZ" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X alsa apm arts audiofile avi berkdb bitmap-fonts bzip2 cdr crypt cups curl directfb eds emboss encode exif expat fam ffmpeg foomaticdb fortran gdbm gif glut gnome gpm gstreamer gtk gtk2 idn imagemagick imlib ipv6 jpeg kde lcms libg++ libwww mad mikmod mng motif mp3 mpeg ncurses nls ogg oggvorbis opengl oss pam pcre pdflib perl png python qt quicktime readline sdl spell ssl tcpd tetex tiff truetype truetype-fonts type1-fonts udev vorbis xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Created attachment 88875 [details, diff] patch for eterm-0.9.3-r4 (dead keys problem) i created small and bit nasty patch, which temporarily solves this problem for czech keyboard. however it seems, that eterm has somehow dead_keys functionality already implemented, because when i experimented with code in term.c it happened a couple of times, that dead keys suddenly started working corectly for some time during one run-time of eterm. unfortunately i was not able to determine how did it happen.
is this problem valid anymore with current versions of eterm? if there is no problem please close this bug
Created attachment 177551 [details] /opt/doublehp/usr/portage/x11-terms/eterm/eterm-0.9.5.ebuild This version is not in the tree any more. As reporter seems away, I suggest "CLOSE - TEST-REQUESTED" Any way, what's described in the first report is a locale related problem. Eterm only supports ISO. We would need a deeper description of the system; but if reporter dont feedback, we cant help at all. We would need, amongst otherthings, reporter to recompile eterm with -unicode, and, if still bugs, use provided ebuild. I also advise the reporter to connect IRC freenode, #E, and discuss this with Raster or Mekius or Kainx ...
