From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-15?q?Gro=DFjohann?=) Newsgroups: gmane.emacs.help Subject: Re: MULE shows gibberish; now what? Date: Fri, 27 Sep 2002 13:51:06 +0200 Organization: University of Dortmund, Germany Sender: help-gnu-emacs-admin@gnu.org Message-ID: References: NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-9 Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1033129002 11952 127.0.0.1 (27 Sep 2002 12:16:42 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 27 Sep 2002 12:16:42 +0000 (UTC) Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 17uu2x-00036W-00 for ; Fri, 27 Sep 2002 14:16:39 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 17uu38-0001pb-00; Fri, 27 Sep 2002 08:16:50 -0400 Original-Path: shelby.stanford.edu!nntp.stanford.edu!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!eusc.inter.net!Informatik.Uni-Dortmund.DE!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 74 Original-NNTP-Posting-Host: lucy.cs.uni-dortmund.de Mail-Copies-To: never User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.3.50 (i686-pc-linux-gnu) Cancel-Lock: sha1:h6WNa1j3+ahY/1qPJJdBFUL8GQY= Original-Xref: nntp.stanford.edu gnu.emacs.help:105383 Original-To: help-gnu-emacs@gnu.org Errors-To: help-gnu-emacs-admin@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.help:1932 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:1932 Ilya Zakharevich writes: > [A complimentary Cc of this posting was sent to > Kai > =?iso-8859-15?q?Gro=DFjohann?= > ], who wrote in article : >> /---- >> | character: ¤ (07444, 3876, 0xf24) >> | charset: latin-iso8859-15 >> | (Right-Hand Part of Latin Alphabet 9 (ISO/IEC 8859-15): ISO-IR-203.) >> | code point: 36 >> | syntax: w which means: word >> | category: l:Latin >> | buffer code: 0x8E 0xA4 >> | file code: 0x8E 0xA4 (encoded by coding system emacs-mule) >> | Unicode: 20AC >> | font: -Misc-Fixed-Medium-R-Normal--14-130-75-75-C-70-ISO8859-15 > > So it does not show which codepoint inside the font is chosen! You see "code point: 36", and you see that it is the right-hand part of the alphabet only. So 128+36=164 is the actual code point you want. >> | There are text properties here: >> | fontified t >> \---- >> >> In the above output, it is easy to see if the glyph matches what it >> should be. I can do "man iso-8859-15" to look up what character has >> code 128+36, and then I can compare it with the glyph. And if the >> "man" command told me to expect a Euro sign, but I'm seeing a >> currency sign, then I know that something is wrong. > > As I said, I *know* that the output is wrong. So how would what you > say help me to debug/fix the problem. You can look at the font name, for example. And you can look at the charset and compare that with your font, to see whether they match. >> As you can easily see, the font name can be different. And the glyph >> (directly after "character: ") is of course also different. > > Is it the same glyph as in the buffer? So what is the point of > looking at *that*? ;-) Argh. >> You can tell Emacs to use the foo font for the bar encoding. > > How? And how do I tell Emacs in which encoding this font actually is? You can't. But you can do it the other way round: you can tell Emacs to use the foo font for the bar encoding. Investigate fontsets in the Emacs documentation. >> Maybe >> you have (accidentally) told Emacs to use a KOI-R font for the >> iso-8859-5 encoding, or something like this. > > With -no-init-file? I doubt it. ;-) With a X11 resource, for instance. You probably set the font for your X11 apps somewhere (otherwise it would be "fixed"). >> If all else fails, you can of course also install fonts in your home >> dir and tell X11 about them, and then tell Emacs to use one of those... > > I have seen machines where X server can't see user directories. Oh, boy. kai -- ~/.signature is: umop ap!sdn (Frank Nobis)