Re: [Q] documenting font construction

Ilya> Moving it to xemacs-beta. Concerning what is matched Ilya> against charset registry while instancing font in X. Ilya> A *generic* matching function (knowing nothing about X) is Ilya> really applied to entire font name. Oh, you're talking about the target string, not the matched substring. Bogus, yes. But I don't see why there is confusion; the "registry field" of an XLFD is well-defined; the possibility of bogus matches would be confusing if somebody used a registry name in another field but that seems unlikely. (This could be fixed either by anchoring the regexp at the end (concat the property contents with "$") or even generating a regexp that matches the full XLFD.) I'm currently looking at moving what is currently in font.el down into C (where redisplay can get at it efficiently), probably based on the model in fontconfig (as used in Xft). Whatever it is will have to be consistent with the font information and specifications for non-X11 platforms, of course. So I really would rather not put any implementation-dependent language into the documentation. Can you be more specific about where the confusion comes in? -- 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.