[3960] in SIPB bug reports
Re: dvips
daemon@ATHENA.MIT.EDU (bert@mit.edu)
Wed Jul 21 18:42:48 1993
From: bert@mit.edu
Date: Wed, 21 Jul 93 18:42:24 EDT
To: Calvin Clark <ckclark@mit.edu>
Cc: <tlyu@mit.edu>, Richard J. Barbalace <rjbarbal@athena.mit.edu>,
bug-sipb@athena.mit.edu, ckclark@athena.mit.edu
In-Reply-To: [3959]
OK, I think that some things here demand an explanation.
Richard said:
> Couldn't find font amcsc10 at 540dpi.
> -
> dvips: Font amcsc10.518pk at 540 not found; scaling 518 instead.
> dvips: Such scaling will generate extremely poor output.
> dvips: Checksum mismatch in font lasy10.657pk
> dvips: Checksum mismatch in font line10.600pk
> Couldn't find font circle10 at 600dpi.
> -
This means:
1) amcsc10 is not built for 600dpi.
we don't have the source.
CONCLUSION: it never will be.
2) circle10 is not built for 600dpi.
We have the sources, and I'll build it sometime soon (unless the
release happens sooner... =)
3) lasy10 and line10 -- the .tfm TeX used and the .tfm dvips used are
not one and the same. This is probably because TeX used one in
/mit/sipb or in /usr/athena/lib, and dvips used the one in outland.
No big deal.
Then Tom said:
> Did someone blow away symlinks between
> /mit/sipb/lib/tex/fonts/pk and /mit/outland/lib/tex/fonts/pk? That
> seems to be the problem....
Tom, there never existed such a link. It's all done through config
file hacking. /mit/sipb/lib/tex/fonts/pk (300dpi) will probably not
be blown away until the release.
Then Calvin said:
> The problem is that those fonts in those resolutions aren't installed.
> I'll install them when I get a chance.
Calvin, I don't think we have amcsc10 sources:
% archie amcsc10.mf
%
You can build circle10 (and get and build >C<mcsc10) though...
--bert
