Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!agate!shelby!neon!neon!weening From: weening@Gang-of-Four.Stanford.EDU (Joe Weening) Newsgroups: comp.text Subject: Re: Possible TeX bug. Help! Message-ID: Date: 20 Oct 89 14:55:24 GMT References: <113600012@uxa.cso.uiuc.edu> <20287@mimsy.umd.edu> Sender: USENET News System Organization: Computer Science Department, Stanford University Lines: 27 In-Reply-To: chris@mimsy.umd.edu's message of 20 Oct 89 12:27:57 GMT In article <20287@mimsy.umd.edu> chris@mimsy.umd.edu (Chris Torek) writes: It is easy enough to change the `amcsc10 \@ptscale8' and `amcsc10 \@ptscale9' lines to `cmcsc10 \@ptscale8' and `cmcsc10 \@ptscale9', although you will then need GF or PK files corresponding to these downscaled cmcsc10 fonts. This is still a kludge, since there really should be a cmcsc8 and cmcsc9---but for that you have to do much more work. I started on this over a year ago, actually, and got mostly finished but had to stop. The characters look OK but some work needs to be done on the spacing between various pairs of characters. Font design is harder than I thought, even when the hard parts had already been done! If anyone wants to help, let me know, otherwise I'll try to finish it soon. (No one has yet explained the *purpose* of the kludge in TeXhax, although the question came up some time ago.) As I heard it, the conversion from AM to CM fonts was done on a system that didn't have cmcsc10 scaled at .8 and .9 (which are quite non- standard sizes), and that system also didn't have an easy way to create new fonts at the time. So there's really just an excuse, not a reason for the kludge, and for now it is best to generate cmcsc10 at the appropriate sizes with Metafont. -- Joe Weening Computer Science Dept. weening@Gang-of-Four.Stanford.EDU Stanford University