>>>> "Paul" == Paul Stodghill
<stodghil(a)CS.Cornell.EDU> writes:
Paul> According to Jan:
> 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.)
This is not going to be FSF compatible. I don't see anything here
that is propagating to the Custom API level yet, but we have to watch
out for it.
Paul> Ok, the following seems to work for me.
Paul> PLEASE, look at this very carefully, I honestly don't
Paul> understand specifiers, and I'm just winging it....
This is the wrong place to do this, I think; it works here for this
case, but we really need to fix it throughout Custom. If we should
add another type of device or other such condition, this code will
have to be changed.
--
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 two straight lines for? "Free software rules."