From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: bug#7517: 24.0.50; repeated crash under Mac OS X Date: Mon, 03 Jan 2011 08:10:06 -0500 Message-ID: References: <87vd2dyzfj.fsf@stupidchicken.com> <4D1B22A1.6080202@swipnet.se> <4D1B27AF.7010701@swipnet.se> <4D1C6E7D.2040300@swipnet.se> <4D1D0172.8080404@swipnet.se> <4D1DB555.5080002@swipnet.se> <4D1DBD4A.6010303@swipnet.se> <83d3oiaysj.fsf@gnu.org> <4D1DD655.1040809@swipnet.se> <83aajmaxme.fsf@gnu.org> <4D1E5987.2000502@swipnet.se> <83mxnkq1ej.fsf@gnu.org> <8362u8pkg6.fsf__47242.3368752517$1293906238$gmane$org@gnu.org> <83y674ne9h.fsf@gnu.org> <19744.58213.935000.469856@gargle.gargle.HOWL> <83sjxbnekt.fsf@gnu.org> <19745.21925.247000.562416@gargle.gargle.HOWL> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: dough.gmane.org 1294060225 5932 80.91.229.12 (3 Jan 2011 13:10:25 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 3 Jan 2011 13:10:25 +0000 (UTC) Cc: u.s.reddy@cs.bham.ac.uk, user.emacs@gmail.com, emacs-devel@gnu.org To: Uday S Reddy Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 03 14:10:21 2011 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.69) (envelope-from ) id 1PZkB0-0004ol-UE for ged-emacs-devel@m.gmane.org; Mon, 03 Jan 2011 14:10:19 +0100 Original-Received: from localhost ([127.0.0.1]:42343 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PZkB0-0001PA-7u for ged-emacs-devel@m.gmane.org; Mon, 03 Jan 2011 08:10:18 -0500 Original-Received: from [140.186.70.92] (port=36484 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PZkAu-0001P5-FC for emacs-devel@gnu.org; Mon, 03 Jan 2011 08:10:13 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PZkAt-0008FA-11 for emacs-devel@gnu.org; Mon, 03 Jan 2011 08:10:12 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]:44951) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PZkAs-0008F6-UV for emacs-devel@gnu.org; Mon, 03 Jan 2011 08:10:10 -0500 Original-Received: from eliz by fencepost.gnu.org with local (Exim 4.69) (envelope-from ) id 1PZkAo-0001KV-Mp; Mon, 03 Jan 2011 08:10:06 -0500 In-reply-to: <19745.21925.247000.562416@gargle.gargle.HOWL> (message from Uday S Reddy on Mon, 3 Jan 2011 04:50:45 +0000) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) 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:134210 Archived-At: > Date: Mon, 3 Jan 2011 04:50:45 +0000 > From: Uday S Reddy > Cc: Uday S Reddy , > user.emacs@gmail.com, > emacs-devel@gnu.org > > Eli Zaretskii writes: > > > Why, doesn't > > > > (coding-system-get FOO :mime-charset) > > > > work for you, or isn't TRT in this case? > > The FOO in this case is a coding-system? Yes. > But VM doesn't know what coding-system to use. It has to find the > coding-system based on the mime-charset. > > It received a string that is encoded in the MIME charset > "iso-8859-8-i". It tried to find an Emacs coding system that had this > mime-charset property. But there wasn't any. So it gave up. If the attempt to find a coding-system by its MIME charset fails, I think VM should try using the string as the name of a coding-system. Would that work? > Note that (coding-system "iso-8859-8-i" :mime-charset) returns > "iso-8859-8". Right, because iso-8859-8-i is an alias. > What I am doing now is to see if there is a coding-system with the > same name as the mime-charset. I think you should do both, and try looking up MIME charset first. > When I don't find a coding-system with the given name, I am using > 'undecided, which is what I think you reocmmended. This at least gets > us out of the unibyte string problem, even though what is produced is > normally gibberish. That could be the last resort. > That is what I thought. But the OP is getting the "bad coding" text > even if a multibyte string is used as the buffer name. So, perhaps > there is a still problem there. Maybe. > The problem should show up if you do > > (generate-new-buffer "שולח דואר אלקטרוני") > > and switch to that buffer Emacs. At least on MS-Windows (which is what I have here), I see no problems. The text is displayed correctly and is legible.