isaac@goanna.cs.rmit.oz.au (Isaac Balbin) (02/01/91)
I was attempting to preview a document that was latexed using bookman font as a substitute for cmr. (I was using Mittlebach and Schopf's scheme under 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? -- Say NO to PLO
spqr@ecs.soton.ac.uk (Sebastian Rahtz) (02/02/91)
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)vojta@powdermilk.berkeley.edu (Paul Vojta) (02/02/91)
In article <4687@goanna.cs.rmit.oz.au> isaac@goanna.cs.rmit.oz.au (Isaac Balbin) writes: >I was attempting to preview a document that was latexed using bookman >font as a substitute for cmr. (I was using Mittlebach and Schopf's scheme under >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? Yes, the fix should be appearing in Patchlevel 11. Real Soon Now. --Paul Vojta, vojta@math.berkeley.edu
sra@ecs.soton.ac.uk (Stephen Adams) (02/06/91)
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
vojta@powdermilk.berkeley.edu (Paul Vojta) (02/08/91)
In article <SRA.91Feb6152625@pessoa.ecs.soton.ac.uk> sra@ecs.soton.ac.uk (Stephen Adams) writes: >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. It has been fixed (I hope) in patchlevel 11. The patch has been sent already to comp.sources.x, but it may be a week or two before it appears, due to a large backlog. --Paul Vojta, vojta@math.berkeley.edu