Paul Stodghill <stodghil(a)cs.cornell.edu> writes:
o First, x-make-font-bold is called and correctly derives the bold
version of
the default font. The face is then changed ('global) to this font.
o Second, mswindows-make-font-bold is called and derives a Windows font name
of the existing font name. The face is then changed ('global) to the Windows
font!
The final effect is that the font-name is set to a Windows font name for
display under X.
If someone could suggest a way to fix this, I'll submit the patches....
Add the specifier for the font name using a tag set. i.e. the x font
name gets added with an 'x tag set and the windows font name with an
'mswindows tag set.
This should work giving the following excerpt from the info file
* The inst-pairs contained in the specification that was found are
considered in their order in the inst-list, looking for one whose
tag set matches the device that is derived from the window domain.
(The tag set is an unordered list of zero or more tag symbols.
For all tags that have predicates associated with them, the
predicate must match the device.)
Jan