Well, I'm going slowly nuts here. To get to the key point first, xrdb shows that xterm's font is set to helvetica. However, I am completely unable to find where that happens. One clue is that under KDE2 I have the bad font, while under AfterStep things are "normal" (i.e., using fixed).
On Sun, Jan 04, 2004 at 10:21:27AM -0500, Thomas Dickey wrote: > On Sun, 4 Jan 2004, Ross Boylan wrote: > > > With help from the tips here, I've managed to build a debug version of > > xterm. > > > > This shows the font being used is > > -adobe-helvetica-medium-r-normal--18-180-75-75-p-98-iso10646-1 > > That's probably from an X resource setting that looks like > > *VT100*font5: -adobe-helvetica-medium-r-normal--18-180-75-75-p-98-iso10646-1 Do you mean that literally font5 is the default font, or was that just suggestive? At any rate, looking in my .Xresources, /etc/X11/Xresources/ (which I think is Debian specific) and app-defaults, the only stuff I see with helvetica is *SimpleMenu*menuLabel.font: -adobe-helvetica-bold-r-normal--*-120-*-*-*-*-iso8859-* in XTerm. There is no definition of a font property (opposed to fontn or font.label. Here's some more font stuff from XTerm *fontMenu.Label: VT Fonts *fontMenu*fontdefault*Label: Default *fontMenu*font1*Label: Unreadable *VT100*font1: nil2 *IconFont: nil2 *fontMenu*font2*Label: Tiny *VT100*font2: 5x7 *fontMenu*font3*Label: Small *VT100*font3: 6x10 *fontMenu*font4*Label: Medium *VT100*font4: 7x13 *fontMenu*font5*Label: Large *VT100*font5: 9x15 *fontMenu*font6*Label: Huge *VT100*font6: 10x20 *fontMenu*fontescape*Label: Escape Sequence *fontMenu*fontsel*Label: Selection !fontescape and fontsel overridden by application *fontMenu*font-linedrawing*Label: Line-Drawing Characters *fontMenu*font-doublesize*Label: Doublesized Characters *fontMenu*font-loadable*Label: VT220 Soft Fonts UXTerm, which it's possible I'm using, has *fontMenu.Label: Unicode Fonts *VT100*utf8: 1 *VT100*font2: -misc-fixed-medium-r-normal--8-80-75-75-c-50-iso10646-1 *VT100*font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1 *VT100*font3: -misc-fixed-medium-r-normal--14-130-75-75-c-70-iso10646-1 *VT100*font4: -misc-fixed-medium-r-normal--13-120-75-75-c-80-iso10646-1 *VT100*font5: -misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1 *VT100*font6: -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1 This does have a font entry, but it does not seem to govern. > > The second "*" is redundant and will cause current xterm to produce a > different font than older code. See the "XTerm" app-defaults file, > where it lists the ".utf8fonts" lines. I guess that's been broken into UXTerm in my distro? > > > I verified that starting xterm with this as -fn produces the same > > result as plain xterm (namely spaced out fonts). > > > > It appears this is set in a call to XtVaCreateManagedWidget > > term = (XtermWidget) XtVaCreateManagedWidget( > > "vt100", xtermWidgetClass, form_top, > > > > which is outside of xterm (i.e., not in code I can debug easily). The > > startup trace shows -fn set to (standard). > > Not exactly. This calls functions that are declared for each widget. > For xterm, the interesting ones are in charproc.c, e.g., VTInitialize(). > When the debug-trace is compiled in, most of the resource initialization > is logged in "Trace-parent.out". Is there a good way to find out what the sequence of call-backs is? Is it sufficient to put a break on VTInitialize? > > > Also, a header file defines DEFONT as "fixed", but this is never used > > in the code, as far as I can tell (with grep). Again, 4.2.1 source. > > (4.2.1 is a little old, and current xterm source should build against that > in any case). My mistake: I used DEFONT not DEFFONT. With that I see all but the fontutils.c entry you have below. > > % Command: fgrep -n DEFFONT * > > fgrep -n DEFFONT * > charproc.c:456: Sres(XtNfont, XtCFont, misc.default_font.f_n, DEFFONT), > fontutils.c:971: Sres(XtNfont, XtCFont, default_font.f_n, DEFFONT), > main.h:35:#define DEFFONT "fixed" > > > Does this mean that xterm is picking up X's general default font? If > > so, where is that set? > > "fixed" is an alias, e.g., one of the symbols in a "fonts.alias" file > under /usr/X11R6/lib/X11/fonts/... (see mkfontdir). > The only alias for fixed was innocuous, not helvetica $locate fonts.alias | xargs egrep -H '^fixed' /usr/X11R6/lib/X11/fonts/misc/fonts.alias:fixed -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1 But xrdb -query returns xterm*Font: -adobe-helvetica-medium-r-normal--18-180-75-75-p-98-iso10646-1 xterm*background: #ffffff xterm*foreground: #000000 xterm.SimpleMenu*background: #eaeaea xterm.SimpleMenu*font: -adobe-helvetica-medium-r-normal--18-180-75-75-p-0-iso8859-1 xterm.SimpleMenu*foreground: #000000 This is also kind of odd, because there are many more resources set for xterm in app-defaults. _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
