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: Tue, 09 Jun 2009 10:51:43 -0400 Message-ID: <4A2E76FF.1010306@mousecar.com> References: 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: 8bit X-Trace: ger.gmane.org 1244559290 9286 80.91.229.12 (9 Jun 2009 14:54:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 9 Jun 2009 14:54:50 +0000 (UTC) To: GNU Emacs List Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Jun 09 16:54:46 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 1ME2ir-0004K8-Ls for geh-help-gnu-emacs@m.gmane.org; Tue, 09 Jun 2009 16:54:46 +0200 Original-Received: from localhost ([127.0.0.1]:36987 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ME2ir-0000nA-8f for geh-help-gnu-emacs@m.gmane.org; Tue, 09 Jun 2009 10:54:45 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ME2g0-0007fi-M7 for help-gnu-emacs@gnu.org; Tue, 09 Jun 2009 10:51:48 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ME2g0-0007eh-0V for help-gnu-emacs@gnu.org; Tue, 09 Jun 2009 10:51:48 -0400 Original-Received: from [199.232.76.173] (port=49544 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ME2fz-0007eJ-PB for help-gnu-emacs@gnu.org; Tue, 09 Jun 2009 10:51:47 -0400 Original-Received: from mout.perfora.net ([74.208.4.194]:54301) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1ME2fz-0008LU-9x for help-gnu-emacs@gnu.org; Tue, 09 Jun 2009 10:51:47 -0400 Original-Received: from [192.168.0.26] (dsl093-011-017.cle1.dsl.speakeasy.net [66.93.11.17]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1ME2fw3iP5-000cv7; Tue, 09 Jun 2009 10:51:46 -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: V01U2FsdGVkX19PrpoghtO1EOJb2zk4f+55BzV9JLkg41H991a 39/pb8XoX54V/X1Ua1Sxs2XdyecWP5iKguuO4x07Ai1OIjg7SP gBY5z/J/SZVqr3mEHaU6HEr3T+Aut71 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:65094 Archived-At: On 06/09/2009 09:03 AM B. T. Raven wrote: > ken wrote: >> On 06/08/2009 04:43 PM B. T. Raven wrote: >>> ken wrote: >>>> .... >>>> >>> C-x ret C-\ latin-4-postfix >>> >>> then a,e,i,o,u followed by hyphen generate macroned vowels >>> >>> .... >> >> Fantastic! But... when I save and close the buffer and then open it up >> again, in place of the beautiful and correct characters, there are >> little boxes. > > After you see then correctly in the buffer do: > > C-x ret c utf-8 > > then > > C-x C-s > > Now next time you load that file it should appear correctly. > ā and ī are not in iso-8859-1 and so you must use a more comprehensive > coding system. Hmmm... it doesn't. Doing everything just as you say above, I still get the little boxes in place of the non-English characters. When after reloading the buffer, I run "describe-coding-system" on this buffer, I get: ============================================= Coding system for saving this buffer: u -- mule-utf-8-unix Default coding system (for new files): u -- mule-utf-8 (alias: utf-8) Coding system for keyboard input: nil Coding system for terminal output: 0 -- iso-latin-9 (alias: iso-8859-15 latin-9 latin-0) Defaults for subprocess I/O: decoding: u -- mule-utf-8 (alias: utf-8) encoding: u -- mule-utf-8 (alias: utf-8) Priority order for recognizing coding systems when reading files: 1. mule-utf-8 (alias: utf-8) 2. iso-latin-1 (alias: iso-8859-1 latin-1) 3. iso-2022-jp (alias: junet) 4. iso-2022-7bit 5. iso-2022-7bit-lock (alias: iso-2022-int-1) 6. iso-2022-8bit-ss2 7. emacs-mule 8. raw-text 9. japanese-shift-jis (alias: shift_jis sjis) 10. chinese-big5 (alias: big5 cn-big5) 11. no-conversion (alias: binary) Other coding systems cannot be distinguished automatically from these, and therefore cannot be recognized automatically with the present coding system priorities. The followings are decoded correctly but recognized as iso-2022-7bit-lock: iso-2022-7bit-ss2 iso-2022-7bit-lock-ss2 iso-2022-cn iso-2022-cn-ext iso-2022-jp-2 iso-2022-kr .... ================================================================== I don't know... does utf-8 or mule-utf-8 contain latin-4, greek, and/or German characters? (This file has some of each.) >> >> I tried using ‘C-x C-m c utf-8 RET’ prior to 'C-x C-f filename'... but >> no joy. Same no-go with 'C-x C-m c mule-utf-8 RET'. >> >> The fact that these non-English characters display properly in the >> buffer initially tells me that I have the requisite fonts installed. So >> what little connection is emacs not making (and how do I tell it to make >> that connection)? > > If you use utf-8 a lot you can put ;; -*- coding: utf-8[;] -*- into the > first line of the file. I don't know whether that sem in brackets is > needed or not. Sorry, I should have mentioned that I have this (with the semi-colon) at the top of the file. Let me also say that, though the little boxes appear in the emacs buffer, the proper non-English characters appear when the file is loaded into firefox. (Yeah, this emacs file is an HTML page.) > >> >> Thanks, all. >> >>