Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!mcsun!ukc!icdoc!sot-ecs!spqr From: spqr@ecs.soton.ac.uk (Sebastian Rahtz) Newsgroups: comp.text.tex Subject: Re: Substitute font bug under xdvi Message-ID: Date: 1 Feb 91 22:48:36 GMT References: <4687@goanna.cs.rmit.oz.au> Sender: news@ecs.soton.ac.uk Followup-To: comp.text.tex Organization: Southampton University Computer Science Lines: 28 In-reply-to: isaac@goanna.cs.rmit.oz.au's message of 1 Feb 91 00:59:37 GMT In article <4687@goanna.cs.rmit.oz.au> isaac@goanna.cs.rmit.oz.au (Isaac Balbin) writes: TeX 3.0) When I went to xdvi the thing, of course, it had to use cmr as a substitute. However, xdvi bombed out. The messages were: Can't find font pbkdi; using cmr10 instead at 300 dpi Can't find font pbkdi; using cmr10 instead at 330 dpi Can't find font pbkd; using cmr10 instead at 510 dpi Can't find font pbkl; using cmr10 instead at 330 dpi xdvi: Character 174 not defined in font cmr10 Has anyone seen this and fixed it? ^^^^^^^^^ Many, *many*, times.... If this is a request for someone to post some changes to xdvi, then I second it with deep enthusiasm. I am sure it is trivial to make xdvi *not* crash when a character is missing, but to insert a space instead. I keep meaning to look at it, but never do. Is anyone implementing support for virtual fonts into xdvi? sebastian -- Sebastian Rahtz S.Rahtz@uk.ac.soton.ecs (JANET) Computer Science S.Rahtz@ecs.soton.ac.uk (Bitnet) Southampton S09 5NH, UK S.Rahtz@sot-ecs.uucp (uucp)