Re: mm-with-unibyte-current-buffer is bad for Emacs 23

[Katsumi Yamaoka <yamaoka@jpl.org>]

>> On Tue, Feb 28 2006, Katsumi Yamaoka wrote:

>>> The macro `mm-with-unibyte-current-buffer' is used here and
>>> there in Gnus.  In Emacs 23, I realized there is a possibility
>>> that it breaks non-ASCII text.

I encountered actual problems.  In Emacs 23, text parts contained
in Japanese multipart messages that are encoded by the shift_jis
charset and the 8bit encoding are displayed with some broken
characters.  In that case, `mm-with-unibyte-current-buffer' is
called at least twice on the raw message; one is for extracting
the whole body, the others are for extracting parts.  The raw
message is broken at the first time the macro is called.  So,
I've modified the `mm-get-part' function so as not to use the
`mm-with-unibyte-current-buffer' macro.

In addition, I've also fixed the display table used in the
summary buffer.  It nixed out data 127 through 255, however some
Latin characters have values 160 through 255 in Emacs 23.  For
example:

(make-char 'latin-iso8859-1 160)
;; Emacs 23
 => 160
;; Emacs 22
 => 2208

Because of this, "Sébastien" was displayed as "S?bastien" in the
summary buffer.

* trunk and v5-10 branch *