Hide Forgot
I've just generated a document using latex which has \usepackage{pifont} at the top, and then uses the \ding{nnn} command to generate characters from the ZapfDingbats font. The same document used to work fine under RedHat 7.2, but has now stopped working - xdvi displaying the generated DVI file displays Courier (I think) instead of the expected ZapfDingbats characters. pdflatex on the same file generates a PDF with the correct fonts, though.
Please attach an example file. Thanks.
OK - I'll attach a short sample LaTeX source and the generated DVI file. According to the psnfss docs, it should display as 4 different pairs of scissors. Having run latex on it on my machine, xdvi displays it as the following four characters: ! " # $ Thanks.
Created attachment 61844 [details] Short LaTeX file using ZapfDingbats characters
Created attachment 61845 [details] DVI generated from dingsample.ltx
The DVI file is fine---dvips converts it to a PS file containing scissors. Some xdvi problem.
Not on this machine, I'm afraid. dvips converts it to a PS file containing exactly the same four Courier characters (! " # $).
_That_ I can't reproduce. Even your attached DVI converts to working PS for me.
OK, problem solved - nothing to do with tetex specifically. ZapfDingbats is missing from the urw-fonts package (there's an entry for d050000l.pfb in /usr/share/fonts/default/Type1/fonts.dir, but the corresponding d050000l.* files don't exist). That's why ghostscript was substituting Courier instead. Copying those files from the urw-fonts distributed with RH 7.2 solves that problem. For some reason I don't quite understand it also seems to have solved the xdvi problem (after clearing out /var/lib/texmf and re-running xdvi). I'll file a bug against urw-fonts. Thanks.
Okay.