On Sun, Oct 08, 2006 at 11:56:21AM -0700, Dan Nicholson wrote: > > I think the problem here might be the *locale resource. I don't think > that you pass the locale you want, you are actually telling the resource > whether you want it to respect for current locale setting or not. So, > it's a boolean, and I have it set to 1. > I remember Alexander told me it was wrong. But I also remember that setting it to 1 didn't seem to work. My history suggested I probably did something wrong. I'll retry later (probably tomorrow, at the moment I'm experimenting with a Compose key again after realising my ~/.Xresources was only looking in /usr/X11R6). > That would in turn affect Fontconfig, which tries to make font > selections based on your charset, etc. > > I could be wrong there, but I've had these settings working for a while. > Here's exactly what I'm applying: > > [11:22 AM [EMAIL PROTECTED] tail /usr/share/X11/app-defaults/XTerm > XTerm*Geometry: 80x40 So narrow! Don't you ever look at kernel source ? (Yes, I know the kernel is 'supposed' to fit in 80 columns).
> XTerm*scrollBar: on > XTerm*rightScrollBar: on > Xterm*color255: on ooh, I hadn't spotted that option. > > *VT100.locale: 1 > *VT100.faceName: Monospace So, that would tell fontconfig to use the first matching font for Monospace, which in blfs is DejaVu ? Oh, I've now read a couple of paragraphs further... > *VT100.faceSize: 10 > > *customization: -color > > But, here's what I played around with when I was testing, and it seems > to work. I just tried it again right now, and it seems to work, although > I can't recall exactly what FreeMono looks like. > That's easy - "horrible" ! A thin/light font, and far too much space around ascii characters. When I see it on a white background it looks grey, on a black background like I normally use it's thin and therefore faint. Or, in Alexander's description, "ugly". > ! *VT100.locale: 1 > ! *VT100.faceName: "DejaVu Sans Mono" > *VT100.faceName: "FreeMono" > ! *VT100.faceName: "Luxi Mono" > ! *VT100.faceName: "Monospace" > ! *VT100.faceName: Monospace > ! *VT100.faceSize: 8 > > Hmm, no I take that back. It keeps selecting DejaVu every time. The only > way I could get FreeMono explicitly was by passing -fa on the command > line. I'm not sure what's going on there. Interesting. That pretty much matches what I'm seeing. > > > 1. The faceSize seems to be used, but is this enough in itself to > > make xterm use a TTF ? If not, what is/are the other key value(s) ? > > Look at XTerm(1), seems there's a resource renderFont, but it defaults > to True. > > > 2. Anybody know how to write a resource to force the specified font, > > with size and charwidth ? (e.g. so that my xterms suddenly use > > FreeMono with size 10 and charwidth 9). > > I don't know anything about setting the width. > > > One of my test documents is 'quickbrown.txt' from the ucs-fonts > > package (which _doesn't_ provide TTFs). With DejaVu I can see the > > Latin and Cyrillic, with FreeMono I can see the hebrew, but none of > > my fonts seem to work correctly on the Japanese or Thai examples. > > >From the above, it appears that I'm not using xterm's fonts correctly. > But even when I force FreeMono, it doesn't do the right thing. You need > a smarter terminal, unfortunately, which knows how to better interact > with Fontconfig. Gnome-terminal is handling it nicely, and I'm sure this > comes from Pango. But I also have the baekmuk, firefly and kochi fonts > installed. The thai looks like it could be sketchy. See screenshot here: > > http://anduin.linuxfromscratch.org/~dnicholson/terminal_chars.png > Not quite sure what the first glyph for the Thai is, and it's all a bit small for me to see clearly. Ignoring the "it's supposed to line up in two columns" issue, that looks pretty good. Mine mostly shows as either blank, or as outlined cells. I've got the same fonts, which I guess are being used by my browsers. > That's the best I can say about the subject. Good luck. Many thanks, Dan. I can see I'll have to try alernatives to xterm (which is a bit of a pain, all I really want is a minimal terminal without lots of dependencies). I do currently build a lot of gnome on the boxes using just /lib, but on the multilib builds it's a whole different can of worms. Ken -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
