Re: Examining font properties under Windows

Hrvoje> Adrian Aichner <adrian(a)xemacs.org&gt; writes: Hrvoje> Heh, that's pretty bad. Thanks for trying it, anyway. I think that the truename of the font under Windows is better behaved than that under X11. Get the truename of the font and parse it according to this comment (from objects-msw.c) on mswindows_font_instance_truename: /* Fill in missing parts of a font spec. This is primarily intended as a * helper function for the functions below. * mswindows fonts look like: * fontname[:[weight][ style][:pointsize[:effects]]][:charset] * A minimal mswindows font spec looks like: * Courier New * A maximal mswindows font spec looks like: * Courier New:Bold Italic:10:underline strikeout:Western * Missing parts of the font spec should be filled in with these values: * Courier New:Regular:10::Western */ There are long lists of values for the various properties in that file. According to a comment in 21.5's version of that file, MSFT is not defining character sets any more, you have to get the set of characters (or check whether the font supports the code point, I forget exactly). I think that the others (weight, style, and effects) are pretty well-defined. So if you check against the lists in that file, you should have pretty complete coverage. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.