[Home]History of MuttFaq/Attachment

MuttWiki | RecentChanges | Preferences | EDITwiki


Revision 44 . . (edit) June 8, 2010 1:34 am by Sum [add information about html attachements and encoding]
Revision 43 . . April 20, 2010 1:55 pm by SeanWhitton [Really, mutt does support this if you use the "alternative" method which does exactly what people normally want in this situation.]
Revision 42 . . June 10, 2008 6:57 am by Rcbarnes [Added section on detecting if X is running as a conditional in .mailcap file]
  

Difference (from prior major revision) (minor diff, author diff)

Added: 75a76,84
Note: Mutt exports text/* attachements in the character set/encoding used by the terminal it
runs on. By using text/html attachements, there is a problem with this that needs to be circumvented:
the html attachement can contain a key for specifying the character encoding of the html text, which
is not neccessarily in accordance with the terminal encoding (the sender of the email does not know,
what encoding mutt on the recieving end uses). Thus viewing these attachements with text encoded
in the terminal encoding will fail. Work arounds:
# tell the html-to-text converter (e.g. lynx) to ignore the html tag specifying the encoding (as done above)
# re-encode the file using the correct character set. This can be done by a script using iconv [Bugreport with attached script]


Changed: 103,106c112,113
Mutt does not support quoting the first part and attaching the
rest of the parts. Just add your comments like you were sending a
new message. Another way is to go to the attachment-menu, tag all
attachments you want to forward and invoke "tag-prefix" +
Go to the attachment-menu, tag all
attachments you want to forward and also tag the text part of the e-mail. Then invoke "tag-prefix" +

MuttWiki | RecentChanges | Preferences | EDITwiki
Search: