Teemu Likonen <tlikonen@xxxxxx> writes:
> On 2009-04-05 13:02 (-0700), Junio C Hamano wrote:
>
>> Reece Dunn <msclrhd@xxxxxxxxxxxxxx> writes:
>>> I think Junio is trying to learn base64 :)!
>>
>> I think that is what my Gnus/message-mode did. I do not know which
>> letter triggered it to decide it is UTF-8 to begin with, though. As
>> far as I am aware, I didn't type anything non-ascii in my message.
>
> You can customize the encoding decision mechanism, for example:
>
> (setq mm-body-charset-encoding-alist
> '((iso-8859-1 . 8bit)
> (utf-8 . 8bit)))
>
> For more info, see:
>
> C-h v mm-body-charset-encoding-alist RET
Interesting.
I have had these for a long time:
(setq mm-coding-system-priorities '(us-ascii iso-2022-jp utf-8 iso-8859-1))
(setq mm-content-transfer-encoding-defaults
'(("text/.*" 8bit)
("message/rfc822" 8bit)
("application/emacs-lisp" qp-or-base64)
("application/x-emacs-lisp" qp-or-base64)
("application/x-patch" qp-or-base64)
(".*" base64)))
I did not have any customization on my own to body-charset-encoding-alist
and C-h v gave me:
mm-body-charset-encoding-alist's value is
((iso-2022-jp . 7bit)
(iso-2022-jp-2 . 7bit)
(utf-16 . base64)
(utf-16be . base64)
(utf-16le . base64))
I'll have the following in my .emacs in addition to the coding-system-prio
and c-t-e-defaults I already have:
(setq mm-body-charset-encoding-alist
'((iso-2022-jp . 7bit)
(iso-2022-jp-2 . 7bit)
(iso-8859-1 . 8bit)
(utf-8 . 8bit)))
and will see what happens, but I wonder how this new one interacts with
the c-t-e-defaults.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html