Alright thank you, I am pulling, compiling On Wed, Apr 19, 2017 at 10:56:40AM +0300, Sergey Poznyakoff wrote: > 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.
The first one works for sure, the Content-Type: text/plain; charset=utf-8 > > (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. Thank you, I will use this solution now. Jean _______________________________________________ Bug-mailutils mailing list Bug-mailutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-mailutils
