My locale-settings are set to de_DE@euro right. I recompiled mutt with the locales-fix, i.e. +LOCALES_HACK. But anyway, it seems that there is no way beeing able to type in my umlauts. When I press the o umlaut, a single v appears. Only mutt has this problem. Reproducible: Always Steps to Reproduce: 1. Start mutt 2. Send mail, so hotkey m 3. Type in any address 4. The appearing subjectline does not accept any umlauts. Actual Results: German umlauts can't be typed in. Expected Results: German umlauts should appear. As stated in http://sdb.suse.de/en/sdb/html/umlaute_gettext.html, I think, that the installed gettext-lib has a problem with the german umlauts
Where are you using mutt? On the console or in some X terminal?
I am using mutt 1.5.4 with the locale fix enabled. It does not matter, where (X, console) I want to type in umlauts. I think, that this is an gettext issue. The mc for example, does not accept umlauts, too. mc is displaying the same wrong characters as mutt does.
I'm not familiar with mutt, can you briefly explain how to apply the locales-fix?
I took the original mutt-1.5.4-r1.ebuild. I added in the econf-statement "--enable-locales-fix". This feature means --enable-locales-fix The result of isprint() is unreliable Have a look at http://archives.neohapsis.com/archives/openbsd/2000-12/0679.html So I decided to enable the locales fix.
So does it work without that locale fix for OpenBSD? I would think that Linux supports locales pretty well and isprint() would yield a reliable result.
No, it does not work correctly without --enables-locales-fix and with that param.
Ok. Please post emerge info output. Maybe I can reproduce this behaviour with your use flags.
Portage 2.0.48-r1 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r4) ================================================================= System uname: 2.4.19 i686 AMD Duron(tm) Processor GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /var/bind /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/local/portage" USE="x86 oss 3dnow apm avi crypt encode gif jpeg libg++ mad mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gtkhtml alsa gdbm berkdb slang readline arts tetex aalib nas bonobo svga ggi tcltk java guile mysql X sdl gpm libwww perl python esd imlib oggvorbis gnome qt kde motif opengl mozilla ldap cdr gtk -cups flash scanner directfb sasl tiff tcpd ssl pam acpi doc dvd evo fbcon gb gd imap innodb ipv6 jikes mbox pic samba socks5" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-O2 -mcpu=i686 -pipe" CXXFLAGS="" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
I can't reproduce this. Can you type umlauts at all in the terminal or console? In one comment you say, only mutt has this problem, in another one mc has it, too :). What about the address line in mutt? Also, what versions of ncurses and slang do you have installed?
slang: 1.4.5-r2 ncurses: 5.3-r1 gettext: 0.11.5-r1 Sorry, it was my fault. mc _and_ mutt has this problem. A plain textconsole accepts umlauts and all term-windows accept umlauts, too. The address line in mutt shows the same behaviour as the subject-line. mutt for example is _not_ linked against ncurses, mc of course. Perhaps it is more a slang problem? What do you think of the idea that I compile my mutt statically und mail you the binary?
I'd like to ask you to try slang-1.4.9 and see if that fixes it, if not I'd like to try your mutt binary. If that's possible for you I'd rather like to download it somewhere instead of having it sent to me by email. If that's not possible, you can send it by email.
Oh, I incredible sorry for any inconvenience, that I caused. I thought it it would be interesting, if the user root has the same problem. OK, I created a minimal .muttrc: set charset="iso-8859-1", Set export LANG=de_DE@euro and started mutt. Oh great, everything works fine. The addressline accepts umlauts, the subjectline accept umlauts. Marcus, thank your very much for your help. I'll post what was my fault. My proposal is to close this bug, 'cause my environment is broken.
No problem.
Now I found the problem. It is the configuration option "set meta_key". This option handles keystrokes differently, when bit 8 is set. But anyway, mc has this problem still yet. But it does not really matter.
