From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: ken Newsgroups: gmane.emacs.help Subject: Re: utf8 char display in buffer Date: Fri, 12 Jun 2009 18:23:09 -0400 Message-ID: <4A32D54D.1040405@mousecar.com> References: <7I2dndeTy7sqkLLXnZ2dnUVZ_gmdnZ2d@sysmatrix.net> Reply-To: gebser@mousecar.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1244845422 28584 80.91.229.12 (12 Jun 2009 22:23:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 12 Jun 2009 22:23:42 +0000 (UTC) To: GNU Emacs List Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Jun 13 00:23:40 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MFF9v-0001cn-Di for geh-help-gnu-emacs@m.gmane.org; Sat, 13 Jun 2009 00:23:39 +0200 Original-Received: from localhost ([127.0.0.1]:34899 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MFF9u-00017w-Fp for geh-help-gnu-emacs@m.gmane.org; Fri, 12 Jun 2009 18:23:38 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MFF9b-00017r-91 for help-gnu-emacs@gnu.org; Fri, 12 Jun 2009 18:23:19 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MFF9Y-00017f-Qc for help-gnu-emacs@gnu.org; Fri, 12 Jun 2009 18:23:18 -0400 Original-Received: from [199.232.76.173] (port=53569 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MFF9Y-00017c-Ku for help-gnu-emacs@gnu.org; Fri, 12 Jun 2009 18:23:16 -0400 Original-Received: from mout.perfora.net ([74.208.4.195]:53664) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MFF9Y-0001M4-AU for help-gnu-emacs@gnu.org; Fri, 12 Jun 2009 18:23:16 -0400 Original-Received: from [192.168.0.26] (dsl093-011-017.cle1.dsl.speakeasy.net [66.93.11.17]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1MFF9V1UHa-000fvq; Fri, 12 Jun 2009 18:23:15 -0400 User-Agent: Thunderbird 2.0.0.0 (X11/20070326) In-Reply-To: X-Enigmail-Version: 0.95.7 OpenPGP: id=5AD091E7 X-Provags-ID: V01U2FsdGVkX1/RZYOge4rug2bcmI9klJUd5aeUsgWAsRGl7Os KLiS/e1NZAh7Y7ozjEa+ZOJ5+ffmviOLVmEOEAAH0MtEIf0IOd cI8AH1aqwtRizzT9GUwHvecBOgsQao4 X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:65227 Archived-At: On 06/12/2009 01:53 PM Xah Lee wrote: > On Jun 12, 7:54 am, ken wrote: >> B) It would be helpful if the code which does the decoding of a file and >> renders it into the buffer display, if that part of it would throw an >> error message when it encounters a character it doesn't know how to >> display, i.e., when a little box character is displayed. After all, >> isn't it an error when a little box is displayed in lieu of the correct >> character? Possible error messages would be something like: "decoding >> process can't find /path/to/charset.file" or "decoding process doesn't >> have requisite permission to read /path/to/charset.file" or "invalid >> character: [hex/decimal value]" or other. > > some thought process in the above is not correct. Yet emacs puts a little box in the place of a character it cannot find (or, per your explanation) possibly confused about. The fact remains that the little box is not a correct rendering of the code. It is an error... at least it is for me, because that's not what I typed in. So it is an error. As an error, there should be a corresponding error message, hopefully one (or more) which would help diagnose the problem. It seems obvious that, given the long thread on this issue with no resolution, we could use some help-- like an error message-- which would help in diagnosis. Thanks for the information and the links though. > > ....