cca13@seq1.keele.ac.uk (G.D. Pratt) (09/11/90)
I've just spent two days building the AMSFonts Version 2.0 at 406DPI for use on our laser printer. My previous mailing about "problem with format of msym5.mf file" seemed to be that the "MSYM" files are not supported by NEW METAFONT and I should use the "MSAM" and "MSBM" fonts in AMSFonts Version 2.0 from labrea.stanford.edu. Thanks for the replies I got about this. I now seemed to have a problem building the "Euler" family. Some, eg euex10, build OK:- ./virmf &cmplain \mode=localfont; input euex10 This is METAFONT, C Version 1.5 (no base preloaded) (mfs/euex10.mf (mfs/ebigop.mf [82] [90]........etc whereas others, eg eusm10, produce an error message, continue if I press <RETURN> and then appear to run OK but do not produce correct files:- ./virmf &cmplain \mode=localfont; input eusm10 This is METAFONT, C Version 1.5 (no base preloaded) (mfs/eusm10.mf (mfs/eusmch.mf (mfs/eubase.mf ! Inconsistent equation (off by 0.0027). <to be read again> ; l.17 h#=ptsize/programem; ? ) [48] [64] [65]........etc If I use "testfont.tex" or try to print out the AMSFonts Version 2.0 document I get no characters, ie just blank spaces. Anyone know what I'm doing wrong here? thanks in advance, gerry -- gerry pratt - workstation support - university of keele email: cca13@uk.ac.keele.seq1 * tel: 0782 621111 x 3290
dhosek@sif.claremont.edu (Hosek, Donald A.) (09/12/90)
In article <613@keele.keele.ac.uk>, cca13@seq1.keele.ac.uk (G.D. Pratt) writes... >whereas others, eg eusm10, produce an error message, continue if >I press <RETURN> and then appear to run OK but do not produce >correct files:- > ./virmf &cmplain \mode=localfont; input eusm10 ^^^^^^^^^ Don't use cmbase to build the fonts. I believe the readme files even say this. -dh --- Don Hosek TeX, LaTeX, and Metafont support, consulting dhosek@ymir.claremont.edu installation and production work. dhosek@ymir.bitnet Free Estimates. uunet!jarthur!ymir Phone: 714-625-0147 finger dhosek@ymir.claremont.edu for more info