When I try to write a cyrillic email in koi8-r encoding mutt always recodes it to utf-8. I have the following settings: set allow_8bit set charset="koi8-r" set send_charset="us-ascii:iso-8859-1:koi8-r:utf8" When I finish editing my message and exit vim, mutt shows the following line in the Attaches section: -> - I 1 /tmp/mutt-laptop-1000-21749-0 [text/plain, 8bit, koi8-r, 0,1K] looks correct. But in fact the file is in utf-8 encoding, I can restore it with iconf -f utf8 -t koi8r /tmp/mutt-laptop-1000-21749-0 Reproducible: Always Steps to Reproduce: 1. set send_charset to "koi8r" 2. try to compose a message with cyrillic characters 3. check resulting encoding Actual Results: message is encoded using utf-8 Expected Results: message ought to be in the koi8-r encoding Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.4.3-20050110, glibc-2.3.4.20050125-r1, 2.6.11-cko2 i686) ================================================================= System uname: 2.6.11-cko2 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.6.10 Python: dev-lang/python-2.3.5,dev-lang/python-2.2.3-r5 [2.3.5 (#1, Mar 23 2005, 19:35:04)] distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.4 [enabled] dev-lang/python: 2.3.5, 2.2.3-r5 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.6.3, 1.5, 1.9.5, 1.7.9-r1, 1.4_p6, 1.8.5-r3 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.14 virtual/os-headers: 2.6.8.1-r4 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -mtune=pentium4 -O3 -pipe -fomit-frame-pointer -ffast-math -fprefetch-loop-arrays" 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 /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium4 -mtune=pentium4 -O3 -pipe -fomit-frame-pointer -ffast-math -fprefetch-loop-arrays" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distcc distlocks sandbox sfperms" GENTOO_MIRRORS="ftp://10.1.1.146/gentoo http://www.ibiblio.org/pub/Linux/distributions/gentoo" LANG="ru_RU.KOI8-R" MAKEOPTS="-j11" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/usr/portage-tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://10.1.1.146/gentoo-portage" USE="x86 X Xaw3d acpi alsa apm arts avi bash-completion beepmp bitmap-fonts bluetooth bootsplash cdr crypt cups curl dts dv dvb dvd dvdread edl emboss encode erandom fam fbcon flac font-server foomaticdb fortran gdbm gif gphoto2 gpm gtk gtk2 i8x0 imagemagick imap imlib innodb ipv6 java jpeg junit kde libg++ libwww live lzo mad maildir matroska mbox mikmod mmx mmxext motif mozilla mp3 mpeg mysql nas ncurses nls nptl nptlonly nvidia oav objc oggvorbis opengl oss pam pcmcia pda pdflib perl png pnp python qt quicktime readline real rtc sdl silverxp slang slp socks5 speex spell sse sse2 ssl svg svga tcltk tcpd theora tiff truetype truetype-fonts type1-fonts usb xanim xgetdefault xinerama xml xml2 xv xvid zlib" Unset: ASFLAGS, CBUILD, CTARGET, LC_ALL, LDFLAGS
forgot to mention, mutt-1.5.8-r2 this problem wasn't present in the previous versions
Sorry, I was too fast to say that it wasn't present in the previous versions. I can reproduce it on 1.5.6i even with USE="vanilla" (also tried muttng, the same problem), so I suspect that this is an original mutt's bug. Dunno why I didn't notice it before..
Hemm.. wich $EDITOR are you using? set editor= Read GLEP 31 :-)
this appeared to be a vim problem, by some reason it started to set fileencoding to utf-8. Fixed with the following: set editor="vim +8 -c 'set tw=72 ft=mail fileencoding=koi8-r noautoindent'"
