Re: Examining font properties under Windows
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
>>>>> "Hrvoje" == Hrvoje Niksic
<hniksic(a)xemacs.org> writes:
Hrvoje> For example, `face-bold-p' and `face-italic-p' and, in
Hrvoje> newer incarnations, (face-attribute FACE :weight) and
Hrvoje> (face-attribute FACE :slant) -- you get the idea.
Oh, those. We have those.
I don't use those in htmlize, partly because I don't consider
`custom-face-*' part of the public face API, and partly because I
don't trust that code. And I'm the one who put it in!
Note the comment above those illustrious functions:
;; Really, we should get rid of these font.el dependencies... They
;; are still presenting a problem with dumping the faces (font.el is
;; too bloated for us to dump). I am thinking about hacking up
;; font-like functionality myself for the sake of this file. It will
;; probably be to-the-point and more efficient.
The predicates are called `custom-face-bold-p' etc in XEmacs.
Why I
don't know.
Because when they were added, they were internal functions in a state
of flux. I didn't want to make them "official" by naming them
`face-bold-p', etc. That was a good decision. An even better one
would have been not to add them in the first place, but then our
custom would have been too incomplete.
I don't know if they work; I don't use Custom since it
doesn't know
about Japanese.
:-(
I don't use Custom with faces because it just sucks. I set my fonts
using X resources.
Hrvoje> Also note that `M-x apropos' only lists
interactive
Hrvoje> commands under FSF.
That's exactly what I wanted. If the users can't get at it, it's
not properly supported.
I guess I didn't realize what you meant by supported. For example, a
user cannot type `M-x make-extent', or `M-x make-face' yet both
interfaces are supported for my definitions of the word.