content transfer encoding

content transfer encoding

[James H. Cloos Jr.]

I added:

(setq mm-content-transfer-encoding-defaults
  '(("text/x-patch" 8bit)
    ("text/.*" 8bit)
    ("message/rfc822" 8bit)
    ("application/emacs-lisp" 8bit)
    ("application/x-patch" 8bit)
    (".*" qp-or-base64)))

to ~/.gnus.

Running (mm-content-transfer-encoding "text/plain") returns 8bit.

I also customised gnus-group-posting-charset-alist and changed 
(message-this-is-mail nil nil) to (message-this-is-mail nil t).

Nonetheless, sending a message with 8859-1 or utf8 non-ascii
characters results in qp encoding.

I can see 7 bit for headers, but I do not want it at all for bodies.

What is the trick?

-JimC

Re: content transfer encoding

[Katsumi Yamaoka]

Hi,

>>>>> In <m37kfgbd19.fsf@lugabout.jhcloos.org>
>>>>>	"James H. Cloos Jr." <cloos@jhcloos.com> wrote:

> I added:

> (setq mm-content-transfer-encoding-defaults
> '(("text/x-patch" 8bit)
> ("text/.*" 8bit)

[...]

> Nonetheless, sending a message with 8859-1 or utf8 non-ascii
> characters results in qp encoding.

That is no more than a default value.  You can customize the
option mm-body-charset-encoding-alist as follows:

(eval-after-load "mm-bodies"
  '(add-to-list 'mm-body-charset-encoding-alist
		'(iso-8859-1 . 8bit)))

and also:

(eval-after-load "gnus-msg"
  '(setcdr (assq 'message-this-is-mail
		 gnus-group-posting-charset-alist)
	   '(iso-8859-1 iso-8859-1)))

However, such a mail might not be delivered correctly all over
the world.
(I'm not knowledgeable about the Latin characters, though.)
-- 
Katsumi Yamaoka <yamaoka@jpl.org>