Re: 'mule-fonts' hadling (Re: gtk mule-fonts note)
> So the `mule-fonts' specifier tag is for use only while
> adding specifications to specifier, and it is never used to
> restrict match while instancing specifiers.
What makes you say that? I used to use it a lot in my own code, just
as x-symbol does.
That is, only to ensure that specifications being added will not be
removed by other additions, but not for use in instancing. Then the
original point holds.
What makes you say this? Specifier tags can be defined any time
before use, even (as above) in user code.
The known usage of the tag suggests that it may be used in added
specifications regardless of types of devices currently initialized.
It must be defined before any possible use, that is, very early. Or
one has to scatter code like:
(unless (valid-specifier-tag-p 'mule-fonts)
(define-specifier-tag 'mule-fonts))
throughout packages.
If you want to research the ChangeLogs and patches and explain what
he
thought he was doing, fine.
Do not want. The highest priority for me is ensuring that
documentation answers to user (my) questions: "What is happening to my
fonts? Why is the text displayed in these particular ones?". That
is, describing the current rules.