the fonts like phvr8a are missing in tested TeXlive

Petr Olsak
Mon, 13 Mar 2000 10:35:23 +0100 (MET)

Hello TeXlive editors,

I have sent the bugreport to about fontname problem or
p*8a missing fonts problem. This problem is still not solved in tested
texmf tree at

I am not able to solve this because doing some changes in texmf tree
correctly (in order to keeping a consistence with some database files) is
too difficult to me. 

I suppose: 

# vi texmf/fontname/

remove (or comment out) the line "include"

More better:

Return the support of p*8a fonts to the staff. These names
were supported in some older versions of web2c and dvips. I dont know why
this support is missing in current verions.

Petr Olsak

---------- Forwarded message ----------
Date: Wed, 9 Feb 2000 14:11:09 +0100 (MET)
From: Petr Olsak <>
Subject: why the is present in font aliases?


I was found some special problem with font aliasing in our actual (and
all pre) version of TeXlive.

There is a font alias algorithm described in kpathsea documentation.
This aliasing is configured via texmf/fontname/
The historical reason is clear: the lcircle10<->circle10 alias has his
significance. But why the file is included?

I prepared some example in sun2:/texlive/whyfontname.
There is a virtual font AHelvetica.vf used in test.dvi.
This virtual font points to font Helvetica (sure, this name).
The includes one line: "Helvetica Helvetica".
Thus the dvips works OK:
1. AHelvetica points to Helvetica
2. Helvetica is in, so the Helvetica PSfont is
   used but not downloaded.

On the other hand, the xdvi works very bad:
1. AHelvetica points to Helvetica
2. Helvetica*.pk is not found, the aliases are used.
3. Aliases in say: this is the phvr8a font!
4. The phvr8a.*pk is not found, so the mktexpk is run.
5. mktexpk does not found the phvr8a in, so Metafont is run
6. Metafont crashes.

I mean that the problem has to be solved.

Petr Olsak