From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/62137 Path: news.gmane.org!not-for-mail From: Katsumi Yamaoka Newsgroups: gmane.emacs.gnus.general Subject: Re: mm-with-unibyte-current-buffer is bad for Emacs 23 Date: Fri, 03 Mar 2006 13:29:58 +0900 Organization: Emacsen advocacy group Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1141360286 24908 80.91.229.2 (3 Mar 2006 04:31:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 3 Mar 2006 04:31:26 +0000 (UTC) Original-X-From: ding-owner+m10665@lists.math.uh.edu Fri Mar 03 05:31:19 2006 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FF1wa-0000zN-VS for ding-account@gmane.org; Fri, 03 Mar 2006 05:31:09 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu ident=lists) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1FF1wV-0001rT-00; Thu, 02 Mar 2006 22:31:03 -0600 Original-Received: from nas02.math.uh.edu ([129.7.128.40]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1FF1vj-0001rO-00 for ding@lists.math.uh.edu; Thu, 02 Mar 2006 22:30:15 -0600 Original-Received: from quimby.gnus.org ([80.91.224.244]) by nas02.math.uh.edu with esmtp (Exim 4.52) id 1FF1vh-0006Hq-Gh for ding@lists.math.uh.edu; Thu, 02 Mar 2006 22:30:15 -0600 Original-Received: from washington.hostforweb.net ([66.225.201.13]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1FF1vg-0006R8-00 for ; Fri, 03 Mar 2006 05:30:12 +0100 Original-Received: from [205.234.185.198] (port=41166 helo=mail.jpl.org) by washington.hostforweb.net with esmtpa (Exim 4.52) id 1FF1wE-0006gp-Cq for ding@gnus.org; Thu, 02 Mar 2006 22:30:46 -0600 Original-To: ding@gnus.org X-Face: #kKnN,xUnmKia.'[pp`;Omh}odZK)?7wQSl"4o04=EixTF+V[""w~iNbM9ZL+.b*_CxUmFk B#Fu[*?MZZH@IkN:!"\w%I_zt>[$nm7nQosZ<3eu;B:$Q_:p!',P.c0-_Cy[dz4oIpw0ESA^D*1Lw= L&i*6&( User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/23.0.0 (gnu/linux) Cancel-Lock: sha1:kfpbN+dwwWTGrr9QOBoPcSAcMJo= X-Hashcash: 1:20:060303:ding@gnus.org::5mZlJZX/A1fisLuV:00001vtI X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - washington.hostforweb.net X-AntiAbuse: Original Domain - gnus.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jpl.org X-Source: X-Source-Args: X-Source-Dir: X-Spam-Score: -2.5 (--) Precedence: bulk Original-Sender: ding-owner@lists.math.uh.edu Xref: news.gmane.org gmane.emacs.gnus.general:62137 Archived-At: >> 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 =3D> 160 ;; Emacs 22 =3D> 2208 Because of this, "S=E9bastien" was displayed as "S?bastien" in the summary buffer. * trunk and v5-10 branch *