Bugs item #721, was opened at 2007-01-23 20:17 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=721&group_id=106 Category: Fonts Group: v1.40.1 Status: Open Resolution: Accepted Priority: 7 Submitted By: Hartmut Henkel (hhenkel) Assigned to: Hartmut Henkel (hhenkel) Summary: Missing /Font object of PK file not found Initial Comment: There are several cases, the buggy one is no. 3. See test files test1...4.tex in the attached file. 1. No TFM file found in the 1st place. ---> No TeX font will be started. Ok. See test1.tex. 2. TFM file found, map entry existing, but no PFB font file in map line ---> "pdfTeX warning: pdftex: font `CMR' is not a standard font; I suppose it is available to your PDF viewer then". Ok. See test2.tex. 3. TFM file found, no map entry, and no PK font available. ---> "pdfTeX warning: pdftex (file mf-nonexist): Font mf-nonexist at 600 not found". Not ok. See test3.tex. Here a /Font object is referenced, which is not existing, rendering the resulting PDF file buggy. There should be either pdftex_fail() or or at least a /Font object with a dummy /FontDescriptor object should be created (the latter filled with defaults from the TFM file), and the same warning should be given as in case 4 below, since these cases are similar: fontfile expected, but not available. 4. TFM file found, map entry with PFB font file existing, but no PFB font file found. ---> "pdfTeX warning: pdftex (file t1-nonexist.pfb): cannot open Type 1 font file for reading". /FontDescriptor without /FontFile, correct. Ok. See test4.tex. Regards, Hartmut ----------------------------------------------------------------------

Comment By: The Thanh Han (hanthethanh) Date: 2007-03-01 08:58

Message: Logged In: YES user_id=710 Here is a patch to turn some warnings that can lead to invalid pdf output to fatal errors. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=721&group_id=106