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 conversion
I also get a series of:
twm: warning: font for charset XXX is lacking.
Where XXX is replaced by each of these in turn:
JISX0208.1983-0
KSC5601.1987-0
GB2312.1980-0
Those three lines repeat 6 times.
Also:
1) the whole deal takes noticeably longer to start
2) xemacs does not receive its normal geometry from .Xdefaults
3) each xterm started from .xinitrc has a blank line
before the initial bash prompt, that wasn't present before
I can reproduce that, but I can't make any sense of it. What on earth
does that have to do with setting LANG to "en_US.UTF-8"?!?
I'll redirect this to the cygwin-xfree list.
Thanks for the redirect, Corinna. I can report a bit more ...
- Adding the locale lines for C.UTF-8 into locale.dir and compose.dir
do work to get X to start for me. (These are the patches discussed
in the "X11R7.5 and C.UTF-8" thread on cygwin-xfree.)
- The other problems go away if I set LANG=C, so it's definitely
something about the locale.
Am I unusual in using twm :-) ?
Anyway, for now I am using LANG=C, set in the Windows environment variables,
but once there are patches or updates to test, I am happy to try them ...
Best wishes -- Eliot Moss
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
