Re: [Q] documenting font construction

Ilya> In particular, on my sco 5.0.2 `8x14pc437', `8x14pc850', Ilya> `8x14pc932' have no XLFD aliases. Well, fix the broken system then. If you can't, you have my condolences. But there is no reasonable way to handle those aliases automatically. If you get to the point where you are dependent on XEmacs figuring out something sane to do with those font names, you're in bad shape indeed. It's reasonable to ask for a way to specify that such and such a font name corresponds to such and such a charset. I believe you can use CCL to accomplish that, if not we can see about hacking something up later. But even then, there's no cross-platform guarantees about what the X server will deliver! Ilya> What happens if non-XLFD font names match charset registry Ilya> currently is unclear, And will remain so, because it's hard enough to predict what happens with XLFDs. You've read the code, so presumably you've seen Jamie's rants on the subject. Ilya> re-implementation must provide a trapdoor to use non-XLFD Ilya> font names after all XLFD ones are exhausted. I see no reason why this should be supported, except in the form of the wildcard "*" for last resort. Does your sysadmin really hate you so much that they won't add a couple of lines to fonts.dir? -- 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.