Re: MULE shows gibberish; now what?

[Ilya Zakharevich]

[A complimentary Cc of this posting was sent to
Stefan Monnier 
<foo@acm.com>], 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