On Sun, Jul 08, 2012 at 06:58:20PM +0200, Harald Weis wrote:
 > On Tue, Jul 03, 2012 at 11:15:03AM +0900, Daniel P. Wright wrote:
 >  > I am running mutt 1.5.21 compiled from the mutt repo (no ports) on
 >  > FreeBSD with no trouble.  The parameters I passed to "prepare" are as
 >  > follows:
 >  > 
 >  >     ./prepare --prefix=/usr/local --enable-locales-fix --disable-fcntl 
 > --enable-hcache --with-libiconv-prefix=/usr/local --with-slang=/usr/local
 >  > 
 >  > (I am using slang over ncurses because of weird colour issues I was
 >  > getting with curses; that part is optional)
 >  > 
 >  > Having said that, I just tried to build mutt from ports using defaults
 >  > options (version 1.4.2.3i, curses, not slang; locales fix enabled), and
 >  > it displays unicode fine.
 >  > 
 >  > If you did want to use 1.5.21, the mutt-devel port is usually
 >  > up-to-date.
 >  > 
 >  > Did you check your locale settings?  Mine are as follows:
 >  > 
 >  >     LANG=ja_JP.UTF-8
 >  >     LC_ALL=ja_JP.UTF-8
 >  >     LC_CTYPE=ja_JP.UTF-8
 >  > 
 >  > You probably don't want Japanese, but some sort of locale setting with
 >  > "UTF-8" in the name ought to do you.  I can confirm these settings are
 >  > working on my FreeBSD machine with both the "mutt" and "mutt-devel"
 >  > ports, and with my own version compiled from sources.
 >  > 
 >  > Hope that helps.
 >  > 
 >  > -Dani.
 >  
 > Following the FreeBSD Handbook, I use login classes set in /etc/login.conf.
 > If I remember correctly, nothing else is required.
 > me@pollux:~ % setenv |grep UTF
 > MM_CHARSET=UTF-8
 > LANG=en_US.UTF-8
 > XTERM_LOCALE=en_US.UTF-8
 > --
 > No change whatsoever if I add in .cshrc the following lines.
 > setenv LC_ALL  en_US.UTF-8
 > setenv LC_CTYPE        en_US.UTF-8
 > --
 > Not surprising.
 > 
 > muttrc contains the following lines.
 > me@pollux:~ % egrep "charset" .mutt/muttrc
 > #set charset="utf-8"    # "never EVER EVER EVER set $charset yourself"
 > #set send_charset="us-ascii:iso-8859-15:utf-8"  # A list of character sets
 > #  for outgoing messages (Default: "us-ascii:iso-8859-1:utf-8")
 > charset-hook ^unknown-8bit$ WINDOWS-1252
 > charset-hook ^x-user-defined$ WINDOWS-1252
 > charset-hook ^ISO-8859-1$ WINDOWS-1252
 > charset-hook ^US-ASCII$ WINDOWS-1252
 > charset-hook ^none$ WINDOWS-1252
 > charset-hook ^ISO-8859-8-1$ ISO-8859-8
 > charset-hook ^GB2312$ GB18030
 > --
 > The charset and charset-hook lines come from this mailing list.
 > 
 > Output of mutt -v is:
 > Mutt 1.4.2.3i (2007-05-26)
 > Copyright (C) 1996-2002 Michael R. Elkins and others.
 > Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
 > Mutt is free software, and you are welcome to redistribute it
 > under certain conditions; type `mutt -vv' for details.
 > 
 > System: FreeBSD 8.3-RELEASE (i386) [using ncurses 5.7]
 > Compile options:
 > -DOMAIN
 > -DEBUG
 > -HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE  
 > -USE_FCNTL  +USE_FLOCK
 > +USE_POP  +USE_IMAP  +USE_GSS  +USE_SSL  -USE_SASL  
 > +HAVE_REGCOMP  -USE_GNU_REGEX  +COMPRESSED  
 > +HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET  
 > +HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM  
 > +HAVE_PGP  -BUFFY_SIZE -EXACT_ADDRESS  -SUN_ATTACHMENT  
 > +ENABLE_NLS  +LOCALES_HACK  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET
 > +HAVE_LANGINFO_YESEXPR  
 > +HAVE_ICONV  -ICONV_NONTRANS  +HAVE_GETSID  +HAVE_GETADDRINFO  
 > -ISPELL
 > SENDMAIL="/usr/sbin/sendmail"
 > MAILPATH="/var/mail"
 > PKGDATADIR="/usr/local/share/mutt"
 > SYSCONFDIR="/usr/local/etc"
 > EXECSHELL="/bin/sh"
 > -MIXMASTER
 > To contact the developers, please mail to <mutt-...@mutt.org>.
 > To report a bug, please use the flea(1) utility.
 > 
 > vvv.initials
 > 1.3.28.nr.threadcomplete
 > rr.compressed
 > --
 > Installing mutt-devel does not help. No change, with the exception that
 > mutt-devel does not use .mailcap, God knows why.
 > 
 > So back to mutt. Everything okay, excepting the builtin pager not displaying
 > the famous (multi-byte) characters.
 > 
 > Finally, using the enter-command function in the index menu,
 > I set the pager to w3m. That works!
 > 
 > What is the missing option here?

Does everybody think - when reading this message -
that my case is hopeless ?

Harald :-)

Reply via email to