On 08/11/2009 14:11, Eliot Moss wrote:
Corinna Vinschen wrote:
On Nov 7 09:27, Eliot Moss wrote:
Like another user, I had difficulty getting X to fire up.
After setting LANG=en_US.UTF-8 I got farther, but these issues
remain:
Each xterm, xemacs, and xclock I start outputs this:
Warning:
Thanks, Jon!
Installing the three font collections you suggested seems to have
solved all THREE of the problems I mentioned. I can only guess
that somehow the font/locale issues prevented some .Xdefault
information from being loaded or used properly, but I attach
the .Xdefaults file anyway.
The
On Nov 7 09:27, Eliot Moss wrote:
Like another user, I had difficulty getting X to fire up.
After setting LANG=en_US.UTF-8 I got farther, but these issues
remain:
Each xterm, xemacs, and xclock I start outputs this:
Warning: Missing charsets in String to FontSet conversion
I also get
Corinna Vinschen wrote:
On Nov 7 09:27, Eliot Moss wrote:
Like another user, I had difficulty getting X to fire up.
After setting LANG=en_US.UTF-8 I got farther, but these issues
remain:
Each xterm, xemacs, and xclock I start outputs this:
Warning: Missing charsets in String to FontSet
