Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!icdoc!sot-ecs!sra From: sra@ecs.soton.ac.uk (Stephen Adams) Newsgroups: comp.text.tex Subject: Re: Substitute font bug under xdvi Message-ID: Date: 6 Feb 91 15:26:24 GMT References: <4687@goanna.cs.rmit.oz.au> <1991Feb1.233536.12514@agate.berkeley.edu> Sender: news@ecs.soton.ac.uk Organization: Southampton University Computer Science Lines: 29 In-reply-to: vojta@powdermilk.berkeley.edu's message of 1 Feb 91 23:35:36 GMT In article <1991Feb1.233536.12514@agate.berkeley.edu> vojta@powdermilk.berkeley.edu (Paul Vojta) writes: > In article <4687@goanna.cs.rmit.oz.au> isaac@goanna.cs.rmit.oz.au (Isaac Balbin) writes: > >... However, xdvi bombed out. The messages were: > >... > >xdvi: Character 174 not defined in font cmr10 > > > >Has anyone seen this and fixed it? > > Yes, the fix should be appearing in Patchlevel 11. Real Soon Now. Wonderful! The other behaviour of xdvi that I find annoying is that it sometimes locks up, eating vast amounts of cpu time. It will not respond to Q and has to be killed manually. This seems to happen immediately after I have accidentally asked it redisplay something while latex is running and creating the .dvi file. I assume that it tries to read from a half written .dvi file and falls over, but I am only guessing. This happend on sun3s and sun4s, sunos 4.0 & 4.1, X11R4. Has anyone observed this behaviour? Can it be fixed too? -- Stephen Adams S.R.Adams@ecs.soton.ac.uk Computer Science S.R.Adams@sot-ecs.uucp Southampton University Southampton SO9 5NH, UK