[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-mailutils] multipart/alternative not displaying in Yahoo.com

From: Sergey Poznyakoff
Subject: Re: [bug-mailutils] multipart/alternative not displaying in Yahoo.com
Date: Wed, 19 Apr 2017 10:56:40 +0300

Hi Jean,

> Thank you. It is working now in Yahoo, I can see the message. It looks
> like charset is being set automatically? The HTML file shows
> iso-8859-1 and I just hope it does not disturb vieweing the HTML file
> which has inside UTF-8 settings, I still think it can disturb it.

You can specify charset with the --content-type option:

  --content-type='text/plain; charset=utf-8'

> (defun mu-header-unicode ()
>   (concatenate 'string
>                " -a \"Content-Type: text/plain; charset=utf-8\" "
>                " -a \"Content-Disposition: inline\" "
>                " -a \"Content-Transfer-Encoding: 8bit\" "))

That's useless -- none of Content-* options can be set from the command
line.  You will get error messages for all three.

> (defun mu-html-alternative (file)
>   (if (not (zerop (length file)))
>     (format nil " --alternative --content-type=text/html --attach=~a" file)
>     ""))

To pass charset, I'd propose the following change:

(defun mu-html-alternative (file cset)
  (if (not (zerop (length file)))
    (format nil " --alternative --content-type='text/html; charset=~a' 
--attach=~a" cset file)

> (defun mu-body-type (type)
>    (format nil " --content-type=~a " type))

The same trivial change applies to this defun as well.  Also, please pull.
I've just pushed ff1a8a6e, which makes --content-type apply to the
message read from stdin.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]