Bug 689727

Summary:	embedded font is assigned MacExpertEncoding, doesn't display in acroread 8
Product:	Ghostscript	Reporter:	keinbiervorvier <keinbiervorvier>
Component:	PDF Writer	Assignee:	Ken Sharp <ken.sharp>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	smr
Priority:	P4
Version:	master
Hardware:	PC
OS:	Linux
Customer:		Word Size:	---
Attachments:	pdf file for which acroread 8 does not display small caps glyphs pdf file which displays correctly in acroread 8 postscript file corresponding to t-u.pdf postscript file corresponding to t-u1.pdf

Description keinbiervorvier 2008-02-27 12:59:49 UTC

I am converting a tex generated postscript file using txfonts to PDF via ps2pdf.
Some glyphs from the embedded subsetted font rtxsc (tx small caps) do not show in 
acroread 8 on linux. They do appear correctly when viewed with gs, xpdf, evince,
etc., though.

The embedded font is assigned MacExpertEncoding. This seems to confuse acroread.

Processing almost the same file with a smaller subset of the same font, the font
is assigned a separate Encoding object with /BaseEncoding /WinAnsiEncoding and
displays fine in acroread 8.  

I attach 2 short PDF files and corresponding ps files, which demonstrate the effect.

Could be an acroread bug, but it is odd that the assigned encoding changes
depending on subset of the font.

Cheers
T.

Comment 1 keinbiervorvier 2008-02-27 13:01:43 UTC

Created attachment 3823 [details]
pdf file for which acroread 8 does not display small caps glyphs

Comment 2 keinbiervorvier 2008-02-27 13:02:33 UTC

Created attachment 3824 [details]
pdf file which displays correctly in acroread 8

Comment 3 keinbiervorvier 2008-02-27 13:03:52 UTC

Created attachment 3825 [details]
postscript file corresponding to t-u.pdf

Comment 4 keinbiervorvier 2008-02-27 13:05:46 UTC

Created attachment 3826 [details]
postscript file corresponding to t-u1.pdf

Comment 5 Szymon Rusinkiewicz 2008-10-10 12:10:46 UTC

A patch for this problem was posted under bug 689370.

Comment 6 Ken Sharp 2009-02-13 06:17:47 UTC


*** This bug has been marked as a duplicate of 689370 ***