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 <5lit0gj2dq.fsf@rum.cs.yale.edu>:
> > name:  -cronyx-courier-bold-o-normal--10-100-75-75-m-60-iso8859-5
> [...]
> >       FONT                  
> > -Cronyx-Courier-Bold-O-Normal--10-100-75-75-M-60-RAWIN-R
> 
> So that's indeed the problem.  What kind of system is that ?
> Solaris ?

Yes; 2.6.

> GNU/Linux ?  Which distribution ?  Mandrake ?  Debian ?
> It would be good if you could figure out where the alias for the fontname
> comes from, so we can try and make sure it won't happen again.

Have no idea how...

> > 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?

Ilya