From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Ilya Zakharevich Newsgroups: gmane.emacs.help Subject: Re: MULE shows gibberish; now what? Date: Tue, 8 Oct 2002 00:39:38 +0000 (UTC) Organization: U.C. Berkeley Math. Department. Sender: help-gnu-emacs-admin@gnu.org Message-ID: References: <5lit0gj2dq.fsf@rum.cs.yale.edu> <5ladlqhuia.fsf@rum.cs.yale.edu> NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1034037711 20763 127.0.0.1 (8 Oct 2002 00:41:51 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 8 Oct 2002 00:41:51 +0000 (UTC) Bcc: ilya 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 17yiRY-0005OZ-00 for ; Tue, 08 Oct 2002 02:41:48 +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 17yiR9-0004tI-00; Mon, 07 Oct 2002 20:41:23 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!newsfeed.berkeley.edu!ucberkeley!agate.berkeley.edu!agate!ilya Original-Newsgroups: gnu.emacs.help Original-Lines: 26 Original-NNTP-Posting-Host: powdermilk.math.berkeley.edu Original-X-Trace: agate.berkeley.edu 1034037578 17104 169.229.140.13 (8 Oct 2002 00:39:38 GMT) Original-X-Complaints-To: usenet@agate.berkeley.edu Original-NNTP-Posting-Date: Tue, 8 Oct 2002 00:39:38 +0000 (UTC) X-How-To-Reach-Me: The From: address is valid Originator: ilya@powdermilk Original-Xref: shelby.stanford.edu gnu.emacs.help:105808 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:2355 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:2355 [A complimentary Cc of this posting was sent to Stefan Monnier ], who wrote in article <5ladlqhuia.fsf@rum.cs.yale.edu>: > >> > What can a sysadm do to fix this misconfiguration of thinking that > >> > rawin-r is iso8859-5 (if it is one)? > >> Yes, it is a misconfiguration since the two encodings are not the same. > >> A sysadmin can just look at the /some/where/fonts.aliases file and > >> remove the bogus alias. > > Is it enough grep the fontpath reported by xset? Or can this > > fonts.aliases file be long gone, so that the traces are present in the > > compiled version only? > > I think you're right: the file might indeed be long gone, included inside > the resulting `fonts.dir' file. I'd grep through any `fonts.*' in the > fontpath directories returned by xset. Neither RAWIN, nor iso8859-5 found (grep -i). There is also tcp/169.229.58.58:7100 in the fontpath, but I do not know how to grep there. :-( Ilya