Hartmut Henkel hartmut_henkel at gmx.de
Sun Feb 25 11:04:50 CET 2007

On Sun, 25 Feb 2007, Reinhard Kotucha wrote:

> >>>>> "Karl" == Karl Berry <karl at freefriends.org> writes:
>
>   >> pdfTeX warning: pdftex (file ugqb8r.1200pk): Pixel font file for
>   >> font ugqb8r at 1200 dpi not found
>
>   >     this message is much more helpful than the original one.
>
>   > But it will lead users to try to find pk files, which will cause
>   > just as much if not more confusion.  The real issue here is map
>   > files, but I don't know how pdftex can determine that.
>
> Suppose there is an entry for this font in pdftex.map, why does pdftex
> try to access a bitmap font?

right, this happens only if there is _no_ map entry for the TeX font
(else it would just complain that the .pfb is not readable). E. g.:

\pdfmapline{} \nopagenumbers
\font\ugqb ugqb8r at 10pt \ugqb foo \bye

here no pdftex.map is read. To force the error you need to remove
ugqb8a.pfb from the path, e. g. by renaming the file. Then pdftex tries
to generate a PK file for ugqb8r.tfm by running gsftopk on ugqb8a.pfb
(some name magic here), gsftopk fails, then the warning is issued.

So it happens if one thinks yes it should be a .pfb file, but the
relevant entry is not in pdftex.map or the wrong pdftex.map is used
(error 1) and not even the .pfb file is in the search path (error 2).

BTW trying it with Helvetica gave confusion; i had removed all
phvr8a.pfb from the path, kpsewhich found nothing, still the Helvetica
PK file was generated --- because gs then obviously uses its own
PostScript font repository; gsftopk adds one level of fuzziness :-)

Regards, Hartmut