Bug 687929 - missing character boxes
Summary: missing character boxes
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: PDF Interpreter (show other bugs)
Version: master
Hardware: All All
: P2 normal
Assignee: Ray Johnston
QA Contact: Bug traffic
Depends on:
Reported: 2005-02-06 16:11 UTC by Jack Moffitt
Modified: 2008-12-19 08:31 UTC (History)
0 users

See Also:
Customer: 850
Word Size: ---

file with munged fontname (265.37 KB, application/pdf)
2005-02-09 10:10 UTC, Raph Levien

Note You need to log in before you can comment on or make changes to this bug.
Description Jack Moffitt 2005-02-06 16:11:21 UTC
Rendering the attached customer file with CVS HEAD gives many of the missing
glyph boxes instead of spaces.  Preview and Adobe Reader have no problems with
this file.  This is not a high priority for the customer, since this came out in
internal testing.
Comment 1 Jack Moffitt 2005-02-06 16:12:14 UTC
Created attachment 1193 [details]
Comment 2 Igor Melichev 2005-02-09 09:56:36 UTC
See also the bug 687510.
Comment 3 Ray Johnston 2005-02-09 10:09:09 UTC
The file contains tab characters (\t) that apparently is not in the
embedded font (Helvetica-Bold subset, Truetype format). The font
has a .notdef character and this character is the rectangular box.

We suspect that Adobe is using their own .notdef character that is
a null character (a character that produces no space). It may be that
Adobe is using Helvetica-Bold from their own font (on the system)
rather than using the embedded font.

We confirm that the embedded font contains the .notdef that is a box.

Apparently Adobe Reader chooses to ignore the .notdef in the font
and instead displays nothing.
Comment 4 Raph Levien 2005-02-09 10:10:17 UTC
Created attachment 1202 [details]
file with munged fontname

This file was prepared by (a) expanding compressed streams using pdfclean -x,
and (b) doing a global search-and-replace of "Helvetica" to "Helvutica", so as
to defeat any font substitution in the viewer. It renders in Acrobat 5 as a
space, which seems to be inconsistent with section 5.5.5 of the PDF rendering,
which specifies that .notdef is drawn.