Bug 29380 - cannot see text that uses fonts that were embedded after pdf generation
Summary: cannot see text that uses fonts that were embedded after pdf generation
Status: RESOLVED NOTOURBUG
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-03 05:21 UTC by Carlos Garcia Campos
Modified: 2010-08-10 12:55 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Carlos Garcia Campos 2010-08-03 05:21:47 UTC
Bug forwarded from Evince: https://bugzilla.gnome.org/show_bug.cgi?id=607780

"Hi,
  I cannot see some text in pdf files were fonts were embedded after the pdf
creation.


How to replicate:

echo "50 600 moveto /Courier findfont 30 scalefont setfont (the quick brown
fox) show" | ps2pdf - test.pdf


embed fonts using Enfocus PitStop Server 9


opne with xpdf ----> ok
open with evince --> fail
  Error: could not create type1 face
  some font thing failed

open with okular --> fail
  Error: Couldn't create a font for 'Courier'



I am attaching an archive containing:

test.pdf: fonts NOT embedded

test-p.pdf: fonts embedded by PitStop Server (evince cannot see text)

test-g.pdf: fonts embedded by ghostscript (evince sees the text)


Some info:

$ evince --version
GNOME Document Viewer 2.28.1

$ gs --version
8.70"

I can confirm FT_New_Memory_Face returns an error code (3, Invalid_File_Format). It works with xpdf that saves the font into a temp file, so I don't think the font is invalid. Acroread doesn't fail either. Maybe we are doing something wrong in GfxFont::readEmbFontFile() or it's a bug in freetype. 

Test cases can be found attached to the original bug report.
Comment 1 Albert Astals Cid 2010-08-10 12:55:10 UTC
Works with freetype 2.4.2


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.