Bug 687815 - InDesign PDFs with CID Fonts missinterpreted
Summary: InDesign PDFs with CID Fonts missinterpreted
Status: RESOLVED DUPLICATE of bug 687832
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: Font API (show other bugs)
Version: 8.50
Hardware: All MacOS X
: P2 normal
Assignee: Igor Melichev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-24 06:07 UTC by ademmler
Modified: 2007-12-13 12:55 UTC (History)
0 users

See Also:
Customer:
Word Size: ---

Attachments
InDesign file with CID fonts (28.13 KB, application/pdf)
2004-11-29 10:41 UTC, Raph Levien 		Details
PDF with missinterpreted CID Fonts (444.55 KB, application/octet-stream)
2004-12-05 04:54 UTC, ademmler 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ademmler 2004-11-24 06:07:37 UTC 
InDesign PDFs (direkt export) with CID fonts appear to 
have a wrong character spacing in the output.

How to send you a sample file?

Regards Alex
Comment 1 Alex Cherepanov 2004-11-25 03:04:11 UTC 
Please re-visit the bug report and attach the sample file.
Comment 2 Jack Moffitt 2004-11-29 07:41:04 UTC 
You can attach the sample file by visiting the bug report and clicking "Create a
New Attachment", or you can mail it to me at jack@artifex.com.
Comment 3 Raph Levien 2004-11-29 10:41:39 UTC 
Created attachment 1063 [details]
InDesign file with CID fonts

The attached PDF file was exported from InDesign CS using default settings, and
contains CID Type 0, Type 0C, and Type 2 fonts. Ghostscript rendering looks
fine, so if there is a problem with CID fonts, it seems likely to be specific
to a particular font.
Comment 4 ademmler 2004-12-05 04:54:38 UTC 
Created attachment 1073 [details]
PDF with missinterpreted CID Fonts

testCIDfonts.pdf = original PDF
testCIDfonts_ok.jpg = sample as it should look like
testCIDfonts_GSout.jpg = sample how I get it from GS
Comment 5 Jack Moffitt 2004-12-09 21:05:35 UTC 
8.14 and 8.15 produce output identical to your *_ok.jpg file, but HEAD output is
quite ugly.  Assigning to Igor.
Comment 6 Igor Melichev 2004-12-23 16:00:00 UTC 

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