From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/66401 Path: news.gmane.org!not-for-mail From: Katsumi Yamaoka Newsgroups: gmane.emacs.devel,gmane.emacs.gnus.general Subject: Re: Why multibyte for original-article buffer Date: Fri, 29 Feb 2008 09:35:30 +0900 Organization: Emacsen advocacy group Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=shift_jis Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1204245361 18107 80.91.229.12 (29 Feb 2008 00:36:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 29 Feb 2008 00:36:01 +0000 (UTC) Cc: bugs@gnus.org, ding@gnus.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 29 01:36:26 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JUtEe-0007DG-0v for ged-emacs-devel@m.gmane.org; Fri, 29 Feb 2008 01:36:24 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JUtE7-00060r-Ic for ged-emacs-devel@m.gmane.org; Thu, 28 Feb 2008 19:35:51 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JUtE2-00060N-Cd for emacs-devel@gnu.org; Thu, 28 Feb 2008 19:35:46 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JUtE1-0005zm-Ny for emacs-devel@gnu.org; Thu, 28 Feb 2008 19:35:46 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JUtE1-0005zc-LD for emacs-devel@gnu.org; Thu, 28 Feb 2008 19:35:45 -0500 Original-Received: from orlando.hostforweb.net ([216.246.45.90]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JUtE1-0001pg-BH for emacs-devel@gnu.org; Thu, 28 Feb 2008 19:35:45 -0500 Original-Received: from [66.225.201.151] (port=49764 helo=mail.jpl.org) by orlando.hostforweb.net with esmtpa (Exim 4.68) (envelope-from ) id 1JUtDu-0005Tz-SK; Thu, 28 Feb 2008 18:35:40 -0600 X-Hashcash: 1:20:080229:monnier@iro.umontreal.ca::qcTsUK1ljcGnoyV9:00000000000000000000000000000000000002tjj X-Hashcash: 1:20:080229:bugs@gnus.org::+JnnaDu5L3dz08UK:000024sy X-Hashcash: 1:20:080229:emacs-devel@gnu.org::oU5dT6clai17csP6:0000000000000000000000000000000000000000001fSE X-Hashcash: 1:20:080229:ding@gnus.org::XnNCtE0dxBVy7g/p:00003TPF 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.110007 (No Gnus v0.7) Emacs/23.0.60 (gnu/linux) Cancel-Lock: sha1:0mqP6GFmFEOAImotPHqylVDdUHE= Content-Disposition: inline X-Antivirus-Scanner: Clean mail though you should still use an Antivirus X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - orlando.hostforweb.net X-AntiAbuse: Original Domain - gnu.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-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:90802 gmane.emacs.gnus.general:66401 Archived-At: >>>>> Stefan Monnier wrote: > I've been running with the following patch with good results. > Also the patch makes sense to me: the original article is a sequence of > bytes (i.e. encoded chars), so a unibyte buffer makes a lot of sense > (it's more efficient and is likely to hide fewer bugs). So, it is better to make also the " *nntpd*" buffer, the process buffer for pop3, etc. be unibyte. If such changes cause a problem, it will be due to a code that copies data from those buffers to a multibyte buffer and then decodes the data. Actually, making the original article buffer be unibyte prevents me from reading a Japanese 8bit shift_jis message like this. “ú–{Œê (Try `g' in the summary buffer.) > Yet the code currently explicitly sets the buffer to multibyte mode. > Does anybody know why? IIRC, it was done about ten years ago. I guess it was probably a workaround for a problem like the one mentioned above. > --- gnus-art.el.~1.154.~ 2008-02-28 14:10:39.000000000 -0500 > +++ gnus-art.el 2008-02-28 14:09:51.000000000 -0500 > @@ -4342,7 +4342,7 @@ > (gnus-article-setup-highlight-words) > ;; Init original article buffer. > (with-current-buffer (gnus-get-buffer-create gnus-original-article-buffer) > - (mm-enable-multibyte) > + (mm-disable-multibyte) > (setq major-mode 'gnus-original-article-mode) > (make-local-variable 'gnus-original-article)) > (if (and (get-buffer name) It is beyond my capacity to verify (and possibly to fix) all the Gnus codes that copy data from there to somewhere. Regards,