Mailinglist Archive: opensuse-bugs (4691 mails)

< Previous Next >
[Bug 581645] mutt passes wrong input encoding to w3m
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 23 Feb 2010 09:48:13 +0000
  • Message-id: <20100223094813.446B324551B@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=581645

http://bugzilla.novell.com/show_bug.cgi?id=581645#c1


Dr. Werner Fink <werner@xxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |max@xxxxxxxxxx,
| |ro@xxxxxxxxxx,
| |werner@xxxxxxxxxx
AssignedTo|werner@xxxxxxxxxx |max@xxxxxxxxxx

--- Comment #1 from Dr. Werner Fink <werner@xxxxxxxxxx> 2010-02-23 09:48:12 UTC
---
Beside the attachment mutt does convert anything, it simply
does:

3.3.3. Command Expansion

The various commands defined in the mailcap files are passed to the
/bin/sh shell using the system(3) function. Before the command is
passed to /bin/sh -c, it is parsed to expand various special parameters
with information from Mutt. The keywords Mutt expands are:

[...]

%{<parameter>}
Mutt will expand this to the value of the specified parameter
from the Content-Type: line of the mail message. For instance,
if Your mail message contains:

Content-Type: text/plain; charset=iso-8859-1

then Mutt will expand %{charset} to iso-8859-1. The default
metamail mailcap file uses this feature to test the charset to
spawn an xterm using the right charset to view the message.

[...]

that is that mutt executes accordingly to the /etc/mailcap `-I ISO-8859-1'
and this is *exactly* what /etc/mailcap told mutt. The only thing which
is missed is the output format of the terminal its self. This should
be done by w3m its self accordingly to the variable LANG.

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
References