Re: Font-bug?

Marcus> I think the problem is, that xemacs does some wildcard Marcus> match on the font name, when requested through customize Marcus> and then it gets my ugly bitstream-courier-version font. I Marcus> wish I could specify the font-vendor with customize :-) I don't recall if Customize creates a 14-hyphen XLFD. If it wildcards where possible (which is consistent with the general quality of Customize code), you may be able to fool it by setting the family to "adobe-courier" in the Customize buffer for the font. This of course won't work in the menus, which strip off the foundry information before even displaying the menu to you. Marcus> I tried, seems to work. What is that specifier tag ? An attempt to get custom to leave the specification alone. The main purpose for built-in specifier tags is to specify that some face settings should be used only in certain circumstances. For example, the 'x tag says "only use this specification on X displays", the 'color tag says "only use this specificatoin on color displays". That allows you to use color only on displays that can handle it, but use a different font or size for emphasis on mono/grayscale displays. However, it also affects what specifications are changed by a call to set-face-font and other specifier manipulations. See the Lispref info manual, topic Specifiers, for the dense but very complete full story. Marcus> I come to the conclusion that it is currently the best, to Marcus> avoid italic fonts completely. I also searched this list, Marcus> and it seems that there are more people discovering this Marcus> behaviour. Italic fonts are hard. The terminology is confusing, because most people think it means "slanted", but that's not correct (although most familiar italic fonts _are_ slanted). -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."